sick_safevisionary_driver package from sick_safevisionary_ros2 reposick_safevisionary_driver sick_safevisionary_interfaces sick_safevisionary_tests |
|
Package Summary
Tags | No category tags. |
Version | 1.0.3 |
License | Apache-2.0 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/SICKAG/sick_safevisionary_ros2.git |
VCS Type | git |
VCS Version | main |
Last Updated | 2023-11-25 |
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
Additional Links
Maintainers
- Marvin Grosse Besselmann
- Stefan Scherzinger
- Jochen Lienhart
Authors
Sick Safevisionary Driver
This is the official ROS2 driver for the Sick safeVisionary2 cameras. See the top-level readme for getting started.
Lifecycle states
This driver implements a thin ROS2 wrapper around the sick_safevisionary_base library in form of a lifecycle node. In contrast to conventional ROS2 nodes, lifecycle nodes give us more control about the driver's individual states. This is handy e.g. when performing a clean reset at runtime. You'll find more information on the individual states and state transitions in this design article.
This driver's behavior is roughly as follows:
State | Behavior |
---|---|
Unconfigured | No topics are advertised and previously advertised topics are removed. |
Inactive | The driver establishes a UDP data connection to the camera and processes sensor data without publishing. |
Active | The driver continuously publishes all camera data with a consistent time stamp across all topics. |
Finalized | The driver has been shutdown and all resources have been cleaned up. All previously advertised topics are removed. |
Managing the lifecycle
ROS2 has a command line interface to trigger state transitions. Here are the commands to get the /sick_safevisionary node through its primary states:
ros2 lifecycle set /sick_safevisionary configure
ros2 lifecycle set /sick_safevisionary activate
ros2 lifecycle set /sick_safevisionary deactivate
ros2 lifecycle set /sick_safevisionary shutdown
Also see this example from the integration tests how to do that in Python.
Changelog for package sick_safevisionary_driver
1.0.3 (2023-11-25)
- Use ROS version-dependent cv_bridge include
- Contributors: Stefan Scherzinger
1.0.2 (2023-11-23)
- Add rosdep key for [boost]{.title-ref}
- Contributors: Stefan Scherzinger
1.0.1 (2023-11-22)
- Update maintainer tags
-
Transition from configuring to active by itself once on launch (#2)
- Transition from configuring to active by itself once on launch
- Initially deactivate and cleanup node during integration test
* Added additional comments to clarify launch file Co-authored-by: Stefan Scherzinger <scherzin@fzi.de> - Updated ReadMe for auto lifecycle configuration
* Updated driver ReadMe for auto lifecycle configuration Co-authored-by: Stefan Scherzinger <scherzin@fzi.de>
Add a readme for the driver package Also rename the sensor in the tests package for consistency.
Add a launch file parameter for CI testing We now use a launch file parameter to specify if we are running as part of a CI pipeline and don\'t check the UDP connection if that\'s the case. Also provide the [port]{.title-ref} and [frame_id]{.title-ref} as launch file parameters.
Add configure check for the UDP connection The [configure]{.title-ref} lifecycle transition now fails if there\'s no incoming sensor data, i.e. if something\'s wrong with the connection.
Changed doxygen indentation
Added doxygen comments
Initialize shared pointer correctly
Added license and maintainer infos
Message variable cleanup
added header to custom msgs
Put pointcloud publisher to the end since its non const
Check if intensity and points vector match
Publish topics in node namespace
Fixed dependency issues
Publish depth,intensity and state map
Publish field information
Publish region of interest
Publish ios
Publish device status
Naming consistency
Publish Pointcloud
Publish IMU data
Only publish with a non-zero subscription count This keeps the driver\'s computations lean if nobody is listening.
Make [frame_id]{.title-ref} a parameter This allows users to set the [frame_id]{.title-ref} of the published messages at runtime via the node\'s parameter interfaces.
Use a unique pointer for the compound publisher That\'s cleaner and makes sure that the compound publisher is valid after construction.
Add a publisher for camera info We use a separate class to encapsulate the different publishers so that the lifecycle part stays nice and clean.
Format launch file with black
Add an integration test for repetitive driver resets
Add boilerplate code for integration tests
Adjust includes from previous move
Move relevant files into a subfolder
Contributors: Marvin Gro
Wiki Tutorials
Source Tutorials
Package Dependencies
Deps | Name | |
---|---|---|
1 | ament_cmake | |
1 | cv_bridge | |
1 | lifecycle_msgs | |
1 | rclcpp | |
1 | rclcpp_lifecycle | |
2 | sensor_msgs | |
1 | sick_safevisionary_base | |
1 | sick_safevisionary_interfaces |
System Dependencies
Name |
---|
boost |
Dependant Packages
Name | Repo | Deps |
---|---|---|
sick_safevisionary_tests | github-SICKAG-sick_safevisionary_ros2 |
Launch files
Messages
Services
Plugins
Recent questions tagged sick_safevisionary_driver at Robotics Stack Exchange
sick_safevisionary_driver package from sick_safevisionary_ros2 reposick_safevisionary_driver sick_safevisionary_interfaces sick_safevisionary_tests |
|
Package Summary
Tags | No category tags. |
Version | 1.0.3 |
License | Apache-2.0 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/SICKAG/sick_safevisionary_ros2.git |
VCS Type | git |
VCS Version | main |
Last Updated | 2023-11-25 |
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
Additional Links
Maintainers
- Marvin Grosse Besselmann
- Stefan Scherzinger
- Jochen Lienhart
Authors
Sick Safevisionary Driver
This is the official ROS2 driver for the Sick safeVisionary2 cameras. See the top-level readme for getting started.
Lifecycle states
This driver implements a thin ROS2 wrapper around the sick_safevisionary_base library in form of a lifecycle node. In contrast to conventional ROS2 nodes, lifecycle nodes give us more control about the driver's individual states. This is handy e.g. when performing a clean reset at runtime. You'll find more information on the individual states and state transitions in this design article.
This driver's behavior is roughly as follows:
State | Behavior |
---|---|
Unconfigured | No topics are advertised and previously advertised topics are removed. |
Inactive | The driver establishes a UDP data connection to the camera and processes sensor data without publishing. |
Active | The driver continuously publishes all camera data with a consistent time stamp across all topics. |
Finalized | The driver has been shutdown and all resources have been cleaned up. All previously advertised topics are removed. |
Managing the lifecycle
ROS2 has a command line interface to trigger state transitions. Here are the commands to get the /sick_safevisionary node through its primary states:
ros2 lifecycle set /sick_safevisionary configure
ros2 lifecycle set /sick_safevisionary activate
ros2 lifecycle set /sick_safevisionary deactivate
ros2 lifecycle set /sick_safevisionary shutdown
Also see this example from the integration tests how to do that in Python.
Changelog for package sick_safevisionary_driver
1.0.3 (2023-11-25)
- Use ROS version-dependent cv_bridge include
- Contributors: Stefan Scherzinger
1.0.2 (2023-11-23)
- Add rosdep key for [boost]{.title-ref}
- Contributors: Stefan Scherzinger
1.0.1 (2023-11-22)
- Update maintainer tags
-
Transition from configuring to active by itself once on launch (#2)
- Transition from configuring to active by itself once on launch
- Initially deactivate and cleanup node during integration test
* Added additional comments to clarify launch file Co-authored-by: Stefan Scherzinger <scherzin@fzi.de> - Updated ReadMe for auto lifecycle configuration
* Updated driver ReadMe for auto lifecycle configuration Co-authored-by: Stefan Scherzinger <scherzin@fzi.de>
Add a readme for the driver package Also rename the sensor in the tests package for consistency.
Add a launch file parameter for CI testing We now use a launch file parameter to specify if we are running as part of a CI pipeline and don\'t check the UDP connection if that\'s the case. Also provide the [port]{.title-ref} and [frame_id]{.title-ref} as launch file parameters.
Add configure check for the UDP connection The [configure]{.title-ref} lifecycle transition now fails if there\'s no incoming sensor data, i.e. if something\'s wrong with the connection.
Changed doxygen indentation
Added doxygen comments
Initialize shared pointer correctly
Added license and maintainer infos
Message variable cleanup
added header to custom msgs
Put pointcloud publisher to the end since its non const
Check if intensity and points vector match
Publish topics in node namespace
Fixed dependency issues
Publish depth,intensity and state map
Publish field information
Publish region of interest
Publish ios
Publish device status
Naming consistency
Publish Pointcloud
Publish IMU data
Only publish with a non-zero subscription count This keeps the driver\'s computations lean if nobody is listening.
Make [frame_id]{.title-ref} a parameter This allows users to set the [frame_id]{.title-ref} of the published messages at runtime via the node\'s parameter interfaces.
Use a unique pointer for the compound publisher That\'s cleaner and makes sure that the compound publisher is valid after construction.
Add a publisher for camera info We use a separate class to encapsulate the different publishers so that the lifecycle part stays nice and clean.
Format launch file with black
Add an integration test for repetitive driver resets
Add boilerplate code for integration tests
Adjust includes from previous move
Move relevant files into a subfolder
Contributors: Marvin Gro
Wiki Tutorials
Source Tutorials
Package Dependencies
Deps | Name | |
---|---|---|
1 | ament_cmake | |
1 | cv_bridge | |
1 | lifecycle_msgs | |
1 | rclcpp | |
1 | rclcpp_lifecycle | |
2 | sensor_msgs | |
1 | sick_safevisionary_base | |
1 | sick_safevisionary_interfaces |
System Dependencies
Name |
---|
boost |
Dependant Packages
Name | Repo | Deps |
---|---|---|
sick_safevisionary_tests | github-SICKAG-sick_safevisionary_ros2 |
Launch files
Messages
Services
Plugins
Recent questions tagged sick_safevisionary_driver at Robotics Stack Exchange
sick_safevisionary_driver package from sick_safevisionary_ros2 reposick_safevisionary_driver sick_safevisionary_interfaces sick_safevisionary_tests |
|
Package Summary
Tags | No category tags. |
Version | 1.0.3 |
License | Apache-2.0 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/SICKAG/sick_safevisionary_ros2.git |
VCS Type | git |
VCS Version | main |
Last Updated | 2023-11-25 |
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
Additional Links
Maintainers
- Marvin Grosse Besselmann
- Stefan Scherzinger
- Jochen Lienhart
Authors
Sick Safevisionary Driver
This is the official ROS2 driver for the Sick safeVisionary2 cameras. See the top-level readme for getting started.
Lifecycle states
This driver implements a thin ROS2 wrapper around the sick_safevisionary_base library in form of a lifecycle node. In contrast to conventional ROS2 nodes, lifecycle nodes give us more control about the driver's individual states. This is handy e.g. when performing a clean reset at runtime. You'll find more information on the individual states and state transitions in this design article.
This driver's behavior is roughly as follows:
State | Behavior |
---|---|
Unconfigured | No topics are advertised and previously advertised topics are removed. |
Inactive | The driver establishes a UDP data connection to the camera and processes sensor data without publishing. |
Active | The driver continuously publishes all camera data with a consistent time stamp across all topics. |
Finalized | The driver has been shutdown and all resources have been cleaned up. All previously advertised topics are removed. |
Managing the lifecycle
ROS2 has a command line interface to trigger state transitions. Here are the commands to get the /sick_safevisionary node through its primary states:
ros2 lifecycle set /sick_safevisionary configure
ros2 lifecycle set /sick_safevisionary activate
ros2 lifecycle set /sick_safevisionary deactivate
ros2 lifecycle set /sick_safevisionary shutdown
Also see this example from the integration tests how to do that in Python.
Changelog for package sick_safevisionary_driver
1.0.3 (2023-11-25)
- Use ROS version-dependent cv_bridge include
- Contributors: Stefan Scherzinger
1.0.2 (2023-11-23)
- Add rosdep key for [boost]{.title-ref}
- Contributors: Stefan Scherzinger
1.0.1 (2023-11-22)
- Update maintainer tags
-
Transition from configuring to active by itself once on launch (#2)
- Transition from configuring to active by itself once on launch
- Initially deactivate and cleanup node during integration test
* Added additional comments to clarify launch file Co-authored-by: Stefan Scherzinger <scherzin@fzi.de> - Updated ReadMe for auto lifecycle configuration
* Updated driver ReadMe for auto lifecycle configuration Co-authored-by: Stefan Scherzinger <scherzin@fzi.de>
Add a readme for the driver package Also rename the sensor in the tests package for consistency.
Add a launch file parameter for CI testing We now use a launch file parameter to specify if we are running as part of a CI pipeline and don\'t check the UDP connection if that\'s the case. Also provide the [port]{.title-ref} and [frame_id]{.title-ref} as launch file parameters.
Add configure check for the UDP connection The [configure]{.title-ref} lifecycle transition now fails if there\'s no incoming sensor data, i.e. if something\'s wrong with the connection.
Changed doxygen indentation
Added doxygen comments
Initialize shared pointer correctly
Added license and maintainer infos
Message variable cleanup
added header to custom msgs
Put pointcloud publisher to the end since its non const
Check if intensity and points vector match
Publish topics in node namespace
Fixed dependency issues
Publish depth,intensity and state map
Publish field information
Publish region of interest
Publish ios
Publish device status
Naming consistency
Publish Pointcloud
Publish IMU data
Only publish with a non-zero subscription count This keeps the driver\'s computations lean if nobody is listening.
Make [frame_id]{.title-ref} a parameter This allows users to set the [frame_id]{.title-ref} of the published messages at runtime via the node\'s parameter interfaces.
Use a unique pointer for the compound publisher That\'s cleaner and makes sure that the compound publisher is valid after construction.
Add a publisher for camera info We use a separate class to encapsulate the different publishers so that the lifecycle part stays nice and clean.
Format launch file with black
Add an integration test for repetitive driver resets
Add boilerplate code for integration tests
Adjust includes from previous move
Move relevant files into a subfolder
Contributors: Marvin Gro
Wiki Tutorials
Source Tutorials
Package Dependencies
Deps | Name | |
---|---|---|
1 | ament_cmake | |
1 | cv_bridge | |
1 | lifecycle_msgs | |
1 | rclcpp | |
1 | rclcpp_lifecycle | |
2 | sensor_msgs | |
1 | sick_safevisionary_base | |
1 | sick_safevisionary_interfaces |
System Dependencies
Name |
---|
boost |
Dependant Packages
Name | Repo | Deps |
---|---|---|
sick_safevisionary_tests | github-SICKAG-sick_safevisionary_ros2 |
Launch files
Messages
Services
Plugins
Recent questions tagged sick_safevisionary_driver at Robotics Stack Exchange
sick_safevisionary_driver package from sick_safevisionary_ros2 reposick_safevisionary_driver sick_safevisionary_interfaces sick_safevisionary_tests |
|
Package Summary
Tags | No category tags. |
Version | 1.0.3 |
License | Apache-2.0 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/SICKAG/sick_safevisionary_ros2.git |
VCS Type | git |
VCS Version | main |
Last Updated | 2023-11-25 |
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
Additional Links
Maintainers
- Marvin Grosse Besselmann
- Stefan Scherzinger
- Jochen Lienhart
Authors
Sick Safevisionary Driver
This is the official ROS2 driver for the Sick safeVisionary2 cameras. See the top-level readme for getting started.
Lifecycle states
This driver implements a thin ROS2 wrapper around the sick_safevisionary_base library in form of a lifecycle node. In contrast to conventional ROS2 nodes, lifecycle nodes give us more control about the driver's individual states. This is handy e.g. when performing a clean reset at runtime. You'll find more information on the individual states and state transitions in this design article.
This driver's behavior is roughly as follows:
State | Behavior |
---|---|
Unconfigured | No topics are advertised and previously advertised topics are removed. |
Inactive | The driver establishes a UDP data connection to the camera and processes sensor data without publishing. |
Active | The driver continuously publishes all camera data with a consistent time stamp across all topics. |
Finalized | The driver has been shutdown and all resources have been cleaned up. All previously advertised topics are removed. |
Managing the lifecycle
ROS2 has a command line interface to trigger state transitions. Here are the commands to get the /sick_safevisionary node through its primary states:
ros2 lifecycle set /sick_safevisionary configure
ros2 lifecycle set /sick_safevisionary activate
ros2 lifecycle set /sick_safevisionary deactivate
ros2 lifecycle set /sick_safevisionary shutdown
Also see this example from the integration tests how to do that in Python.
Changelog for package sick_safevisionary_driver
1.0.3 (2023-11-25)
- Use ROS version-dependent cv_bridge include
- Contributors: Stefan Scherzinger
1.0.2 (2023-11-23)
- Add rosdep key for [boost]{.title-ref}
- Contributors: Stefan Scherzinger
1.0.1 (2023-11-22)
- Update maintainer tags
-
Transition from configuring to active by itself once on launch (#2)
- Transition from configuring to active by itself once on launch
- Initially deactivate and cleanup node during integration test
* Added additional comments to clarify launch file Co-authored-by: Stefan Scherzinger <scherzin@fzi.de> - Updated ReadMe for auto lifecycle configuration
* Updated driver ReadMe for auto lifecycle configuration Co-authored-by: Stefan Scherzinger <scherzin@fzi.de>
Add a readme for the driver package Also rename the sensor in the tests package for consistency.
Add a launch file parameter for CI testing We now use a launch file parameter to specify if we are running as part of a CI pipeline and don\'t check the UDP connection if that\'s the case. Also provide the [port]{.title-ref} and [frame_id]{.title-ref} as launch file parameters.
Add configure check for the UDP connection The [configure]{.title-ref} lifecycle transition now fails if there\'s no incoming sensor data, i.e. if something\'s wrong with the connection.
Changed doxygen indentation
Added doxygen comments
Initialize shared pointer correctly
Added license and maintainer infos
Message variable cleanup
added header to custom msgs
Put pointcloud publisher to the end since its non const
Check if intensity and points vector match
Publish topics in node namespace
Fixed dependency issues
Publish depth,intensity and state map
Publish field information
Publish region of interest
Publish ios
Publish device status
Naming consistency
Publish Pointcloud
Publish IMU data
Only publish with a non-zero subscription count This keeps the driver\'s computations lean if nobody is listening.
Make [frame_id]{.title-ref} a parameter This allows users to set the [frame_id]{.title-ref} of the published messages at runtime via the node\'s parameter interfaces.
Use a unique pointer for the compound publisher That\'s cleaner and makes sure that the compound publisher is valid after construction.
Add a publisher for camera info We use a separate class to encapsulate the different publishers so that the lifecycle part stays nice and clean.
Format launch file with black
Add an integration test for repetitive driver resets
Add boilerplate code for integration tests
Adjust includes from previous move
Move relevant files into a subfolder
Contributors: Marvin Gro
Wiki Tutorials
Source Tutorials
Package Dependencies
Deps | Name | |
---|---|---|
1 | ament_cmake | |
1 | cv_bridge | |
1 | lifecycle_msgs | |
1 | rclcpp | |
1 | rclcpp_lifecycle | |
2 | sensor_msgs | |
1 | sick_safevisionary_base | |
1 | sick_safevisionary_interfaces |
System Dependencies
Name |
---|
boost |
Dependant Packages
Name | Repo | Deps |
---|---|---|
sick_safevisionary_tests | github-SICKAG-sick_safevisionary_ros2 |
Launch files
Messages
Services
Plugins
Recent questions tagged sick_safevisionary_driver at Robotics Stack Exchange
sick_safevisionary_driver package from sick_safevisionary_ros1 reposick_safevisionary_driver sick_safevisionary_msgs |
|
Package Summary
Tags | No category tags. |
Version | 1.0.1 |
License | Apache-2.0 |
Build type | CATKIN |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/SICKAG/sick_safevisionary_ros1.git |
VCS Type | git |
VCS Version | main |
Last Updated | 2023-10-17 |
Dev Status | DEVELOPED |
CI status | Continuous Integration |
Released | RELEASED |
Tags | No category tags. |
Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Marvin Grosse Besselmann
- Stefan Scherzinger
Authors
Sick Safevisionary Driver
This is the official ROS driver for the Sick safeVisionary2 cameras. See the top-level readme for getting started.
Changelog for package sick_safevisionary_driver
1.0.1 (2023-10-17)
- Add a minimal readme to the driver package
- Added doxygen comments
- Added licensing and maintainer infos
- Updated msg names and included header
- Check intensity and point vector size for mismatch
- Split into driver and publisher class
- Removed unnecessary info from cmake and package files
- renamed variables
- Renamed classes and files
- Contributors: Marvin Gro
Wiki Tutorials
Source Tutorials
Package Dependencies
Deps | Name | |
---|---|---|
1 | catkin | |
1 | roscpp | |
2 | sensor_msgs | |
1 | image_transport | |
1 | cv_bridge | |
1 | sick_safevisionary_base | |
1 | sick_safevisionary_msgs |