You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey all,
So i've got the roboclaw_ros package built and running. Roboclaw plugged in over usb and powered / tested running. In the process of trying to pass some messages to the node I found some errors that came up in the roboclaw_node-1.log file.
I think the main takeaway that I have is that "Could not get version from roboclaw" means that the firmware may no longer be compatible.
If anyone has an idea of what might be going wrong id super appreciate any and all advice. Thanks so much in advance. Thank you @sonyccd for writing this node, it's really helpful to have a ROS node written already.
roboclaw_node-1.log file:
[rosout][INFO] 2019-02-11 15:39:51,365: Connecting to roboclaw
[rospy.internal][INFO] 2019-02-11 15:39:51,554: topic[/rosout] adding connection to [/rosout],
count 0
[rospy.internal][INFO] 2019-02-11 15:39:51,657: topic[/diagnostics] adding connection to [/diag
nostic_aggregator], count 0
[rosout][WARNING] 2019-02-11 15:39:51,704: Could not get version from roboclaw
[rosout][WARNING] 2019-02-11 15:39:52,397: Could not process inbound connection: topic types do
not match: [std_msgs/Int32] vs. [nav_msgs/Odometry]{'message_definition': 'int32 data', 'calle
rid': '/rosbridge_websocket', 'tcp_nodelay': '0', 'md5sum': 'da5909fbe378aeaf85e547e830cc1bb7',
'topic': '/odom', 'type': 'std_msgs/Int32'}
[rosout][INFO] 2019-02-11 15:39:53,389: Starting motor drive
[rosout][INFO] 2019-02-11 15:39:53,392: Did not get command for 1 second, stopping
[rosout][WARNING] 2019-02-11 15:39:53,418: Could not process inbound connection: topic types do
not match: [std_msgs/Int32] vs. [nav_msgs/Odometry]{'message_definition': 'int32 data', 'calle
rid': '/rosbridge_websocket', 'tcp_nodelay': '0', 'md5sum': 'da5909fbe378aeaf85e547e830cc1bb7',
'topic': '/odom', 'type': 'std_msgs/Int32'}
[rosout][WARNING] 2019-02-11 15:39:54,424: Could not process inbound connection: topic types do
not match: [std_msgs/Int32] vs. [nav_msgs/Odometry]{'message_definition': 'int32 data', 'calle
rid': '/rosbridge_websocket', 'tcp_nodelay': '0', 'md5sum': 'da5909fbe378aeaf85e547e830cc1bb7',
The text was updated successfully, but these errors were encountered:
Ok so what I missed was in the process of launching the node (roslaunch roboclaw_node roboclaw.launch), was that there is an error that mentioned.....
"ROS_MASTER_URI=http://BLAH.local:11311
ERROR: cannot launch node of type [roboclaw_node/roboclaw_node.py]: can't locate node [roboclaw_node.py] in package [roboclaw_node]"
Even though catkin make did come back without any errors I may not have built correctly or seemed to have missed a step. I can launch the aggregator.launch on its own just fine.
Thanks in advance for any help.
MFlego
changed the title
Issues connecting roboclaw_ros to roboclaw (versioning?)
Issues launching roboclaw_node
Feb 18, 2019
Hey all,
So i've got the roboclaw_ros package built and running. Roboclaw plugged in over usb and powered / tested running. In the process of trying to pass some messages to the node I found some errors that came up in the roboclaw_node-1.log file.
I think the main takeaway that I have is that "Could not get version from roboclaw" means that the firmware may no longer be compatible.
If anyone has an idea of what might be going wrong id super appreciate any and all advice. Thanks so much in advance. Thank you @sonyccd for writing this node, it's really helpful to have a ROS node written already.
roboclaw_node-1.log file:
[rosout][INFO] 2019-02-11 15:39:51,365: Connecting to roboclaw
[rospy.internal][INFO] 2019-02-11 15:39:51,554: topic[/rosout] adding connection to [/rosout],
count 0
[rospy.internal][INFO] 2019-02-11 15:39:51,657: topic[/diagnostics] adding connection to [/diag
nostic_aggregator], count 0
[rosout][WARNING] 2019-02-11 15:39:51,704: Could not get version from roboclaw
[rosout][WARNING] 2019-02-11 15:39:52,397: Could not process inbound connection: topic types do
not match: [std_msgs/Int32] vs. [nav_msgs/Odometry]{'message_definition': 'int32 data', 'calle
rid': '/rosbridge_websocket', 'tcp_nodelay': '0', 'md5sum': 'da5909fbe378aeaf85e547e830cc1bb7',
'topic': '/odom', 'type': 'std_msgs/Int32'}
[rosout][INFO] 2019-02-11 15:39:53,389: Starting motor drive
[rosout][INFO] 2019-02-11 15:39:53,392: Did not get command for 1 second, stopping
[rosout][WARNING] 2019-02-11 15:39:53,418: Could not process inbound connection: topic types do
not match: [std_msgs/Int32] vs. [nav_msgs/Odometry]{'message_definition': 'int32 data', 'calle
rid': '/rosbridge_websocket', 'tcp_nodelay': '0', 'md5sum': 'da5909fbe378aeaf85e547e830cc1bb7',
'topic': '/odom', 'type': 'std_msgs/Int32'}
[rosout][WARNING] 2019-02-11 15:39:54,424: Could not process inbound connection: topic types do
not match: [std_msgs/Int32] vs. [nav_msgs/Odometry]{'message_definition': 'int32 data', 'calle
rid': '/rosbridge_websocket', 'tcp_nodelay': '0', 'md5sum': 'da5909fbe378aeaf85e547e830cc1bb7',
The text was updated successfully, but these errors were encountered: