Repository Summary
| Checkout URI | https://github.com/mrpt-ros-pkg/mrpt_sensors.git |
| VCS Type | git |
| VCS Version | ros2 |
| Last Updated | 2026-05-20 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Packages
| Name | Version |
|---|---|
| mrpt_generic_sensor | 0.3.0 |
| mrpt_sensor_bumblebee_stereo | 0.3.0 |
| mrpt_sensor_gnss_nmea | 0.3.0 |
| mrpt_sensor_gnss_novatel | 0.3.0 |
| mrpt_sensor_imu_taobotics | 0.3.0 |
| mrpt_sensorlib | 0.3.0 |
| mrpt_sensors | 0.3.0 |
| novatel_oem6_msgs | 0.3.0 |
README
| Distro | Build dev | Release |
|---|---|---|
| ROS 2 Humble (u22.04) | ||
| ROS 2 Jazzy (u24.04) | ||
| ROS 2 Kilted (u24.04) | ||
| ROS 2 Rolling (u24.04) |
| EOL Distro | Last release |
|---|---|
| ROS 2 Iron (u22.04) |
mrpt_sensors
ROS nodes for various robotics sensors via mrpt-hwdrivers.
All packages follow REP-2003 regarding ROS 2 topic QoS.
Table of Contents
- Diagnostics support
mrpt_sensor_bumblebee_stereomrpt_sensor_gnss_nmeamrpt_sensor_gnss_novatelmrpt_sensor_imu_taoboticsmrpt_sensor_velodyne- novatel_oem6_msgs
- Individual package build status
Diagnostics support
All sensor nodes in this package publish ROS 2 diagnostics to the /diagnostics topic via the
diagnostic_updater package. The diagnostic status tracks
these conditions:
| Status | Condition |
|---|---|
WARN |
Node started but no observation has arrived yet within the startup timeout window |
ERROR |
Sensor exception (e.g., serial port unavailable) - node keeps retrying every retry_on_error_delay seconds |
ERROR |
Sensor was working but no observation has been received for longer than 3x the expected period |
WARN |
Observation rate is below 50% of the configured expected rate |
OK |
Observations are arriving at the expected rate |
ROS 2 parameters controlling diagnostic thresholds and retry behavior (settable at launch or via ros2 param set):
| Parameter | Default | Description |
|---|---|---|
diag_startup_timeout |
30.0 s |
How long to wait for the first observation before reporting an error |
diag_expected_rate |
1.0 Hz |
Expected observation rate; used for stale and rate-warning checks |
retry_on_error_delay |
5.0 s |
How long to wait before retrying after a sensor exception |
The diagnostic status also reports the measured observation rate, the observation count, and the hardware ID (node name).
Viewing diagnostics
Echo the raw topic directly:
ros2 topic echo /diagnostics
For a human-friendly live view, use rqt_runtime_monitor or the ros2 run equivalent:
ros2 run rqt_runtime_monitor rqt_runtime_monitor
Running a diagnostic aggregator
The diagnostic_aggregator collects and categorizes /diagnostics messages into
/diagnostics_agg. This is required by tools such as robot_monitor. To launch one quickly for
testing, install the package and create a minimal analyzers config:
sudo apt install ros-${ROS_DISTRO}-diagnostic-aggregator
Create a file analyzers.yaml:
analyzers:
ros__parameters:
path: Sensors
sensors:
type: diagnostic_aggregator/GenericAnalyzer
path: Sensors
contains:
- 'Sensor status'
Then run the aggregator with that config:
```bash
ros2 run diagnostic_aggregator aggregator_node –ros-args
–params-file analyzers.yaml
File truncated at 100 lines see the full file
CONTRIBUTING
Repository Summary
| Checkout URI | https://github.com/mrpt-ros-pkg/mrpt_sensors.git |
| VCS Type | git |
| VCS Version | ros2 |
| Last Updated | 2026-05-20 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Packages
| Name | Version |
|---|---|
| mrpt_generic_sensor | 0.3.0 |
| mrpt_sensor_bumblebee_stereo | 0.3.0 |
| mrpt_sensor_gnss_nmea | 0.3.0 |
| mrpt_sensor_gnss_novatel | 0.3.0 |
| mrpt_sensor_imu_taobotics | 0.3.0 |
| mrpt_sensorlib | 0.3.0 |
| mrpt_sensors | 0.3.0 |
| novatel_oem6_msgs | 0.3.0 |
README
| Distro | Build dev | Release |
|---|---|---|
| ROS 2 Humble (u22.04) | ||
| ROS 2 Jazzy (u24.04) | ||
| ROS 2 Kilted (u24.04) | ||
| ROS 2 Rolling (u24.04) |
| EOL Distro | Last release |
|---|---|
| ROS 2 Iron (u22.04) |
mrpt_sensors
ROS nodes for various robotics sensors via mrpt-hwdrivers.
All packages follow REP-2003 regarding ROS 2 topic QoS.
Table of Contents
- Diagnostics support
mrpt_sensor_bumblebee_stereomrpt_sensor_gnss_nmeamrpt_sensor_gnss_novatelmrpt_sensor_imu_taoboticsmrpt_sensor_velodyne- novatel_oem6_msgs
- Individual package build status
Diagnostics support
All sensor nodes in this package publish ROS 2 diagnostics to the /diagnostics topic via the
diagnostic_updater package. The diagnostic status tracks
these conditions:
| Status | Condition |
|---|---|
WARN |
Node started but no observation has arrived yet within the startup timeout window |
ERROR |
Sensor exception (e.g., serial port unavailable) - node keeps retrying every retry_on_error_delay seconds |
ERROR |
Sensor was working but no observation has been received for longer than 3x the expected period |
WARN |
Observation rate is below 50% of the configured expected rate |
OK |
Observations are arriving at the expected rate |
ROS 2 parameters controlling diagnostic thresholds and retry behavior (settable at launch or via ros2 param set):
| Parameter | Default | Description |
|---|---|---|
diag_startup_timeout |
30.0 s |
How long to wait for the first observation before reporting an error |
diag_expected_rate |
1.0 Hz |
Expected observation rate; used for stale and rate-warning checks |
retry_on_error_delay |
5.0 s |
How long to wait before retrying after a sensor exception |
The diagnostic status also reports the measured observation rate, the observation count, and the hardware ID (node name).
Viewing diagnostics
Echo the raw topic directly:
ros2 topic echo /diagnostics
For a human-friendly live view, use rqt_runtime_monitor or the ros2 run equivalent:
ros2 run rqt_runtime_monitor rqt_runtime_monitor
Running a diagnostic aggregator
The diagnostic_aggregator collects and categorizes /diagnostics messages into
/diagnostics_agg. This is required by tools such as robot_monitor. To launch one quickly for
testing, install the package and create a minimal analyzers config:
sudo apt install ros-${ROS_DISTRO}-diagnostic-aggregator
Create a file analyzers.yaml:
analyzers:
ros__parameters:
path: Sensors
sensors:
type: diagnostic_aggregator/GenericAnalyzer
path: Sensors
contains:
- 'Sensor status'
Then run the aggregator with that config:
```bash
ros2 run diagnostic_aggregator aggregator_node –ros-args
–params-file analyzers.yaml
File truncated at 100 lines see the full file
CONTRIBUTING
Repository Summary
| Checkout URI | https://github.com/mrpt-ros-pkg/mrpt_sensors.git |
| VCS Type | git |
| VCS Version | ros2 |
| Last Updated | 2026-05-20 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Packages
| Name | Version |
|---|---|
| mrpt_generic_sensor | 0.3.0 |
| mrpt_sensor_bumblebee_stereo | 0.3.0 |
| mrpt_sensor_gnss_nmea | 0.3.0 |
| mrpt_sensor_gnss_novatel | 0.3.0 |
| mrpt_sensor_imu_taobotics | 0.3.0 |
| mrpt_sensorlib | 0.3.0 |
| mrpt_sensors | 0.3.0 |
| novatel_oem6_msgs | 0.3.0 |
README
| Distro | Build dev | Release |
|---|---|---|
| ROS 2 Humble (u22.04) | ||
| ROS 2 Jazzy (u24.04) | ||
| ROS 2 Kilted (u24.04) | ||
| ROS 2 Rolling (u24.04) |
| EOL Distro | Last release |
|---|---|
| ROS 2 Iron (u22.04) |
mrpt_sensors
ROS nodes for various robotics sensors via mrpt-hwdrivers.
All packages follow REP-2003 regarding ROS 2 topic QoS.
Table of Contents
- Diagnostics support
mrpt_sensor_bumblebee_stereomrpt_sensor_gnss_nmeamrpt_sensor_gnss_novatelmrpt_sensor_imu_taoboticsmrpt_sensor_velodyne- novatel_oem6_msgs
- Individual package build status
Diagnostics support
All sensor nodes in this package publish ROS 2 diagnostics to the /diagnostics topic via the
diagnostic_updater package. The diagnostic status tracks
these conditions:
| Status | Condition |
|---|---|
WARN |
Node started but no observation has arrived yet within the startup timeout window |
ERROR |
Sensor exception (e.g., serial port unavailable) - node keeps retrying every retry_on_error_delay seconds |
ERROR |
Sensor was working but no observation has been received for longer than 3x the expected period |
WARN |
Observation rate is below 50% of the configured expected rate |
OK |
Observations are arriving at the expected rate |
ROS 2 parameters controlling diagnostic thresholds and retry behavior (settable at launch or via ros2 param set):
| Parameter | Default | Description |
|---|---|---|
diag_startup_timeout |
30.0 s |
How long to wait for the first observation before reporting an error |
diag_expected_rate |
1.0 Hz |
Expected observation rate; used for stale and rate-warning checks |
retry_on_error_delay |
5.0 s |
How long to wait before retrying after a sensor exception |
The diagnostic status also reports the measured observation rate, the observation count, and the hardware ID (node name).
Viewing diagnostics
Echo the raw topic directly:
ros2 topic echo /diagnostics
For a human-friendly live view, use rqt_runtime_monitor or the ros2 run equivalent:
ros2 run rqt_runtime_monitor rqt_runtime_monitor
Running a diagnostic aggregator
The diagnostic_aggregator collects and categorizes /diagnostics messages into
/diagnostics_agg. This is required by tools such as robot_monitor. To launch one quickly for
testing, install the package and create a minimal analyzers config:
sudo apt install ros-${ROS_DISTRO}-diagnostic-aggregator
Create a file analyzers.yaml:
analyzers:
ros__parameters:
path: Sensors
sensors:
type: diagnostic_aggregator/GenericAnalyzer
path: Sensors
contains:
- 'Sensor status'
Then run the aggregator with that config:
```bash
ros2 run diagnostic_aggregator aggregator_node –ros-args
–params-file analyzers.yaml
File truncated at 100 lines see the full file
CONTRIBUTING
Repository Summary
| Checkout URI | https://github.com/mrpt-ros-pkg/mrpt_sensors.git |
| VCS Type | git |
| VCS Version | ros2 |
| Last Updated | 2026-05-20 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Packages
| Name | Version |
|---|---|
| mrpt_generic_sensor | 0.3.0 |
| mrpt_sensor_bumblebee_stereo | 0.3.0 |
| mrpt_sensor_gnss_nmea | 0.3.0 |
| mrpt_sensor_gnss_novatel | 0.3.0 |
| mrpt_sensor_imu_taobotics | 0.3.0 |
| mrpt_sensorlib | 0.3.0 |
| mrpt_sensors | 0.3.0 |
| novatel_oem6_msgs | 0.3.0 |
README
| Distro | Build dev | Release |
|---|---|---|
| ROS 2 Humble (u22.04) | ||
| ROS 2 Jazzy (u24.04) | ||
| ROS 2 Kilted (u24.04) | ||
| ROS 2 Rolling (u24.04) |
| EOL Distro | Last release |
|---|---|
| ROS 2 Iron (u22.04) |
mrpt_sensors
ROS nodes for various robotics sensors via mrpt-hwdrivers.
All packages follow REP-2003 regarding ROS 2 topic QoS.
Table of Contents
- Diagnostics support
mrpt_sensor_bumblebee_stereomrpt_sensor_gnss_nmeamrpt_sensor_gnss_novatelmrpt_sensor_imu_taoboticsmrpt_sensor_velodyne- novatel_oem6_msgs
- Individual package build status
Diagnostics support
All sensor nodes in this package publish ROS 2 diagnostics to the /diagnostics topic via the
diagnostic_updater package. The diagnostic status tracks
these conditions:
| Status | Condition |
|---|---|
WARN |
Node started but no observation has arrived yet within the startup timeout window |
ERROR |
Sensor exception (e.g., serial port unavailable) - node keeps retrying every retry_on_error_delay seconds |
ERROR |
Sensor was working but no observation has been received for longer than 3x the expected period |
WARN |
Observation rate is below 50% of the configured expected rate |
OK |
Observations are arriving at the expected rate |
ROS 2 parameters controlling diagnostic thresholds and retry behavior (settable at launch or via ros2 param set):
| Parameter | Default | Description |
|---|---|---|
diag_startup_timeout |
30.0 s |
How long to wait for the first observation before reporting an error |
diag_expected_rate |
1.0 Hz |
Expected observation rate; used for stale and rate-warning checks |
retry_on_error_delay |
5.0 s |
How long to wait before retrying after a sensor exception |
The diagnostic status also reports the measured observation rate, the observation count, and the hardware ID (node name).
Viewing diagnostics
Echo the raw topic directly:
ros2 topic echo /diagnostics
For a human-friendly live view, use rqt_runtime_monitor or the ros2 run equivalent:
ros2 run rqt_runtime_monitor rqt_runtime_monitor
Running a diagnostic aggregator
The diagnostic_aggregator collects and categorizes /diagnostics messages into
/diagnostics_agg. This is required by tools such as robot_monitor. To launch one quickly for
testing, install the package and create a minimal analyzers config:
sudo apt install ros-${ROS_DISTRO}-diagnostic-aggregator
Create a file analyzers.yaml:
analyzers:
ros__parameters:
path: Sensors
sensors:
type: diagnostic_aggregator/GenericAnalyzer
path: Sensors
contains:
- 'Sensor status'
Then run the aggregator with that config:
```bash
ros2 run diagnostic_aggregator aggregator_node –ros-args
–params-file analyzers.yaml
File truncated at 100 lines see the full file
CONTRIBUTING
Repository Summary
| Checkout URI | https://github.com/mrpt-ros-pkg/mrpt_sensors.git |
| VCS Type | git |
| VCS Version | ros2 |
| Last Updated | 2026-05-20 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Packages
| Name | Version |
|---|---|
| mrpt_generic_sensor | 0.3.0 |
| mrpt_sensor_bumblebee_stereo | 0.3.0 |
| mrpt_sensor_gnss_nmea | 0.3.0 |
| mrpt_sensor_gnss_novatel | 0.3.0 |
| mrpt_sensor_imu_taobotics | 0.3.0 |
| mrpt_sensorlib | 0.3.0 |
| mrpt_sensors | 0.3.0 |
| novatel_oem6_msgs | 0.3.0 |
README
| Distro | Build dev | Release |
|---|---|---|
| ROS 2 Humble (u22.04) | ||
| ROS 2 Jazzy (u24.04) | ||
| ROS 2 Kilted (u24.04) | ||
| ROS 2 Rolling (u24.04) |
| EOL Distro | Last release |
|---|---|
| ROS 2 Iron (u22.04) |
mrpt_sensors
ROS nodes for various robotics sensors via mrpt-hwdrivers.
All packages follow REP-2003 regarding ROS 2 topic QoS.
Table of Contents
- Diagnostics support
mrpt_sensor_bumblebee_stereomrpt_sensor_gnss_nmeamrpt_sensor_gnss_novatelmrpt_sensor_imu_taoboticsmrpt_sensor_velodyne- novatel_oem6_msgs
- Individual package build status
Diagnostics support
All sensor nodes in this package publish ROS 2 diagnostics to the /diagnostics topic via the
diagnostic_updater package. The diagnostic status tracks
these conditions:
| Status | Condition |
|---|---|
WARN |
Node started but no observation has arrived yet within the startup timeout window |
ERROR |
Sensor exception (e.g., serial port unavailable) - node keeps retrying every retry_on_error_delay seconds |
ERROR |
Sensor was working but no observation has been received for longer than 3x the expected period |
WARN |
Observation rate is below 50% of the configured expected rate |
OK |
Observations are arriving at the expected rate |
ROS 2 parameters controlling diagnostic thresholds and retry behavior (settable at launch or via ros2 param set):
| Parameter | Default | Description |
|---|---|---|
diag_startup_timeout |
30.0 s |
How long to wait for the first observation before reporting an error |
diag_expected_rate |
1.0 Hz |
Expected observation rate; used for stale and rate-warning checks |
retry_on_error_delay |
5.0 s |
How long to wait before retrying after a sensor exception |
The diagnostic status also reports the measured observation rate, the observation count, and the hardware ID (node name).
Viewing diagnostics
Echo the raw topic directly:
ros2 topic echo /diagnostics
For a human-friendly live view, use rqt_runtime_monitor or the ros2 run equivalent:
ros2 run rqt_runtime_monitor rqt_runtime_monitor
Running a diagnostic aggregator
The diagnostic_aggregator collects and categorizes /diagnostics messages into
/diagnostics_agg. This is required by tools such as robot_monitor. To launch one quickly for
testing, install the package and create a minimal analyzers config:
sudo apt install ros-${ROS_DISTRO}-diagnostic-aggregator
Create a file analyzers.yaml:
analyzers:
ros__parameters:
path: Sensors
sensors:
type: diagnostic_aggregator/GenericAnalyzer
path: Sensors
contains:
- 'Sensor status'
Then run the aggregator with that config:
```bash
ros2 run diagnostic_aggregator aggregator_node –ros-args
–params-file analyzers.yaml
File truncated at 100 lines see the full file
CONTRIBUTING
Repository Summary
| Checkout URI | https://github.com/mrpt-ros-pkg/mrpt_sensors.git |
| VCS Type | git |
| VCS Version | ros2 |
| Last Updated | 2026-05-20 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Packages
| Name | Version |
|---|---|
| mrpt_generic_sensor | 0.3.0 |
| mrpt_sensor_bumblebee_stereo | 0.3.0 |
| mrpt_sensor_gnss_nmea | 0.3.0 |
| mrpt_sensor_gnss_novatel | 0.3.0 |
| mrpt_sensor_imu_taobotics | 0.3.0 |
| mrpt_sensorlib | 0.3.0 |
| mrpt_sensors | 0.3.0 |
| novatel_oem6_msgs | 0.3.0 |
README
| Distro | Build dev | Release |
|---|---|---|
| ROS 2 Humble (u22.04) | ||
| ROS 2 Jazzy (u24.04) | ||
| ROS 2 Kilted (u24.04) | ||
| ROS 2 Rolling (u24.04) |
| EOL Distro | Last release |
|---|---|
| ROS 2 Iron (u22.04) |
mrpt_sensors
ROS nodes for various robotics sensors via mrpt-hwdrivers.
All packages follow REP-2003 regarding ROS 2 topic QoS.
Table of Contents
- Diagnostics support
mrpt_sensor_bumblebee_stereomrpt_sensor_gnss_nmeamrpt_sensor_gnss_novatelmrpt_sensor_imu_taoboticsmrpt_sensor_velodyne- novatel_oem6_msgs
- Individual package build status
Diagnostics support
All sensor nodes in this package publish ROS 2 diagnostics to the /diagnostics topic via the
diagnostic_updater package. The diagnostic status tracks
these conditions:
| Status | Condition |
|---|---|
WARN |
Node started but no observation has arrived yet within the startup timeout window |
ERROR |
Sensor exception (e.g., serial port unavailable) - node keeps retrying every retry_on_error_delay seconds |
ERROR |
Sensor was working but no observation has been received for longer than 3x the expected period |
WARN |
Observation rate is below 50% of the configured expected rate |
OK |
Observations are arriving at the expected rate |
ROS 2 parameters controlling diagnostic thresholds and retry behavior (settable at launch or via ros2 param set):
| Parameter | Default | Description |
|---|---|---|
diag_startup_timeout |
30.0 s |
How long to wait for the first observation before reporting an error |
diag_expected_rate |
1.0 Hz |
Expected observation rate; used for stale and rate-warning checks |
retry_on_error_delay |
5.0 s |
How long to wait before retrying after a sensor exception |
The diagnostic status also reports the measured observation rate, the observation count, and the hardware ID (node name).
Viewing diagnostics
Echo the raw topic directly:
ros2 topic echo /diagnostics
For a human-friendly live view, use rqt_runtime_monitor or the ros2 run equivalent:
ros2 run rqt_runtime_monitor rqt_runtime_monitor
Running a diagnostic aggregator
The diagnostic_aggregator collects and categorizes /diagnostics messages into
/diagnostics_agg. This is required by tools such as robot_monitor. To launch one quickly for
testing, install the package and create a minimal analyzers config:
sudo apt install ros-${ROS_DISTRO}-diagnostic-aggregator
Create a file analyzers.yaml:
analyzers:
ros__parameters:
path: Sensors
sensors:
type: diagnostic_aggregator/GenericAnalyzer
path: Sensors
contains:
- 'Sensor status'
Then run the aggregator with that config:
```bash
ros2 run diagnostic_aggregator aggregator_node –ros-args
–params-file analyzers.yaml
File truncated at 100 lines see the full file
CONTRIBUTING
Repository Summary
| Checkout URI | https://github.com/mrpt-ros-pkg/mrpt_sensors.git |
| VCS Type | git |
| VCS Version | ros2 |
| Last Updated | 2026-05-20 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Packages
| Name | Version |
|---|---|
| mrpt_generic_sensor | 0.3.0 |
| mrpt_sensor_bumblebee_stereo | 0.3.0 |
| mrpt_sensor_gnss_nmea | 0.3.0 |
| mrpt_sensor_gnss_novatel | 0.3.0 |
| mrpt_sensor_imu_taobotics | 0.3.0 |
| mrpt_sensorlib | 0.3.0 |
| mrpt_sensors | 0.3.0 |
| novatel_oem6_msgs | 0.3.0 |
README
| Distro | Build dev | Release |
|---|---|---|
| ROS 2 Humble (u22.04) | ||
| ROS 2 Jazzy (u24.04) | ||
| ROS 2 Kilted (u24.04) | ||
| ROS 2 Rolling (u24.04) |
| EOL Distro | Last release |
|---|---|
| ROS 2 Iron (u22.04) |
mrpt_sensors
ROS nodes for various robotics sensors via mrpt-hwdrivers.
All packages follow REP-2003 regarding ROS 2 topic QoS.
Table of Contents
- Diagnostics support
mrpt_sensor_bumblebee_stereomrpt_sensor_gnss_nmeamrpt_sensor_gnss_novatelmrpt_sensor_imu_taoboticsmrpt_sensor_velodyne- novatel_oem6_msgs
- Individual package build status
Diagnostics support
All sensor nodes in this package publish ROS 2 diagnostics to the /diagnostics topic via the
diagnostic_updater package. The diagnostic status tracks
these conditions:
| Status | Condition |
|---|---|
WARN |
Node started but no observation has arrived yet within the startup timeout window |
ERROR |
Sensor exception (e.g., serial port unavailable) - node keeps retrying every retry_on_error_delay seconds |
ERROR |
Sensor was working but no observation has been received for longer than 3x the expected period |
WARN |
Observation rate is below 50% of the configured expected rate |
OK |
Observations are arriving at the expected rate |
ROS 2 parameters controlling diagnostic thresholds and retry behavior (settable at launch or via ros2 param set):
| Parameter | Default | Description |
|---|---|---|
diag_startup_timeout |
30.0 s |
How long to wait for the first observation before reporting an error |
diag_expected_rate |
1.0 Hz |
Expected observation rate; used for stale and rate-warning checks |
retry_on_error_delay |
5.0 s |
How long to wait before retrying after a sensor exception |
The diagnostic status also reports the measured observation rate, the observation count, and the hardware ID (node name).
Viewing diagnostics
Echo the raw topic directly:
ros2 topic echo /diagnostics
For a human-friendly live view, use rqt_runtime_monitor or the ros2 run equivalent:
ros2 run rqt_runtime_monitor rqt_runtime_monitor
Running a diagnostic aggregator
The diagnostic_aggregator collects and categorizes /diagnostics messages into
/diagnostics_agg. This is required by tools such as robot_monitor. To launch one quickly for
testing, install the package and create a minimal analyzers config:
sudo apt install ros-${ROS_DISTRO}-diagnostic-aggregator
Create a file analyzers.yaml:
analyzers:
ros__parameters:
path: Sensors
sensors:
type: diagnostic_aggregator/GenericAnalyzer
path: Sensors
contains:
- 'Sensor status'
Then run the aggregator with that config:
```bash
ros2 run diagnostic_aggregator aggregator_node –ros-args
–params-file analyzers.yaml
File truncated at 100 lines see the full file
CONTRIBUTING
Repository Summary
| Checkout URI | https://github.com/mrpt-ros-pkg/mrpt_sensors.git |
| VCS Type | git |
| VCS Version | ros2 |
| Last Updated | 2026-05-20 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Packages
| Name | Version |
|---|---|
| mrpt_generic_sensor | 0.3.0 |
| mrpt_sensor_bumblebee_stereo | 0.3.0 |
| mrpt_sensor_gnss_nmea | 0.3.0 |
| mrpt_sensor_gnss_novatel | 0.3.0 |
| mrpt_sensor_imu_taobotics | 0.3.0 |
| mrpt_sensorlib | 0.3.0 |
| mrpt_sensors | 0.3.0 |
| novatel_oem6_msgs | 0.3.0 |
README
| Distro | Build dev | Release |
|---|---|---|
| ROS 2 Humble (u22.04) | ||
| ROS 2 Jazzy (u24.04) | ||
| ROS 2 Kilted (u24.04) | ||
| ROS 2 Rolling (u24.04) |
| EOL Distro | Last release |
|---|---|
| ROS 2 Iron (u22.04) |
mrpt_sensors
ROS nodes for various robotics sensors via mrpt-hwdrivers.
All packages follow REP-2003 regarding ROS 2 topic QoS.
Table of Contents
- Diagnostics support
mrpt_sensor_bumblebee_stereomrpt_sensor_gnss_nmeamrpt_sensor_gnss_novatelmrpt_sensor_imu_taoboticsmrpt_sensor_velodyne- novatel_oem6_msgs
- Individual package build status
Diagnostics support
All sensor nodes in this package publish ROS 2 diagnostics to the /diagnostics topic via the
diagnostic_updater package. The diagnostic status tracks
these conditions:
| Status | Condition |
|---|---|
WARN |
Node started but no observation has arrived yet within the startup timeout window |
ERROR |
Sensor exception (e.g., serial port unavailable) - node keeps retrying every retry_on_error_delay seconds |
ERROR |
Sensor was working but no observation has been received for longer than 3x the expected period |
WARN |
Observation rate is below 50% of the configured expected rate |
OK |
Observations are arriving at the expected rate |
ROS 2 parameters controlling diagnostic thresholds and retry behavior (settable at launch or via ros2 param set):
| Parameter | Default | Description |
|---|---|---|
diag_startup_timeout |
30.0 s |
How long to wait for the first observation before reporting an error |
diag_expected_rate |
1.0 Hz |
Expected observation rate; used for stale and rate-warning checks |
retry_on_error_delay |
5.0 s |
How long to wait before retrying after a sensor exception |
The diagnostic status also reports the measured observation rate, the observation count, and the hardware ID (node name).
Viewing diagnostics
Echo the raw topic directly:
ros2 topic echo /diagnostics
For a human-friendly live view, use rqt_runtime_monitor or the ros2 run equivalent:
ros2 run rqt_runtime_monitor rqt_runtime_monitor
Running a diagnostic aggregator
The diagnostic_aggregator collects and categorizes /diagnostics messages into
/diagnostics_agg. This is required by tools such as robot_monitor. To launch one quickly for
testing, install the package and create a minimal analyzers config:
sudo apt install ros-${ROS_DISTRO}-diagnostic-aggregator
Create a file analyzers.yaml:
analyzers:
ros__parameters:
path: Sensors
sensors:
type: diagnostic_aggregator/GenericAnalyzer
path: Sensors
contains:
- 'Sensor status'
Then run the aggregator with that config:
```bash
ros2 run diagnostic_aggregator aggregator_node –ros-args
–params-file analyzers.yaml
File truncated at 100 lines see the full file
CONTRIBUTING
Repository Summary
| Checkout URI | https://github.com/mrpt-ros-pkg/mrpt_sensors.git |
| VCS Type | git |
| VCS Version | ros2 |
| Last Updated | 2026-05-20 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Packages
| Name | Version |
|---|---|
| mrpt_generic_sensor | 0.3.0 |
| mrpt_sensor_bumblebee_stereo | 0.3.0 |
| mrpt_sensor_gnss_nmea | 0.3.0 |
| mrpt_sensor_gnss_novatel | 0.3.0 |
| mrpt_sensor_imu_taobotics | 0.3.0 |
| mrpt_sensorlib | 0.3.0 |
| mrpt_sensors | 0.3.0 |
| novatel_oem6_msgs | 0.3.0 |
README
| Distro | Build dev | Release |
|---|---|---|
| ROS 2 Humble (u22.04) | ||
| ROS 2 Jazzy (u24.04) | ||
| ROS 2 Kilted (u24.04) | ||
| ROS 2 Rolling (u24.04) |
| EOL Distro | Last release |
|---|---|
| ROS 2 Iron (u22.04) |
mrpt_sensors
ROS nodes for various robotics sensors via mrpt-hwdrivers.
All packages follow REP-2003 regarding ROS 2 topic QoS.
Table of Contents
- Diagnostics support
mrpt_sensor_bumblebee_stereomrpt_sensor_gnss_nmeamrpt_sensor_gnss_novatelmrpt_sensor_imu_taoboticsmrpt_sensor_velodyne- novatel_oem6_msgs
- Individual package build status
Diagnostics support
All sensor nodes in this package publish ROS 2 diagnostics to the /diagnostics topic via the
diagnostic_updater package. The diagnostic status tracks
these conditions:
| Status | Condition |
|---|---|
WARN |
Node started but no observation has arrived yet within the startup timeout window |
ERROR |
Sensor exception (e.g., serial port unavailable) - node keeps retrying every retry_on_error_delay seconds |
ERROR |
Sensor was working but no observation has been received for longer than 3x the expected period |
WARN |
Observation rate is below 50% of the configured expected rate |
OK |
Observations are arriving at the expected rate |
ROS 2 parameters controlling diagnostic thresholds and retry behavior (settable at launch or via ros2 param set):
| Parameter | Default | Description |
|---|---|---|
diag_startup_timeout |
30.0 s |
How long to wait for the first observation before reporting an error |
diag_expected_rate |
1.0 Hz |
Expected observation rate; used for stale and rate-warning checks |
retry_on_error_delay |
5.0 s |
How long to wait before retrying after a sensor exception |
The diagnostic status also reports the measured observation rate, the observation count, and the hardware ID (node name).
Viewing diagnostics
Echo the raw topic directly:
ros2 topic echo /diagnostics
For a human-friendly live view, use rqt_runtime_monitor or the ros2 run equivalent:
ros2 run rqt_runtime_monitor rqt_runtime_monitor
Running a diagnostic aggregator
The diagnostic_aggregator collects and categorizes /diagnostics messages into
/diagnostics_agg. This is required by tools such as robot_monitor. To launch one quickly for
testing, install the package and create a minimal analyzers config:
sudo apt install ros-${ROS_DISTRO}-diagnostic-aggregator
Create a file analyzers.yaml:
analyzers:
ros__parameters:
path: Sensors
sensors:
type: diagnostic_aggregator/GenericAnalyzer
path: Sensors
contains:
- 'Sensor status'
Then run the aggregator with that config:
```bash
ros2 run diagnostic_aggregator aggregator_node –ros-args
–params-file analyzers.yaml
File truncated at 100 lines see the full file
CONTRIBUTING
Repository Summary
| Checkout URI | https://github.com/mrpt-ros-pkg/mrpt_sensors.git |
| VCS Type | git |
| VCS Version | ros2 |
| Last Updated | 2026-05-20 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Packages
| Name | Version |
|---|---|
| mrpt_generic_sensor | 0.3.0 |
| mrpt_sensor_bumblebee_stereo | 0.3.0 |
| mrpt_sensor_gnss_nmea | 0.3.0 |
| mrpt_sensor_gnss_novatel | 0.3.0 |
| mrpt_sensor_imu_taobotics | 0.3.0 |
| mrpt_sensorlib | 0.3.0 |
| mrpt_sensors | 0.3.0 |
| novatel_oem6_msgs | 0.3.0 |
README
| Distro | Build dev | Release |
|---|---|---|
| ROS 2 Humble (u22.04) | ||
| ROS 2 Jazzy (u24.04) | ||
| ROS 2 Kilted (u24.04) | ||
| ROS 2 Rolling (u24.04) |
| EOL Distro | Last release |
|---|---|
| ROS 2 Iron (u22.04) |
mrpt_sensors
ROS nodes for various robotics sensors via mrpt-hwdrivers.
All packages follow REP-2003 regarding ROS 2 topic QoS.
Table of Contents
- Diagnostics support
mrpt_sensor_bumblebee_stereomrpt_sensor_gnss_nmeamrpt_sensor_gnss_novatelmrpt_sensor_imu_taoboticsmrpt_sensor_velodyne- novatel_oem6_msgs
- Individual package build status
Diagnostics support
All sensor nodes in this package publish ROS 2 diagnostics to the /diagnostics topic via the
diagnostic_updater package. The diagnostic status tracks
these conditions:
| Status | Condition |
|---|---|
WARN |
Node started but no observation has arrived yet within the startup timeout window |
ERROR |
Sensor exception (e.g., serial port unavailable) - node keeps retrying every retry_on_error_delay seconds |
ERROR |
Sensor was working but no observation has been received for longer than 3x the expected period |
WARN |
Observation rate is below 50% of the configured expected rate |
OK |
Observations are arriving at the expected rate |
ROS 2 parameters controlling diagnostic thresholds and retry behavior (settable at launch or via ros2 param set):
| Parameter | Default | Description |
|---|---|---|
diag_startup_timeout |
30.0 s |
How long to wait for the first observation before reporting an error |
diag_expected_rate |
1.0 Hz |
Expected observation rate; used for stale and rate-warning checks |
retry_on_error_delay |
5.0 s |
How long to wait before retrying after a sensor exception |
The diagnostic status also reports the measured observation rate, the observation count, and the hardware ID (node name).
Viewing diagnostics
Echo the raw topic directly:
ros2 topic echo /diagnostics
For a human-friendly live view, use rqt_runtime_monitor or the ros2 run equivalent:
ros2 run rqt_runtime_monitor rqt_runtime_monitor
Running a diagnostic aggregator
The diagnostic_aggregator collects and categorizes /diagnostics messages into
/diagnostics_agg. This is required by tools such as robot_monitor. To launch one quickly for
testing, install the package and create a minimal analyzers config:
sudo apt install ros-${ROS_DISTRO}-diagnostic-aggregator
Create a file analyzers.yaml:
analyzers:
ros__parameters:
path: Sensors
sensors:
type: diagnostic_aggregator/GenericAnalyzer
path: Sensors
contains:
- 'Sensor status'
Then run the aggregator with that config:
```bash
ros2 run diagnostic_aggregator aggregator_node –ros-args
–params-file analyzers.yaml
File truncated at 100 lines see the full file
CONTRIBUTING
Repository Summary
| Checkout URI | https://github.com/mrpt-ros-pkg/mrpt_sensors.git |
| VCS Type | git |
| VCS Version | ros2 |
| Last Updated | 2026-05-20 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Packages
| Name | Version |
|---|---|
| mrpt_generic_sensor | 0.3.0 |
| mrpt_sensor_bumblebee_stereo | 0.3.0 |
| mrpt_sensor_gnss_nmea | 0.3.0 |
| mrpt_sensor_gnss_novatel | 0.3.0 |
| mrpt_sensor_imu_taobotics | 0.3.0 |
| mrpt_sensorlib | 0.3.0 |
| mrpt_sensors | 0.3.0 |
| novatel_oem6_msgs | 0.3.0 |
README
| Distro | Build dev | Release |
|---|---|---|
| ROS 2 Humble (u22.04) | ||
| ROS 2 Jazzy (u24.04) | ||
| ROS 2 Kilted (u24.04) | ||
| ROS 2 Rolling (u24.04) |
| EOL Distro | Last release |
|---|---|
| ROS 2 Iron (u22.04) |
mrpt_sensors
ROS nodes for various robotics sensors via mrpt-hwdrivers.
All packages follow REP-2003 regarding ROS 2 topic QoS.
Table of Contents
- Diagnostics support
mrpt_sensor_bumblebee_stereomrpt_sensor_gnss_nmeamrpt_sensor_gnss_novatelmrpt_sensor_imu_taoboticsmrpt_sensor_velodyne- novatel_oem6_msgs
- Individual package build status
Diagnostics support
All sensor nodes in this package publish ROS 2 diagnostics to the /diagnostics topic via the
diagnostic_updater package. The diagnostic status tracks
these conditions:
| Status | Condition |
|---|---|
WARN |
Node started but no observation has arrived yet within the startup timeout window |
ERROR |
Sensor exception (e.g., serial port unavailable) - node keeps retrying every retry_on_error_delay seconds |
ERROR |
Sensor was working but no observation has been received for longer than 3x the expected period |
WARN |
Observation rate is below 50% of the configured expected rate |
OK |
Observations are arriving at the expected rate |
ROS 2 parameters controlling diagnostic thresholds and retry behavior (settable at launch or via ros2 param set):
| Parameter | Default | Description |
|---|---|---|
diag_startup_timeout |
30.0 s |
How long to wait for the first observation before reporting an error |
diag_expected_rate |
1.0 Hz |
Expected observation rate; used for stale and rate-warning checks |
retry_on_error_delay |
5.0 s |
How long to wait before retrying after a sensor exception |
The diagnostic status also reports the measured observation rate, the observation count, and the hardware ID (node name).
Viewing diagnostics
Echo the raw topic directly:
ros2 topic echo /diagnostics
For a human-friendly live view, use rqt_runtime_monitor or the ros2 run equivalent:
ros2 run rqt_runtime_monitor rqt_runtime_monitor
Running a diagnostic aggregator
The diagnostic_aggregator collects and categorizes /diagnostics messages into
/diagnostics_agg. This is required by tools such as robot_monitor. To launch one quickly for
testing, install the package and create a minimal analyzers config:
sudo apt install ros-${ROS_DISTRO}-diagnostic-aggregator
Create a file analyzers.yaml:
analyzers:
ros__parameters:
path: Sensors
sensors:
type: diagnostic_aggregator/GenericAnalyzer
path: Sensors
contains:
- 'Sensor status'
Then run the aggregator with that config:
```bash
ros2 run diagnostic_aggregator aggregator_node –ros-args
–params-file analyzers.yaml
File truncated at 100 lines see the full file
CONTRIBUTING
Repository Summary
| Checkout URI | https://github.com/mrpt-ros-pkg/mrpt_sensors.git |
| VCS Type | git |
| VCS Version | ros2 |
| Last Updated | 2026-05-20 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Packages
| Name | Version |
|---|---|
| mrpt_generic_sensor | 0.3.0 |
| mrpt_sensor_bumblebee_stereo | 0.3.0 |
| mrpt_sensor_gnss_nmea | 0.3.0 |
| mrpt_sensor_gnss_novatel | 0.3.0 |
| mrpt_sensor_imu_taobotics | 0.3.0 |
| mrpt_sensorlib | 0.3.0 |
| mrpt_sensors | 0.3.0 |
| novatel_oem6_msgs | 0.3.0 |
README
| Distro | Build dev | Release |
|---|---|---|
| ROS 2 Humble (u22.04) | ||
| ROS 2 Jazzy (u24.04) | ||
| ROS 2 Kilted (u24.04) | ||
| ROS 2 Rolling (u24.04) |
| EOL Distro | Last release |
|---|---|
| ROS 2 Iron (u22.04) |
mrpt_sensors
ROS nodes for various robotics sensors via mrpt-hwdrivers.
All packages follow REP-2003 regarding ROS 2 topic QoS.
Table of Contents
- Diagnostics support
mrpt_sensor_bumblebee_stereomrpt_sensor_gnss_nmeamrpt_sensor_gnss_novatelmrpt_sensor_imu_taoboticsmrpt_sensor_velodyne- novatel_oem6_msgs
- Individual package build status
Diagnostics support
All sensor nodes in this package publish ROS 2 diagnostics to the /diagnostics topic via the
diagnostic_updater package. The diagnostic status tracks
these conditions:
| Status | Condition |
|---|---|
WARN |
Node started but no observation has arrived yet within the startup timeout window |
ERROR |
Sensor exception (e.g., serial port unavailable) - node keeps retrying every retry_on_error_delay seconds |
ERROR |
Sensor was working but no observation has been received for longer than 3x the expected period |
WARN |
Observation rate is below 50% of the configured expected rate |
OK |
Observations are arriving at the expected rate |
ROS 2 parameters controlling diagnostic thresholds and retry behavior (settable at launch or via ros2 param set):
| Parameter | Default | Description |
|---|---|---|
diag_startup_timeout |
30.0 s |
How long to wait for the first observation before reporting an error |
diag_expected_rate |
1.0 Hz |
Expected observation rate; used for stale and rate-warning checks |
retry_on_error_delay |
5.0 s |
How long to wait before retrying after a sensor exception |
The diagnostic status also reports the measured observation rate, the observation count, and the hardware ID (node name).
Viewing diagnostics
Echo the raw topic directly:
ros2 topic echo /diagnostics
For a human-friendly live view, use rqt_runtime_monitor or the ros2 run equivalent:
ros2 run rqt_runtime_monitor rqt_runtime_monitor
Running a diagnostic aggregator
The diagnostic_aggregator collects and categorizes /diagnostics messages into
/diagnostics_agg. This is required by tools such as robot_monitor. To launch one quickly for
testing, install the package and create a minimal analyzers config:
sudo apt install ros-${ROS_DISTRO}-diagnostic-aggregator
Create a file analyzers.yaml:
analyzers:
ros__parameters:
path: Sensors
sensors:
type: diagnostic_aggregator/GenericAnalyzer
path: Sensors
contains:
- 'Sensor status'
Then run the aggregator with that config:
```bash
ros2 run diagnostic_aggregator aggregator_node –ros-args
–params-file analyzers.yaml
File truncated at 100 lines see the full file
CONTRIBUTING
Repository Summary
| Checkout URI | https://github.com/mrpt-ros-pkg/mrpt_sensors.git |
| VCS Type | git |
| VCS Version | ros2 |
| Last Updated | 2026-05-20 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Packages
| Name | Version |
|---|---|
| mrpt_generic_sensor | 0.3.0 |
| mrpt_sensor_bumblebee_stereo | 0.3.0 |
| mrpt_sensor_gnss_nmea | 0.3.0 |
| mrpt_sensor_gnss_novatel | 0.3.0 |
| mrpt_sensor_imu_taobotics | 0.3.0 |
| mrpt_sensorlib | 0.3.0 |
| mrpt_sensors | 0.3.0 |
| novatel_oem6_msgs | 0.3.0 |
README
| Distro | Build dev | Release |
|---|---|---|
| ROS 2 Humble (u22.04) | ||
| ROS 2 Jazzy (u24.04) | ||
| ROS 2 Kilted (u24.04) | ||
| ROS 2 Rolling (u24.04) |
| EOL Distro | Last release |
|---|---|
| ROS 2 Iron (u22.04) |
mrpt_sensors
ROS nodes for various robotics sensors via mrpt-hwdrivers.
All packages follow REP-2003 regarding ROS 2 topic QoS.
Table of Contents
- Diagnostics support
mrpt_sensor_bumblebee_stereomrpt_sensor_gnss_nmeamrpt_sensor_gnss_novatelmrpt_sensor_imu_taoboticsmrpt_sensor_velodyne- novatel_oem6_msgs
- Individual package build status
Diagnostics support
All sensor nodes in this package publish ROS 2 diagnostics to the /diagnostics topic via the
diagnostic_updater package. The diagnostic status tracks
these conditions:
| Status | Condition |
|---|---|
WARN |
Node started but no observation has arrived yet within the startup timeout window |
ERROR |
Sensor exception (e.g., serial port unavailable) - node keeps retrying every retry_on_error_delay seconds |
ERROR |
Sensor was working but no observation has been received for longer than 3x the expected period |
WARN |
Observation rate is below 50% of the configured expected rate |
OK |
Observations are arriving at the expected rate |
ROS 2 parameters controlling diagnostic thresholds and retry behavior (settable at launch or via ros2 param set):
| Parameter | Default | Description |
|---|---|---|
diag_startup_timeout |
30.0 s |
How long to wait for the first observation before reporting an error |
diag_expected_rate |
1.0 Hz |
Expected observation rate; used for stale and rate-warning checks |
retry_on_error_delay |
5.0 s |
How long to wait before retrying after a sensor exception |
The diagnostic status also reports the measured observation rate, the observation count, and the hardware ID (node name).
Viewing diagnostics
Echo the raw topic directly:
ros2 topic echo /diagnostics
For a human-friendly live view, use rqt_runtime_monitor or the ros2 run equivalent:
ros2 run rqt_runtime_monitor rqt_runtime_monitor
Running a diagnostic aggregator
The diagnostic_aggregator collects and categorizes /diagnostics messages into
/diagnostics_agg. This is required by tools such as robot_monitor. To launch one quickly for
testing, install the package and create a minimal analyzers config:
sudo apt install ros-${ROS_DISTRO}-diagnostic-aggregator
Create a file analyzers.yaml:
analyzers:
ros__parameters:
path: Sensors
sensors:
type: diagnostic_aggregator/GenericAnalyzer
path: Sensors
contains:
- 'Sensor status'
Then run the aggregator with that config:
```bash
ros2 run diagnostic_aggregator aggregator_node –ros-args
–params-file analyzers.yaml
File truncated at 100 lines see the full file
CONTRIBUTING
Repository Summary
| Checkout URI | https://github.com/mrpt-ros-pkg/mrpt_sensors.git |
| VCS Type | git |
| VCS Version | ros2 |
| Last Updated | 2026-05-20 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Packages
| Name | Version |
|---|---|
| mrpt_generic_sensor | 0.3.0 |
| mrpt_sensor_bumblebee_stereo | 0.3.0 |
| mrpt_sensor_gnss_nmea | 0.3.0 |
| mrpt_sensor_gnss_novatel | 0.3.0 |
| mrpt_sensor_imu_taobotics | 0.3.0 |
| mrpt_sensorlib | 0.3.0 |
| mrpt_sensors | 0.3.0 |
| novatel_oem6_msgs | 0.3.0 |
README
| Distro | Build dev | Release |
|---|---|---|
| ROS 2 Humble (u22.04) | ||
| ROS 2 Jazzy (u24.04) | ||
| ROS 2 Kilted (u24.04) | ||
| ROS 2 Rolling (u24.04) |
| EOL Distro | Last release |
|---|---|
| ROS 2 Iron (u22.04) |
mrpt_sensors
ROS nodes for various robotics sensors via mrpt-hwdrivers.
All packages follow REP-2003 regarding ROS 2 topic QoS.
Table of Contents
- Diagnostics support
mrpt_sensor_bumblebee_stereomrpt_sensor_gnss_nmeamrpt_sensor_gnss_novatelmrpt_sensor_imu_taoboticsmrpt_sensor_velodyne- novatel_oem6_msgs
- Individual package build status
Diagnostics support
All sensor nodes in this package publish ROS 2 diagnostics to the /diagnostics topic via the
diagnostic_updater package. The diagnostic status tracks
these conditions:
| Status | Condition |
|---|---|
WARN |
Node started but no observation has arrived yet within the startup timeout window |
ERROR |
Sensor exception (e.g., serial port unavailable) - node keeps retrying every retry_on_error_delay seconds |
ERROR |
Sensor was working but no observation has been received for longer than 3x the expected period |
WARN |
Observation rate is below 50% of the configured expected rate |
OK |
Observations are arriving at the expected rate |
ROS 2 parameters controlling diagnostic thresholds and retry behavior (settable at launch or via ros2 param set):
| Parameter | Default | Description |
|---|---|---|
diag_startup_timeout |
30.0 s |
How long to wait for the first observation before reporting an error |
diag_expected_rate |
1.0 Hz |
Expected observation rate; used for stale and rate-warning checks |
retry_on_error_delay |
5.0 s |
How long to wait before retrying after a sensor exception |
The diagnostic status also reports the measured observation rate, the observation count, and the hardware ID (node name).
Viewing diagnostics
Echo the raw topic directly:
ros2 topic echo /diagnostics
For a human-friendly live view, use rqt_runtime_monitor or the ros2 run equivalent:
ros2 run rqt_runtime_monitor rqt_runtime_monitor
Running a diagnostic aggregator
The diagnostic_aggregator collects and categorizes /diagnostics messages into
/diagnostics_agg. This is required by tools such as robot_monitor. To launch one quickly for
testing, install the package and create a minimal analyzers config:
sudo apt install ros-${ROS_DISTRO}-diagnostic-aggregator
Create a file analyzers.yaml:
analyzers:
ros__parameters:
path: Sensors
sensors:
type: diagnostic_aggregator/GenericAnalyzer
path: Sensors
contains:
- 'Sensor status'
Then run the aggregator with that config:
```bash
ros2 run diagnostic_aggregator aggregator_node –ros-args
–params-file analyzers.yaml
File truncated at 100 lines see the full file
CONTRIBUTING
Repository Summary
| Checkout URI | https://github.com/mrpt-ros-pkg/mrpt_sensors.git |
| VCS Type | git |
| VCS Version | ros2 |
| Last Updated | 2026-05-20 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Packages
| Name | Version |
|---|---|
| mrpt_generic_sensor | 0.3.0 |
| mrpt_sensor_bumblebee_stereo | 0.3.0 |
| mrpt_sensor_gnss_nmea | 0.3.0 |
| mrpt_sensor_gnss_novatel | 0.3.0 |
| mrpt_sensor_imu_taobotics | 0.3.0 |
| mrpt_sensorlib | 0.3.0 |
| mrpt_sensors | 0.3.0 |
| novatel_oem6_msgs | 0.3.0 |
README
| Distro | Build dev | Release |
|---|---|---|
| ROS 2 Humble (u22.04) | ||
| ROS 2 Jazzy (u24.04) | ||
| ROS 2 Kilted (u24.04) | ||
| ROS 2 Rolling (u24.04) |
| EOL Distro | Last release |
|---|---|
| ROS 2 Iron (u22.04) |
mrpt_sensors
ROS nodes for various robotics sensors via mrpt-hwdrivers.
All packages follow REP-2003 regarding ROS 2 topic QoS.
Table of Contents
- Diagnostics support
mrpt_sensor_bumblebee_stereomrpt_sensor_gnss_nmeamrpt_sensor_gnss_novatelmrpt_sensor_imu_taoboticsmrpt_sensor_velodyne- novatel_oem6_msgs
- Individual package build status
Diagnostics support
All sensor nodes in this package publish ROS 2 diagnostics to the /diagnostics topic via the
diagnostic_updater package. The diagnostic status tracks
these conditions:
| Status | Condition |
|---|---|
WARN |
Node started but no observation has arrived yet within the startup timeout window |
ERROR |
Sensor exception (e.g., serial port unavailable) - node keeps retrying every retry_on_error_delay seconds |
ERROR |
Sensor was working but no observation has been received for longer than 3x the expected period |
WARN |
Observation rate is below 50% of the configured expected rate |
OK |
Observations are arriving at the expected rate |
ROS 2 parameters controlling diagnostic thresholds and retry behavior (settable at launch or via ros2 param set):
| Parameter | Default | Description |
|---|---|---|
diag_startup_timeout |
30.0 s |
How long to wait for the first observation before reporting an error |
diag_expected_rate |
1.0 Hz |
Expected observation rate; used for stale and rate-warning checks |
retry_on_error_delay |
5.0 s |
How long to wait before retrying after a sensor exception |
The diagnostic status also reports the measured observation rate, the observation count, and the hardware ID (node name).
Viewing diagnostics
Echo the raw topic directly:
ros2 topic echo /diagnostics
For a human-friendly live view, use rqt_runtime_monitor or the ros2 run equivalent:
ros2 run rqt_runtime_monitor rqt_runtime_monitor
Running a diagnostic aggregator
The diagnostic_aggregator collects and categorizes /diagnostics messages into
/diagnostics_agg. This is required by tools such as robot_monitor. To launch one quickly for
testing, install the package and create a minimal analyzers config:
sudo apt install ros-${ROS_DISTRO}-diagnostic-aggregator
Create a file analyzers.yaml:
analyzers:
ros__parameters:
path: Sensors
sensors:
type: diagnostic_aggregator/GenericAnalyzer
path: Sensors
contains:
- 'Sensor status'
Then run the aggregator with that config:
```bash
ros2 run diagnostic_aggregator aggregator_node –ros-args
–params-file analyzers.yaml
File truncated at 100 lines see the full file
CONTRIBUTING
Repository Summary
| Checkout URI | https://github.com/mrpt-ros-pkg/mrpt_sensors.git |
| VCS Type | git |
| VCS Version | ros2 |
| Last Updated | 2026-05-20 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Packages
| Name | Version |
|---|---|
| mrpt_generic_sensor | 0.3.0 |
| mrpt_sensor_bumblebee_stereo | 0.3.0 |
| mrpt_sensor_gnss_nmea | 0.3.0 |
| mrpt_sensor_gnss_novatel | 0.3.0 |
| mrpt_sensor_imu_taobotics | 0.3.0 |
| mrpt_sensorlib | 0.3.0 |
| mrpt_sensors | 0.3.0 |
| novatel_oem6_msgs | 0.3.0 |
README
| Distro | Build dev | Release |
|---|---|---|
| ROS 2 Humble (u22.04) | ||
| ROS 2 Jazzy (u24.04) | ||
| ROS 2 Kilted (u24.04) | ||
| ROS 2 Rolling (u24.04) |
| EOL Distro | Last release |
|---|---|
| ROS 2 Iron (u22.04) |
mrpt_sensors
ROS nodes for various robotics sensors via mrpt-hwdrivers.
All packages follow REP-2003 regarding ROS 2 topic QoS.
Table of Contents
- Diagnostics support
mrpt_sensor_bumblebee_stereomrpt_sensor_gnss_nmeamrpt_sensor_gnss_novatelmrpt_sensor_imu_taoboticsmrpt_sensor_velodyne- novatel_oem6_msgs
- Individual package build status
Diagnostics support
All sensor nodes in this package publish ROS 2 diagnostics to the /diagnostics topic via the
diagnostic_updater package. The diagnostic status tracks
these conditions:
| Status | Condition |
|---|---|
WARN |
Node started but no observation has arrived yet within the startup timeout window |
ERROR |
Sensor exception (e.g., serial port unavailable) - node keeps retrying every retry_on_error_delay seconds |
ERROR |
Sensor was working but no observation has been received for longer than 3x the expected period |
WARN |
Observation rate is below 50% of the configured expected rate |
OK |
Observations are arriving at the expected rate |
ROS 2 parameters controlling diagnostic thresholds and retry behavior (settable at launch or via ros2 param set):
| Parameter | Default | Description |
|---|---|---|
diag_startup_timeout |
30.0 s |
How long to wait for the first observation before reporting an error |
diag_expected_rate |
1.0 Hz |
Expected observation rate; used for stale and rate-warning checks |
retry_on_error_delay |
5.0 s |
How long to wait before retrying after a sensor exception |
The diagnostic status also reports the measured observation rate, the observation count, and the hardware ID (node name).
Viewing diagnostics
Echo the raw topic directly:
ros2 topic echo /diagnostics
For a human-friendly live view, use rqt_runtime_monitor or the ros2 run equivalent:
ros2 run rqt_runtime_monitor rqt_runtime_monitor
Running a diagnostic aggregator
The diagnostic_aggregator collects and categorizes /diagnostics messages into
/diagnostics_agg. This is required by tools such as robot_monitor. To launch one quickly for
testing, install the package and create a minimal analyzers config:
sudo apt install ros-${ROS_DISTRO}-diagnostic-aggregator
Create a file analyzers.yaml:
analyzers:
ros__parameters:
path: Sensors
sensors:
type: diagnostic_aggregator/GenericAnalyzer
path: Sensors
contains:
- 'Sensor status'
Then run the aggregator with that config:
```bash
ros2 run diagnostic_aggregator aggregator_node –ros-args
–params-file analyzers.yaml
File truncated at 100 lines see the full file
CONTRIBUTING
Repository Summary
| Checkout URI | https://github.com/mrpt-ros-pkg/mrpt_sensors.git |
| VCS Type | git |
| VCS Version | ros2 |
| Last Updated | 2026-05-20 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Packages
| Name | Version |
|---|---|
| mrpt_generic_sensor | 0.3.0 |
| mrpt_sensor_bumblebee_stereo | 0.3.0 |
| mrpt_sensor_gnss_nmea | 0.3.0 |
| mrpt_sensor_gnss_novatel | 0.3.0 |
| mrpt_sensor_imu_taobotics | 0.3.0 |
| mrpt_sensorlib | 0.3.0 |
| mrpt_sensors | 0.3.0 |
| novatel_oem6_msgs | 0.3.0 |
README
| Distro | Build dev | Release |
|---|---|---|
| ROS 2 Humble (u22.04) | ||
| ROS 2 Jazzy (u24.04) | ||
| ROS 2 Kilted (u24.04) | ||
| ROS 2 Rolling (u24.04) |
| EOL Distro | Last release |
|---|---|
| ROS 2 Iron (u22.04) |
mrpt_sensors
ROS nodes for various robotics sensors via mrpt-hwdrivers.
All packages follow REP-2003 regarding ROS 2 topic QoS.
Table of Contents
- Diagnostics support
mrpt_sensor_bumblebee_stereomrpt_sensor_gnss_nmeamrpt_sensor_gnss_novatelmrpt_sensor_imu_taoboticsmrpt_sensor_velodyne- novatel_oem6_msgs
- Individual package build status
Diagnostics support
All sensor nodes in this package publish ROS 2 diagnostics to the /diagnostics topic via the
diagnostic_updater package. The diagnostic status tracks
these conditions:
| Status | Condition |
|---|---|
WARN |
Node started but no observation has arrived yet within the startup timeout window |
ERROR |
Sensor exception (e.g., serial port unavailable) - node keeps retrying every retry_on_error_delay seconds |
ERROR |
Sensor was working but no observation has been received for longer than 3x the expected period |
WARN |
Observation rate is below 50% of the configured expected rate |
OK |
Observations are arriving at the expected rate |
ROS 2 parameters controlling diagnostic thresholds and retry behavior (settable at launch or via ros2 param set):
| Parameter | Default | Description |
|---|---|---|
diag_startup_timeout |
30.0 s |
How long to wait for the first observation before reporting an error |
diag_expected_rate |
1.0 Hz |
Expected observation rate; used for stale and rate-warning checks |
retry_on_error_delay |
5.0 s |
How long to wait before retrying after a sensor exception |
The diagnostic status also reports the measured observation rate, the observation count, and the hardware ID (node name).
Viewing diagnostics
Echo the raw topic directly:
ros2 topic echo /diagnostics
For a human-friendly live view, use rqt_runtime_monitor or the ros2 run equivalent:
ros2 run rqt_runtime_monitor rqt_runtime_monitor
Running a diagnostic aggregator
The diagnostic_aggregator collects and categorizes /diagnostics messages into
/diagnostics_agg. This is required by tools such as robot_monitor. To launch one quickly for
testing, install the package and create a minimal analyzers config:
sudo apt install ros-${ROS_DISTRO}-diagnostic-aggregator
Create a file analyzers.yaml:
analyzers:
ros__parameters:
path: Sensors
sensors:
type: diagnostic_aggregator/GenericAnalyzer
path: Sensors
contains:
- 'Sensor status'
Then run the aggregator with that config:
```bash
ros2 run diagnostic_aggregator aggregator_node –ros-args
–params-file analyzers.yaml
File truncated at 100 lines see the full file
CONTRIBUTING
Repository Summary
| Checkout URI | https://github.com/mrpt-ros-pkg/mrpt_sensors.git |
| VCS Type | git |
| VCS Version | ros2 |
| Last Updated | 2026-05-20 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Packages
| Name | Version |
|---|---|
| mrpt_generic_sensor | 0.3.0 |
| mrpt_sensor_bumblebee_stereo | 0.3.0 |
| mrpt_sensor_gnss_nmea | 0.3.0 |
| mrpt_sensor_gnss_novatel | 0.3.0 |
| mrpt_sensor_imu_taobotics | 0.3.0 |
| mrpt_sensorlib | 0.3.0 |
| mrpt_sensors | 0.3.0 |
| novatel_oem6_msgs | 0.3.0 |
README
| Distro | Build dev | Release |
|---|---|---|
| ROS 2 Humble (u22.04) | ||
| ROS 2 Jazzy (u24.04) | ||
| ROS 2 Kilted (u24.04) | ||
| ROS 2 Rolling (u24.04) |
| EOL Distro | Last release |
|---|---|
| ROS 2 Iron (u22.04) |
mrpt_sensors
ROS nodes for various robotics sensors via mrpt-hwdrivers.
All packages follow REP-2003 regarding ROS 2 topic QoS.
Table of Contents
- Diagnostics support
mrpt_sensor_bumblebee_stereomrpt_sensor_gnss_nmeamrpt_sensor_gnss_novatelmrpt_sensor_imu_taoboticsmrpt_sensor_velodyne- novatel_oem6_msgs
- Individual package build status
Diagnostics support
All sensor nodes in this package publish ROS 2 diagnostics to the /diagnostics topic via the
diagnostic_updater package. The diagnostic status tracks
these conditions:
| Status | Condition |
|---|---|
WARN |
Node started but no observation has arrived yet within the startup timeout window |
ERROR |
Sensor exception (e.g., serial port unavailable) - node keeps retrying every retry_on_error_delay seconds |
ERROR |
Sensor was working but no observation has been received for longer than 3x the expected period |
WARN |
Observation rate is below 50% of the configured expected rate |
OK |
Observations are arriving at the expected rate |
ROS 2 parameters controlling diagnostic thresholds and retry behavior (settable at launch or via ros2 param set):
| Parameter | Default | Description |
|---|---|---|
diag_startup_timeout |
30.0 s |
How long to wait for the first observation before reporting an error |
diag_expected_rate |
1.0 Hz |
Expected observation rate; used for stale and rate-warning checks |
retry_on_error_delay |
5.0 s |
How long to wait before retrying after a sensor exception |
The diagnostic status also reports the measured observation rate, the observation count, and the hardware ID (node name).
Viewing diagnostics
Echo the raw topic directly:
ros2 topic echo /diagnostics
For a human-friendly live view, use rqt_runtime_monitor or the ros2 run equivalent:
ros2 run rqt_runtime_monitor rqt_runtime_monitor
Running a diagnostic aggregator
The diagnostic_aggregator collects and categorizes /diagnostics messages into
/diagnostics_agg. This is required by tools such as robot_monitor. To launch one quickly for
testing, install the package and create a minimal analyzers config:
sudo apt install ros-${ROS_DISTRO}-diagnostic-aggregator
Create a file analyzers.yaml:
analyzers:
ros__parameters:
path: Sensors
sensors:
type: diagnostic_aggregator/GenericAnalyzer
path: Sensors
contains:
- 'Sensor status'
Then run the aggregator with that config:
```bash
ros2 run diagnostic_aggregator aggregator_node –ros-args
–params-file analyzers.yaml
File truncated at 100 lines see the full file
CONTRIBUTING
|
mrpt_sensors repositorymrpt_generic_sensor mrpt_sensorlib mrpt_sensors mrpt_sensors_examples |
ROS Distro
|
Repository Summary
| Checkout URI | https://github.com/mrpt-ros-pkg/mrpt_sensors.git |
| VCS Type | git |
| VCS Version | ros1 |
| Last Updated | 2024-03-19 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Packages
| Name | Version |
|---|---|
| mrpt_generic_sensor | 0.0.4 |
| mrpt_sensorlib | 0.0.4 |
| mrpt_sensors | 0.0.4 |
| mrpt_sensors_examples | 0.0.4 |
README
| Distro | Build dev | Build release | Stable sync |
|---|---|---|---|
| ROS1 Noetic (u20.04) |
| EOL Distro | Last release |
|---|---|
| ROS1 Melodic (u18.04) |
mrpt_sensors
ROS nodes for various robotics sensors via mrpt-hwdrivers
This branch ros1 will see no further development.
CONTRIBUTING
|
mrpt_sensors repositorymrpt_generic_sensor mrpt_sensorlib mrpt_sensors mrpt_sensors_examples |
ROS Distro
|
Repository Summary
| Checkout URI | https://github.com/mrpt-ros-pkg/mrpt_sensors.git |
| VCS Type | git |
| VCS Version | ros1 |
| Last Updated | 2024-03-19 |
| Dev Status | DEVELOPED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Packages
| Name | Version |
|---|---|
| mrpt_generic_sensor | 0.0.4 |
| mrpt_sensorlib | 0.0.4 |
| mrpt_sensors | 0.0.4 |
| mrpt_sensors_examples | 0.0.4 |
README
| Distro | Build dev | Build release | Stable sync |
|---|---|---|---|
| ROS1 Noetic (u20.04) |
| EOL Distro | Last release |
|---|---|
| ROS1 Melodic (u18.04) |
mrpt_sensors
ROS nodes for various robotics sensors via mrpt-hwdrivers
This branch ros1 will see no further development.