Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - PHITEK

Pages: [1]
I found my issue, I have change the Display On method to sending a single byte for testing the I2C interface with a scope and never changed it back to 0xFE, 0x41. So once I turned the display off there was not way to turn it on again.

Thanks for you help on this matter


Yes the baud rate, parity, data bits, and handshaking all match.

I have a test program that does quite a bit of the functionality, and is based on this sample.

I have adjusted the timing (increased the delays), especially have the Clear command, I had to fix a number of issues, mainly how backspace is handled. Got this code running on the SPI interface fine, switching to RS-232 was mainly adding more delay to the clear command and the crash with Turn Display Off, commenting out this command it runs fine overnight.

I will see if I can get a smaller program to exhibit the display crash, and post back here in a few days.

Thanks for your attention to this matter.

I am having a problem with the Turn off display command when I use RS-232 communication mode. I have some test code in C# running on .NETMF platforms from

Initially I had hoped to use SPI communications mode with worked fine on one platform. Two of there other platforms I could not slow the SPI Clock down low enough, so I decided to use the RS-232 communications mode.  I am using the default 9600 baud rate.

My test program ran for many hours using the SPI communications mode.

What happens on the first use of the Display OFF command, is the characters on the display disappear but then nothing else seems to turn the display back on. I have to remove the power and re-power up the display.

Is this a known issue?

Pages: [1]