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 know I can monitor whether the RAPID code is running or not through the /rws/system_states topic. However, when the RAPID code stops due to collision, I would like to provide some additional insight on the reason why the RAPID code has stopped through the ROS log messages. This way, the user wouldn't need to have access to the robot controller to know what happened.
Does the RWS driver provide any means to access the robot's internal log messages or just indicate if the robot is in collision mode or not?
This discussion was converted from issue #86 on February 22, 2023 08:23.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I know I can monitor whether the RAPID code is running or not through the
/rws/system_states
topic. However, when the RAPID code stops due to collision, I would like to provide some additional insight on the reason why the RAPID code has stopped through the ROS log messages. This way, the user wouldn't need to have access to the robot controller to know what happened.Does the RWS driver provide any means to access the robot's internal log messages or just indicate if the robot is in collision mode or not?
Beta Was this translation helpful? Give feedback.
All reactions