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
I am using Locobot wx250s with ROS1 noetic and I am writing my own node to control it. I have a time consuming controller that can not be implemented on the Locobot's computer. But I can not run my node on the remote controller.
To check that, I am running the same message in the locobt's computer and remote computer with different results! why?
Locobot's computer:
locobot@locobot1:~$ rosmsg show irobot_create_msgs/WheelVels
std_msgs/Header header
uint32 seq
time stamp
string frame_id
float32 velocity_left
float32 velocity_right
Question
I am using Locobot wx250s with ROS1 noetic and I am writing my own node to control it. I have a time consuming controller that can not be implemented on the Locobot's computer. But I can not run my node on the remote controller.
To check that, I am running the same message in the locobt's computer and remote computer with different results! why?
Locobot's computer:
locobot@locobot1:~$ rosmsg show irobot_create_msgs/WheelVels
std_msgs/Header header
uint32 seq
time stamp
string frame_id
float32 velocity_left
float32 velocity_right
remote computer:
mhsnar@MME-EME203-L01:~/HRI$ rosmsg show irobot_create_msgs/WheelVels
Unable to load msg [irobot_create_msgs/WheelVels]: Cannot locate message [WheelVels]: unknown package [irobot_create_msgs] on search path [{'ros_environment': ['/opt/ros/noetic/share/ros_environment/msg'], 'rqt_rviz': ['/opt/ros/noetic/share/rqt_rviz/msg'], 'husky_navigation': ['/opt/ros/noetic/share/husky_navigation/msg'], 'diagnostic_aggregator': ['/opt/ros/noetic/share/diagnostic_aggregator/msg'], 'catkin': ['/opt/ros/noetic/share/catkin/msg'], 'amcl': ['/opt/ros/noetic/share/amcl/msg'], 'tf2_geometry_msgs': ['/opt/ros/noetic/share/tf2_geometry_msgs/msg'],
Robot Model
locobot wx250s
Operating System
Ubuntu 20.04
ROS Version
ROS 1 Noetic
Additional Info
No response
The text was updated successfully, but these errors were encountered: