I bought a Roombe 4XXX back when they were new, and (8 years later) have just received the OK from Mrs. XLCior to hack it. It is from a date prior to SCI being included in the firmware. It would require a black OSMO, but I couldn't find a source, so I went ahead and bought a scheduler remote
+ cable. Here's where it gets interesting:
When I hook up the remote, it counts down from 100 as expected, and seems to successfully complete the update. When I hook it up to an Arduino (using a home-built cable), I get:
So it appears that the update was successful. (Also worth noting that I get the expected output from the Roomba when charging, so I have some indications that the cable and baud rate are working OK.) The problem is that when I send a "start" byte to the Roomba, i.e. 128 per the SCI spec and as further described at http://www.robotappstore.com/Knowledge- ... ba/18.html
, the Roomba starts sending back random bits. It doesn't seem to honor any of the commands that I send. (Using an Arduino and appropriate sketches, not a direct connection to the computer.)
This leads me to wonder whether the scheduler remote
update really enables SCI for my Roomba? Another funky thing is that if I re-connect the scheduler remote
to the Roomba, it will again "update", i.e. count down from 100.
So is this a problem with my Roomba? Or am I just wrong in drawing the conclusion that the scheduler remote
should actually perform the update? If the latter, anybody have ideas on where I might buy/borrow a black osmo?