| ??? 03/09/10 02:58 Read: times |
#173951 - working Responding to: ???'s previous message |
So after a straight 18 hour stint, it took me 4 hours to get it working, and 12 hours excitment writing the drivers from scratch. I'll explain:
dodgy soldering led to some very odd errors. simple as that! I am now using a timer, and the scope shows the delay is as close as needs be, however may I ask why the timing is supposed to be so crucial, I can understand that an underestimated delay would lead to the display not reading the data correctly, but lengthy delays will surely only mean the code will run slowly. Is this truly a problem when writing quick prototyping code? With regards to magic, i am sure the reason it started working is because of the orientation supporting the dodgy soldering, as you say, always find out WHY it started working, I started tearing my hair out when it began to stop working after I had changed a function in code (and knocked the display) and could not figure out why it would not go back to its past stable / predictable state! cheers again guys |
| Topic | Author | Date |
| Display problems | 01/01/70 00:00 | |
| forgot to mention! | 01/01/70 00:00 | |
| read the datasheet and buy the iron | 01/01/70 00:00 | |
| just a minute ... | 01/01/70 00:00 | |
| If you can't "afford" the one pin for the R/W signal | 01/01/70 00:00 | |
| Why not address his question instead of wasting more money? | 01/01/70 00:00 | |
| odd behaviour | 01/01/70 00:00 | |
| Magic? | 01/01/70 00:00 | |
| oscilloscope is fine, but in this case... | 01/01/70 00:00 | |
| Both, I think | 01/01/70 00:00 | |
| "magic" is synonym for "luck" | 01/01/70 00:00 | |
| working | 01/01/70 00:00 | |
| min & max limits | 01/01/70 00:00 | |
| Delay lengths | 01/01/70 00:00 | |
If only folks would do what we once always did ... | 01/01/70 00:00 | |
| RW pin is defined but | 01/01/70 00:00 |