Hard to say without more diagnostics. After all, in the case of my robot car, something that should have worked perfectly in theory was just showing very low voltages on the oscilloscope. Hence I had to add a buffer chip. So sometimes just hearing a description of the problem doesn't help.However a solitary 0 (as I surmise is happening) could be caused by attempting to read from the serial port before things have stabilized (eg. one part has "come online" before another). I think a short delay, before opening the serial port, might help.
Glad that it's working. It's still a mystery to me why taking those steps was necessary.
The second one makes sense though, need the delay before serial.begin because the arduino needs a power up cooldown time.
Quote from: falven on Jan 21, 2012, 01:48 amThe second one makes sense though, need the delay before serial.begin because the arduino needs a power up cooldown time.Hmmm, not sure what that means, exactly. And strange I haven't noticed it. A 500ms delay does the trick. I'd wonder how short I could make it and still have it work.
Really! Interesting! Maybe if you sneak up on it you can take it out, haha! But then there is delayMicroseconds() ...
Keep in mind this is writing from cold boot. Every one of those "Hello's" is me hitting the reset button on the Arduino. It resets and writes "Hello" once.
Please enter a valid email to subscribe
We need to confirm your email address.
To complete the subscription, please click the link in the
email we just sent you.
Thank you for subscribing!
via Egeo 16