Timeline for Serial.read has garbled data after a Serial.write
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 27, 2014 at 18:49 | comment | added | imjosh | .flush() pauses execution until the output buffer is empty. It shouldn't have anything to do with garbage on your input. Try putting a ~2.2k+- pull-down resistor between serial-in and ground to make sure you aren't getting noise or cross talk in the input buffer. | |
| Mar 27, 2014 at 11:50 | comment | added | JohnnyDeauville | I don't know why, but, for example, for prevent in a project the malfunction of a clock module, I must call to read it fewer than times, when the documentation not tell nothing about this.The fact is that many times the execution speed of the main loop can make some features of functions and/or response of devices will be wrong. As if you push data onto a funnel and arrives to the exit mistaken. | |
| Mar 27, 2014 at 8:59 | review | First posts | |||
| Mar 27, 2014 at 10:37 | |||||
| Mar 27, 2014 at 8:54 | comment | added | Cybergibbons | I don't understand why this would be. Surely .flush() should do as documented unless Roberto has overridden it? | |
| Mar 27, 2014 at 8:42 | history | answered | JohnnyDeauville | CC BY-SA 3.0 |