#25 $Chr(131) and up are one to low

[mod]

The real value transmitted to the lcd by $Chr(131),
$Chr(132) and so on seems to be one to low here. So for
$Chr(131) 130 (0x82) is transmitted to the lcd. Tested
without a lcd by capturing the output of the serial
port with another serial port. Driver was crystal fontz
and OS is XPpro.

[Chris Lansley]

Logged In: YES
user_id=1114156

Yes, that's right for the CF driver (for some displays; but
not 633 and 631). I have no idea why it was implemented
that way.

131 -> 130
132 -> 131
133 -> 132
134 -> 133
135 -> 134
136 -> 135

137 and above are left alone.

If you want a device indepentant way of using custom
characters then use these values:

for cc 1 use 176
for cc 2 use 158
for cc 3 use 131
for cc 4 use 132
for cc 5 use 133
for cc 6 use 134
for cc 7 use 135
for cc 8 use 136

These will then be mapped on to the correct value for each
display driver.

[Chris Lansley]

Logged In: YES
user_id=1114156

I've updated the command reference page for $CustomChar.