Add new status information #109
Conversation
…able change executable node name in launch file
|
The checks curently fail, because the needed changes for the urg_node_msgs package are not yet in the official repos, which the jenkins bot relies on? Is there any way to use the current github master of that repo for the jenkins checks? |
|
Still working towards a release of the update to messages - we shouldn't change the message in released distros (Humble/Iron) so I needed up branch off for a rolling release. Still waiting for that PR to be merged in rosdistro, and then I will do a new message package release. |
|
ros/rosdistro#37629 is the release for urg_node_msgs - now we have to wait for that to be merged, built and synced, and then this should pass. |
|
I pushed an empty commit to retrigger the actions and seems there are atleast no errors in those. Can you have a look if it is possible to merge this @mikeferguson ? |
|
@mikeferguson did you have time to check the MR in the meantime? :) |
This MR adds the ability to output the current warning and OSSD states the scanner calculates and transmits as part of the AR00 message. This is necessary to be able to use the scanner for any safety setup.
This MR relies on ros-drivers/urg_node_msgs#6 to be merged first.