| ??? 12/15/06 18:09 Read: times |
#129565 - usually it's the program, not the hardware Responding to: ???'s previous message |
These LCD's are not terribly fussy, provided you adhere to the specified signal definitions and timing. You should note that there are prescribed timing constraints on the intialization sequence, which you must meet or exceed. By this, I mean you can exceed the limits by hundreds of milliseconds, but must meet the minimum delay in each case. Once initialized, the device provides a busy flag which you can monitor so that you're certain the previous action is complete before sending a new command.
RE |
| Topic | Author | Date |
| LCD+error | 01/01/70 00:00 | |
| sure, about what | 01/01/70 00:00 | |
| LCD+error | 01/01/70 00:00 | |
| Initialization | 01/01/70 00:00 | |
| Thank you | 01/01/70 00:00 | |
| Post all of your display code | 01/01/70 00:00 | |
| Oops... try this | 01/01/70 00:00 | |
| LCD+error | 01/01/70 00:00 | |
| usually it's the program, not the hardware | 01/01/70 00:00 | |
| 99% SOLVED | 01/01/70 00:00 | |
| Are you still... | 01/01/70 00:00 | |
| strange coding | 01/01/70 00:00 | |
| Sorry for mistake | 01/01/70 00:00 | |
fortunately happy end | 01/01/70 00:00 |