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 (-)

README

CI Build colcon CI clang-format

Distro Build dev Release
ROS 2 Humble (u22.04) Build Status Version
ROS 2 Jazzy (u24.04) Build Status Version
ROS 2 Kilted (u24.04) Build Status Version
ROS 2 Rolling (u24.04) Build Status Version
EOL Distro Last release
ROS 2 Iron (u22.04) Version

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

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

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 (-)

README

CI Build colcon CI clang-format

Distro Build dev Release
ROS 2 Humble (u22.04) Build Status Version
ROS 2 Jazzy (u24.04) Build Status Version
ROS 2 Kilted (u24.04) Build Status Version
ROS 2 Rolling (u24.04) Build Status Version
EOL Distro Last release
ROS 2 Iron (u22.04) Version

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

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

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 (-)

README

CI Build colcon CI clang-format

Distro Build dev Release
ROS 2 Humble (u22.04) Build Status Version
ROS 2 Jazzy (u24.04) Build Status Version
ROS 2 Kilted (u24.04) Build Status Version
ROS 2 Rolling (u24.04) Build Status Version
EOL Distro Last release
ROS 2 Iron (u22.04) Version

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

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

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 (-)

README

CI Build colcon CI clang-format

Distro Build dev Release
ROS 2 Humble (u22.04) Build Status Version
ROS 2 Jazzy (u24.04) Build Status Version
ROS 2 Kilted (u24.04) Build Status Version
ROS 2 Rolling (u24.04) Build Status Version
EOL Distro Last release
ROS 2 Iron (u22.04) Version

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

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

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 (-)

README

CI Build colcon CI clang-format

Distro Build dev Release
ROS 2 Humble (u22.04) Build Status Version
ROS 2 Jazzy (u24.04) Build Status Version
ROS 2 Kilted (u24.04) Build Status Version
ROS 2 Rolling (u24.04) Build Status Version
EOL Distro Last release
ROS 2 Iron (u22.04) Version

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

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

No version for distro ardent showing humble. Known supported distros are highlighted in the buttons above.

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 (-)

README

CI Build colcon CI clang-format

Distro Build dev Release
ROS 2 Humble (u22.04) Build Status Version
ROS 2 Jazzy (u24.04) Build Status Version
ROS 2 Kilted (u24.04) Build Status Version
ROS 2 Rolling (u24.04) Build Status Version
EOL Distro Last release
ROS 2 Iron (u22.04) Version

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

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

No version for distro bouncy showing humble. Known supported distros are highlighted in the buttons above.

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 (-)

README

CI Build colcon CI clang-format

Distro Build dev Release
ROS 2 Humble (u22.04) Build Status Version
ROS 2 Jazzy (u24.04) Build Status Version
ROS 2 Kilted (u24.04) Build Status Version
ROS 2 Rolling (u24.04) Build Status Version
EOL Distro Last release
ROS 2 Iron (u22.04) Version

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

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

No version for distro crystal showing humble. Known supported distros are highlighted in the buttons above.

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 (-)

README

CI Build colcon CI clang-format

Distro Build dev Release
ROS 2 Humble (u22.04) Build Status Version
ROS 2 Jazzy (u24.04) Build Status Version
ROS 2 Kilted (u24.04) Build Status Version
ROS 2 Rolling (u24.04) Build Status Version
EOL Distro Last release
ROS 2 Iron (u22.04) Version

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

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

No version for distro eloquent showing humble. Known supported distros are highlighted in the buttons above.

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 (-)

README

CI Build colcon CI clang-format

Distro Build dev Release
ROS 2 Humble (u22.04) Build Status Version
ROS 2 Jazzy (u24.04) Build Status Version
ROS 2 Kilted (u24.04) Build Status Version
ROS 2 Rolling (u24.04) Build Status Version
EOL Distro Last release
ROS 2 Iron (u22.04) Version

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

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

No version for distro dashing showing humble. Known supported distros are highlighted in the buttons above.

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 (-)

README

CI Build colcon CI clang-format

Distro Build dev Release
ROS 2 Humble (u22.04) Build Status Version
ROS 2 Jazzy (u24.04) Build Status Version
ROS 2 Kilted (u24.04) Build Status Version
ROS 2 Rolling (u24.04) Build Status Version
EOL Distro Last release
ROS 2 Iron (u22.04) Version

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

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

No version for distro galactic showing humble. Known supported distros are highlighted in the buttons above.

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 (-)

README

CI Build colcon CI clang-format

Distro Build dev Release
ROS 2 Humble (u22.04) Build Status Version
ROS 2 Jazzy (u24.04) Build Status Version
ROS 2 Kilted (u24.04) Build Status Version
ROS 2 Rolling (u24.04) Build Status Version
EOL Distro Last release
ROS 2 Iron (u22.04) Version

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

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

No version for distro foxy showing humble. Known supported distros are highlighted in the buttons above.

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 (-)

README

CI Build colcon CI clang-format

Distro Build dev Release
ROS 2 Humble (u22.04) Build Status Version
ROS 2 Jazzy (u24.04) Build Status Version
ROS 2 Kilted (u24.04) Build Status Version
ROS 2 Rolling (u24.04) Build Status Version
EOL Distro Last release
ROS 2 Iron (u22.04) Version

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

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

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 (-)

README

CI Build colcon CI clang-format

Distro Build dev Release
ROS 2 Humble (u22.04) Build Status Version
ROS 2 Jazzy (u24.04) Build Status Version
ROS 2 Kilted (u24.04) Build Status Version
ROS 2 Rolling (u24.04) Build Status Version
EOL Distro Last release
ROS 2 Iron (u22.04) Version

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

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

No version for distro lunar showing humble. Known supported distros are highlighted in the buttons above.

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 (-)

README

CI Build colcon CI clang-format

Distro Build dev Release
ROS 2 Humble (u22.04) Build Status Version
ROS 2 Jazzy (u24.04) Build Status Version
ROS 2 Kilted (u24.04) Build Status Version
ROS 2 Rolling (u24.04) Build Status Version
EOL Distro Last release
ROS 2 Iron (u22.04) Version

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

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

No version for distro jade showing humble. Known supported distros are highlighted in the buttons above.

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 (-)

README

CI Build colcon CI clang-format

Distro Build dev Release
ROS 2 Humble (u22.04) Build Status Version
ROS 2 Jazzy (u24.04) Build Status Version
ROS 2 Kilted (u24.04) Build Status Version
ROS 2 Rolling (u24.04) Build Status Version
EOL Distro Last release
ROS 2 Iron (u22.04) Version

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

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

No version for distro indigo showing humble. Known supported distros are highlighted in the buttons above.

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 (-)

README

CI Build colcon CI clang-format

Distro Build dev Release
ROS 2 Humble (u22.04) Build Status Version
ROS 2 Jazzy (u24.04) Build Status Version
ROS 2 Kilted (u24.04) Build Status Version
ROS 2 Rolling (u24.04) Build Status Version
EOL Distro Last release
ROS 2 Iron (u22.04) Version

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

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

No version for distro hydro showing humble. Known supported distros are highlighted in the buttons above.

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 (-)

README

CI Build colcon CI clang-format

Distro Build dev Release
ROS 2 Humble (u22.04) Build Status Version
ROS 2 Jazzy (u24.04) Build Status Version
ROS 2 Kilted (u24.04) Build Status Version
ROS 2 Rolling (u24.04) Build Status Version
EOL Distro Last release
ROS 2 Iron (u22.04) Version

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

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

No version for distro kinetic showing humble. Known supported distros are highlighted in the buttons above.

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 (-)

README

CI Build colcon CI clang-format

Distro Build dev Release
ROS 2 Humble (u22.04) Build Status Version
ROS 2 Jazzy (u24.04) Build Status Version
ROS 2 Kilted (u24.04) Build Status Version
ROS 2 Rolling (u24.04) Build Status Version
EOL Distro Last release
ROS 2 Iron (u22.04) Version

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

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

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

README

Distro Build dev Build release Stable sync
ROS1 Noetic (u20.04) Build Status Build Status Version
EOL Distro Last release
ROS1 Melodic (u18.04) Version

mrpt_sensors

ROS nodes for various robotics sensors via mrpt-hwdrivers

This branch ros1 will see no further development.

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

README

Distro Build dev Build release Stable sync
ROS1 Noetic (u20.04) Build Status Build Status Version
EOL Distro Last release
ROS1 Melodic (u18.04) Version

mrpt_sensors

ROS nodes for various robotics sensors via mrpt-hwdrivers

This branch ros1 will see no further development.