Your mileage may vary of course, but the few VFD's I've seen in direct sunlight were horrid, couldn't see a thing.

Long day? Post says 7:00pm, slave-drivers up there in Canada I tell ya!

psylence wrote: I can do all commands I can verify on the display visually (show a bitmap, clear the screen, change contrast/backlight etc...), but I can't write a string of text. Kinda weird.

Yeah, I guess I could, that's no fun though! :)

I'll give that a shot sometime soon. I assume this would cause no text to be displayed if the font has been corrupted/otherwise borked? I did make sure to test all of that, all 3 fonts I have in it before doing the I2C conversion, but I guess it could ...

Hey, I've gotten the I2C working seemingly fine on my GLK12232-25-SM, but I can't write simple text to it.

I can do all commands I can verify on the display visually (show a bitmap, clear the screen, change contrast/backlight etc...), but I can't write a string of text. Kinda weird.

I'm assuming ...

Not a documentation error, but the PDF itself seems to be faulty.

The GLK12232-25 SM PDF, in the section where it describes settings for I2C and RS-232 is missing critical information (for my use at least!) :).

Page 10 of the PDF, the images at the bottom, the RS-232 is missing most of the caption ...

Nope, the manual override seems to do nothing...

I short C5 to R1, power it up, then power it down, remove the short and start it up and try to talk to it @ 19.2kbps but it doesn't respond to anything.

I do plan on putting delays into my code but that's only after I have an LCD to talk to!

Got a problem. I have a GLK12232 connected to a microcontroller for control, this has been working fine for months but recently I apparently flooded it with information causing it to freak out, it would randomly display images and garbled lines and not respond to commands.

A few hours ago I took it ...