driver_name: neobotix_usboard | neobotix_usboard_msgs
...
Message Type | Topic Name | Description | can_msgs/Frame | can_tx | A copy of all raw CAN data received by the driver from the USBoard.|
---|---|---|---|---|---|
can_msgs/Frame | can_rx_echoA copy of all raw CAN data sent from the driver to the USBoard | All data published on this topic is intended to be sent to the sensor via a CAN interface. | |||
neobotix_usboard_msgs/Data1to4 | parsed_tx/usboard_data1to4 | Raw sensor values, warnings, and alerts generated by connected ultrasonics 1 through 4. | |||
neobotix_usboard_msgs/Data5to8 | parsed_tx/usboard_data5to8 | Raw sensor values, warnings, and alerts generated by connected ultrasonics 5 through 8. | |||
neobotix_usboard_msgs/Data9to12 | parsed_tx/usboard_data9to12 | Raw sensor values, warnings, and alerts generated by connected ultrasonics 9 through 12. | |||
neobotix_usboard_msgs/Data13to16 | parsed_tx/usboard_data13to16 | Raw sensor values, warnings, and alerts generated by connected ultrasonics 13 through 16. | |||
visualization_msgs/MarkerArray | as_tx/sonar_markers | Visualization information for RViz based on data abstracted from the raw ultrasonic readings. |
Published Topics
Message Type | Topic Name | Description |
---|---|---|
can_msgs/Frame | can_rxWill forward any raw CAN messages tx | All data published to this topic directly to the USBoard. |
Parameters
~can_hardware_id
The serial number of the Kvaser device.
~can_circuit_id
The 0-based index of the channel on the Kvaser device.
...
will be parsed by the driver. This should be connected to a CAN interface. |
Parameters
~can_basic_address
The decimal representation of the base address used for the CAN messages coming from the device.
...