ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
Yep, I'm having the same problem. It looks like what's happening is that when we update the servo command with a new command, it simply ORs the bits together.
In other words, if your first command was 5, which is 00000101 in binary, and you send over 3 as your next command, which is 00000011 in binary, the next value will be 7, which is 00000111 in binary.
It looks like this problem has already been solved here
https://kforge.ros.org/rosserial/hg/rev/10cb30606b34
but I don't know how to apply it.
I've removed the old copy of rosserial in /opt/ros/electric/stacks and added the new version from the trunk into my ROS package path, but I still get the same error.
Any thoughts?
(I'm also running Electric.)
2 | Revised Explanation |
Yep, I'm having the same problem. It looks like what's happening is that when we update the servo command with a new command, it simply ORs the bits together.
In other words, if your first command was 5, which is 00000101 in binary, and you send over 3 as your next command, which is 00000011 in binary, the next value will be 7, which is 00000111 in binary.
It looks like this problem has already been solved here
https://kforge.ros.org/rosserial/hg/rev/10cb30606b34
but I don't know how to apply it.
I've removed the old copy of rosserial in /opt/ros/electric/stacks and added the new version from the trunk into my ROS package path, but I still get the same error.
Any thoughts?
(I'm also running Electric.)
UPDATE: Whoop--it looks like I've discovered the answer! Here's what I did:
Note: I've only gotten this to work with electric.
(My problem was that I was still running version 022.)
Hope this helps!
(Thanks, Mike Ferguson!)