-
Notifications
You must be signed in to change notification settings - Fork 193
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
FS 100 response to MOTO_MOTION_CTRL message incorrect. #1
Labels
Comments
Eric has released a fix already. I will try to upload this weekend. |
JeremyZoss
added a commit
that referenced
this issue
Jun 18, 2013
…quence/robot_id fields bugFix: always publish state for all active robot groups, even if no motion pending
Fixed in 292b5cc |
thiagodefreitas
pushed a commit
to thiagodefreitas/motoman
that referenced
this issue
May 16, 2014
Changed to the motoman repository
thiagodefreitas
pushed a commit
to thiagodefreitas/motoman
that referenced
this issue
Jun 12, 2014
Adds changes to the sia10f name
gavanderhoorn
pushed a commit
that referenced
this issue
Mar 16, 2017
Merge pull request #148 from ted-miller/jade-devel
gavanderhoorn
pushed a commit
that referenced
this issue
Nov 17, 2017
Merge kinetic-devel into personal fork
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The robot id and sequence fields in the MOTO_MOTION_CTRL reply are not set correctly. See the email snippet below for more details.
On 12/06/2013 20:01, Zoss, Jeremy K. wrote:
Yes, -1 interpreted as an unsigned would be 0xFFFFFFFF.
Looks like a copy/pasta error to me then. The 'else if' checks again for a ROS_MSG_MOTO_MOTION_CTRL, just as the 'if' before it did.
Ok.
If I get the dissector in a good enough state, I'll push it to my github
repo.
Gijs
The text was updated successfully, but these errors were encountered: