Rnet Error Code 0B02?

[Rye]

Just got an error code that I've never seen- 0B02. The Rnet manual says "EEPROM Write Timeout" Any guesses?

[Burgerman]

Try again. Bad connection, bad cable?

[Rye]

It went away. It'll be back when it really matters.

[Rye]

It came back and I didn't have my phone so I sat broke down for 30min. But the error code from hell went away again.

[Rye]

electrically erasable programmable read-only memory
https://upload.wikimedia.org/wikipedia/ ... hancer.jpg

[Burgerman]

Electronics tend to work very reliably. Or they fail permanantly. This will be a bad connection somewhere on a bus cable. Take all apart, use switch cleaner and replug several times. If its on a permobil, no clue. If you can, swap all bus cables.

[Rye]

It does seem to be a bad wire. It didn't have any outward damage, but I swapped it out and so far no more troubles. Thanks.

[Rye]

It came back and I took a pic of the gibberish on the OMNI.

[steves1977uk]

This MIGHT be your problem (although I seriously doubt it!)... https://arduino.stackexchange.com/quest ... -of-eeprom EEPROMs do have a finite number of write cycles, so maybe your OMNI or PM needs a new EEPROM chip in it. But highly unlikely as this would require 100K+ of changes written to it!

Steve

[Burgerman]

Or its just faulty. Unreliable.

[Rye]

Maybe it's just an internal moisture issue or something. I'll ditch the OMNI and see if it helps.