Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

irobot_create_2_1: /odom (z and w) and /sensorPacket (distance and angle) returning nonsense #6

Open
GoogleCodeExporter opened this issue Jul 7, 2015 · 9 comments

Comments

@GoogleCodeExporter
Copy link

Hello,

I'm trying to get the irobot_create_2_1 working "out of the box" with my iRobot 
Create.  I've hooked up the iRobot to a serial port (/dev/ttyUSB0) via a 
serial-to-USB converter.  I'm able to start the irobot_create_2_1 package 
successfully with the .launch file.  (Incidentally, the test .launch file was 
missing a name attribute for the node; accordingly, I updated that line to 
reflect:  <node pkg="irobot_create" type="driver" output="screen"/>.)

When I listen on the /odom and /sensorPacket topics, they are publishing 
successfully but the /odom messages' position x, position y, orientation z, 
orientation w, and linear x are returning seemingly random numbers on every 
publication.  Likewise, the /sensorPacket messages' distance and angle are also 
returning random numbers and the bumpers, cliffs and other sensors don't appear 
to be changing at all to any resulting physical interaction with the Create.

Finally, the /tank and other services are returning true as a confirmation, but 
aren't making the Create do anything.  The /reset service is the only thing 
which seems to do anything for me; it simply makes /odom and /sensorPacket stop 
publishing.

Any tips would be much appreciated!

Thanks very much!!
Billy McCafferty
http://www.sharprobotica.com

Original issue reported on code.google.com by [email protected] on 26 Oct 2010 at 5:35

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant