Go Down

Topic: LCD Display communication (Read 617 times) previous topic - next topic


I am working with 16x2 LCD with SparkFun SerLCD backpack.
I found that I have to disconnect backpack rx input from Arduino Tx
while uploading new sketch into Ard, as well while just applying power to Arduino board (that is, just connecting it to USB or battery). Otherwise there is a lot of garbage transmitted by board to backpack at boot time, which takes LCD into unknown state.
So, my question is:
what is the best way programmatically connect/disconnect backpack serial input from Ard?
I think it's not 'doable' without adding, say, transistor or something like that.
Please share your opinion!


Instead of using the hardware serial port on pins 0 and 1, use the software serial library and connect the LCD to some different pins.



Thank you, this is basically correct, but I had in mind rather some hardware solution... like, connect/disconnect backpack Rx using some transistor or mosfet... just trying to save myself some time of googling on long forgotten electronics details...


On my breadboard with a serial lcd display ive just got a toggle switch on flying leads on the 5v feed to the serial interface.
When I upload a sketch to the Arduino I just flip it off and when it finishes I flip it back on.
You may want to then reset the board to refresh anything you display on the lcd if your sketch doesnt update the lcd very much like my sketch.

You could replace the switch with a relay. if you realy need to.
There are plenty of examples on using relays with the arduino if you search on google.



Yes, Gordon, I was thinking the same way, some small relay with normally opened contacts.
The thing is, if LCD is in unknown state, resetting Arduino will not help, you need to reset backpack, and the only way to do is by switching of it's power.
What's interesting - it's like _there is_ some way of resetting backpack by some command, because when in "garbaged state" a couple of times I managed to reset it (initiate splash-screen) sending out some x7E combinations, but it never worked next time :)
So I think there are some undocumented backpack commands that may invoke reboot.

Go Up