Looking through the version 1 manual for the vk204-24-usb, it seems a lot of it is lcd related. There are 3 ways to set the brightness. The one I know works (I've tested, is 254 89 [brightness] described in 7.1.2 on page 26), though the values of brightness are backwards - 00 is the brightest, while 03 is 25% (dimmest). But it cannot be 'remembered'.
On the misc table at the end of the manual, however, 8.6 on pg 35, it has 'Set Brightness 254 153 [brightness]', which takes values from 0-255, and then the 'set brightness and save 254 152 [brighness]' below that command. I'm not sure if those work, haven't tested them, but I'm 'suspecting' they don't.
Is there a way to set the default brighness (to 25%) and have that be the startup brighness on power-on?
Its especially important with the VFD to have this given its tendancy to 'burn in' the elements of the vfd over time.
VK-204-24-USB ... Any way to SAVE default brightness setting
Hello...
I can understand your frustration as the manual has it listed as an appropriate function, however upon further tests I can't seem to get it working either. The command that should do this is 254 152 [brightness]. I will look into this and let you know ASAP...Sorry for any inconvenience.
I can understand your frustration as the manual has it listed as an appropriate function, however upon further tests I can't seem to get it working either. The command that should do this is 254 152 [brightness]. I will look into this and let you know ASAP...Sorry for any inconvenience.
Miles Y.
Head of Technical Support
Product Manager
Matrix Orbital
Head of Technical Support
Product Manager
Matrix Orbital
-
GermanMan
- LCD Geek
- Posts: 23
- Joined: Thu Sep 04, 2003 6:29 pm
- Location: The Real LA - On the South Coast
My guess is that that command affects the brightness of the LCD - probably backlighting brightness - since the VFD brighness is actually a different command (254 89 [brighness] ) and not (254 153 [brightness]).
I suspect that the 254 89 command produces a change in signal on a different logic path/wire than the 254 153 command and end up tying into a different part of the VFD.
I'm hoping its something that can be fixed with a firmware upgrade.
I suspect that the 254 89 command produces a change in signal on a different logic path/wire than the 254 153 command and end up tying into a different part of the VFD.
I'm hoping its something that can be fixed with a firmware upgrade.