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

erdi_lrf_driver repository

erdi_lrf_driver

ROS Distro
rolling

Repository Summary

Description
Checkout URI https://github.com/ErdiTech/erdi_lrf_driver.git
VCS Type git
VCS Version main
Last Updated 2026-11-17
Dev Status DEVELOPED
Released UNRELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Packages

Name Version
erdi_lrf_driver 0.3.0

README

erdi_lrf_driver

CI

ROS 2 driver for ERDI UART laser rangefinder modules (905 nm, hundreds of metres to kilometre-class range). It publishes the distance sensor reading as sensor_msgs/msg/Range, so the module can feed nav2, robot_localization, PX4/ArduPilot companion bridges, or your own altitude/obstacle logic.

Both published ERDI serial protocol families are supported (family A 55 AA command/response, family B free-running 5C frames). The serial codec is vendored in the package (erdi_lrf_driver/_erdi_lrf, MIT, mirrored byte-for-byte from the erdi-lrf 0.1.8 Python driver by tools/sync_codec.py; 24 models), so the only runtime dependency is pyserial (python3-serial).

Install

cd ~/ros2_ws/src
git clone https://github.com/ErdiTech/erdi_lrf_driver.git
cd ~/ros2_ws
rosdep install --from-paths src --ignore-src -y
colcon build --packages-select erdi_lrf_driver
source install/setup.bash

Run

ros2 launch erdi_lrf_driver erdi_lrf.launch.py port:=/dev/ttyUSB0 model:=LRF3000A1 rate:=10.0
# or
ros2 run erdi_lrf_driver erdi_lrf_node --ros-args -p port:=/dev/ttyUSB0 -p model:=LRF1500H
ros2 topic echo /range

Add yourself to the serial group first: sudo usermod -aG dialout $USER.

Parameters

Name Default Description
port /dev/ttyUSB0 Serial device.
model LRF3000A1 Module model, e.g. LR1200E2, LRF3000A1, SPD1200N2, LRF100H, LRF1500H, LRF22VB. See the model table at erdilrf.com/models.
baud 0 0 = the model’s documented default. SPD1200D03 has no safe default: set it explicitly.
frame_id erdi_lrf_link TF frame of the message header.
rate 10.0 Polling rate in Hz.
timeout 0.5 Serial read timeout in seconds.
min_range / max_range 0.0 Metres. 0.0 takes the value from the model table.
field_of_view 0.0 Full beam divergence in radians. 0.0 = use the per-model value from the table below (fallback 0.002 for models without a published divergence).
continuous false Stream continuously instead of one request per tick.
acknowledge_protocol_hold false Needed for continuous on LRF1200A1 / LRF3000A1, whose manuals leave the continuous-reply function byte unresolved.
topic range Output topic name.

Beam divergence (field_of_view)

Parsed from each model’s published specification table at erdilrf.com/models (checked 2026-11-06); the datasheet upper bound is used (< 6 mrad becomes 0.006).

Model field_of_view (rad)
LR1000E2 0.009
LR1000E4 0.009
LR1200E2 0.004
LR1200E4 0.004
LR1500E2 0.006
LR1500E4 0.006
LR2000E2 0.006
LR2000E4 0.006
LRF3000A1 0.01
SPD1200N0 0.0045
SPD1200N2 0.0045
SPD1200N4 0.0045

No divergence row is published for LRF1200A1, SPD1200D03, LRF50H, LRF100H, LRF200H, LRF300H, LRF600H, LRF1500H, LRF22VB, LRF50VB, LRF10VB, SPD1200S2G; these keep the 0.002 default, so set field_of_view yourself for them.

Topics

range (sensor_msgs/msg/Range, sensor-data QoS): radiation_type is INFRARED. Out-of-range readings follow REP-117: -inf below the minimum range, +inf beyond the maximum or when the module reports no target, nan for an invalid measurement.

Tests

colcon test --packages-select erdi_lrf_driver && colcon test-result --verbose

Includes ament_copyright, ament_flake8, ament_pep257 and a node test that runs against a fake serial port, so no hardware is needed.

See also

File truncated at 100 lines see the full file

CONTRIBUTING

Contributing

Thanks for helping improve erdi_lrf_driver.

Any contribution that you make to this repository will be under the MIT license, as dictated by that license.

  • Open an issue first for larger changes. Then fork, create a branch, and open a pull request against main.
  • Keep changes focused, add or update tests, and update CHANGELOG.rst for user-visible changes.
  • Run the tests before pushing (ROS 2 Jazzy or Humble):
cd ~/ros2_ws
colcon build --packages-select erdi_lrf_driver
colcon test --packages-select erdi_lrf_driver --event-handlers console_direct+
colcon test-result --verbose

CI runs the same commands in ros:jazzy and ros:humble containers.

# Contributing Thanks for helping improve `erdi_lrf_driver`. Any contribution that you make to this repository will be under the MIT license, as dictated by that [license](https://opensource.org/licenses/MIT). * Open an issue first for larger changes. Then fork, create a branch, and open a pull request against `main`. * Keep changes focused, add or update tests, and update `CHANGELOG.rst` for user-visible changes. * Run the tests before pushing (ROS 2 Jazzy or Humble): ```bash cd ~/ros2_ws colcon build --packages-select erdi_lrf_driver colcon test --packages-select erdi_lrf_driver --event-handlers console_direct+ colcon test-result --verbose ``` CI runs the same commands in `ros:jazzy` and `ros:humble` containers.
No version for distro jazzy showing rolling. Known supported distros are highlighted in the buttons above.
Repo symbol

erdi_lrf_driver repository

erdi_lrf_driver

ROS Distro
rolling

Repository Summary

Description
Checkout URI https://github.com/ErdiTech/erdi_lrf_driver.git
VCS Type git
VCS Version main
Last Updated 2026-11-17
Dev Status DEVELOPED
Released UNRELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Packages

Name Version
erdi_lrf_driver 0.3.0

README

erdi_lrf_driver

CI

ROS 2 driver for ERDI UART laser rangefinder modules (905 nm, hundreds of metres to kilometre-class range). It publishes the distance sensor reading as sensor_msgs/msg/Range, so the module can feed nav2, robot_localization, PX4/ArduPilot companion bridges, or your own altitude/obstacle logic.

Both published ERDI serial protocol families are supported (family A 55 AA command/response, family B free-running 5C frames). The serial codec is vendored in the package (erdi_lrf_driver/_erdi_lrf, MIT, mirrored byte-for-byte from the erdi-lrf 0.1.8 Python driver by tools/sync_codec.py; 24 models), so the only runtime dependency is pyserial (python3-serial).

Install

cd ~/ros2_ws/src
git clone https://github.com/ErdiTech/erdi_lrf_driver.git
cd ~/ros2_ws
rosdep install --from-paths src --ignore-src -y
colcon build --packages-select erdi_lrf_driver
source install/setup.bash

Run

ros2 launch erdi_lrf_driver erdi_lrf.launch.py port:=/dev/ttyUSB0 model:=LRF3000A1 rate:=10.0
# or
ros2 run erdi_lrf_driver erdi_lrf_node --ros-args -p port:=/dev/ttyUSB0 -p model:=LRF1500H
ros2 topic echo /range

Add yourself to the serial group first: sudo usermod -aG dialout $USER.

Parameters

Name Default Description
port /dev/ttyUSB0 Serial device.
model LRF3000A1 Module model, e.g. LR1200E2, LRF3000A1, SPD1200N2, LRF100H, LRF1500H, LRF22VB. See the model table at erdilrf.com/models.
baud 0 0 = the model’s documented default. SPD1200D03 has no safe default: set it explicitly.
frame_id erdi_lrf_link TF frame of the message header.
rate 10.0 Polling rate in Hz.
timeout 0.5 Serial read timeout in seconds.
min_range / max_range 0.0 Metres. 0.0 takes the value from the model table.
field_of_view 0.0 Full beam divergence in radians. 0.0 = use the per-model value from the table below (fallback 0.002 for models without a published divergence).
continuous false Stream continuously instead of one request per tick.
acknowledge_protocol_hold false Needed for continuous on LRF1200A1 / LRF3000A1, whose manuals leave the continuous-reply function byte unresolved.
topic range Output topic name.

Beam divergence (field_of_view)

Parsed from each model’s published specification table at erdilrf.com/models (checked 2026-11-06); the datasheet upper bound is used (< 6 mrad becomes 0.006).

Model field_of_view (rad)
LR1000E2 0.009
LR1000E4 0.009
LR1200E2 0.004
LR1200E4 0.004
LR1500E2 0.006
LR1500E4 0.006
LR2000E2 0.006
LR2000E4 0.006
LRF3000A1 0.01
SPD1200N0 0.0045
SPD1200N2 0.0045
SPD1200N4 0.0045

No divergence row is published for LRF1200A1, SPD1200D03, LRF50H, LRF100H, LRF200H, LRF300H, LRF600H, LRF1500H, LRF22VB, LRF50VB, LRF10VB, SPD1200S2G; these keep the 0.002 default, so set field_of_view yourself for them.

Topics

range (sensor_msgs/msg/Range, sensor-data QoS): radiation_type is INFRARED. Out-of-range readings follow REP-117: -inf below the minimum range, +inf beyond the maximum or when the module reports no target, nan for an invalid measurement.

Tests

colcon test --packages-select erdi_lrf_driver && colcon test-result --verbose

Includes ament_copyright, ament_flake8, ament_pep257 and a node test that runs against a fake serial port, so no hardware is needed.

See also

File truncated at 100 lines see the full file

CONTRIBUTING

Contributing

Thanks for helping improve erdi_lrf_driver.

Any contribution that you make to this repository will be under the MIT license, as dictated by that license.

  • Open an issue first for larger changes. Then fork, create a branch, and open a pull request against main.
  • Keep changes focused, add or update tests, and update CHANGELOG.rst for user-visible changes.
  • Run the tests before pushing (ROS 2 Jazzy or Humble):
cd ~/ros2_ws
colcon build --packages-select erdi_lrf_driver
colcon test --packages-select erdi_lrf_driver --event-handlers console_direct+
colcon test-result --verbose

CI runs the same commands in ros:jazzy and ros:humble containers.

# Contributing Thanks for helping improve `erdi_lrf_driver`. Any contribution that you make to this repository will be under the MIT license, as dictated by that [license](https://opensource.org/licenses/MIT). * Open an issue first for larger changes. Then fork, create a branch, and open a pull request against `main`. * Keep changes focused, add or update tests, and update `CHANGELOG.rst` for user-visible changes. * Run the tests before pushing (ROS 2 Jazzy or Humble): ```bash cd ~/ros2_ws colcon build --packages-select erdi_lrf_driver colcon test --packages-select erdi_lrf_driver --event-handlers console_direct+ colcon test-result --verbose ``` CI runs the same commands in `ros:jazzy` and `ros:humble` containers.
No version for distro kilted showing rolling. Known supported distros are highlighted in the buttons above.
Repo symbol

erdi_lrf_driver repository

erdi_lrf_driver

ROS Distro
rolling

Repository Summary

Description
Checkout URI https://github.com/ErdiTech/erdi_lrf_driver.git
VCS Type git
VCS Version main
Last Updated 2026-11-17
Dev Status DEVELOPED
Released UNRELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Packages

Name Version
erdi_lrf_driver 0.3.0

README

erdi_lrf_driver

CI

ROS 2 driver for ERDI UART laser rangefinder modules (905 nm, hundreds of metres to kilometre-class range). It publishes the distance sensor reading as sensor_msgs/msg/Range, so the module can feed nav2, robot_localization, PX4/ArduPilot companion bridges, or your own altitude/obstacle logic.

Both published ERDI serial protocol families are supported (family A 55 AA command/response, family B free-running 5C frames). The serial codec is vendored in the package (erdi_lrf_driver/_erdi_lrf, MIT, mirrored byte-for-byte from the erdi-lrf 0.1.8 Python driver by tools/sync_codec.py; 24 models), so the only runtime dependency is pyserial (python3-serial).

Install

cd ~/ros2_ws/src
git clone https://github.com/ErdiTech/erdi_lrf_driver.git
cd ~/ros2_ws
rosdep install --from-paths src --ignore-src -y
colcon build --packages-select erdi_lrf_driver
source install/setup.bash

Run

ros2 launch erdi_lrf_driver erdi_lrf.launch.py port:=/dev/ttyUSB0 model:=LRF3000A1 rate:=10.0
# or
ros2 run erdi_lrf_driver erdi_lrf_node --ros-args -p port:=/dev/ttyUSB0 -p model:=LRF1500H
ros2 topic echo /range

Add yourself to the serial group first: sudo usermod -aG dialout $USER.

Parameters

Name Default Description
port /dev/ttyUSB0 Serial device.
model LRF3000A1 Module model, e.g. LR1200E2, LRF3000A1, SPD1200N2, LRF100H, LRF1500H, LRF22VB. See the model table at erdilrf.com/models.
baud 0 0 = the model’s documented default. SPD1200D03 has no safe default: set it explicitly.
frame_id erdi_lrf_link TF frame of the message header.
rate 10.0 Polling rate in Hz.
timeout 0.5 Serial read timeout in seconds.
min_range / max_range 0.0 Metres. 0.0 takes the value from the model table.
field_of_view 0.0 Full beam divergence in radians. 0.0 = use the per-model value from the table below (fallback 0.002 for models without a published divergence).
continuous false Stream continuously instead of one request per tick.
acknowledge_protocol_hold false Needed for continuous on LRF1200A1 / LRF3000A1, whose manuals leave the continuous-reply function byte unresolved.
topic range Output topic name.

Beam divergence (field_of_view)

Parsed from each model’s published specification table at erdilrf.com/models (checked 2026-11-06); the datasheet upper bound is used (< 6 mrad becomes 0.006).

Model field_of_view (rad)
LR1000E2 0.009
LR1000E4 0.009
LR1200E2 0.004
LR1200E4 0.004
LR1500E2 0.006
LR1500E4 0.006
LR2000E2 0.006
LR2000E4 0.006
LRF3000A1 0.01
SPD1200N0 0.0045
SPD1200N2 0.0045
SPD1200N4 0.0045

No divergence row is published for LRF1200A1, SPD1200D03, LRF50H, LRF100H, LRF200H, LRF300H, LRF600H, LRF1500H, LRF22VB, LRF50VB, LRF10VB, SPD1200S2G; these keep the 0.002 default, so set field_of_view yourself for them.

Topics

range (sensor_msgs/msg/Range, sensor-data QoS): radiation_type is INFRARED. Out-of-range readings follow REP-117: -inf below the minimum range, +inf beyond the maximum or when the module reports no target, nan for an invalid measurement.

Tests

colcon test --packages-select erdi_lrf_driver && colcon test-result --verbose

Includes ament_copyright, ament_flake8, ament_pep257 and a node test that runs against a fake serial port, so no hardware is needed.

See also

File truncated at 100 lines see the full file

CONTRIBUTING

Contributing

Thanks for helping improve erdi_lrf_driver.

Any contribution that you make to this repository will be under the MIT license, as dictated by that license.

  • Open an issue first for larger changes. Then fork, create a branch, and open a pull request against main.
  • Keep changes focused, add or update tests, and update CHANGELOG.rst for user-visible changes.
  • Run the tests before pushing (ROS 2 Jazzy or Humble):
cd ~/ros2_ws
colcon build --packages-select erdi_lrf_driver
colcon test --packages-select erdi_lrf_driver --event-handlers console_direct+
colcon test-result --verbose

CI runs the same commands in ros:jazzy and ros:humble containers.

# Contributing Thanks for helping improve `erdi_lrf_driver`. Any contribution that you make to this repository will be under the MIT license, as dictated by that [license](https://opensource.org/licenses/MIT). * Open an issue first for larger changes. Then fork, create a branch, and open a pull request against `main`. * Keep changes focused, add or update tests, and update `CHANGELOG.rst` for user-visible changes. * Run the tests before pushing (ROS 2 Jazzy or Humble): ```bash cd ~/ros2_ws colcon build --packages-select erdi_lrf_driver colcon test --packages-select erdi_lrf_driver --event-handlers console_direct+ colcon test-result --verbose ``` CI runs the same commands in `ros:jazzy` and `ros:humble` containers.
No version for distro lyrical showing rolling. Known supported distros are highlighted in the buttons above.
Repo symbol

erdi_lrf_driver repository

erdi_lrf_driver

ROS Distro
rolling

Repository Summary

Description
Checkout URI https://github.com/ErdiTech/erdi_lrf_driver.git
VCS Type git
VCS Version main
Last Updated 2026-11-17
Dev Status DEVELOPED
Released UNRELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Packages

Name Version
erdi_lrf_driver 0.3.0

README

erdi_lrf_driver

CI

ROS 2 driver for ERDI UART laser rangefinder modules (905 nm, hundreds of metres to kilometre-class range). It publishes the distance sensor reading as sensor_msgs/msg/Range, so the module can feed nav2, robot_localization, PX4/ArduPilot companion bridges, or your own altitude/obstacle logic.

Both published ERDI serial protocol families are supported (family A 55 AA command/response, family B free-running 5C frames). The serial codec is vendored in the package (erdi_lrf_driver/_erdi_lrf, MIT, mirrored byte-for-byte from the erdi-lrf 0.1.8 Python driver by tools/sync_codec.py; 24 models), so the only runtime dependency is pyserial (python3-serial).

Install

cd ~/ros2_ws/src
git clone https://github.com/ErdiTech/erdi_lrf_driver.git
cd ~/ros2_ws
rosdep install --from-paths src --ignore-src -y
colcon build --packages-select erdi_lrf_driver
source install/setup.bash

Run

ros2 launch erdi_lrf_driver erdi_lrf.launch.py port:=/dev/ttyUSB0 model:=LRF3000A1 rate:=10.0
# or
ros2 run erdi_lrf_driver erdi_lrf_node --ros-args -p port:=/dev/ttyUSB0 -p model:=LRF1500H
ros2 topic echo /range

Add yourself to the serial group first: sudo usermod -aG dialout $USER.

Parameters

Name Default Description
port /dev/ttyUSB0 Serial device.
model LRF3000A1 Module model, e.g. LR1200E2, LRF3000A1, SPD1200N2, LRF100H, LRF1500H, LRF22VB. See the model table at erdilrf.com/models.
baud 0 0 = the model’s documented default. SPD1200D03 has no safe default: set it explicitly.
frame_id erdi_lrf_link TF frame of the message header.
rate 10.0 Polling rate in Hz.
timeout 0.5 Serial read timeout in seconds.
min_range / max_range 0.0 Metres. 0.0 takes the value from the model table.
field_of_view 0.0 Full beam divergence in radians. 0.0 = use the per-model value from the table below (fallback 0.002 for models without a published divergence).
continuous false Stream continuously instead of one request per tick.
acknowledge_protocol_hold false Needed for continuous on LRF1200A1 / LRF3000A1, whose manuals leave the continuous-reply function byte unresolved.
topic range Output topic name.

Beam divergence (field_of_view)

Parsed from each model’s published specification table at erdilrf.com/models (checked 2026-11-06); the datasheet upper bound is used (< 6 mrad becomes 0.006).

Model field_of_view (rad)
LR1000E2 0.009
LR1000E4 0.009
LR1200E2 0.004
LR1200E4 0.004
LR1500E2 0.006
LR1500E4 0.006
LR2000E2 0.006
LR2000E4 0.006
LRF3000A1 0.01
SPD1200N0 0.0045
SPD1200N2 0.0045
SPD1200N4 0.0045

No divergence row is published for LRF1200A1, SPD1200D03, LRF50H, LRF100H, LRF200H, LRF300H, LRF600H, LRF1500H, LRF22VB, LRF50VB, LRF10VB, SPD1200S2G; these keep the 0.002 default, so set field_of_view yourself for them.

Topics

range (sensor_msgs/msg/Range, sensor-data QoS): radiation_type is INFRARED. Out-of-range readings follow REP-117: -inf below the minimum range, +inf beyond the maximum or when the module reports no target, nan for an invalid measurement.

Tests

colcon test --packages-select erdi_lrf_driver && colcon test-result --verbose

Includes ament_copyright, ament_flake8, ament_pep257 and a node test that runs against a fake serial port, so no hardware is needed.

See also

File truncated at 100 lines see the full file

CONTRIBUTING

Contributing

Thanks for helping improve erdi_lrf_driver.

Any contribution that you make to this repository will be under the MIT license, as dictated by that license.

  • Open an issue first for larger changes. Then fork, create a branch, and open a pull request against main.
  • Keep changes focused, add or update tests, and update CHANGELOG.rst for user-visible changes.
  • Run the tests before pushing (ROS 2 Jazzy or Humble):
cd ~/ros2_ws
colcon build --packages-select erdi_lrf_driver
colcon test --packages-select erdi_lrf_driver --event-handlers console_direct+
colcon test-result --verbose

CI runs the same commands in ros:jazzy and ros:humble containers.

# Contributing Thanks for helping improve `erdi_lrf_driver`. Any contribution that you make to this repository will be under the MIT license, as dictated by that [license](https://opensource.org/licenses/MIT). * Open an issue first for larger changes. Then fork, create a branch, and open a pull request against `main`. * Keep changes focused, add or update tests, and update `CHANGELOG.rst` for user-visible changes. * Run the tests before pushing (ROS 2 Jazzy or Humble): ```bash cd ~/ros2_ws colcon build --packages-select erdi_lrf_driver colcon test --packages-select erdi_lrf_driver --event-handlers console_direct+ colcon test-result --verbose ``` CI runs the same commands in `ros:jazzy` and `ros:humble` containers.
Repo symbol

erdi_lrf_driver repository

erdi_lrf_driver

ROS Distro
rolling

Repository Summary

Description
Checkout URI https://github.com/ErdiTech/erdi_lrf_driver.git
VCS Type git
VCS Version main
Last Updated 2026-11-17
Dev Status DEVELOPED
Released UNRELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Packages

Name Version
erdi_lrf_driver 0.3.0

README

erdi_lrf_driver

CI

ROS 2 driver for ERDI UART laser rangefinder modules (905 nm, hundreds of metres to kilometre-class range). It publishes the distance sensor reading as sensor_msgs/msg/Range, so the module can feed nav2, robot_localization, PX4/ArduPilot companion bridges, or your own altitude/obstacle logic.

Both published ERDI serial protocol families are supported (family A 55 AA command/response, family B free-running 5C frames). The serial codec is vendored in the package (erdi_lrf_driver/_erdi_lrf, MIT, mirrored byte-for-byte from the erdi-lrf 0.1.8 Python driver by tools/sync_codec.py; 24 models), so the only runtime dependency is pyserial (python3-serial).

Install

cd ~/ros2_ws/src
git clone https://github.com/ErdiTech/erdi_lrf_driver.git
cd ~/ros2_ws
rosdep install --from-paths src --ignore-src -y
colcon build --packages-select erdi_lrf_driver
source install/setup.bash

Run

ros2 launch erdi_lrf_driver erdi_lrf.launch.py port:=/dev/ttyUSB0 model:=LRF3000A1 rate:=10.0
# or
ros2 run erdi_lrf_driver erdi_lrf_node --ros-args -p port:=/dev/ttyUSB0 -p model:=LRF1500H
ros2 topic echo /range

Add yourself to the serial group first: sudo usermod -aG dialout $USER.

Parameters

Name Default Description
port /dev/ttyUSB0 Serial device.
model LRF3000A1 Module model, e.g. LR1200E2, LRF3000A1, SPD1200N2, LRF100H, LRF1500H, LRF22VB. See the model table at erdilrf.com/models.
baud 0 0 = the model’s documented default. SPD1200D03 has no safe default: set it explicitly.
frame_id erdi_lrf_link TF frame of the message header.
rate 10.0 Polling rate in Hz.
timeout 0.5 Serial read timeout in seconds.
min_range / max_range 0.0 Metres. 0.0 takes the value from the model table.
field_of_view 0.0 Full beam divergence in radians. 0.0 = use the per-model value from the table below (fallback 0.002 for models without a published divergence).
continuous false Stream continuously instead of one request per tick.
acknowledge_protocol_hold false Needed for continuous on LRF1200A1 / LRF3000A1, whose manuals leave the continuous-reply function byte unresolved.
topic range Output topic name.

Beam divergence (field_of_view)

Parsed from each model’s published specification table at erdilrf.com/models (checked 2026-11-06); the datasheet upper bound is used (< 6 mrad becomes 0.006).

Model field_of_view (rad)
LR1000E2 0.009
LR1000E4 0.009
LR1200E2 0.004
LR1200E4 0.004
LR1500E2 0.006
LR1500E4 0.006
LR2000E2 0.006
LR2000E4 0.006
LRF3000A1 0.01
SPD1200N0 0.0045
SPD1200N2 0.0045
SPD1200N4 0.0045

No divergence row is published for LRF1200A1, SPD1200D03, LRF50H, LRF100H, LRF200H, LRF300H, LRF600H, LRF1500H, LRF22VB, LRF50VB, LRF10VB, SPD1200S2G; these keep the 0.002 default, so set field_of_view yourself for them.

Topics

range (sensor_msgs/msg/Range, sensor-data QoS): radiation_type is INFRARED. Out-of-range readings follow REP-117: -inf below the minimum range, +inf beyond the maximum or when the module reports no target, nan for an invalid measurement.

Tests

colcon test --packages-select erdi_lrf_driver && colcon test-result --verbose

Includes ament_copyright, ament_flake8, ament_pep257 and a node test that runs against a fake serial port, so no hardware is needed.

See also

File truncated at 100 lines see the full file

CONTRIBUTING

Contributing

Thanks for helping improve erdi_lrf_driver.

Any contribution that you make to this repository will be under the MIT license, as dictated by that license.

  • Open an issue first for larger changes. Then fork, create a branch, and open a pull request against main.
  • Keep changes focused, add or update tests, and update CHANGELOG.rst for user-visible changes.
  • Run the tests before pushing (ROS 2 Jazzy or Humble):
cd ~/ros2_ws
colcon build --packages-select erdi_lrf_driver
colcon test --packages-select erdi_lrf_driver --event-handlers console_direct+
colcon test-result --verbose

CI runs the same commands in ros:jazzy and ros:humble containers.

# Contributing Thanks for helping improve `erdi_lrf_driver`. Any contribution that you make to this repository will be under the MIT license, as dictated by that [license](https://opensource.org/licenses/MIT). * Open an issue first for larger changes. Then fork, create a branch, and open a pull request against `main`. * Keep changes focused, add or update tests, and update `CHANGELOG.rst` for user-visible changes. * Run the tests before pushing (ROS 2 Jazzy or Humble): ```bash cd ~/ros2_ws colcon build --packages-select erdi_lrf_driver colcon test --packages-select erdi_lrf_driver --event-handlers console_direct+ colcon test-result --verbose ``` CI runs the same commands in `ros:jazzy` and `ros:humble` containers.
No version for distro github showing rolling. Known supported distros are highlighted in the buttons above.
Repo symbol

erdi_lrf_driver repository

erdi_lrf_driver

ROS Distro
rolling

Repository Summary

Description
Checkout URI https://github.com/ErdiTech/erdi_lrf_driver.git
VCS Type git
VCS Version main
Last Updated 2026-11-17
Dev Status DEVELOPED
Released UNRELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Packages

Name Version
erdi_lrf_driver 0.3.0

README

erdi_lrf_driver

CI

ROS 2 driver for ERDI UART laser rangefinder modules (905 nm, hundreds of metres to kilometre-class range). It publishes the distance sensor reading as sensor_msgs/msg/Range, so the module can feed nav2, robot_localization, PX4/ArduPilot companion bridges, or your own altitude/obstacle logic.

Both published ERDI serial protocol families are supported (family A 55 AA command/response, family B free-running 5C frames). The serial codec is vendored in the package (erdi_lrf_driver/_erdi_lrf, MIT, mirrored byte-for-byte from the erdi-lrf 0.1.8 Python driver by tools/sync_codec.py; 24 models), so the only runtime dependency is pyserial (python3-serial).

Install

cd ~/ros2_ws/src
git clone https://github.com/ErdiTech/erdi_lrf_driver.git
cd ~/ros2_ws
rosdep install --from-paths src --ignore-src -y
colcon build --packages-select erdi_lrf_driver
source install/setup.bash

Run

ros2 launch erdi_lrf_driver erdi_lrf.launch.py port:=/dev/ttyUSB0 model:=LRF3000A1 rate:=10.0
# or
ros2 run erdi_lrf_driver erdi_lrf_node --ros-args -p port:=/dev/ttyUSB0 -p model:=LRF1500H
ros2 topic echo /range

Add yourself to the serial group first: sudo usermod -aG dialout $USER.

Parameters

Name Default Description
port /dev/ttyUSB0 Serial device.
model LRF3000A1 Module model, e.g. LR1200E2, LRF3000A1, SPD1200N2, LRF100H, LRF1500H, LRF22VB. See the model table at erdilrf.com/models.
baud 0 0 = the model’s documented default. SPD1200D03 has no safe default: set it explicitly.
frame_id erdi_lrf_link TF frame of the message header.
rate 10.0 Polling rate in Hz.
timeout 0.5 Serial read timeout in seconds.
min_range / max_range 0.0 Metres. 0.0 takes the value from the model table.
field_of_view 0.0 Full beam divergence in radians. 0.0 = use the per-model value from the table below (fallback 0.002 for models without a published divergence).
continuous false Stream continuously instead of one request per tick.
acknowledge_protocol_hold false Needed for continuous on LRF1200A1 / LRF3000A1, whose manuals leave the continuous-reply function byte unresolved.
topic range Output topic name.

Beam divergence (field_of_view)

Parsed from each model’s published specification table at erdilrf.com/models (checked 2026-11-06); the datasheet upper bound is used (< 6 mrad becomes 0.006).

Model field_of_view (rad)
LR1000E2 0.009
LR1000E4 0.009
LR1200E2 0.004
LR1200E4 0.004
LR1500E2 0.006
LR1500E4 0.006
LR2000E2 0.006
LR2000E4 0.006
LRF3000A1 0.01
SPD1200N0 0.0045
SPD1200N2 0.0045
SPD1200N4 0.0045

No divergence row is published for LRF1200A1, SPD1200D03, LRF50H, LRF100H, LRF200H, LRF300H, LRF600H, LRF1500H, LRF22VB, LRF50VB, LRF10VB, SPD1200S2G; these keep the 0.002 default, so set field_of_view yourself for them.

Topics

range (sensor_msgs/msg/Range, sensor-data QoS): radiation_type is INFRARED. Out-of-range readings follow REP-117: -inf below the minimum range, +inf beyond the maximum or when the module reports no target, nan for an invalid measurement.

Tests

colcon test --packages-select erdi_lrf_driver && colcon test-result --verbose

Includes ament_copyright, ament_flake8, ament_pep257 and a node test that runs against a fake serial port, so no hardware is needed.

See also

File truncated at 100 lines see the full file

CONTRIBUTING

Contributing

Thanks for helping improve erdi_lrf_driver.

Any contribution that you make to this repository will be under the MIT license, as dictated by that license.

  • Open an issue first for larger changes. Then fork, create a branch, and open a pull request against main.
  • Keep changes focused, add or update tests, and update CHANGELOG.rst for user-visible changes.
  • Run the tests before pushing (ROS 2 Jazzy or Humble):
cd ~/ros2_ws
colcon build --packages-select erdi_lrf_driver
colcon test --packages-select erdi_lrf_driver --event-handlers console_direct+
colcon test-result --verbose

CI runs the same commands in ros:jazzy and ros:humble containers.

# Contributing Thanks for helping improve `erdi_lrf_driver`. Any contribution that you make to this repository will be under the MIT license, as dictated by that [license](https://opensource.org/licenses/MIT). * Open an issue first for larger changes. Then fork, create a branch, and open a pull request against `main`. * Keep changes focused, add or update tests, and update `CHANGELOG.rst` for user-visible changes. * Run the tests before pushing (ROS 2 Jazzy or Humble): ```bash cd ~/ros2_ws colcon build --packages-select erdi_lrf_driver colcon test --packages-select erdi_lrf_driver --event-handlers console_direct+ colcon test-result --verbose ``` CI runs the same commands in `ros:jazzy` and `ros:humble` containers.
No version for distro galactic showing rolling. Known supported distros are highlighted in the buttons above.
Repo symbol

erdi_lrf_driver repository

erdi_lrf_driver

ROS Distro
rolling

Repository Summary

Description
Checkout URI https://github.com/ErdiTech/erdi_lrf_driver.git
VCS Type git
VCS Version main
Last Updated 2026-11-17
Dev Status DEVELOPED
Released UNRELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Packages

Name Version
erdi_lrf_driver 0.3.0

README

erdi_lrf_driver

CI

ROS 2 driver for ERDI UART laser rangefinder modules (905 nm, hundreds of metres to kilometre-class range). It publishes the distance sensor reading as sensor_msgs/msg/Range, so the module can feed nav2, robot_localization, PX4/ArduPilot companion bridges, or your own altitude/obstacle logic.

Both published ERDI serial protocol families are supported (family A 55 AA command/response, family B free-running 5C frames). The serial codec is vendored in the package (erdi_lrf_driver/_erdi_lrf, MIT, mirrored byte-for-byte from the erdi-lrf 0.1.8 Python driver by tools/sync_codec.py; 24 models), so the only runtime dependency is pyserial (python3-serial).

Install

cd ~/ros2_ws/src
git clone https://github.com/ErdiTech/erdi_lrf_driver.git
cd ~/ros2_ws
rosdep install --from-paths src --ignore-src -y
colcon build --packages-select erdi_lrf_driver
source install/setup.bash

Run

ros2 launch erdi_lrf_driver erdi_lrf.launch.py port:=/dev/ttyUSB0 model:=LRF3000A1 rate:=10.0
# or
ros2 run erdi_lrf_driver erdi_lrf_node --ros-args -p port:=/dev/ttyUSB0 -p model:=LRF1500H
ros2 topic echo /range

Add yourself to the serial group first: sudo usermod -aG dialout $USER.

Parameters

Name Default Description
port /dev/ttyUSB0 Serial device.
model LRF3000A1 Module model, e.g. LR1200E2, LRF3000A1, SPD1200N2, LRF100H, LRF1500H, LRF22VB. See the model table at erdilrf.com/models.
baud 0 0 = the model’s documented default. SPD1200D03 has no safe default: set it explicitly.
frame_id erdi_lrf_link TF frame of the message header.
rate 10.0 Polling rate in Hz.
timeout 0.5 Serial read timeout in seconds.
min_range / max_range 0.0 Metres. 0.0 takes the value from the model table.
field_of_view 0.0 Full beam divergence in radians. 0.0 = use the per-model value from the table below (fallback 0.002 for models without a published divergence).
continuous false Stream continuously instead of one request per tick.
acknowledge_protocol_hold false Needed for continuous on LRF1200A1 / LRF3000A1, whose manuals leave the continuous-reply function byte unresolved.
topic range Output topic name.

Beam divergence (field_of_view)

Parsed from each model’s published specification table at erdilrf.com/models (checked 2026-11-06); the datasheet upper bound is used (< 6 mrad becomes 0.006).

Model field_of_view (rad)
LR1000E2 0.009
LR1000E4 0.009
LR1200E2 0.004
LR1200E4 0.004
LR1500E2 0.006
LR1500E4 0.006
LR2000E2 0.006
LR2000E4 0.006
LRF3000A1 0.01
SPD1200N0 0.0045
SPD1200N2 0.0045
SPD1200N4 0.0045

No divergence row is published for LRF1200A1, SPD1200D03, LRF50H, LRF100H, LRF200H, LRF300H, LRF600H, LRF1500H, LRF22VB, LRF50VB, LRF10VB, SPD1200S2G; these keep the 0.002 default, so set field_of_view yourself for them.

Topics

range (sensor_msgs/msg/Range, sensor-data QoS): radiation_type is INFRARED. Out-of-range readings follow REP-117: -inf below the minimum range, +inf beyond the maximum or when the module reports no target, nan for an invalid measurement.

Tests

colcon test --packages-select erdi_lrf_driver && colcon test-result --verbose

Includes ament_copyright, ament_flake8, ament_pep257 and a node test that runs against a fake serial port, so no hardware is needed.

See also

File truncated at 100 lines see the full file

CONTRIBUTING

Contributing

Thanks for helping improve erdi_lrf_driver.

Any contribution that you make to this repository will be under the MIT license, as dictated by that license.

  • Open an issue first for larger changes. Then fork, create a branch, and open a pull request against main.
  • Keep changes focused, add or update tests, and update CHANGELOG.rst for user-visible changes.
  • Run the tests before pushing (ROS 2 Jazzy or Humble):
cd ~/ros2_ws
colcon build --packages-select erdi_lrf_driver
colcon test --packages-select erdi_lrf_driver --event-handlers console_direct+
colcon test-result --verbose

CI runs the same commands in ros:jazzy and ros:humble containers.

# Contributing Thanks for helping improve `erdi_lrf_driver`. Any contribution that you make to this repository will be under the MIT license, as dictated by that [license](https://opensource.org/licenses/MIT). * Open an issue first for larger changes. Then fork, create a branch, and open a pull request against `main`. * Keep changes focused, add or update tests, and update `CHANGELOG.rst` for user-visible changes. * Run the tests before pushing (ROS 2 Jazzy or Humble): ```bash cd ~/ros2_ws colcon build --packages-select erdi_lrf_driver colcon test --packages-select erdi_lrf_driver --event-handlers console_direct+ colcon test-result --verbose ``` CI runs the same commands in `ros:jazzy` and `ros:humble` containers.
No version for distro iron showing rolling. Known supported distros are highlighted in the buttons above.
Repo symbol

erdi_lrf_driver repository

erdi_lrf_driver

ROS Distro
rolling

Repository Summary

Description
Checkout URI https://github.com/ErdiTech/erdi_lrf_driver.git
VCS Type git
VCS Version main
Last Updated 2026-11-17
Dev Status DEVELOPED
Released UNRELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Packages

Name Version
erdi_lrf_driver 0.3.0

README

erdi_lrf_driver

CI

ROS 2 driver for ERDI UART laser rangefinder modules (905 nm, hundreds of metres to kilometre-class range). It publishes the distance sensor reading as sensor_msgs/msg/Range, so the module can feed nav2, robot_localization, PX4/ArduPilot companion bridges, or your own altitude/obstacle logic.

Both published ERDI serial protocol families are supported (family A 55 AA command/response, family B free-running 5C frames). The serial codec is vendored in the package (erdi_lrf_driver/_erdi_lrf, MIT, mirrored byte-for-byte from the erdi-lrf 0.1.8 Python driver by tools/sync_codec.py; 24 models), so the only runtime dependency is pyserial (python3-serial).

Install

cd ~/ros2_ws/src
git clone https://github.com/ErdiTech/erdi_lrf_driver.git
cd ~/ros2_ws
rosdep install --from-paths src --ignore-src -y
colcon build --packages-select erdi_lrf_driver
source install/setup.bash

Run

ros2 launch erdi_lrf_driver erdi_lrf.launch.py port:=/dev/ttyUSB0 model:=LRF3000A1 rate:=10.0
# or
ros2 run erdi_lrf_driver erdi_lrf_node --ros-args -p port:=/dev/ttyUSB0 -p model:=LRF1500H
ros2 topic echo /range

Add yourself to the serial group first: sudo usermod -aG dialout $USER.

Parameters

Name Default Description
port /dev/ttyUSB0 Serial device.
model LRF3000A1 Module model, e.g. LR1200E2, LRF3000A1, SPD1200N2, LRF100H, LRF1500H, LRF22VB. See the model table at erdilrf.com/models.
baud 0 0 = the model’s documented default. SPD1200D03 has no safe default: set it explicitly.
frame_id erdi_lrf_link TF frame of the message header.
rate 10.0 Polling rate in Hz.
timeout 0.5 Serial read timeout in seconds.
min_range / max_range 0.0 Metres. 0.0 takes the value from the model table.
field_of_view 0.0 Full beam divergence in radians. 0.0 = use the per-model value from the table below (fallback 0.002 for models without a published divergence).
continuous false Stream continuously instead of one request per tick.
acknowledge_protocol_hold false Needed for continuous on LRF1200A1 / LRF3000A1, whose manuals leave the continuous-reply function byte unresolved.
topic range Output topic name.

Beam divergence (field_of_view)

Parsed from each model’s published specification table at erdilrf.com/models (checked 2026-11-06); the datasheet upper bound is used (< 6 mrad becomes 0.006).

Model field_of_view (rad)
LR1000E2 0.009
LR1000E4 0.009
LR1200E2 0.004
LR1200E4 0.004
LR1500E2 0.006
LR1500E4 0.006
LR2000E2 0.006
LR2000E4 0.006
LRF3000A1 0.01
SPD1200N0 0.0045
SPD1200N2 0.0045
SPD1200N4 0.0045

No divergence row is published for LRF1200A1, SPD1200D03, LRF50H, LRF100H, LRF200H, LRF300H, LRF600H, LRF1500H, LRF22VB, LRF50VB, LRF10VB, SPD1200S2G; these keep the 0.002 default, so set field_of_view yourself for them.

Topics

range (sensor_msgs/msg/Range, sensor-data QoS): radiation_type is INFRARED. Out-of-range readings follow REP-117: -inf below the minimum range, +inf beyond the maximum or when the module reports no target, nan for an invalid measurement.

Tests

colcon test --packages-select erdi_lrf_driver && colcon test-result --verbose

Includes ament_copyright, ament_flake8, ament_pep257 and a node test that runs against a fake serial port, so no hardware is needed.

See also

File truncated at 100 lines see the full file

CONTRIBUTING

Contributing

Thanks for helping improve erdi_lrf_driver.

Any contribution that you make to this repository will be under the MIT license, as dictated by that license.

  • Open an issue first for larger changes. Then fork, create a branch, and open a pull request against main.
  • Keep changes focused, add or update tests, and update CHANGELOG.rst for user-visible changes.
  • Run the tests before pushing (ROS 2 Jazzy or Humble):
cd ~/ros2_ws
colcon build --packages-select erdi_lrf_driver
colcon test --packages-select erdi_lrf_driver --event-handlers console_direct+
colcon test-result --verbose

CI runs the same commands in ros:jazzy and ros:humble containers.

# Contributing Thanks for helping improve `erdi_lrf_driver`. Any contribution that you make to this repository will be under the MIT license, as dictated by that [license](https://opensource.org/licenses/MIT). * Open an issue first for larger changes. Then fork, create a branch, and open a pull request against `main`. * Keep changes focused, add or update tests, and update `CHANGELOG.rst` for user-visible changes. * Run the tests before pushing (ROS 2 Jazzy or Humble): ```bash cd ~/ros2_ws colcon build --packages-select erdi_lrf_driver colcon test --packages-select erdi_lrf_driver --event-handlers console_direct+ colcon test-result --verbose ``` CI runs the same commands in `ros:jazzy` and `ros:humble` containers.
No version for distro melodic showing rolling. Known supported distros are highlighted in the buttons above.
Repo symbol

erdi_lrf_driver repository

erdi_lrf_driver

ROS Distro
rolling

Repository Summary

Description
Checkout URI https://github.com/ErdiTech/erdi_lrf_driver.git
VCS Type git
VCS Version main
Last Updated 2026-11-17
Dev Status DEVELOPED
Released UNRELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Packages

Name Version
erdi_lrf_driver 0.3.0

README

erdi_lrf_driver

CI

ROS 2 driver for ERDI UART laser rangefinder modules (905 nm, hundreds of metres to kilometre-class range). It publishes the distance sensor reading as sensor_msgs/msg/Range, so the module can feed nav2, robot_localization, PX4/ArduPilot companion bridges, or your own altitude/obstacle logic.

Both published ERDI serial protocol families are supported (family A 55 AA command/response, family B free-running 5C frames). The serial codec is vendored in the package (erdi_lrf_driver/_erdi_lrf, MIT, mirrored byte-for-byte from the erdi-lrf 0.1.8 Python driver by tools/sync_codec.py; 24 models), so the only runtime dependency is pyserial (python3-serial).

Install

cd ~/ros2_ws/src
git clone https://github.com/ErdiTech/erdi_lrf_driver.git
cd ~/ros2_ws
rosdep install --from-paths src --ignore-src -y
colcon build --packages-select erdi_lrf_driver
source install/setup.bash

Run

ros2 launch erdi_lrf_driver erdi_lrf.launch.py port:=/dev/ttyUSB0 model:=LRF3000A1 rate:=10.0
# or
ros2 run erdi_lrf_driver erdi_lrf_node --ros-args -p port:=/dev/ttyUSB0 -p model:=LRF1500H
ros2 topic echo /range

Add yourself to the serial group first: sudo usermod -aG dialout $USER.

Parameters

Name Default Description
port /dev/ttyUSB0 Serial device.
model LRF3000A1 Module model, e.g. LR1200E2, LRF3000A1, SPD1200N2, LRF100H, LRF1500H, LRF22VB. See the model table at erdilrf.com/models.
baud 0 0 = the model’s documented default. SPD1200D03 has no safe default: set it explicitly.
frame_id erdi_lrf_link TF frame of the message header.
rate 10.0 Polling rate in Hz.
timeout 0.5 Serial read timeout in seconds.
min_range / max_range 0.0 Metres. 0.0 takes the value from the model table.
field_of_view 0.0 Full beam divergence in radians. 0.0 = use the per-model value from the table below (fallback 0.002 for models without a published divergence).
continuous false Stream continuously instead of one request per tick.
acknowledge_protocol_hold false Needed for continuous on LRF1200A1 / LRF3000A1, whose manuals leave the continuous-reply function byte unresolved.
topic range Output topic name.

Beam divergence (field_of_view)

Parsed from each model’s published specification table at erdilrf.com/models (checked 2026-11-06); the datasheet upper bound is used (< 6 mrad becomes 0.006).

Model field_of_view (rad)
LR1000E2 0.009
LR1000E4 0.009
LR1200E2 0.004
LR1200E4 0.004
LR1500E2 0.006
LR1500E4 0.006
LR2000E2 0.006
LR2000E4 0.006
LRF3000A1 0.01
SPD1200N0 0.0045
SPD1200N2 0.0045
SPD1200N4 0.0045

No divergence row is published for LRF1200A1, SPD1200D03, LRF50H, LRF100H, LRF200H, LRF300H, LRF600H, LRF1500H, LRF22VB, LRF50VB, LRF10VB, SPD1200S2G; these keep the 0.002 default, so set field_of_view yourself for them.

Topics

range (sensor_msgs/msg/Range, sensor-data QoS): radiation_type is INFRARED. Out-of-range readings follow REP-117: -inf below the minimum range, +inf beyond the maximum or when the module reports no target, nan for an invalid measurement.

Tests

colcon test --packages-select erdi_lrf_driver && colcon test-result --verbose

Includes ament_copyright, ament_flake8, ament_pep257 and a node test that runs against a fake serial port, so no hardware is needed.

See also

File truncated at 100 lines see the full file

CONTRIBUTING

Contributing

Thanks for helping improve erdi_lrf_driver.

Any contribution that you make to this repository will be under the MIT license, as dictated by that license.

  • Open an issue first for larger changes. Then fork, create a branch, and open a pull request against main.
  • Keep changes focused, add or update tests, and update CHANGELOG.rst for user-visible changes.
  • Run the tests before pushing (ROS 2 Jazzy or Humble):
cd ~/ros2_ws
colcon build --packages-select erdi_lrf_driver
colcon test --packages-select erdi_lrf_driver --event-handlers console_direct+
colcon test-result --verbose

CI runs the same commands in ros:jazzy and ros:humble containers.

# Contributing Thanks for helping improve `erdi_lrf_driver`. Any contribution that you make to this repository will be under the MIT license, as dictated by that [license](https://opensource.org/licenses/MIT). * Open an issue first for larger changes. Then fork, create a branch, and open a pull request against `main`. * Keep changes focused, add or update tests, and update `CHANGELOG.rst` for user-visible changes. * Run the tests before pushing (ROS 2 Jazzy or Humble): ```bash cd ~/ros2_ws colcon build --packages-select erdi_lrf_driver colcon test --packages-select erdi_lrf_driver --event-handlers console_direct+ colcon test-result --verbose ``` CI runs the same commands in `ros:jazzy` and `ros:humble` containers.
No version for distro noetic showing rolling. Known supported distros are highlighted in the buttons above.
Repo symbol

erdi_lrf_driver repository

erdi_lrf_driver

ROS Distro
rolling

Repository Summary

Description
Checkout URI https://github.com/ErdiTech/erdi_lrf_driver.git
VCS Type git
VCS Version main
Last Updated 2026-11-17
Dev Status DEVELOPED
Released UNRELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Packages

Name Version
erdi_lrf_driver 0.3.0

README

erdi_lrf_driver

CI

ROS 2 driver for ERDI UART laser rangefinder modules (905 nm, hundreds of metres to kilometre-class range). It publishes the distance sensor reading as sensor_msgs/msg/Range, so the module can feed nav2, robot_localization, PX4/ArduPilot companion bridges, or your own altitude/obstacle logic.

Both published ERDI serial protocol families are supported (family A 55 AA command/response, family B free-running 5C frames). The serial codec is vendored in the package (erdi_lrf_driver/_erdi_lrf, MIT, mirrored byte-for-byte from the erdi-lrf 0.1.8 Python driver by tools/sync_codec.py; 24 models), so the only runtime dependency is pyserial (python3-serial).

Install

cd ~/ros2_ws/src
git clone https://github.com/ErdiTech/erdi_lrf_driver.git
cd ~/ros2_ws
rosdep install --from-paths src --ignore-src -y
colcon build --packages-select erdi_lrf_driver
source install/setup.bash

Run

ros2 launch erdi_lrf_driver erdi_lrf.launch.py port:=/dev/ttyUSB0 model:=LRF3000A1 rate:=10.0
# or
ros2 run erdi_lrf_driver erdi_lrf_node --ros-args -p port:=/dev/ttyUSB0 -p model:=LRF1500H
ros2 topic echo /range

Add yourself to the serial group first: sudo usermod -aG dialout $USER.

Parameters

Name Default Description
port /dev/ttyUSB0 Serial device.
model LRF3000A1 Module model, e.g. LR1200E2, LRF3000A1, SPD1200N2, LRF100H, LRF1500H, LRF22VB. See the model table at erdilrf.com/models.
baud 0 0 = the model’s documented default. SPD1200D03 has no safe default: set it explicitly.
frame_id erdi_lrf_link TF frame of the message header.
rate 10.0 Polling rate in Hz.
timeout 0.5 Serial read timeout in seconds.
min_range / max_range 0.0 Metres. 0.0 takes the value from the model table.
field_of_view 0.0 Full beam divergence in radians. 0.0 = use the per-model value from the table below (fallback 0.002 for models without a published divergence).
continuous false Stream continuously instead of one request per tick.
acknowledge_protocol_hold false Needed for continuous on LRF1200A1 / LRF3000A1, whose manuals leave the continuous-reply function byte unresolved.
topic range Output topic name.

Beam divergence (field_of_view)

Parsed from each model’s published specification table at erdilrf.com/models (checked 2026-11-06); the datasheet upper bound is used (< 6 mrad becomes 0.006).

Model field_of_view (rad)
LR1000E2 0.009
LR1000E4 0.009
LR1200E2 0.004
LR1200E4 0.004
LR1500E2 0.006
LR1500E4 0.006
LR2000E2 0.006
LR2000E4 0.006
LRF3000A1 0.01
SPD1200N0 0.0045
SPD1200N2 0.0045
SPD1200N4 0.0045

No divergence row is published for LRF1200A1, SPD1200D03, LRF50H, LRF100H, LRF200H, LRF300H, LRF600H, LRF1500H, LRF22VB, LRF50VB, LRF10VB, SPD1200S2G; these keep the 0.002 default, so set field_of_view yourself for them.

Topics

range (sensor_msgs/msg/Range, sensor-data QoS): radiation_type is INFRARED. Out-of-range readings follow REP-117: -inf below the minimum range, +inf beyond the maximum or when the module reports no target, nan for an invalid measurement.

Tests

colcon test --packages-select erdi_lrf_driver && colcon test-result --verbose

Includes ament_copyright, ament_flake8, ament_pep257 and a node test that runs against a fake serial port, so no hardware is needed.

See also

File truncated at 100 lines see the full file

CONTRIBUTING

Contributing

Thanks for helping improve erdi_lrf_driver.

Any contribution that you make to this repository will be under the MIT license, as dictated by that license.

  • Open an issue first for larger changes. Then fork, create a branch, and open a pull request against main.
  • Keep changes focused, add or update tests, and update CHANGELOG.rst for user-visible changes.
  • Run the tests before pushing (ROS 2 Jazzy or Humble):
cd ~/ros2_ws
colcon build --packages-select erdi_lrf_driver
colcon test --packages-select erdi_lrf_driver --event-handlers console_direct+
colcon test-result --verbose

CI runs the same commands in ros:jazzy and ros:humble containers.

# Contributing Thanks for helping improve `erdi_lrf_driver`. Any contribution that you make to this repository will be under the MIT license, as dictated by that [license](https://opensource.org/licenses/MIT). * Open an issue first for larger changes. Then fork, create a branch, and open a pull request against `main`. * Keep changes focused, add or update tests, and update `CHANGELOG.rst` for user-visible changes. * Run the tests before pushing (ROS 2 Jazzy or Humble): ```bash cd ~/ros2_ws colcon build --packages-select erdi_lrf_driver colcon test --packages-select erdi_lrf_driver --event-handlers console_direct+ colcon test-result --verbose ``` CI runs the same commands in `ros:jazzy` and `ros:humble` containers.