The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
UPDATE: still having problems.
I now have my pseudoterminals nulled together. I have tested this with Brown university's irobot_create_2_1 driver.py. I am selecting the correct port, etc. When I run the driver.py on the other end of my pseudoterminals, I get two hex values from driver.py: 80 07 which is a request for the cliff and bump sensors. Regardless of what I return I get nothing back.
When I snoop in on communications to a REAL irobotCreate (just changing the serial port in driver.py) I sniff 0xfd from the driver.py on startup. I then get a reply from the iRobotCreate containing something similar to the following: 5e 72 0a be b0
Why would the driver.py send different bytes to the real serial port than my pseudoterminals? How does that even make sense?
Anyway,I think that since I have socat relaying at least something now, that the above can be "solved" though I might start a new question thread with the new issue I am having.
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
