| ??? 04/28/08 19:24 Modified: 04/28/08 19:26 Read: times |
#154123 - My Bad!!! Responding to: ???'s previous message |
Oops:
I now understand how the code calls the INIT_LCD routine and I spotted the CLEAR_LCD routine. Sorry I missed those. I still wonder at the wisdom of calling the INIT_LCD toutine at each and every time you go to write a string to it. That is going to be slow and inefficient on a real application and will cause annoying flashing and blanking of the display all the time. This should be called once at startup for most products. Make sure that you achieve the full LCD initialize before trying to call CLEAR_LCD too. Michael Karas |
| Topic | Author | Date |
| Damaged LCD? | 01/01/70 00:00 | |
| Some code comments first. | 01/01/70 00:00 | |
| Thanks... | 01/01/70 00:00 | |
| Well if you need it later... | 01/01/70 00:00 | |
| Hmmpf. | 01/01/70 00:00 | |
| Multiple Problems | 01/01/70 00:00 | |
| My Bad!!! | 01/01/70 00:00 | |
| :) some improvement | 01/01/70 00:00 | |
| try to initialise at startup | 01/01/70 00:00 | |
| Wahey...... O not quite | 01/01/70 00:00 | |
| Hex value | 01/01/70 00:00 | |
| Check your soldering. | 01/01/70 00:00 | |
| Oops | 01/01/70 00:00 | |
| Wahey..... o not AGain | 01/01/70 00:00 | |
| Leading 0 | 01/01/70 00:00 | |
| Leading zero | 01/01/70 00:00 | |
| Some help | 01/01/70 00:00 | |
| Cheers guys, all working now | 01/01/70 00:00 | |
Why You Were Content Dependant | 01/01/70 00:00 | |
| The filled in blocks indicate.. | 01/01/70 00:00 | |
| No hardware but software problem | 01/01/70 00:00 |