Closed davidsthayer closed 10 years ago
If that value has never been written to in EEPROM then it could be returning a non-printable character. First write to it with the corresponding command, then try reading it again.
Good thought. So, we can successfully write values and still not read.
OK, I think that's because of the trouble we're having with chars being interpreted as ASCII instead of just bytes. I looked into that in CmdMessenger and confirmed that GetCharArg() is returning the argument as an ASCII character instead of the numeric value. We updated the code at the last meeting to handle the setter for the value, but the getter is still sending a char to Serial.println() which I think is interpreted as ASCII. I'll fix that in the console work I'm doing.
Awesome! Thanks Jacob!
Believe this is fixed with commit 624dfd0
returns resolution:
but with no value