sick_safetyscanners_base package from sick_safetyscanners_base repo

sick_safetyscanners_base

Package Summary

Tags No category tags.
Version 1.0.0
License ALv2
Build type CMAKE
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/SICKAG/sick_safetyscanners_base.git
VCS Type git
VCS Version ros2
Last Updated 2021-04-08
Dev Status DEVELOPED
CI status No Continuous Integration
Released RELEASED
Tags No category tags.
Contributing Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)

Package Description

Provides an Interface to read the sensor output of a SICK Safety Scanner

Additional Links

No additional links.

Maintainers

  • Lennart Puck

Authors

  • Lennart Puck

Sick_Safetyscanners_Base CPP Driver

Table of contents

A CPP standalone Driver which reads the raw data from the SICK Safety Scanners and takes custom functions to publish the data.

Supported Hardware

Supported are all microScan3, nanoScan3 and outdoorScan3 variants with Ethernet connection.

Getting started

The driver will be released on this github repository, and can then be installed from source.

Prerequisites

  • Linux
  • Correctly setup SICK Safety Scanner
  • Connected SICK Safety Scanner and a correctly setup ethernet network. Both the host and the sensor have to be in the same network.
  • Installed libboost

Installation

For installation this github repository has to be cloned and afterwards installed. If a custom install directory is wanted use the -DCMAKE_INSTALL_PREFIX option to specify a path.

git clone https://github.com/SICKAG/sick_safetyscanners_base.git
cd sick_safetyscanners_base
mkdir build
cd build
cmake -DCMAKE_INSTALL_PREFIX=<path to install folder> ..
make -j8
make install

Usage

To use the library in a driver the path of the installation has to be added to the cmake prefix path of your application. You can achieve this by using, bevor invoking cmake on your application.

export CMAKE_PREFIX_PATH=<path to install folder>

Afterwards the driver and the settings for the driver can be included with:

#include <sick_safetyscanners_base/SickSafetyscanners.h>
#include <sick_safetyscanners_base/Exceptions.h>
#include <sick_safetyscanners_base/Types.h>
#include <sick_safetyscanners_base/datastructure/CommSettings.h>

To get the driver up and running you need first to choose between the synchronous and asynchronous APIs based on your needs.

In the latter case you can also pass an instance of boost::asio::io_service to the constructor of the AsyncSickSafetyScanner.

API

Synchronous Client

In cases where you do not want the driver to spawn internal child threads to asynchronously process incomming sensor data you can use the SyncSickSafetyScanner class.

Function Information
SyncSickSafetyScanner
(sick::types::ip_address_t sensor_ip,
sick::types::port_t sensor_port,
sick::datastructure::CommSettings comm_settings);
Constructor call.
bool isDataAvailable(); Non-blocking call that indicates wheether sensor data is available to fetch via the receive-function from the internal sensor data receiving buffer.
const Data receive
(sick::types::time_duration_t timeout = boost::posix_time::pos_infin);
Blocking call to receive one sensor data packet at a time.

Example

// Sensor IP and Port
std::string sensor_ip_str = 192.168.1.11
sick::types::ip_address_t sensor_ip = boost::asio::ip::address_v4::from_string(sensor_ip_str);
sick::types::port_t tcp_port {2122};

// Prepare the CommSettings for Sensor streaming data
sick::datastructure::CommSettings comm_settings;
std::string host_ip_str = "192.168.1.9"
comm_settings.host_ip = boost::asio::ip::address_v4::from_string(host_ip_str);
comm_settings.host_udp_port = 0;

// Create a sensor instance
auto safety_scanner = std::make_uniqe<sick::SyncSickSafetyScanner>(sensor_ip, tcp_port, comm_settings);

// Receive one sensor data packet
auto timeout = boost::posix_time::seconds(5);
sick::datastructure::Data data = safety_scanner->receive(timeout);

// ...

Asynchronous Client

If you dont need restrict your client to work with single-threaded blocking receive calls in a strict sequential manner you can use the AsyncSickSafetyScanner class. The sensor data callback required by the constructor has the following signature

void callback(const sick::datastructure::Data& data);

Function Information
AsyncSickSafetyScanner
(sick::types::ip_address_t sensor_ip,
sick::types::port_t sensor_port,
sick::datastructure::CommSettings comm_settings,
sick::types::ScanDataCb callback);
Constructor call with custom data sensor callback.
AsyncSickSafetyScanner
(sick::types::ip_address_t sensor_ip,
sick::types::port_t sensor_port,
sick::datastructure::CommSettings comm_settings,
boost::asio::ip::address_v4 interface_ip,
sick::types::ScanDataCb callback);
Constructor call with custom data sensor callback for multicast ip addresses.
AsyncSickSafetyScanner
(sick::types::ip_address_t sensor_ip,
sick::types::port_t sensor_port,
sick::datastructure::CommSettings comm_settings,
sick::types::ScanDataCb callback,
boost::asio::io_service& io_service);
Constructor call. This variant allows the user to pass through an instance of boost::asio::io_service to get full control over the thread execution. In this case the driver is not spawning an internal child thread but relies on the user to perform regular io_service.run() operations and keep the service busy.
void run(); Starts to receive sensor data via UDP and passes the data to the callback as specified in the constructor.
void stop(); Stops all asynchronous receiving and processing operations.

Example

// Sensor IP and Port
std::string sensor_ip_str = 192.168.1.11
sick::types::ip_address_t sensor_ip = boost::asio::ip::address_v4::from_string(sensor_ip_str);
sick::types::port_t tcp_port {2122};

// Prepare the CommSettings for Sensor streaming data
sick::datastructure::CommSettings comm_settings;
std::string host_ip_str = "192.168.1.9"
comm_settings.host_ip = boost::asio::ip::address_v4::from_string(host_ip_str);
comm_settings.host_udp_port = 0;

// Define a sensor data callback
sick::types::ScanDataCb cb = [](const sick::datastructure::Data &data) {
    std::cout << "Number of beams: " << data.getMeasurementDataPtr()->getNumberOfBeams() << std::endl;
};

// Create a sensor instance
auto safety_scanner = std::make_unique<sick::AsyncSickSafetyScanner>(sensor_ip, tcp_port, comm_settings, cb);

// Special case if a multicast IP is seltected as host_ip
// std::string host_ip_str = "235.235.235.2"
// comm_settings.host_ip = boost::asio::ip::address_v4::from_string(host_ip_str);
// std::string interface_ip_str = "192.168.1.9"
// auto interface_ip = boost::asio::ip::address_v4::from_string(interface_ip_str);
// auto safety_scanner = std::make_unique<sick::AsyncSickSafetyScanner>(sensor_ip, tcp_port, comm_settings, interface_ip, cb);

// Start async receiving and processing of sensor data
safety_scanner->run();

// ... Do other stuff

// Stop async processing
safety_scanner->stop();

Parameters of Communication Settings

The parameters can be set using the setters of the CommSettings class. To set for example to host_ip the following function can be called.

sick::datastructure::CommSettings m_communication_settings;
m_communication_settings.setHostIp("192.168.1.100");

Parameter Name API Default Information
sensor_ip void setSensorIp(const std::string& sensor_ip); 192.168.1.11 Sensor IP address. Can be passed as an argument to the launch file.
host_ip void setHostIp(const std::string& host_ip); 192.168.1.9 Host IP address. Can be passed as an argument to the launch file.
host_udp_port void setHostUdpPort(const uint16_t& host_udp_port); 0 Host UDP Port. Can be passed as an argument to the launch file. Zero allows system chosen port.
publishing_frequency void setPublishingFrequency(const uint16_t& publishing_frequency) 1 Publish every n_th scan, where n is the publishing frequency. For a 25Hz laser, setting to 1 makes it publish at 25Hz, to 2 makes it publish at 12.5Hz.
start_angle void setStartAngle(const uint32_t& start_angle) 0.0 Start angle of scan in radians, if both start and end angle are equal, all angels are regarded. 0° is at the front of the scanner.
end_angle void setEndAngle(const uint32_t& start_angle) 0.0 End angle of scan in radians, if both start and end angle are equal, all angels are regarded. 0° is at the front of the scanner.
channel_enabled void setEnabled(bool enabled); true If the channel should be enabled
e_interface_type void setEInterfaceType(const uint8_t& e_interface_type) 0 Sets the interface type of the sensor
0: EFI-pro
1: EtherNet/IP
3: Profinet
4: Non-safe Ethernet
features void CommSettings::setFeatures
(
bool general_system_state,
bool derived_settings,
bool measurement_data,
bool intrusion_data,
bool application_data
)
all true Enables the individual data outputs.

COLA2 Functions (available on both driver API variants)

The Library allows to access variables of the sensor and invoke methods to change settings using the COLA2 protocol. The following methods can be called:

Function Information
void changeSensorSettings
(const sick::datastructure::CommSettings& settings)
Updates the sensor settings to the passed configuration.
void findSensor
(
uint16_t blink_time);
Lets the sensor flash the display for the specified time.
void requestApplicationName
(sick::datastructure::ApplicationName& application_name);
Returns the name of the current application.
void requestConfigMetadata
(sick::datastructure::ConfigMetadata& config_metadata);
Returns the metadata of the current configuration of the sensor.
void requestDeviceName
(sick::datastructure::DeviceName& device_name);
Returns the device name.
void requestDeviceStatus
(sick::datastructure::DeviceStatus& device_status);
Returns the device status.
void requestFieldData
(std::vector< sick::datastructure::FieldData>& field_data);
Returns the field data of the warning and safety fields.
void requestFirmwareVersion
(sick::datastructure::FirmwareVersion& firmware_version);
Returns the firmware version.
void requestLatestTelegram
(sick::datastructure::Data& data,
int8_t index = 0);
Returns the latest telegram for the channel index. Up to 4 Channels can be supported by the cola protocol, the actual number depends on the used scanner. Channel 0 is set as default value.
void requestMonitoringCases
(std::vector< sick::datastructure::MonitoringCaseData>& monitoring_cases);
Returns the data of the Monitoring Cases.
void requestOrderNumber
(sick::datastructure::OrderNumber& order_number);
Returns the order Number.
void requestPersistentConfig
(sick::datastructure::ConfigData& config_data);
Returns the Persistent configuration of the sensor, which was set in the Safety Designer.
void requestProjectName
(sick::datastructure::ProjectName& project_name);
Returns the project name.
void requestRequiredUserAction
(sick::datastructure::RequiredUserAction& required_user_action);
Returns the required user actions as specified in the cola 2 manual.
void requestSerialNumber
(sick::datastructure::SerialNumber& serial_number);
Returns the serial number of the sensor.
void requestStatusOverview
(sick::datastructure::StatusOverview& status_overview);
Returns the status overview.
void requestTypeCode
(sick::datastructure::TypeCode& type_code)
Returns the type code of the sensor.
void requestUserName
(sick::datastructure::UserName& user_name);
Returns the user name.

Troubleshooting

  • Check if the sensor has power and is connected to the host.
  • Check if both sensor and host are in the same subnet e.g. 192.168.1
  • Are the correct IPs configured for the application?
  • Is the correct Interface Type configured?

Creators

Lennart Puck
Martin Schulze

FZI Forschungszentrum Informatik

on behalf of SICK AG

CHANGELOG

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Changelog for package sick_safetyscanners_base ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

1.0.0 (2021-01-11)

  • Initial Release

Wiki Tutorials

See ROS Wiki Tutorials for more details.

Source Tutorials

Not currently indexed.

Package Dependencies

No dependencies on ROS packages.

System Dependencies

Name
cmake
boost

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged sick_safetyscanners_base at answers.ros.org

No version for distro dashing. Known supported distros are highlighted in the buttons above.
No version for distro noetic. Known supported distros are highlighted in the buttons above.
No version for distro melodic. Known supported distros are highlighted in the buttons above.
No version for distro kinetic. Known supported distros are highlighted in the buttons above.
No version for distro ardent. Known supported distros are highlighted in the buttons above.
No version for distro bouncy. Known supported distros are highlighted in the buttons above.
No version for distro crystal. Known supported distros are highlighted in the buttons above.
No version for distro eloquent. Known supported distros are highlighted in the buttons above.
No version for distro lunar. Known supported distros are highlighted in the buttons above.
No version for distro jade. Known supported distros are highlighted in the buttons above.
No version for distro indigo. Known supported distros are highlighted in the buttons above.
No version for distro hydro. Known supported distros are highlighted in the buttons above.