Go Down

Topic: 4D systems 3.2" TFT display SGC ( serial controlled ) (Read 3 times) previous topic - next topic

Razorblade

If his loop() was empty it still shouldn't show the device info because the 4D chip will blank the display as soon as it gets an autobaud command.

?¿ Have you looked at his setup() code? I don't think so.
Or try to explain better why it wouldn't show the device info, please.
Arduino Uno (R2fix) / Duemilanove (328p)
Ethernet Shield SD (v5)

extent


If his loop() was empty it still shouldn't show the device info because the 4D chip will blank the display as soon as it gets an autobaud command.

?¿ Have you looked at his setup() code? I don't think so.
Or try to explain better why it wouldn't show the device info, please.


His setup() issues the autobaud command, the 4d displays will go into their show info screensaver mode only if they receive no autobaud for 5 or so seconds after startup.  If you mean the device capabilities screen His CMD_VERSION call is likely being eaten up because he's sending smashing it into the display when it's not ready, so waiting longer after you've issued the (now lost) command isn't going to make any difference either.

On that point as well just calling CMD_VERSION will put at least 5 bytes of data into your serial input buffer (on the GOLDELOX chip, probably more on the one in the 3.2") which OFC he's not clearing out before going into his loop.  Every time through the loop he's only taking 1 byte off the input buffer and making a new call to touch status.

Razorblade

#7
Sep 18, 2011, 01:38 pm Last Edit: Sep 18, 2011, 03:31 pm by Razorblade Reason: 1
Ok extent, so the problem is that you name things wrong. Your "device info screen" is the "Splash Screen on Power Up", and the "Version-Device Info Request - 56hex" is your "device capabilities screen". :smiley-roll:

"His CMD_VERSION call is likely being eaten up because he's sending smashing it into the display when it's not ready,"
That's not true. The display is ready, because it was reset 3 seconds ago. He's just sending Autobaud and Touch enable before Device Info Request, and display responses to those commands are fast enough, so there's no need to wait for that ACK bytes. Anyway, I was who recommended him to wait for ACK bytes few lines above.

So.. if he has connected the LCD correctly, no component damaged, and puts an empty loop(), he will see the Device Info screen. In fact, I do see it (yes, copy-paste his code).
Arduino Uno (R2fix) / Duemilanove (328p)
Ethernet Shield SD (v5)

Go Up