sick_scan2 repository

Repository Summary

Checkout URI
VCS Type git
VCS Version 0.1.4
Last Updated 2019-10-23


Name Version
sick_scan2 0.1.4



This stack provides a ROS2 driver for the SICK lidar sensors mentioned in the following list.

Table of contents

This stack provides a ROS2 driver for the SICK TiM series of laser scanners mentioned in the following list.

Supported Hardware

This driver should work with all of the following products.

ROS Device Driver for SICK lidar sensors - supported scanner types:

device name part no. description tested?
TiM551 1060445 1 layer max. range: 10 m, ang. resol. 1.00[deg] ✔ [stable]
Scan-Rate: 15 Hz
TiM561 1071419 1 layer max. range: 10 m, ang. resol. 0.33 [deg] ✔ [stable]
Scan-Rate: 15 Hz
TiM571 1079742 1 layer max. range: 25 m, ang. resol. 0.33 [deg] ✔ [stable]
Scan-Rate: 15 Hz
TiM781 1096807 1 layer max. range: 25 m, ang. resol. 0.33 [deg] ✔ [stable]
Scan-Rate: 15 Hz
TiM781S 1096363 1 layer max. range: 25 m, ang. resol. 0.33 [deg] ✔ [stable]
Scan-Rate: 15 Hz

Start Node

See quick start for further hints.

Sopas Mode

This driver supports both COLA-B (binary) and COLA-A (ASCII) communication with the laser scanner. Binary mode is activated by default. Since this mode generates less network traffic. If the communication mode set in the scanner memory is different from that used by the driver, the scanner's communication mode is changed. This requires a restart of the TCP-IP connection, which can extend the start time by up to 30 seconds. There are two ways to prevent this: 1. [Recommended] Set the communication mode with the SOPAS ET software to binary and save this setting in the scanner's EEPROM. 2. Use the parameter "use_binary_protocol" to overwrite the default settings of the driver. 3. Setting "use_binary_protocol" to "False" activates COLA-A and disables COLA-B (default)

Known issue

If the scanner has not been set to binary Sopas in the EEPROM, the automatic restart of the TCP-IP connection does not work after the protocol change. The driver stops in this state: Wrong SOPAS Mode


restart the driver node.

Bugs and feature requests

  • Stability issues: Driver is experimental and brand new
  • Sopas protocol mapping: -- All scanners: COLA-B (Binary)
  • Software should be further tested, documented and beautified


  1. Check Scanner IP by using fping or SOPAS ET under Windows
  2. Check Ethernet connection to scanner with netcat e.g. nc -z -v -w5 $SCANNERIPADDRESS 2112 . For further details about setting up the correct ip settings see IP configuration 3. View node startup output wether the IP connection could be established 4. Check the scanner status using the LEDs on the device. The LED codes are described in the above mentioned operation manuals. 5. Further testing and troubleshooting informations can found in the file test/readme_testplan.txt 6. If you stop the scanner in your debugging IDE or by other hard interruption (like Ctrl-C), you must wait until 60 sec. before the scanner is up and running again. During this time the MRS6124 reconnects twice. If you do not wait this waiting time you could see one of the following messages: * TCP connection error * Error-Message 0x0d 7. Amplitude values in rviz: If you see only one color in rviz try the following: Set the min/max-Range of intensity display in the range [0...200] and switch on the intensity flag in the lauch file
    8. In case of network problems check your own ip address and the ip address of your laser scanner (by using SOPAS ET). * List of own IP-addresses: ifconfig|grep "inet addr" * Try to ping scanner ip address (used in launch file) 9. If the driver stops during init phase please stop the driver with ctrl-c and restart (could be caused due to protocol ASCII/Binary cola-dialect).


  • In case of technical support please open a new issue. For optimal support, add the following information to your request:
    1. Scanner model name,
    2. Ros node startup log,
    3. Sopas file of your scanner configuration. The instructions at show how to create the Sopas file.
  • In case of application support please use .
  • Issue Handling: Issues, for which no reply was received from the questioner for more than 7 days,
    are closed by us because we assume that the user has solved the problem.


In the following instructions, replace <rosdistro> with the name of your ROS distro (e.g., dashing).

From source

source /opt/ros/$ROS_DISTRO/setup.bash
mkdir -p ~/sick_scan_ws/src/
cd ~/sick_scan_ws/src/
git clone
cd ..
colcon build --symlink-install
source ~/sick_scan_ws/install/setup.bash

Quick Start

cd ~/sick_scan_ws
source ./install/setup.bash

Attention: Replace the ip address for "__hostname" with your scanner ip address. Default ip address of scanner is In this example we use the ip address

For TiM5xx:

ros2 run sick_scan2 sick_generic_caller __hostname:= __port:=2112 __name:=sick_tim_5xx

For TiM781:

ros2 run sick_scan2 sick_generic_caller __hostname:= __port:=2112 __name:=sick_tim_7xx

For TiM781S:

ros2 run sick_scan2 sick_generic_caller __hostname:= __port:=2112 __name:=sick_tim_7xxS

Start a second terminal window

cd ~/sick_scan_ws
source ./install/setup.bash
ros2 run tf2_ros static_transform_publisher 0 0 0 0 0 0 world laser

Start a third terminal window

cd ~/sick_scan_ws
source ./install/setup.bash
rviz2 ./install/sick_scan2/share/sick_scan2/launch/rviz/tim_5xx.rviz

The result shoud look like this: rviz2_scan

Developing with CLion IDE

  • Change to workspace directory, e.g.:
cd ~/sick_scan_ws
source ./install/setup.bash

~/.local/share/JetBrains/Toolbox/apps/CLion/ch-0/182.4323.58/bin/ ./src/sick_scan2

Comment: Please modify the path to your local installation.


ROS LiDAR SICK LiDAR SICK Laser SICK Laserscanner TiM5xx TiM551 TiM561 TiM571 TiM781 TiM781S


Michael Lehning

on behalf of SICK AG

Lehning Logo