ROS IndexNo version for distro humble showing kinetic. Known supported distros are highlighted in the buttons above.
|
ouster_driver package from ouster repoouster_driver |
ROS Distro
|
Package Summary
| Tags | No category tags. |
| Version | 0.1.7 |
| License | Apache 2 |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/CPFL/ouster.git |
| VCS Type | git |
| VCS Version | autoware_branch |
| Last Updated | 2019-03-28 |
| 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
OS1 ROS client
Additional Links
No additional links.
Maintainers
- Alexander Carballo
- Abraham Monrroy
Authors
- ouster developers
README
No README found.
No README in repository either.
CHANGELOG
Changelog for package ouster
0.1.7 (2019-03-28)
- Sensor model and firmware version validation
- Added sensor model and firmware version validation. The driver currently only works for OS-1-64 and on firmware version 1.10 some configuration parameters disappeared.
- Parameter validation and new pointcloud types
- Added parameter validation to avoid reinitializing the LiDAR. Added new pointcloud types XYZIRF and XYZIRFN. Changed pulse_mode parameter from integer to string for readability. Updated the readme file.
- Contributors: Alexander Carballo, alexandrx
0.1.6 (2019-03-13)
- Renamed ouster_ros to ouster_driver
0.1.5 (2019-03-13)
- updated package.xml
0.1.4 (2019-03-13)
- Updated project name to follow ros standards
0.1.3 (2019-03-06)
- Updated LICENSE
0.1.2 (2019-03-06)
- Changed operation mode from integer to string to ease reading.
- New pointcloud mode format added
- Improved parameter documentation
- removed the old bool pointcloud_mode_xyzir parameter (to match Velodyne's mode) and replaced with a way to specify the desired pointcloud format, several options added including Ouster's native pointcloud format.
- Added install commands
- run CI on kinetic and melodic only
- Fixed launch file to deal with hidden parameters, fixed readme.md to update the TODO, fixed os1_node.cpp to reduce by half the scan duration variable in case of 20Hz operation.
- Updated the driver to support advanced parameter configuration (lidar-mode, pulse-mode and window-rejection-enable)
- Eliminated the ouster-ros static library
- Updated readme.md incorrect info for lidar address configuration.
- Switched to industrial-ci
- First commit for Autoware version branch. Modified the original Ouster ROS code to suit Autoware needs. Code structure is more simple, only ROS driver code is kept, and the readme.md file has more details on how to configure the sensor and use this driver. To further ease Autoware integration, Velodyne compatibility options were added and tested with nd-_matching, ray-ground-filter and euclidean-cluster nodes.
- Improve positional argument parsing in viz
- Use allocate-shared for Eigen compatibility
- Support building visualizer with newer VTK
- Readme tweaks and new example data
- Update readme.md
- updated the readme to include viz in the contents
- Initial commit of the example visualizer
- Uses VTK6 to display point clouds and range/intensity/noise images
- No dependencies other than VTK6, Eigen3, and a C++11 compiler
- Currently only supports linux; tested on multiple distributions and platforms
- Use correct units in sensor-msgs::Imu
- Deal with time going backwards in replays
- Contributors: Alexander Carballo, Dima Garbuzov, Roy Rinberg, alexandrx, amc-nu, hooic, rafficm, rrinberg
Wiki Tutorials
This package does not provide any links to tutorials in it's rosindex metadata.
You can check on the ROS Wiki Tutorials page for the package.
Package Dependencies
| Deps | Name |
|---|---|
| roscpp | |
| message_generation | |
| std_msgs | |
| sensor_msgs | |
| pcl_ros | |
| pcl_conversions | |
| catkin | |
| message_runtime |
System Dependencies
No direct system dependencies.
Dependant Packages
No known dependants.
Launch files
- launch/os1.launch
- -*- mode: XML -*-
-
- lidar_address [default: 192.168.0.100] — hostname or IP address in dotted decimal form of the Ouster sensor
- pc_address [default: 192.168.0.1] — hostname or IP address of the computer (PC) where the sensor will send data packets
- lidar_port [default: 7502] — port to which the sensor should send lidar data
- imu_port [default: 7503] — port to which the sensor should send imu data
- replay [default: false] — when true, the node will listen on ~/lidar_packets and ~/imu_packets for data instead of attempting to connect to a sensor
- scan_dur_ns [default: 100000000] — nanoseconds to batch lidar packets before publishing a cloud
- pointcloud_mode [default: XYZIR] — Point cloud mode, supported modes: NATIVE, XYZ, XYZI, XYZIR, XYZIF, XYZIRF, XYZIFN, XYZIRFN (I=intensity, R=ring (in ascending order), F=reflectivity, N=ambient noise). NATIVE is XYZIRFt where t=point timestamp and ring follows Ouster's original descending order.
- lidar_frame_name [default: velodyne] — Frame name for lidar output message
- lidar_topic_name [default: /points_raw] — Topic name for lidar output message
- imu_frame_name [default: imu] — Frame name for IMU output message
- imu_topic_name [default: /imu_raw] — Topic name for IMU output message
- operation_mode [default: 1024x10] — Supported operation modes: 512x10, 1024x10, 2048x10, 512x20, 1024x20 (horizontal resolution x scan rate)
- pulse_mode [default: STANDARD] — Laser pulse width, available modes: STANDARD and NARROW
- window_rejection [default: true] — Window (short range) rejection enable
Messages
Services
No service files found
Plugins
No plugins found.
Recent questions tagged ouster_driver at Robotics Stack Exchange
No version for distro jazzy showing kinetic. Known supported distros are highlighted in the buttons above.
|
|
ouster_driver package from ouster repoouster_driver |
ROS Distro
|
Package Summary
| Tags | No category tags. |
| Version | 0.1.7 |
| License | Apache 2 |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/CPFL/ouster.git |
| VCS Type | git |
| VCS Version | autoware_branch |
| Last Updated | 2019-03-28 |
| 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
OS1 ROS client
Additional Links
No additional links.
Maintainers
- Alexander Carballo
- Abraham Monrroy
Authors
- ouster developers
README
No README found.
No README in repository either.
CHANGELOG
Changelog for package ouster
0.1.7 (2019-03-28)
- Sensor model and firmware version validation
- Added sensor model and firmware version validation. The driver currently only works for OS-1-64 and on firmware version 1.10 some configuration parameters disappeared.
- Parameter validation and new pointcloud types
- Added parameter validation to avoid reinitializing the LiDAR. Added new pointcloud types XYZIRF and XYZIRFN. Changed pulse_mode parameter from integer to string for readability. Updated the readme file.
- Contributors: Alexander Carballo, alexandrx
0.1.6 (2019-03-13)
- Renamed ouster_ros to ouster_driver
0.1.5 (2019-03-13)
- updated package.xml
0.1.4 (2019-03-13)
- Updated project name to follow ros standards
0.1.3 (2019-03-06)
- Updated LICENSE
0.1.2 (2019-03-06)
- Changed operation mode from integer to string to ease reading.
- New pointcloud mode format added
- Improved parameter documentation
- removed the old bool pointcloud_mode_xyzir parameter (to match Velodyne's mode) and replaced with a way to specify the desired pointcloud format, several options added including Ouster's native pointcloud format.
- Added install commands
- run CI on kinetic and melodic only
- Fixed launch file to deal with hidden parameters, fixed readme.md to update the TODO, fixed os1_node.cpp to reduce by half the scan duration variable in case of 20Hz operation.
- Updated the driver to support advanced parameter configuration (lidar-mode, pulse-mode and window-rejection-enable)
- Eliminated the ouster-ros static library
- Updated readme.md incorrect info for lidar address configuration.
- Switched to industrial-ci
- First commit for Autoware version branch. Modified the original Ouster ROS code to suit Autoware needs. Code structure is more simple, only ROS driver code is kept, and the readme.md file has more details on how to configure the sensor and use this driver. To further ease Autoware integration, Velodyne compatibility options were added and tested with nd-_matching, ray-ground-filter and euclidean-cluster nodes.
- Improve positional argument parsing in viz
- Use allocate-shared for Eigen compatibility
- Support building visualizer with newer VTK
- Readme tweaks and new example data
- Update readme.md
- updated the readme to include viz in the contents
- Initial commit of the example visualizer
- Uses VTK6 to display point clouds and range/intensity/noise images
- No dependencies other than VTK6, Eigen3, and a C++11 compiler
- Currently only supports linux; tested on multiple distributions and platforms
- Use correct units in sensor-msgs::Imu
- Deal with time going backwards in replays
- Contributors: Alexander Carballo, Dima Garbuzov, Roy Rinberg, alexandrx, amc-nu, hooic, rafficm, rrinberg
Wiki Tutorials
This package does not provide any links to tutorials in it's rosindex metadata.
You can check on the ROS Wiki Tutorials page for the package.
Package Dependencies
| Deps | Name |
|---|---|
| roscpp | |
| message_generation | |
| std_msgs | |
| sensor_msgs | |
| pcl_ros | |
| pcl_conversions | |
| catkin | |
| message_runtime |
System Dependencies
No direct system dependencies.
Dependant Packages
No known dependants.
Launch files
- launch/os1.launch
- -*- mode: XML -*-
-
- lidar_address [default: 192.168.0.100] — hostname or IP address in dotted decimal form of the Ouster sensor
- pc_address [default: 192.168.0.1] — hostname or IP address of the computer (PC) where the sensor will send data packets
- lidar_port [default: 7502] — port to which the sensor should send lidar data
- imu_port [default: 7503] — port to which the sensor should send imu data
- replay [default: false] — when true, the node will listen on ~/lidar_packets and ~/imu_packets for data instead of attempting to connect to a sensor
- scan_dur_ns [default: 100000000] — nanoseconds to batch lidar packets before publishing a cloud
- pointcloud_mode [default: XYZIR] — Point cloud mode, supported modes: NATIVE, XYZ, XYZI, XYZIR, XYZIF, XYZIRF, XYZIFN, XYZIRFN (I=intensity, R=ring (in ascending order), F=reflectivity, N=ambient noise). NATIVE is XYZIRFt where t=point timestamp and ring follows Ouster's original descending order.
- lidar_frame_name [default: velodyne] — Frame name for lidar output message
- lidar_topic_name [default: /points_raw] — Topic name for lidar output message
- imu_frame_name [default: imu] — Frame name for IMU output message
- imu_topic_name [default: /imu_raw] — Topic name for IMU output message
- operation_mode [default: 1024x10] — Supported operation modes: 512x10, 1024x10, 2048x10, 512x20, 1024x20 (horizontal resolution x scan rate)
- pulse_mode [default: STANDARD] — Laser pulse width, available modes: STANDARD and NARROW
- window_rejection [default: true] — Window (short range) rejection enable
Messages
Services
No service files found
Plugins
No plugins found.
Recent questions tagged ouster_driver at Robotics Stack Exchange
No version for distro kilted showing kinetic. Known supported distros are highlighted in the buttons above.
|
|
ouster_driver package from ouster repoouster_driver |
ROS Distro
|
Package Summary
| Tags | No category tags. |
| Version | 0.1.7 |
| License | Apache 2 |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/CPFL/ouster.git |
| VCS Type | git |
| VCS Version | autoware_branch |
| Last Updated | 2019-03-28 |
| 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
OS1 ROS client
Additional Links
No additional links.
Maintainers
- Alexander Carballo
- Abraham Monrroy
Authors
- ouster developers
README
No README found.
No README in repository either.
CHANGELOG
Changelog for package ouster
0.1.7 (2019-03-28)
- Sensor model and firmware version validation
- Added sensor model and firmware version validation. The driver currently only works for OS-1-64 and on firmware version 1.10 some configuration parameters disappeared.
- Parameter validation and new pointcloud types
- Added parameter validation to avoid reinitializing the LiDAR. Added new pointcloud types XYZIRF and XYZIRFN. Changed pulse_mode parameter from integer to string for readability. Updated the readme file.
- Contributors: Alexander Carballo, alexandrx
0.1.6 (2019-03-13)
- Renamed ouster_ros to ouster_driver
0.1.5 (2019-03-13)
- updated package.xml
0.1.4 (2019-03-13)
- Updated project name to follow ros standards
0.1.3 (2019-03-06)
- Updated LICENSE
0.1.2 (2019-03-06)
- Changed operation mode from integer to string to ease reading.
- New pointcloud mode format added
- Improved parameter documentation
- removed the old bool pointcloud_mode_xyzir parameter (to match Velodyne's mode) and replaced with a way to specify the desired pointcloud format, several options added including Ouster's native pointcloud format.
- Added install commands
- run CI on kinetic and melodic only
- Fixed launch file to deal with hidden parameters, fixed readme.md to update the TODO, fixed os1_node.cpp to reduce by half the scan duration variable in case of 20Hz operation.
- Updated the driver to support advanced parameter configuration (lidar-mode, pulse-mode and window-rejection-enable)
- Eliminated the ouster-ros static library
- Updated readme.md incorrect info for lidar address configuration.
- Switched to industrial-ci
- First commit for Autoware version branch. Modified the original Ouster ROS code to suit Autoware needs. Code structure is more simple, only ROS driver code is kept, and the readme.md file has more details on how to configure the sensor and use this driver. To further ease Autoware integration, Velodyne compatibility options were added and tested with nd-_matching, ray-ground-filter and euclidean-cluster nodes.
- Improve positional argument parsing in viz
- Use allocate-shared for Eigen compatibility
- Support building visualizer with newer VTK
- Readme tweaks and new example data
- Update readme.md
- updated the readme to include viz in the contents
- Initial commit of the example visualizer
- Uses VTK6 to display point clouds and range/intensity/noise images
- No dependencies other than VTK6, Eigen3, and a C++11 compiler
- Currently only supports linux; tested on multiple distributions and platforms
- Use correct units in sensor-msgs::Imu
- Deal with time going backwards in replays
- Contributors: Alexander Carballo, Dima Garbuzov, Roy Rinberg, alexandrx, amc-nu, hooic, rafficm, rrinberg
Wiki Tutorials
This package does not provide any links to tutorials in it's rosindex metadata.
You can check on the ROS Wiki Tutorials page for the package.
Package Dependencies
| Deps | Name |
|---|---|
| roscpp | |
| message_generation | |
| std_msgs | |
| sensor_msgs | |
| pcl_ros | |
| pcl_conversions | |
| catkin | |
| message_runtime |
System Dependencies
No direct system dependencies.
Dependant Packages
No known dependants.
Launch files
- launch/os1.launch
- -*- mode: XML -*-
-
- lidar_address [default: 192.168.0.100] — hostname or IP address in dotted decimal form of the Ouster sensor
- pc_address [default: 192.168.0.1] — hostname or IP address of the computer (PC) where the sensor will send data packets
- lidar_port [default: 7502] — port to which the sensor should send lidar data
- imu_port [default: 7503] — port to which the sensor should send imu data
- replay [default: false] — when true, the node will listen on ~/lidar_packets and ~/imu_packets for data instead of attempting to connect to a sensor
- scan_dur_ns [default: 100000000] — nanoseconds to batch lidar packets before publishing a cloud
- pointcloud_mode [default: XYZIR] — Point cloud mode, supported modes: NATIVE, XYZ, XYZI, XYZIR, XYZIF, XYZIRF, XYZIFN, XYZIRFN (I=intensity, R=ring (in ascending order), F=reflectivity, N=ambient noise). NATIVE is XYZIRFt where t=point timestamp and ring follows Ouster's original descending order.
- lidar_frame_name [default: velodyne] — Frame name for lidar output message
- lidar_topic_name [default: /points_raw] — Topic name for lidar output message
- imu_frame_name [default: imu] — Frame name for IMU output message
- imu_topic_name [default: /imu_raw] — Topic name for IMU output message
- operation_mode [default: 1024x10] — Supported operation modes: 512x10, 1024x10, 2048x10, 512x20, 1024x20 (horizontal resolution x scan rate)
- pulse_mode [default: STANDARD] — Laser pulse width, available modes: STANDARD and NARROW
- window_rejection [default: true] — Window (short range) rejection enable
Messages
Services
No service files found
Plugins
No plugins found.
Recent questions tagged ouster_driver at Robotics Stack Exchange
No version for distro rolling showing kinetic. Known supported distros are highlighted in the buttons above.
|
|
ouster_driver package from ouster repoouster_driver |
ROS Distro
|
Package Summary
| Tags | No category tags. |
| Version | 0.1.7 |
| License | Apache 2 |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/CPFL/ouster.git |
| VCS Type | git |
| VCS Version | autoware_branch |
| Last Updated | 2019-03-28 |
| 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
OS1 ROS client
Additional Links
No additional links.
Maintainers
- Alexander Carballo
- Abraham Monrroy
Authors
- ouster developers
README
No README found.
No README in repository either.
CHANGELOG
Changelog for package ouster
0.1.7 (2019-03-28)
- Sensor model and firmware version validation
- Added sensor model and firmware version validation. The driver currently only works for OS-1-64 and on firmware version 1.10 some configuration parameters disappeared.
- Parameter validation and new pointcloud types
- Added parameter validation to avoid reinitializing the LiDAR. Added new pointcloud types XYZIRF and XYZIRFN. Changed pulse_mode parameter from integer to string for readability. Updated the readme file.
- Contributors: Alexander Carballo, alexandrx
0.1.6 (2019-03-13)
- Renamed ouster_ros to ouster_driver
0.1.5 (2019-03-13)
- updated package.xml
0.1.4 (2019-03-13)
- Updated project name to follow ros standards
0.1.3 (2019-03-06)
- Updated LICENSE
0.1.2 (2019-03-06)
- Changed operation mode from integer to string to ease reading.
- New pointcloud mode format added
- Improved parameter documentation
- removed the old bool pointcloud_mode_xyzir parameter (to match Velodyne's mode) and replaced with a way to specify the desired pointcloud format, several options added including Ouster's native pointcloud format.
- Added install commands
- run CI on kinetic and melodic only
- Fixed launch file to deal with hidden parameters, fixed readme.md to update the TODO, fixed os1_node.cpp to reduce by half the scan duration variable in case of 20Hz operation.
- Updated the driver to support advanced parameter configuration (lidar-mode, pulse-mode and window-rejection-enable)
- Eliminated the ouster-ros static library
- Updated readme.md incorrect info for lidar address configuration.
- Switched to industrial-ci
- First commit for Autoware version branch. Modified the original Ouster ROS code to suit Autoware needs. Code structure is more simple, only ROS driver code is kept, and the readme.md file has more details on how to configure the sensor and use this driver. To further ease Autoware integration, Velodyne compatibility options were added and tested with nd-_matching, ray-ground-filter and euclidean-cluster nodes.
- Improve positional argument parsing in viz
- Use allocate-shared for Eigen compatibility
- Support building visualizer with newer VTK
- Readme tweaks and new example data
- Update readme.md
- updated the readme to include viz in the contents
- Initial commit of the example visualizer
- Uses VTK6 to display point clouds and range/intensity/noise images
- No dependencies other than VTK6, Eigen3, and a C++11 compiler
- Currently only supports linux; tested on multiple distributions and platforms
- Use correct units in sensor-msgs::Imu
- Deal with time going backwards in replays
- Contributors: Alexander Carballo, Dima Garbuzov, Roy Rinberg, alexandrx, amc-nu, hooic, rafficm, rrinberg
Wiki Tutorials
This package does not provide any links to tutorials in it's rosindex metadata.
You can check on the ROS Wiki Tutorials page for the package.
Package Dependencies
| Deps | Name |
|---|---|
| roscpp | |
| message_generation | |
| std_msgs | |
| sensor_msgs | |
| pcl_ros | |
| pcl_conversions | |
| catkin | |
| message_runtime |
System Dependencies
No direct system dependencies.
Dependant Packages
No known dependants.
Launch files
- launch/os1.launch
- -*- mode: XML -*-
-
- lidar_address [default: 192.168.0.100] — hostname or IP address in dotted decimal form of the Ouster sensor
- pc_address [default: 192.168.0.1] — hostname or IP address of the computer (PC) where the sensor will send data packets
- lidar_port [default: 7502] — port to which the sensor should send lidar data
- imu_port [default: 7503] — port to which the sensor should send imu data
- replay [default: false] — when true, the node will listen on ~/lidar_packets and ~/imu_packets for data instead of attempting to connect to a sensor
- scan_dur_ns [default: 100000000] — nanoseconds to batch lidar packets before publishing a cloud
- pointcloud_mode [default: XYZIR] — Point cloud mode, supported modes: NATIVE, XYZ, XYZI, XYZIR, XYZIF, XYZIRF, XYZIFN, XYZIRFN (I=intensity, R=ring (in ascending order), F=reflectivity, N=ambient noise). NATIVE is XYZIRFt where t=point timestamp and ring follows Ouster's original descending order.
- lidar_frame_name [default: velodyne] — Frame name for lidar output message
- lidar_topic_name [default: /points_raw] — Topic name for lidar output message
- imu_frame_name [default: imu] — Frame name for IMU output message
- imu_topic_name [default: /imu_raw] — Topic name for IMU output message
- operation_mode [default: 1024x10] — Supported operation modes: 512x10, 1024x10, 2048x10, 512x20, 1024x20 (horizontal resolution x scan rate)
- pulse_mode [default: STANDARD] — Laser pulse width, available modes: STANDARD and NARROW
- window_rejection [default: true] — Window (short range) rejection enable
Messages
Services
No service files found
Plugins
No plugins found.
Recent questions tagged ouster_driver at Robotics Stack Exchange
No version for distro ardent showing kinetic. Known supported distros are highlighted in the buttons above.
|
|
ouster_driver package from ouster repoouster_driver |
ROS Distro
|
Package Summary
| Tags | No category tags. |
| Version | 0.1.7 |
| License | Apache 2 |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/CPFL/ouster.git |
| VCS Type | git |
| VCS Version | autoware_branch |
| Last Updated | 2019-03-28 |
| 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
OS1 ROS client
Additional Links
No additional links.
Maintainers
- Alexander Carballo
- Abraham Monrroy
Authors
- ouster developers
README
No README found.
No README in repository either.
CHANGELOG
Changelog for package ouster
0.1.7 (2019-03-28)
- Sensor model and firmware version validation
- Added sensor model and firmware version validation. The driver currently only works for OS-1-64 and on firmware version 1.10 some configuration parameters disappeared.
- Parameter validation and new pointcloud types
- Added parameter validation to avoid reinitializing the LiDAR. Added new pointcloud types XYZIRF and XYZIRFN. Changed pulse_mode parameter from integer to string for readability. Updated the readme file.
- Contributors: Alexander Carballo, alexandrx
0.1.6 (2019-03-13)
- Renamed ouster_ros to ouster_driver
0.1.5 (2019-03-13)
- updated package.xml
0.1.4 (2019-03-13)
- Updated project name to follow ros standards
0.1.3 (2019-03-06)
- Updated LICENSE
0.1.2 (2019-03-06)
- Changed operation mode from integer to string to ease reading.
- New pointcloud mode format added
- Improved parameter documentation
- removed the old bool pointcloud_mode_xyzir parameter (to match Velodyne's mode) and replaced with a way to specify the desired pointcloud format, several options added including Ouster's native pointcloud format.
- Added install commands
- run CI on kinetic and melodic only
- Fixed launch file to deal with hidden parameters, fixed readme.md to update the TODO, fixed os1_node.cpp to reduce by half the scan duration variable in case of 20Hz operation.
- Updated the driver to support advanced parameter configuration (lidar-mode, pulse-mode and window-rejection-enable)
- Eliminated the ouster-ros static library
- Updated readme.md incorrect info for lidar address configuration.
- Switched to industrial-ci
- First commit for Autoware version branch. Modified the original Ouster ROS code to suit Autoware needs. Code structure is more simple, only ROS driver code is kept, and the readme.md file has more details on how to configure the sensor and use this driver. To further ease Autoware integration, Velodyne compatibility options were added and tested with nd-_matching, ray-ground-filter and euclidean-cluster nodes.
- Improve positional argument parsing in viz
- Use allocate-shared for Eigen compatibility
- Support building visualizer with newer VTK
- Readme tweaks and new example data
- Update readme.md
- updated the readme to include viz in the contents
- Initial commit of the example visualizer
- Uses VTK6 to display point clouds and range/intensity/noise images
- No dependencies other than VTK6, Eigen3, and a C++11 compiler
- Currently only supports linux; tested on multiple distributions and platforms
- Use correct units in sensor-msgs::Imu
- Deal with time going backwards in replays
- Contributors: Alexander Carballo, Dima Garbuzov, Roy Rinberg, alexandrx, amc-nu, hooic, rafficm, rrinberg
Wiki Tutorials
This package does not provide any links to tutorials in it's rosindex metadata.
You can check on the ROS Wiki Tutorials page for the package.
Package Dependencies
| Deps | Name |
|---|---|
| roscpp | |
| message_generation | |
| std_msgs | |
| sensor_msgs | |
| pcl_ros | |
| pcl_conversions | |
| catkin | |
| message_runtime |
System Dependencies
No direct system dependencies.
Dependant Packages
No known dependants.
Launch files
- launch/os1.launch
- -*- mode: XML -*-
-
- lidar_address [default: 192.168.0.100] — hostname or IP address in dotted decimal form of the Ouster sensor
- pc_address [default: 192.168.0.1] — hostname or IP address of the computer (PC) where the sensor will send data packets
- lidar_port [default: 7502] — port to which the sensor should send lidar data
- imu_port [default: 7503] — port to which the sensor should send imu data
- replay [default: false] — when true, the node will listen on ~/lidar_packets and ~/imu_packets for data instead of attempting to connect to a sensor
- scan_dur_ns [default: 100000000] — nanoseconds to batch lidar packets before publishing a cloud
- pointcloud_mode [default: XYZIR] — Point cloud mode, supported modes: NATIVE, XYZ, XYZI, XYZIR, XYZIF, XYZIRF, XYZIFN, XYZIRFN (I=intensity, R=ring (in ascending order), F=reflectivity, N=ambient noise). NATIVE is XYZIRFt where t=point timestamp and ring follows Ouster's original descending order.
- lidar_frame_name [default: velodyne] — Frame name for lidar output message
- lidar_topic_name [default: /points_raw] — Topic name for lidar output message
- imu_frame_name [default: imu] — Frame name for IMU output message
- imu_topic_name [default: /imu_raw] — Topic name for IMU output message
- operation_mode [default: 1024x10] — Supported operation modes: 512x10, 1024x10, 2048x10, 512x20, 1024x20 (horizontal resolution x scan rate)
- pulse_mode [default: STANDARD] — Laser pulse width, available modes: STANDARD and NARROW
- window_rejection [default: true] — Window (short range) rejection enable
Messages
Services
No service files found
Plugins
No plugins found.
Recent questions tagged ouster_driver at Robotics Stack Exchange
No version for distro bouncy showing kinetic. Known supported distros are highlighted in the buttons above.
|
|
ouster_driver package from ouster repoouster_driver |
ROS Distro
|
Package Summary
| Tags | No category tags. |
| Version | 0.1.7 |
| License | Apache 2 |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/CPFL/ouster.git |
| VCS Type | git |
| VCS Version | autoware_branch |
| Last Updated | 2019-03-28 |
| 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
OS1 ROS client
Additional Links
No additional links.
Maintainers
- Alexander Carballo
- Abraham Monrroy
Authors
- ouster developers
README
No README found.
No README in repository either.
CHANGELOG
Changelog for package ouster
0.1.7 (2019-03-28)
- Sensor model and firmware version validation
- Added sensor model and firmware version validation. The driver currently only works for OS-1-64 and on firmware version 1.10 some configuration parameters disappeared.
- Parameter validation and new pointcloud types
- Added parameter validation to avoid reinitializing the LiDAR. Added new pointcloud types XYZIRF and XYZIRFN. Changed pulse_mode parameter from integer to string for readability. Updated the readme file.
- Contributors: Alexander Carballo, alexandrx
0.1.6 (2019-03-13)
- Renamed ouster_ros to ouster_driver
0.1.5 (2019-03-13)
- updated package.xml
0.1.4 (2019-03-13)
- Updated project name to follow ros standards
0.1.3 (2019-03-06)
- Updated LICENSE
0.1.2 (2019-03-06)
- Changed operation mode from integer to string to ease reading.
- New pointcloud mode format added
- Improved parameter documentation
- removed the old bool pointcloud_mode_xyzir parameter (to match Velodyne's mode) and replaced with a way to specify the desired pointcloud format, several options added including Ouster's native pointcloud format.
- Added install commands
- run CI on kinetic and melodic only
- Fixed launch file to deal with hidden parameters, fixed readme.md to update the TODO, fixed os1_node.cpp to reduce by half the scan duration variable in case of 20Hz operation.
- Updated the driver to support advanced parameter configuration (lidar-mode, pulse-mode and window-rejection-enable)
- Eliminated the ouster-ros static library
- Updated readme.md incorrect info for lidar address configuration.
- Switched to industrial-ci
- First commit for Autoware version branch. Modified the original Ouster ROS code to suit Autoware needs. Code structure is more simple, only ROS driver code is kept, and the readme.md file has more details on how to configure the sensor and use this driver. To further ease Autoware integration, Velodyne compatibility options were added and tested with nd-_matching, ray-ground-filter and euclidean-cluster nodes.
- Improve positional argument parsing in viz
- Use allocate-shared for Eigen compatibility
- Support building visualizer with newer VTK
- Readme tweaks and new example data
- Update readme.md
- updated the readme to include viz in the contents
- Initial commit of the example visualizer
- Uses VTK6 to display point clouds and range/intensity/noise images
- No dependencies other than VTK6, Eigen3, and a C++11 compiler
- Currently only supports linux; tested on multiple distributions and platforms
- Use correct units in sensor-msgs::Imu
- Deal with time going backwards in replays
- Contributors: Alexander Carballo, Dima Garbuzov, Roy Rinberg, alexandrx, amc-nu, hooic, rafficm, rrinberg
Wiki Tutorials
This package does not provide any links to tutorials in it's rosindex metadata.
You can check on the ROS Wiki Tutorials page for the package.
Package Dependencies
| Deps | Name |
|---|---|
| roscpp | |
| message_generation | |
| std_msgs | |
| sensor_msgs | |
| pcl_ros | |
| pcl_conversions | |
| catkin | |
| message_runtime |
System Dependencies
No direct system dependencies.
Dependant Packages
No known dependants.
Launch files
- launch/os1.launch
- -*- mode: XML -*-
-
- lidar_address [default: 192.168.0.100] — hostname or IP address in dotted decimal form of the Ouster sensor
- pc_address [default: 192.168.0.1] — hostname or IP address of the computer (PC) where the sensor will send data packets
- lidar_port [default: 7502] — port to which the sensor should send lidar data
- imu_port [default: 7503] — port to which the sensor should send imu data
- replay [default: false] — when true, the node will listen on ~/lidar_packets and ~/imu_packets for data instead of attempting to connect to a sensor
- scan_dur_ns [default: 100000000] — nanoseconds to batch lidar packets before publishing a cloud
- pointcloud_mode [default: XYZIR] — Point cloud mode, supported modes: NATIVE, XYZ, XYZI, XYZIR, XYZIF, XYZIRF, XYZIFN, XYZIRFN (I=intensity, R=ring (in ascending order), F=reflectivity, N=ambient noise). NATIVE is XYZIRFt where t=point timestamp and ring follows Ouster's original descending order.
- lidar_frame_name [default: velodyne] — Frame name for lidar output message
- lidar_topic_name [default: /points_raw] — Topic name for lidar output message
- imu_frame_name [default: imu] — Frame name for IMU output message
- imu_topic_name [default: /imu_raw] — Topic name for IMU output message
- operation_mode [default: 1024x10] — Supported operation modes: 512x10, 1024x10, 2048x10, 512x20, 1024x20 (horizontal resolution x scan rate)
- pulse_mode [default: STANDARD] — Laser pulse width, available modes: STANDARD and NARROW
- window_rejection [default: true] — Window (short range) rejection enable
Messages
Services
No service files found
Plugins
No plugins found.
Recent questions tagged ouster_driver at Robotics Stack Exchange
No version for distro crystal showing kinetic. Known supported distros are highlighted in the buttons above.
|
|
ouster_driver package from ouster repoouster_driver |
ROS Distro
|
Package Summary
| Tags | No category tags. |
| Version | 0.1.7 |
| License | Apache 2 |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/CPFL/ouster.git |
| VCS Type | git |
| VCS Version | autoware_branch |
| Last Updated | 2019-03-28 |
| 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
OS1 ROS client
Additional Links
No additional links.
Maintainers
- Alexander Carballo
- Abraham Monrroy
Authors
- ouster developers
README
No README found.
No README in repository either.
CHANGELOG
Changelog for package ouster
0.1.7 (2019-03-28)
- Sensor model and firmware version validation
- Added sensor model and firmware version validation. The driver currently only works for OS-1-64 and on firmware version 1.10 some configuration parameters disappeared.
- Parameter validation and new pointcloud types
- Added parameter validation to avoid reinitializing the LiDAR. Added new pointcloud types XYZIRF and XYZIRFN. Changed pulse_mode parameter from integer to string for readability. Updated the readme file.
- Contributors: Alexander Carballo, alexandrx
0.1.6 (2019-03-13)
- Renamed ouster_ros to ouster_driver
0.1.5 (2019-03-13)
- updated package.xml
0.1.4 (2019-03-13)
- Updated project name to follow ros standards
0.1.3 (2019-03-06)
- Updated LICENSE
0.1.2 (2019-03-06)
- Changed operation mode from integer to string to ease reading.
- New pointcloud mode format added
- Improved parameter documentation
- removed the old bool pointcloud_mode_xyzir parameter (to match Velodyne's mode) and replaced with a way to specify the desired pointcloud format, several options added including Ouster's native pointcloud format.
- Added install commands
- run CI on kinetic and melodic only
- Fixed launch file to deal with hidden parameters, fixed readme.md to update the TODO, fixed os1_node.cpp to reduce by half the scan duration variable in case of 20Hz operation.
- Updated the driver to support advanced parameter configuration (lidar-mode, pulse-mode and window-rejection-enable)
- Eliminated the ouster-ros static library
- Updated readme.md incorrect info for lidar address configuration.
- Switched to industrial-ci
- First commit for Autoware version branch. Modified the original Ouster ROS code to suit Autoware needs. Code structure is more simple, only ROS driver code is kept, and the readme.md file has more details on how to configure the sensor and use this driver. To further ease Autoware integration, Velodyne compatibility options were added and tested with nd-_matching, ray-ground-filter and euclidean-cluster nodes.
- Improve positional argument parsing in viz
- Use allocate-shared for Eigen compatibility
- Support building visualizer with newer VTK
- Readme tweaks and new example data
- Update readme.md
- updated the readme to include viz in the contents
- Initial commit of the example visualizer
- Uses VTK6 to display point clouds and range/intensity/noise images
- No dependencies other than VTK6, Eigen3, and a C++11 compiler
- Currently only supports linux; tested on multiple distributions and platforms
- Use correct units in sensor-msgs::Imu
- Deal with time going backwards in replays
- Contributors: Alexander Carballo, Dima Garbuzov, Roy Rinberg, alexandrx, amc-nu, hooic, rafficm, rrinberg
Wiki Tutorials
This package does not provide any links to tutorials in it's rosindex metadata.
You can check on the ROS Wiki Tutorials page for the package.
Package Dependencies
| Deps | Name |
|---|---|
| roscpp | |
| message_generation | |
| std_msgs | |
| sensor_msgs | |
| pcl_ros | |
| pcl_conversions | |
| catkin | |
| message_runtime |
System Dependencies
No direct system dependencies.
Dependant Packages
No known dependants.
Launch files
- launch/os1.launch
- -*- mode: XML -*-
-
- lidar_address [default: 192.168.0.100] — hostname or IP address in dotted decimal form of the Ouster sensor
- pc_address [default: 192.168.0.1] — hostname or IP address of the computer (PC) where the sensor will send data packets
- lidar_port [default: 7502] — port to which the sensor should send lidar data
- imu_port [default: 7503] — port to which the sensor should send imu data
- replay [default: false] — when true, the node will listen on ~/lidar_packets and ~/imu_packets for data instead of attempting to connect to a sensor
- scan_dur_ns [default: 100000000] — nanoseconds to batch lidar packets before publishing a cloud
- pointcloud_mode [default: XYZIR] — Point cloud mode, supported modes: NATIVE, XYZ, XYZI, XYZIR, XYZIF, XYZIRF, XYZIFN, XYZIRFN (I=intensity, R=ring (in ascending order), F=reflectivity, N=ambient noise). NATIVE is XYZIRFt where t=point timestamp and ring follows Ouster's original descending order.
- lidar_frame_name [default: velodyne] — Frame name for lidar output message
- lidar_topic_name [default: /points_raw] — Topic name for lidar output message
- imu_frame_name [default: imu] — Frame name for IMU output message
- imu_topic_name [default: /imu_raw] — Topic name for IMU output message
- operation_mode [default: 1024x10] — Supported operation modes: 512x10, 1024x10, 2048x10, 512x20, 1024x20 (horizontal resolution x scan rate)
- pulse_mode [default: STANDARD] — Laser pulse width, available modes: STANDARD and NARROW
- window_rejection [default: true] — Window (short range) rejection enable
Messages
Services
No service files found
Plugins
No plugins found.
Recent questions tagged ouster_driver at Robotics Stack Exchange
No version for distro eloquent showing kinetic. Known supported distros are highlighted in the buttons above.
|
|
ouster_driver package from ouster repoouster_driver |
ROS Distro
|
Package Summary
| Tags | No category tags. |
| Version | 0.1.7 |
| License | Apache 2 |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/CPFL/ouster.git |
| VCS Type | git |
| VCS Version | autoware_branch |
| Last Updated | 2019-03-28 |
| 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
OS1 ROS client
Additional Links
No additional links.
Maintainers
- Alexander Carballo
- Abraham Monrroy
Authors
- ouster developers
README
No README found.
No README in repository either.
CHANGELOG
Changelog for package ouster
0.1.7 (2019-03-28)
- Sensor model and firmware version validation
- Added sensor model and firmware version validation. The driver currently only works for OS-1-64 and on firmware version 1.10 some configuration parameters disappeared.
- Parameter validation and new pointcloud types
- Added parameter validation to avoid reinitializing the LiDAR. Added new pointcloud types XYZIRF and XYZIRFN. Changed pulse_mode parameter from integer to string for readability. Updated the readme file.
- Contributors: Alexander Carballo, alexandrx
0.1.6 (2019-03-13)
- Renamed ouster_ros to ouster_driver
0.1.5 (2019-03-13)
- updated package.xml
0.1.4 (2019-03-13)
- Updated project name to follow ros standards
0.1.3 (2019-03-06)
- Updated LICENSE
0.1.2 (2019-03-06)
- Changed operation mode from integer to string to ease reading.
- New pointcloud mode format added
- Improved parameter documentation
- removed the old bool pointcloud_mode_xyzir parameter (to match Velodyne's mode) and replaced with a way to specify the desired pointcloud format, several options added including Ouster's native pointcloud format.
- Added install commands
- run CI on kinetic and melodic only
- Fixed launch file to deal with hidden parameters, fixed readme.md to update the TODO, fixed os1_node.cpp to reduce by half the scan duration variable in case of 20Hz operation.
- Updated the driver to support advanced parameter configuration (lidar-mode, pulse-mode and window-rejection-enable)
- Eliminated the ouster-ros static library
- Updated readme.md incorrect info for lidar address configuration.
- Switched to industrial-ci
- First commit for Autoware version branch. Modified the original Ouster ROS code to suit Autoware needs. Code structure is more simple, only ROS driver code is kept, and the readme.md file has more details on how to configure the sensor and use this driver. To further ease Autoware integration, Velodyne compatibility options were added and tested with nd-_matching, ray-ground-filter and euclidean-cluster nodes.
- Improve positional argument parsing in viz
- Use allocate-shared for Eigen compatibility
- Support building visualizer with newer VTK
- Readme tweaks and new example data
- Update readme.md
- updated the readme to include viz in the contents
- Initial commit of the example visualizer
- Uses VTK6 to display point clouds and range/intensity/noise images
- No dependencies other than VTK6, Eigen3, and a C++11 compiler
- Currently only supports linux; tested on multiple distributions and platforms
- Use correct units in sensor-msgs::Imu
- Deal with time going backwards in replays
- Contributors: Alexander Carballo, Dima Garbuzov, Roy Rinberg, alexandrx, amc-nu, hooic, rafficm, rrinberg
Wiki Tutorials
This package does not provide any links to tutorials in it's rosindex metadata.
You can check on the ROS Wiki Tutorials page for the package.
Package Dependencies
| Deps | Name |
|---|---|
| roscpp | |
| message_generation | |
| std_msgs | |
| sensor_msgs | |
| pcl_ros | |
| pcl_conversions | |
| catkin | |
| message_runtime |
System Dependencies
No direct system dependencies.
Dependant Packages
No known dependants.
Launch files
- launch/os1.launch
- -*- mode: XML -*-
-
- lidar_address [default: 192.168.0.100] — hostname or IP address in dotted decimal form of the Ouster sensor
- pc_address [default: 192.168.0.1] — hostname or IP address of the computer (PC) where the sensor will send data packets
- lidar_port [default: 7502] — port to which the sensor should send lidar data
- imu_port [default: 7503] — port to which the sensor should send imu data
- replay [default: false] — when true, the node will listen on ~/lidar_packets and ~/imu_packets for data instead of attempting to connect to a sensor
- scan_dur_ns [default: 100000000] — nanoseconds to batch lidar packets before publishing a cloud
- pointcloud_mode [default: XYZIR] — Point cloud mode, supported modes: NATIVE, XYZ, XYZI, XYZIR, XYZIF, XYZIRF, XYZIFN, XYZIRFN (I=intensity, R=ring (in ascending order), F=reflectivity, N=ambient noise). NATIVE is XYZIRFt where t=point timestamp and ring follows Ouster's original descending order.
- lidar_frame_name [default: velodyne] — Frame name for lidar output message
- lidar_topic_name [default: /points_raw] — Topic name for lidar output message
- imu_frame_name [default: imu] — Frame name for IMU output message
- imu_topic_name [default: /imu_raw] — Topic name for IMU output message
- operation_mode [default: 1024x10] — Supported operation modes: 512x10, 1024x10, 2048x10, 512x20, 1024x20 (horizontal resolution x scan rate)
- pulse_mode [default: STANDARD] — Laser pulse width, available modes: STANDARD and NARROW
- window_rejection [default: true] — Window (short range) rejection enable
Messages
Services
No service files found
Plugins
No plugins found.
Recent questions tagged ouster_driver at Robotics Stack Exchange
No version for distro dashing showing kinetic. Known supported distros are highlighted in the buttons above.
|
|
ouster_driver package from ouster repoouster_driver |
ROS Distro
|
Package Summary
| Tags | No category tags. |
| Version | 0.1.7 |
| License | Apache 2 |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/CPFL/ouster.git |
| VCS Type | git |
| VCS Version | autoware_branch |
| Last Updated | 2019-03-28 |
| 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
OS1 ROS client
Additional Links
No additional links.
Maintainers
- Alexander Carballo
- Abraham Monrroy
Authors
- ouster developers
README
No README found.
No README in repository either.
CHANGELOG
Changelog for package ouster
0.1.7 (2019-03-28)
- Sensor model and firmware version validation
- Added sensor model and firmware version validation. The driver currently only works for OS-1-64 and on firmware version 1.10 some configuration parameters disappeared.
- Parameter validation and new pointcloud types
- Added parameter validation to avoid reinitializing the LiDAR. Added new pointcloud types XYZIRF and XYZIRFN. Changed pulse_mode parameter from integer to string for readability. Updated the readme file.
- Contributors: Alexander Carballo, alexandrx
0.1.6 (2019-03-13)
- Renamed ouster_ros to ouster_driver
0.1.5 (2019-03-13)
- updated package.xml
0.1.4 (2019-03-13)
- Updated project name to follow ros standards
0.1.3 (2019-03-06)
- Updated LICENSE
0.1.2 (2019-03-06)
- Changed operation mode from integer to string to ease reading.
- New pointcloud mode format added
- Improved parameter documentation
- removed the old bool pointcloud_mode_xyzir parameter (to match Velodyne's mode) and replaced with a way to specify the desired pointcloud format, several options added including Ouster's native pointcloud format.
- Added install commands
- run CI on kinetic and melodic only
- Fixed launch file to deal with hidden parameters, fixed readme.md to update the TODO, fixed os1_node.cpp to reduce by half the scan duration variable in case of 20Hz operation.
- Updated the driver to support advanced parameter configuration (lidar-mode, pulse-mode and window-rejection-enable)
- Eliminated the ouster-ros static library
- Updated readme.md incorrect info for lidar address configuration.
- Switched to industrial-ci
- First commit for Autoware version branch. Modified the original Ouster ROS code to suit Autoware needs. Code structure is more simple, only ROS driver code is kept, and the readme.md file has more details on how to configure the sensor and use this driver. To further ease Autoware integration, Velodyne compatibility options were added and tested with nd-_matching, ray-ground-filter and euclidean-cluster nodes.
- Improve positional argument parsing in viz
- Use allocate-shared for Eigen compatibility
- Support building visualizer with newer VTK
- Readme tweaks and new example data
- Update readme.md
- updated the readme to include viz in the contents
- Initial commit of the example visualizer
- Uses VTK6 to display point clouds and range/intensity/noise images
- No dependencies other than VTK6, Eigen3, and a C++11 compiler
- Currently only supports linux; tested on multiple distributions and platforms
- Use correct units in sensor-msgs::Imu
- Deal with time going backwards in replays
- Contributors: Alexander Carballo, Dima Garbuzov, Roy Rinberg, alexandrx, amc-nu, hooic, rafficm, rrinberg
Wiki Tutorials
This package does not provide any links to tutorials in it's rosindex metadata.
You can check on the ROS Wiki Tutorials page for the package.
Package Dependencies
| Deps | Name |
|---|---|
| roscpp | |
| message_generation | |
| std_msgs | |
| sensor_msgs | |
| pcl_ros | |
| pcl_conversions | |
| catkin | |
| message_runtime |
System Dependencies
No direct system dependencies.
Dependant Packages
No known dependants.
Launch files
- launch/os1.launch
- -*- mode: XML -*-
-
- lidar_address [default: 192.168.0.100] — hostname or IP address in dotted decimal form of the Ouster sensor
- pc_address [default: 192.168.0.1] — hostname or IP address of the computer (PC) where the sensor will send data packets
- lidar_port [default: 7502] — port to which the sensor should send lidar data
- imu_port [default: 7503] — port to which the sensor should send imu data
- replay [default: false] — when true, the node will listen on ~/lidar_packets and ~/imu_packets for data instead of attempting to connect to a sensor
- scan_dur_ns [default: 100000000] — nanoseconds to batch lidar packets before publishing a cloud
- pointcloud_mode [default: XYZIR] — Point cloud mode, supported modes: NATIVE, XYZ, XYZI, XYZIR, XYZIF, XYZIRF, XYZIFN, XYZIRFN (I=intensity, R=ring (in ascending order), F=reflectivity, N=ambient noise). NATIVE is XYZIRFt where t=point timestamp and ring follows Ouster's original descending order.
- lidar_frame_name [default: velodyne] — Frame name for lidar output message
- lidar_topic_name [default: /points_raw] — Topic name for lidar output message
- imu_frame_name [default: imu] — Frame name for IMU output message
- imu_topic_name [default: /imu_raw] — Topic name for IMU output message
- operation_mode [default: 1024x10] — Supported operation modes: 512x10, 1024x10, 2048x10, 512x20, 1024x20 (horizontal resolution x scan rate)
- pulse_mode [default: STANDARD] — Laser pulse width, available modes: STANDARD and NARROW
- window_rejection [default: true] — Window (short range) rejection enable
Messages
Services
No service files found
Plugins
No plugins found.
Recent questions tagged ouster_driver at Robotics Stack Exchange
No version for distro galactic showing kinetic. Known supported distros are highlighted in the buttons above.
|
|
ouster_driver package from ouster repoouster_driver |
ROS Distro
|
Package Summary
| Tags | No category tags. |
| Version | 0.1.7 |
| License | Apache 2 |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/CPFL/ouster.git |
| VCS Type | git |
| VCS Version | autoware_branch |
| Last Updated | 2019-03-28 |
| 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
OS1 ROS client
Additional Links
No additional links.
Maintainers
- Alexander Carballo
- Abraham Monrroy
Authors
- ouster developers
README
No README found.
No README in repository either.
CHANGELOG
Changelog for package ouster
0.1.7 (2019-03-28)
- Sensor model and firmware version validation
- Added sensor model and firmware version validation. The driver currently only works for OS-1-64 and on firmware version 1.10 some configuration parameters disappeared.
- Parameter validation and new pointcloud types
- Added parameter validation to avoid reinitializing the LiDAR. Added new pointcloud types XYZIRF and XYZIRFN. Changed pulse_mode parameter from integer to string for readability. Updated the readme file.
- Contributors: Alexander Carballo, alexandrx
0.1.6 (2019-03-13)
- Renamed ouster_ros to ouster_driver
0.1.5 (2019-03-13)
- updated package.xml
0.1.4 (2019-03-13)
- Updated project name to follow ros standards
0.1.3 (2019-03-06)
- Updated LICENSE
0.1.2 (2019-03-06)
- Changed operation mode from integer to string to ease reading.
- New pointcloud mode format added
- Improved parameter documentation
- removed the old bool pointcloud_mode_xyzir parameter (to match Velodyne's mode) and replaced with a way to specify the desired pointcloud format, several options added including Ouster's native pointcloud format.
- Added install commands
- run CI on kinetic and melodic only
- Fixed launch file to deal with hidden parameters, fixed readme.md to update the TODO, fixed os1_node.cpp to reduce by half the scan duration variable in case of 20Hz operation.
- Updated the driver to support advanced parameter configuration (lidar-mode, pulse-mode and window-rejection-enable)
- Eliminated the ouster-ros static library
- Updated readme.md incorrect info for lidar address configuration.
- Switched to industrial-ci
- First commit for Autoware version branch. Modified the original Ouster ROS code to suit Autoware needs. Code structure is more simple, only ROS driver code is kept, and the readme.md file has more details on how to configure the sensor and use this driver. To further ease Autoware integration, Velodyne compatibility options were added and tested with nd-_matching, ray-ground-filter and euclidean-cluster nodes.
- Improve positional argument parsing in viz
- Use allocate-shared for Eigen compatibility
- Support building visualizer with newer VTK
- Readme tweaks and new example data
- Update readme.md
- updated the readme to include viz in the contents
- Initial commit of the example visualizer
- Uses VTK6 to display point clouds and range/intensity/noise images
- No dependencies other than VTK6, Eigen3, and a C++11 compiler
- Currently only supports linux; tested on multiple distributions and platforms
- Use correct units in sensor-msgs::Imu
- Deal with time going backwards in replays
- Contributors: Alexander Carballo, Dima Garbuzov, Roy Rinberg, alexandrx, amc-nu, hooic, rafficm, rrinberg
Wiki Tutorials
This package does not provide any links to tutorials in it's rosindex metadata.
You can check on the ROS Wiki Tutorials page for the package.
Package Dependencies
| Deps | Name |
|---|---|
| roscpp | |
| message_generation | |
| std_msgs | |
| sensor_msgs | |
| pcl_ros | |
| pcl_conversions | |
| catkin | |
| message_runtime |
System Dependencies
No direct system dependencies.
Dependant Packages
No known dependants.
Launch files
- launch/os1.launch
- -*- mode: XML -*-
-
- lidar_address [default: 192.168.0.100] — hostname or IP address in dotted decimal form of the Ouster sensor
- pc_address [default: 192.168.0.1] — hostname or IP address of the computer (PC) where the sensor will send data packets
- lidar_port [default: 7502] — port to which the sensor should send lidar data
- imu_port [default: 7503] — port to which the sensor should send imu data
- replay [default: false] — when true, the node will listen on ~/lidar_packets and ~/imu_packets for data instead of attempting to connect to a sensor
- scan_dur_ns [default: 100000000] — nanoseconds to batch lidar packets before publishing a cloud
- pointcloud_mode [default: XYZIR] — Point cloud mode, supported modes: NATIVE, XYZ, XYZI, XYZIR, XYZIF, XYZIRF, XYZIFN, XYZIRFN (I=intensity, R=ring (in ascending order), F=reflectivity, N=ambient noise). NATIVE is XYZIRFt where t=point timestamp and ring follows Ouster's original descending order.
- lidar_frame_name [default: velodyne] — Frame name for lidar output message
- lidar_topic_name [default: /points_raw] — Topic name for lidar output message
- imu_frame_name [default: imu] — Frame name for IMU output message
- imu_topic_name [default: /imu_raw] — Topic name for IMU output message
- operation_mode [default: 1024x10] — Supported operation modes: 512x10, 1024x10, 2048x10, 512x20, 1024x20 (horizontal resolution x scan rate)
- pulse_mode [default: STANDARD] — Laser pulse width, available modes: STANDARD and NARROW
- window_rejection [default: true] — Window (short range) rejection enable
Messages
Services
No service files found
Plugins
No plugins found.
Recent questions tagged ouster_driver at Robotics Stack Exchange
No version for distro foxy showing kinetic. Known supported distros are highlighted in the buttons above.
|
|
ouster_driver package from ouster repoouster_driver |
ROS Distro
|
Package Summary
| Tags | No category tags. |
| Version | 0.1.7 |
| License | Apache 2 |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/CPFL/ouster.git |
| VCS Type | git |
| VCS Version | autoware_branch |
| Last Updated | 2019-03-28 |
| 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
OS1 ROS client
Additional Links
No additional links.
Maintainers
- Alexander Carballo
- Abraham Monrroy
Authors
- ouster developers
README
No README found.
No README in repository either.
CHANGELOG
Changelog for package ouster
0.1.7 (2019-03-28)
- Sensor model and firmware version validation
- Added sensor model and firmware version validation. The driver currently only works for OS-1-64 and on firmware version 1.10 some configuration parameters disappeared.
- Parameter validation and new pointcloud types
- Added parameter validation to avoid reinitializing the LiDAR. Added new pointcloud types XYZIRF and XYZIRFN. Changed pulse_mode parameter from integer to string for readability. Updated the readme file.
- Contributors: Alexander Carballo, alexandrx
0.1.6 (2019-03-13)
- Renamed ouster_ros to ouster_driver
0.1.5 (2019-03-13)
- updated package.xml
0.1.4 (2019-03-13)
- Updated project name to follow ros standards
0.1.3 (2019-03-06)
- Updated LICENSE
0.1.2 (2019-03-06)
- Changed operation mode from integer to string to ease reading.
- New pointcloud mode format added
- Improved parameter documentation
- removed the old bool pointcloud_mode_xyzir parameter (to match Velodyne's mode) and replaced with a way to specify the desired pointcloud format, several options added including Ouster's native pointcloud format.
- Added install commands
- run CI on kinetic and melodic only
- Fixed launch file to deal with hidden parameters, fixed readme.md to update the TODO, fixed os1_node.cpp to reduce by half the scan duration variable in case of 20Hz operation.
- Updated the driver to support advanced parameter configuration (lidar-mode, pulse-mode and window-rejection-enable)
- Eliminated the ouster-ros static library
- Updated readme.md incorrect info for lidar address configuration.
- Switched to industrial-ci
- First commit for Autoware version branch. Modified the original Ouster ROS code to suit Autoware needs. Code structure is more simple, only ROS driver code is kept, and the readme.md file has more details on how to configure the sensor and use this driver. To further ease Autoware integration, Velodyne compatibility options were added and tested with nd-_matching, ray-ground-filter and euclidean-cluster nodes.
- Improve positional argument parsing in viz
- Use allocate-shared for Eigen compatibility
- Support building visualizer with newer VTK
- Readme tweaks and new example data
- Update readme.md
- updated the readme to include viz in the contents
- Initial commit of the example visualizer
- Uses VTK6 to display point clouds and range/intensity/noise images
- No dependencies other than VTK6, Eigen3, and a C++11 compiler
- Currently only supports linux; tested on multiple distributions and platforms
- Use correct units in sensor-msgs::Imu
- Deal with time going backwards in replays
- Contributors: Alexander Carballo, Dima Garbuzov, Roy Rinberg, alexandrx, amc-nu, hooic, rafficm, rrinberg
Wiki Tutorials
This package does not provide any links to tutorials in it's rosindex metadata.
You can check on the ROS Wiki Tutorials page for the package.
Package Dependencies
| Deps | Name |
|---|---|
| roscpp | |
| message_generation | |
| std_msgs | |
| sensor_msgs | |
| pcl_ros | |
| pcl_conversions | |
| catkin | |
| message_runtime |
System Dependencies
No direct system dependencies.
Dependant Packages
No known dependants.
Launch files
- launch/os1.launch
- -*- mode: XML -*-
-
- lidar_address [default: 192.168.0.100] — hostname or IP address in dotted decimal form of the Ouster sensor
- pc_address [default: 192.168.0.1] — hostname or IP address of the computer (PC) where the sensor will send data packets
- lidar_port [default: 7502] — port to which the sensor should send lidar data
- imu_port [default: 7503] — port to which the sensor should send imu data
- replay [default: false] — when true, the node will listen on ~/lidar_packets and ~/imu_packets for data instead of attempting to connect to a sensor
- scan_dur_ns [default: 100000000] — nanoseconds to batch lidar packets before publishing a cloud
- pointcloud_mode [default: XYZIR] — Point cloud mode, supported modes: NATIVE, XYZ, XYZI, XYZIR, XYZIF, XYZIRF, XYZIFN, XYZIRFN (I=intensity, R=ring (in ascending order), F=reflectivity, N=ambient noise). NATIVE is XYZIRFt where t=point timestamp and ring follows Ouster's original descending order.
- lidar_frame_name [default: velodyne] — Frame name for lidar output message
- lidar_topic_name [default: /points_raw] — Topic name for lidar output message
- imu_frame_name [default: imu] — Frame name for IMU output message
- imu_topic_name [default: /imu_raw] — Topic name for IMU output message
- operation_mode [default: 1024x10] — Supported operation modes: 512x10, 1024x10, 2048x10, 512x20, 1024x20 (horizontal resolution x scan rate)
- pulse_mode [default: STANDARD] — Laser pulse width, available modes: STANDARD and NARROW
- window_rejection [default: true] — Window (short range) rejection enable
Messages
Services
No service files found
Plugins
No plugins found.
Recent questions tagged ouster_driver at Robotics Stack Exchange
No version for distro iron showing kinetic. Known supported distros are highlighted in the buttons above.
|
|
ouster_driver package from ouster repoouster_driver |
ROS Distro
|
Package Summary
| Tags | No category tags. |
| Version | 0.1.7 |
| License | Apache 2 |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/CPFL/ouster.git |
| VCS Type | git |
| VCS Version | autoware_branch |
| Last Updated | 2019-03-28 |
| 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
OS1 ROS client
Additional Links
No additional links.
Maintainers
- Alexander Carballo
- Abraham Monrroy
Authors
- ouster developers
README
No README found.
No README in repository either.
CHANGELOG
Changelog for package ouster
0.1.7 (2019-03-28)
- Sensor model and firmware version validation
- Added sensor model and firmware version validation. The driver currently only works for OS-1-64 and on firmware version 1.10 some configuration parameters disappeared.
- Parameter validation and new pointcloud types
- Added parameter validation to avoid reinitializing the LiDAR. Added new pointcloud types XYZIRF and XYZIRFN. Changed pulse_mode parameter from integer to string for readability. Updated the readme file.
- Contributors: Alexander Carballo, alexandrx
0.1.6 (2019-03-13)
- Renamed ouster_ros to ouster_driver
0.1.5 (2019-03-13)
- updated package.xml
0.1.4 (2019-03-13)
- Updated project name to follow ros standards
0.1.3 (2019-03-06)
- Updated LICENSE
0.1.2 (2019-03-06)
- Changed operation mode from integer to string to ease reading.
- New pointcloud mode format added
- Improved parameter documentation
- removed the old bool pointcloud_mode_xyzir parameter (to match Velodyne's mode) and replaced with a way to specify the desired pointcloud format, several options added including Ouster's native pointcloud format.
- Added install commands
- run CI on kinetic and melodic only
- Fixed launch file to deal with hidden parameters, fixed readme.md to update the TODO, fixed os1_node.cpp to reduce by half the scan duration variable in case of 20Hz operation.
- Updated the driver to support advanced parameter configuration (lidar-mode, pulse-mode and window-rejection-enable)
- Eliminated the ouster-ros static library
- Updated readme.md incorrect info for lidar address configuration.
- Switched to industrial-ci
- First commit for Autoware version branch. Modified the original Ouster ROS code to suit Autoware needs. Code structure is more simple, only ROS driver code is kept, and the readme.md file has more details on how to configure the sensor and use this driver. To further ease Autoware integration, Velodyne compatibility options were added and tested with nd-_matching, ray-ground-filter and euclidean-cluster nodes.
- Improve positional argument parsing in viz
- Use allocate-shared for Eigen compatibility
- Support building visualizer with newer VTK
- Readme tweaks and new example data
- Update readme.md
- updated the readme to include viz in the contents
- Initial commit of the example visualizer
- Uses VTK6 to display point clouds and range/intensity/noise images
- No dependencies other than VTK6, Eigen3, and a C++11 compiler
- Currently only supports linux; tested on multiple distributions and platforms
- Use correct units in sensor-msgs::Imu
- Deal with time going backwards in replays
- Contributors: Alexander Carballo, Dima Garbuzov, Roy Rinberg, alexandrx, amc-nu, hooic, rafficm, rrinberg
Wiki Tutorials
This package does not provide any links to tutorials in it's rosindex metadata.
You can check on the ROS Wiki Tutorials page for the package.
Package Dependencies
| Deps | Name |
|---|---|
| roscpp | |
| message_generation | |
| std_msgs | |
| sensor_msgs | |
| pcl_ros | |
| pcl_conversions | |
| catkin | |
| message_runtime |
System Dependencies
No direct system dependencies.
Dependant Packages
No known dependants.
Launch files
- launch/os1.launch
- -*- mode: XML -*-
-
- lidar_address [default: 192.168.0.100] — hostname or IP address in dotted decimal form of the Ouster sensor
- pc_address [default: 192.168.0.1] — hostname or IP address of the computer (PC) where the sensor will send data packets
- lidar_port [default: 7502] — port to which the sensor should send lidar data
- imu_port [default: 7503] — port to which the sensor should send imu data
- replay [default: false] — when true, the node will listen on ~/lidar_packets and ~/imu_packets for data instead of attempting to connect to a sensor
- scan_dur_ns [default: 100000000] — nanoseconds to batch lidar packets before publishing a cloud
- pointcloud_mode [default: XYZIR] — Point cloud mode, supported modes: NATIVE, XYZ, XYZI, XYZIR, XYZIF, XYZIRF, XYZIFN, XYZIRFN (I=intensity, R=ring (in ascending order), F=reflectivity, N=ambient noise). NATIVE is XYZIRFt where t=point timestamp and ring follows Ouster's original descending order.
- lidar_frame_name [default: velodyne] — Frame name for lidar output message
- lidar_topic_name [default: /points_raw] — Topic name for lidar output message
- imu_frame_name [default: imu] — Frame name for IMU output message
- imu_topic_name [default: /imu_raw] — Topic name for IMU output message
- operation_mode [default: 1024x10] — Supported operation modes: 512x10, 1024x10, 2048x10, 512x20, 1024x20 (horizontal resolution x scan rate)
- pulse_mode [default: STANDARD] — Laser pulse width, available modes: STANDARD and NARROW
- window_rejection [default: true] — Window (short range) rejection enable
Messages
Services
No service files found
Plugins
No plugins found.
Recent questions tagged ouster_driver at Robotics Stack Exchange
No version for distro lunar showing kinetic. Known supported distros are highlighted in the buttons above.
|
|
ouster_driver package from ouster repoouster_driver |
ROS Distro
|
Package Summary
| Tags | No category tags. |
| Version | 0.1.7 |
| License | Apache 2 |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/CPFL/ouster.git |
| VCS Type | git |
| VCS Version | autoware_branch |
| Last Updated | 2019-03-28 |
| 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
OS1 ROS client
Additional Links
No additional links.
Maintainers
- Alexander Carballo
- Abraham Monrroy
Authors
- ouster developers
README
No README found.
No README in repository either.
CHANGELOG
Changelog for package ouster
0.1.7 (2019-03-28)
- Sensor model and firmware version validation
- Added sensor model and firmware version validation. The driver currently only works for OS-1-64 and on firmware version 1.10 some configuration parameters disappeared.
- Parameter validation and new pointcloud types
- Added parameter validation to avoid reinitializing the LiDAR. Added new pointcloud types XYZIRF and XYZIRFN. Changed pulse_mode parameter from integer to string for readability. Updated the readme file.
- Contributors: Alexander Carballo, alexandrx
0.1.6 (2019-03-13)
- Renamed ouster_ros to ouster_driver
0.1.5 (2019-03-13)
- updated package.xml
0.1.4 (2019-03-13)
- Updated project name to follow ros standards
0.1.3 (2019-03-06)
- Updated LICENSE
0.1.2 (2019-03-06)
- Changed operation mode from integer to string to ease reading.
- New pointcloud mode format added
- Improved parameter documentation
- removed the old bool pointcloud_mode_xyzir parameter (to match Velodyne's mode) and replaced with a way to specify the desired pointcloud format, several options added including Ouster's native pointcloud format.
- Added install commands
- run CI on kinetic and melodic only
- Fixed launch file to deal with hidden parameters, fixed readme.md to update the TODO, fixed os1_node.cpp to reduce by half the scan duration variable in case of 20Hz operation.
- Updated the driver to support advanced parameter configuration (lidar-mode, pulse-mode and window-rejection-enable)
- Eliminated the ouster-ros static library
- Updated readme.md incorrect info for lidar address configuration.
- Switched to industrial-ci
- First commit for Autoware version branch. Modified the original Ouster ROS code to suit Autoware needs. Code structure is more simple, only ROS driver code is kept, and the readme.md file has more details on how to configure the sensor and use this driver. To further ease Autoware integration, Velodyne compatibility options were added and tested with nd-_matching, ray-ground-filter and euclidean-cluster nodes.
- Improve positional argument parsing in viz
- Use allocate-shared for Eigen compatibility
- Support building visualizer with newer VTK
- Readme tweaks and new example data
- Update readme.md
- updated the readme to include viz in the contents
- Initial commit of the example visualizer
- Uses VTK6 to display point clouds and range/intensity/noise images
- No dependencies other than VTK6, Eigen3, and a C++11 compiler
- Currently only supports linux; tested on multiple distributions and platforms
- Use correct units in sensor-msgs::Imu
- Deal with time going backwards in replays
- Contributors: Alexander Carballo, Dima Garbuzov, Roy Rinberg, alexandrx, amc-nu, hooic, rafficm, rrinberg
Wiki Tutorials
This package does not provide any links to tutorials in it's rosindex metadata.
You can check on the ROS Wiki Tutorials page for the package.
Package Dependencies
| Deps | Name |
|---|---|
| roscpp | |
| message_generation | |
| std_msgs | |
| sensor_msgs | |
| pcl_ros | |
| pcl_conversions | |
| catkin | |
| message_runtime |
System Dependencies
No direct system dependencies.
Dependant Packages
No known dependants.
Launch files
- launch/os1.launch
- -*- mode: XML -*-
-
- lidar_address [default: 192.168.0.100] — hostname or IP address in dotted decimal form of the Ouster sensor
- pc_address [default: 192.168.0.1] — hostname or IP address of the computer (PC) where the sensor will send data packets
- lidar_port [default: 7502] — port to which the sensor should send lidar data
- imu_port [default: 7503] — port to which the sensor should send imu data
- replay [default: false] — when true, the node will listen on ~/lidar_packets and ~/imu_packets for data instead of attempting to connect to a sensor
- scan_dur_ns [default: 100000000] — nanoseconds to batch lidar packets before publishing a cloud
- pointcloud_mode [default: XYZIR] — Point cloud mode, supported modes: NATIVE, XYZ, XYZI, XYZIR, XYZIF, XYZIRF, XYZIFN, XYZIRFN (I=intensity, R=ring (in ascending order), F=reflectivity, N=ambient noise). NATIVE is XYZIRFt where t=point timestamp and ring follows Ouster's original descending order.
- lidar_frame_name [default: velodyne] — Frame name for lidar output message
- lidar_topic_name [default: /points_raw] — Topic name for lidar output message
- imu_frame_name [default: imu] — Frame name for IMU output message
- imu_topic_name [default: /imu_raw] — Topic name for IMU output message
- operation_mode [default: 1024x10] — Supported operation modes: 512x10, 1024x10, 2048x10, 512x20, 1024x20 (horizontal resolution x scan rate)
- pulse_mode [default: STANDARD] — Laser pulse width, available modes: STANDARD and NARROW
- window_rejection [default: true] — Window (short range) rejection enable
Messages
Services
No service files found
Plugins
No plugins found.
Recent questions tagged ouster_driver at Robotics Stack Exchange
No version for distro jade showing kinetic. Known supported distros are highlighted in the buttons above.
|
|
ouster_driver package from ouster repoouster_driver |
ROS Distro
|
Package Summary
| Tags | No category tags. |
| Version | 0.1.7 |
| License | Apache 2 |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/CPFL/ouster.git |
| VCS Type | git |
| VCS Version | autoware_branch |
| Last Updated | 2019-03-28 |
| 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
OS1 ROS client
Additional Links
No additional links.
Maintainers
- Alexander Carballo
- Abraham Monrroy
Authors
- ouster developers
README
No README found.
No README in repository either.
CHANGELOG
Changelog for package ouster
0.1.7 (2019-03-28)
- Sensor model and firmware version validation
- Added sensor model and firmware version validation. The driver currently only works for OS-1-64 and on firmware version 1.10 some configuration parameters disappeared.
- Parameter validation and new pointcloud types
- Added parameter validation to avoid reinitializing the LiDAR. Added new pointcloud types XYZIRF and XYZIRFN. Changed pulse_mode parameter from integer to string for readability. Updated the readme file.
- Contributors: Alexander Carballo, alexandrx
0.1.6 (2019-03-13)
- Renamed ouster_ros to ouster_driver
0.1.5 (2019-03-13)
- updated package.xml
0.1.4 (2019-03-13)
- Updated project name to follow ros standards
0.1.3 (2019-03-06)
- Updated LICENSE
0.1.2 (2019-03-06)
- Changed operation mode from integer to string to ease reading.
- New pointcloud mode format added
- Improved parameter documentation
- removed the old bool pointcloud_mode_xyzir parameter (to match Velodyne's mode) and replaced with a way to specify the desired pointcloud format, several options added including Ouster's native pointcloud format.
- Added install commands
- run CI on kinetic and melodic only
- Fixed launch file to deal with hidden parameters, fixed readme.md to update the TODO, fixed os1_node.cpp to reduce by half the scan duration variable in case of 20Hz operation.
- Updated the driver to support advanced parameter configuration (lidar-mode, pulse-mode and window-rejection-enable)
- Eliminated the ouster-ros static library
- Updated readme.md incorrect info for lidar address configuration.
- Switched to industrial-ci
- First commit for Autoware version branch. Modified the original Ouster ROS code to suit Autoware needs. Code structure is more simple, only ROS driver code is kept, and the readme.md file has more details on how to configure the sensor and use this driver. To further ease Autoware integration, Velodyne compatibility options were added and tested with nd-_matching, ray-ground-filter and euclidean-cluster nodes.
- Improve positional argument parsing in viz
- Use allocate-shared for Eigen compatibility
- Support building visualizer with newer VTK
- Readme tweaks and new example data
- Update readme.md
- updated the readme to include viz in the contents
- Initial commit of the example visualizer
- Uses VTK6 to display point clouds and range/intensity/noise images
- No dependencies other than VTK6, Eigen3, and a C++11 compiler
- Currently only supports linux; tested on multiple distributions and platforms
- Use correct units in sensor-msgs::Imu
- Deal with time going backwards in replays
- Contributors: Alexander Carballo, Dima Garbuzov, Roy Rinberg, alexandrx, amc-nu, hooic, rafficm, rrinberg
Wiki Tutorials
This package does not provide any links to tutorials in it's rosindex metadata.
You can check on the ROS Wiki Tutorials page for the package.
Package Dependencies
| Deps | Name |
|---|---|
| roscpp | |
| message_generation | |
| std_msgs | |
| sensor_msgs | |
| pcl_ros | |
| pcl_conversions | |
| catkin | |
| message_runtime |
System Dependencies
No direct system dependencies.
Dependant Packages
No known dependants.
Launch files
- launch/os1.launch
- -*- mode: XML -*-
-
- lidar_address [default: 192.168.0.100] — hostname or IP address in dotted decimal form of the Ouster sensor
- pc_address [default: 192.168.0.1] — hostname or IP address of the computer (PC) where the sensor will send data packets
- lidar_port [default: 7502] — port to which the sensor should send lidar data
- imu_port [default: 7503] — port to which the sensor should send imu data
- replay [default: false] — when true, the node will listen on ~/lidar_packets and ~/imu_packets for data instead of attempting to connect to a sensor
- scan_dur_ns [default: 100000000] — nanoseconds to batch lidar packets before publishing a cloud
- pointcloud_mode [default: XYZIR] — Point cloud mode, supported modes: NATIVE, XYZ, XYZI, XYZIR, XYZIF, XYZIRF, XYZIFN, XYZIRFN (I=intensity, R=ring (in ascending order), F=reflectivity, N=ambient noise). NATIVE is XYZIRFt where t=point timestamp and ring follows Ouster's original descending order.
- lidar_frame_name [default: velodyne] — Frame name for lidar output message
- lidar_topic_name [default: /points_raw] — Topic name for lidar output message
- imu_frame_name [default: imu] — Frame name for IMU output message
- imu_topic_name [default: /imu_raw] — Topic name for IMU output message
- operation_mode [default: 1024x10] — Supported operation modes: 512x10, 1024x10, 2048x10, 512x20, 1024x20 (horizontal resolution x scan rate)
- pulse_mode [default: STANDARD] — Laser pulse width, available modes: STANDARD and NARROW
- window_rejection [default: true] — Window (short range) rejection enable
Messages
Services
No service files found
Plugins
No plugins found.
Recent questions tagged ouster_driver at Robotics Stack Exchange
No version for distro indigo showing kinetic. Known supported distros are highlighted in the buttons above.
|
|
ouster_driver package from ouster repoouster_driver |
ROS Distro
|
Package Summary
| Tags | No category tags. |
| Version | 0.1.7 |
| License | Apache 2 |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/CPFL/ouster.git |
| VCS Type | git |
| VCS Version | autoware_branch |
| Last Updated | 2019-03-28 |
| 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
OS1 ROS client
Additional Links
No additional links.
Maintainers
- Alexander Carballo
- Abraham Monrroy
Authors
- ouster developers
README
No README found.
No README in repository either.
CHANGELOG
Changelog for package ouster
0.1.7 (2019-03-28)
- Sensor model and firmware version validation
- Added sensor model and firmware version validation. The driver currently only works for OS-1-64 and on firmware version 1.10 some configuration parameters disappeared.
- Parameter validation and new pointcloud types
- Added parameter validation to avoid reinitializing the LiDAR. Added new pointcloud types XYZIRF and XYZIRFN. Changed pulse_mode parameter from integer to string for readability. Updated the readme file.
- Contributors: Alexander Carballo, alexandrx
0.1.6 (2019-03-13)
- Renamed ouster_ros to ouster_driver
0.1.5 (2019-03-13)
- updated package.xml
0.1.4 (2019-03-13)
- Updated project name to follow ros standards
0.1.3 (2019-03-06)
- Updated LICENSE
0.1.2 (2019-03-06)
- Changed operation mode from integer to string to ease reading.
- New pointcloud mode format added
- Improved parameter documentation
- removed the old bool pointcloud_mode_xyzir parameter (to match Velodyne's mode) and replaced with a way to specify the desired pointcloud format, several options added including Ouster's native pointcloud format.
- Added install commands
- run CI on kinetic and melodic only
- Fixed launch file to deal with hidden parameters, fixed readme.md to update the TODO, fixed os1_node.cpp to reduce by half the scan duration variable in case of 20Hz operation.
- Updated the driver to support advanced parameter configuration (lidar-mode, pulse-mode and window-rejection-enable)
- Eliminated the ouster-ros static library
- Updated readme.md incorrect info for lidar address configuration.
- Switched to industrial-ci
- First commit for Autoware version branch. Modified the original Ouster ROS code to suit Autoware needs. Code structure is more simple, only ROS driver code is kept, and the readme.md file has more details on how to configure the sensor and use this driver. To further ease Autoware integration, Velodyne compatibility options were added and tested with nd-_matching, ray-ground-filter and euclidean-cluster nodes.
- Improve positional argument parsing in viz
- Use allocate-shared for Eigen compatibility
- Support building visualizer with newer VTK
- Readme tweaks and new example data
- Update readme.md
- updated the readme to include viz in the contents
- Initial commit of the example visualizer
- Uses VTK6 to display point clouds and range/intensity/noise images
- No dependencies other than VTK6, Eigen3, and a C++11 compiler
- Currently only supports linux; tested on multiple distributions and platforms
- Use correct units in sensor-msgs::Imu
- Deal with time going backwards in replays
- Contributors: Alexander Carballo, Dima Garbuzov, Roy Rinberg, alexandrx, amc-nu, hooic, rafficm, rrinberg
Wiki Tutorials
This package does not provide any links to tutorials in it's rosindex metadata.
You can check on the ROS Wiki Tutorials page for the package.
Package Dependencies
| Deps | Name |
|---|---|
| roscpp | |
| message_generation | |
| std_msgs | |
| sensor_msgs | |
| pcl_ros | |
| pcl_conversions | |
| catkin | |
| message_runtime |
System Dependencies
No direct system dependencies.
Dependant Packages
No known dependants.
Launch files
- launch/os1.launch
- -*- mode: XML -*-
-
- lidar_address [default: 192.168.0.100] — hostname or IP address in dotted decimal form of the Ouster sensor
- pc_address [default: 192.168.0.1] — hostname or IP address of the computer (PC) where the sensor will send data packets
- lidar_port [default: 7502] — port to which the sensor should send lidar data
- imu_port [default: 7503] — port to which the sensor should send imu data
- replay [default: false] — when true, the node will listen on ~/lidar_packets and ~/imu_packets for data instead of attempting to connect to a sensor
- scan_dur_ns [default: 100000000] — nanoseconds to batch lidar packets before publishing a cloud
- pointcloud_mode [default: XYZIR] — Point cloud mode, supported modes: NATIVE, XYZ, XYZI, XYZIR, XYZIF, XYZIRF, XYZIFN, XYZIRFN (I=intensity, R=ring (in ascending order), F=reflectivity, N=ambient noise). NATIVE is XYZIRFt where t=point timestamp and ring follows Ouster's original descending order.
- lidar_frame_name [default: velodyne] — Frame name for lidar output message
- lidar_topic_name [default: /points_raw] — Topic name for lidar output message
- imu_frame_name [default: imu] — Frame name for IMU output message
- imu_topic_name [default: /imu_raw] — Topic name for IMU output message
- operation_mode [default: 1024x10] — Supported operation modes: 512x10, 1024x10, 2048x10, 512x20, 1024x20 (horizontal resolution x scan rate)
- pulse_mode [default: STANDARD] — Laser pulse width, available modes: STANDARD and NARROW
- window_rejection [default: true] — Window (short range) rejection enable
Messages
Services
No service files found
Plugins
No plugins found.
Recent questions tagged ouster_driver at Robotics Stack Exchange
No version for distro hydro showing kinetic. Known supported distros are highlighted in the buttons above.
|
|
ouster_driver package from ouster repoouster_driver |
ROS Distro
|
Package Summary
| Tags | No category tags. |
| Version | 0.1.7 |
| License | Apache 2 |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/CPFL/ouster.git |
| VCS Type | git |
| VCS Version | autoware_branch |
| Last Updated | 2019-03-28 |
| 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
OS1 ROS client
Additional Links
No additional links.
Maintainers
- Alexander Carballo
- Abraham Monrroy
Authors
- ouster developers
README
No README found.
No README in repository either.
CHANGELOG
Changelog for package ouster
0.1.7 (2019-03-28)
- Sensor model and firmware version validation
- Added sensor model and firmware version validation. The driver currently only works for OS-1-64 and on firmware version 1.10 some configuration parameters disappeared.
- Parameter validation and new pointcloud types
- Added parameter validation to avoid reinitializing the LiDAR. Added new pointcloud types XYZIRF and XYZIRFN. Changed pulse_mode parameter from integer to string for readability. Updated the readme file.
- Contributors: Alexander Carballo, alexandrx
0.1.6 (2019-03-13)
- Renamed ouster_ros to ouster_driver
0.1.5 (2019-03-13)
- updated package.xml
0.1.4 (2019-03-13)
- Updated project name to follow ros standards
0.1.3 (2019-03-06)
- Updated LICENSE
0.1.2 (2019-03-06)
- Changed operation mode from integer to string to ease reading.
- New pointcloud mode format added
- Improved parameter documentation
- removed the old bool pointcloud_mode_xyzir parameter (to match Velodyne's mode) and replaced with a way to specify the desired pointcloud format, several options added including Ouster's native pointcloud format.
- Added install commands
- run CI on kinetic and melodic only
- Fixed launch file to deal with hidden parameters, fixed readme.md to update the TODO, fixed os1_node.cpp to reduce by half the scan duration variable in case of 20Hz operation.
- Updated the driver to support advanced parameter configuration (lidar-mode, pulse-mode and window-rejection-enable)
- Eliminated the ouster-ros static library
- Updated readme.md incorrect info for lidar address configuration.
- Switched to industrial-ci
- First commit for Autoware version branch. Modified the original Ouster ROS code to suit Autoware needs. Code structure is more simple, only ROS driver code is kept, and the readme.md file has more details on how to configure the sensor and use this driver. To further ease Autoware integration, Velodyne compatibility options were added and tested with nd-_matching, ray-ground-filter and euclidean-cluster nodes.
- Improve positional argument parsing in viz
- Use allocate-shared for Eigen compatibility
- Support building visualizer with newer VTK
- Readme tweaks and new example data
- Update readme.md
- updated the readme to include viz in the contents
- Initial commit of the example visualizer
- Uses VTK6 to display point clouds and range/intensity/noise images
- No dependencies other than VTK6, Eigen3, and a C++11 compiler
- Currently only supports linux; tested on multiple distributions and platforms
- Use correct units in sensor-msgs::Imu
- Deal with time going backwards in replays
- Contributors: Alexander Carballo, Dima Garbuzov, Roy Rinberg, alexandrx, amc-nu, hooic, rafficm, rrinberg
Wiki Tutorials
This package does not provide any links to tutorials in it's rosindex metadata.
You can check on the ROS Wiki Tutorials page for the package.
Package Dependencies
| Deps | Name |
|---|---|
| roscpp | |
| message_generation | |
| std_msgs | |
| sensor_msgs | |
| pcl_ros | |
| pcl_conversions | |
| catkin | |
| message_runtime |
System Dependencies
No direct system dependencies.
Dependant Packages
No known dependants.
Launch files
- launch/os1.launch
- -*- mode: XML -*-
-
- lidar_address [default: 192.168.0.100] — hostname or IP address in dotted decimal form of the Ouster sensor
- pc_address [default: 192.168.0.1] — hostname or IP address of the computer (PC) where the sensor will send data packets
- lidar_port [default: 7502] — port to which the sensor should send lidar data
- imu_port [default: 7503] — port to which the sensor should send imu data
- replay [default: false] — when true, the node will listen on ~/lidar_packets and ~/imu_packets for data instead of attempting to connect to a sensor
- scan_dur_ns [default: 100000000] — nanoseconds to batch lidar packets before publishing a cloud
- pointcloud_mode [default: XYZIR] — Point cloud mode, supported modes: NATIVE, XYZ, XYZI, XYZIR, XYZIF, XYZIRF, XYZIFN, XYZIRFN (I=intensity, R=ring (in ascending order), F=reflectivity, N=ambient noise). NATIVE is XYZIRFt where t=point timestamp and ring follows Ouster's original descending order.
- lidar_frame_name [default: velodyne] — Frame name for lidar output message
- lidar_topic_name [default: /points_raw] — Topic name for lidar output message
- imu_frame_name [default: imu] — Frame name for IMU output message
- imu_topic_name [default: /imu_raw] — Topic name for IMU output message
- operation_mode [default: 1024x10] — Supported operation modes: 512x10, 1024x10, 2048x10, 512x20, 1024x20 (horizontal resolution x scan rate)
- pulse_mode [default: STANDARD] — Laser pulse width, available modes: STANDARD and NARROW
- window_rejection [default: true] — Window (short range) rejection enable
Messages
Services
No service files found
Plugins
No plugins found.
Recent questions tagged ouster_driver at Robotics Stack Exchange
|
|
ouster_driver package from ouster repoouster_driver |
ROS Distro
|
Package Summary
| Tags | No category tags. |
| Version | 0.1.7 |
| License | Apache 2 |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/CPFL/ouster.git |
| VCS Type | git |
| VCS Version | autoware_branch |
| Last Updated | 2019-03-28 |
| 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
OS1 ROS client
Additional Links
No additional links.
Maintainers
- Alexander Carballo
- Abraham Monrroy
Authors
- ouster developers
README
No README found.
No README in repository either.
CHANGELOG
Changelog for package ouster
0.1.7 (2019-03-28)
- Sensor model and firmware version validation
- Added sensor model and firmware version validation. The driver currently only works for OS-1-64 and on firmware version 1.10 some configuration parameters disappeared.
- Parameter validation and new pointcloud types
- Added parameter validation to avoid reinitializing the LiDAR. Added new pointcloud types XYZIRF and XYZIRFN. Changed pulse_mode parameter from integer to string for readability. Updated the readme file.
- Contributors: Alexander Carballo, alexandrx
0.1.6 (2019-03-13)
- Renamed ouster_ros to ouster_driver
0.1.5 (2019-03-13)
- updated package.xml
0.1.4 (2019-03-13)
- Updated project name to follow ros standards
0.1.3 (2019-03-06)
- Updated LICENSE
0.1.2 (2019-03-06)
- Changed operation mode from integer to string to ease reading.
- New pointcloud mode format added
- Improved parameter documentation
- removed the old bool pointcloud_mode_xyzir parameter (to match Velodyne's mode) and replaced with a way to specify the desired pointcloud format, several options added including Ouster's native pointcloud format.
- Added install commands
- run CI on kinetic and melodic only
- Fixed launch file to deal with hidden parameters, fixed readme.md to update the TODO, fixed os1_node.cpp to reduce by half the scan duration variable in case of 20Hz operation.
- Updated the driver to support advanced parameter configuration (lidar-mode, pulse-mode and window-rejection-enable)
- Eliminated the ouster-ros static library
- Updated readme.md incorrect info for lidar address configuration.
- Switched to industrial-ci
- First commit for Autoware version branch. Modified the original Ouster ROS code to suit Autoware needs. Code structure is more simple, only ROS driver code is kept, and the readme.md file has more details on how to configure the sensor and use this driver. To further ease Autoware integration, Velodyne compatibility options were added and tested with nd-_matching, ray-ground-filter and euclidean-cluster nodes.
- Improve positional argument parsing in viz
- Use allocate-shared for Eigen compatibility
- Support building visualizer with newer VTK
- Readme tweaks and new example data
- Update readme.md
- updated the readme to include viz in the contents
- Initial commit of the example visualizer
- Uses VTK6 to display point clouds and range/intensity/noise images
- No dependencies other than VTK6, Eigen3, and a C++11 compiler
- Currently only supports linux; tested on multiple distributions and platforms
- Use correct units in sensor-msgs::Imu
- Deal with time going backwards in replays
- Contributors: Alexander Carballo, Dima Garbuzov, Roy Rinberg, alexandrx, amc-nu, hooic, rafficm, rrinberg
Wiki Tutorials
This package does not provide any links to tutorials in it's rosindex metadata.
You can check on the ROS Wiki Tutorials page for the package.
Package Dependencies
| Deps | Name |
|---|---|
| roscpp | |
| message_generation | |
| std_msgs | |
| sensor_msgs | |
| pcl_ros | |
| pcl_conversions | |
| catkin | |
| message_runtime |
System Dependencies
No direct system dependencies.
Dependant Packages
No known dependants.
Launch files
- launch/os1.launch
- -*- mode: XML -*-
-
- lidar_address [default: 192.168.0.100] — hostname or IP address in dotted decimal form of the Ouster sensor
- pc_address [default: 192.168.0.1] — hostname or IP address of the computer (PC) where the sensor will send data packets
- lidar_port [default: 7502] — port to which the sensor should send lidar data
- imu_port [default: 7503] — port to which the sensor should send imu data
- replay [default: false] — when true, the node will listen on ~/lidar_packets and ~/imu_packets for data instead of attempting to connect to a sensor
- scan_dur_ns [default: 100000000] — nanoseconds to batch lidar packets before publishing a cloud
- pointcloud_mode [default: XYZIR] — Point cloud mode, supported modes: NATIVE, XYZ, XYZI, XYZIR, XYZIF, XYZIRF, XYZIFN, XYZIRFN (I=intensity, R=ring (in ascending order), F=reflectivity, N=ambient noise). NATIVE is XYZIRFt where t=point timestamp and ring follows Ouster's original descending order.
- lidar_frame_name [default: velodyne] — Frame name for lidar output message
- lidar_topic_name [default: /points_raw] — Topic name for lidar output message
- imu_frame_name [default: imu] — Frame name for IMU output message
- imu_topic_name [default: /imu_raw] — Topic name for IMU output message
- operation_mode [default: 1024x10] — Supported operation modes: 512x10, 1024x10, 2048x10, 512x20, 1024x20 (horizontal resolution x scan rate)
- pulse_mode [default: STANDARD] — Laser pulse width, available modes: STANDARD and NARROW
- window_rejection [default: true] — Window (short range) rejection enable
Messages
Services
No service files found
Plugins
No plugins found.
Recent questions tagged ouster_driver at Robotics Stack Exchange
|
|
ouster_driver package from ouster repoouster_driver |
ROS Distro
|
Package Summary
| Tags | No category tags. |
| Version | 0.1.7 |
| License | Apache 2 |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/CPFL/ouster.git |
| VCS Type | git |
| VCS Version | autoware_branch |
| Last Updated | 2019-03-28 |
| Dev Status | DEVELOPED |
| CI status | Continuous Integration : 0 / 0 |
| Released | RELEASED |
| Tags | No category tags. |
| Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
OS1 ROS client
Additional Links
No additional links.
Maintainers
- Alexander Carballo
- Abraham Monrroy
Authors
- ouster developers
README
No README found.
No README in repository either.
CHANGELOG
Changelog for package ouster
0.1.7 (2019-03-28)
- Sensor model and firmware version validation
- Added sensor model and firmware version validation. The driver currently only works for OS-1-64 and on firmware version 1.10 some configuration parameters disappeared.
- Parameter validation and new pointcloud types
- Added parameter validation to avoid reinitializing the LiDAR. Added new pointcloud types XYZIRF and XYZIRFN. Changed pulse_mode parameter from integer to string for readability. Updated the readme file.
- Contributors: Alexander Carballo, alexandrx
0.1.6 (2019-03-13)
- Renamed ouster_ros to ouster_driver
0.1.5 (2019-03-13)
- updated package.xml
0.1.4 (2019-03-13)
- Updated project name to follow ros standards
0.1.3 (2019-03-06)
- Updated LICENSE
0.1.2 (2019-03-06)
- Changed operation mode from integer to string to ease reading.
- New pointcloud mode format added
- Improved parameter documentation
- removed the old bool pointcloud_mode_xyzir parameter (to match Velodyne's mode) and replaced with a way to specify the desired pointcloud format, several options added including Ouster's native pointcloud format.
- Added install commands
- run CI on kinetic and melodic only
- Fixed launch file to deal with hidden parameters, fixed readme.md to update the TODO, fixed os1_node.cpp to reduce by half the scan duration variable in case of 20Hz operation.
- Updated the driver to support advanced parameter configuration (lidar-mode, pulse-mode and window-rejection-enable)
- Eliminated the ouster-ros static library
- Updated readme.md incorrect info for lidar address configuration.
- Switched to industrial-ci
- First commit for Autoware version branch. Modified the original Ouster ROS code to suit Autoware needs. Code structure is more simple, only ROS driver code is kept, and the readme.md file has more details on how to configure the sensor and use this driver. To further ease Autoware integration, Velodyne compatibility options were added and tested with nd-_matching, ray-ground-filter and euclidean-cluster nodes.
- Improve positional argument parsing in viz
- Use allocate-shared for Eigen compatibility
- Support building visualizer with newer VTK
- Readme tweaks and new example data
- Update readme.md
- updated the readme to include viz in the contents
- Initial commit of the example visualizer
- Uses VTK6 to display point clouds and range/intensity/noise images
- No dependencies other than VTK6, Eigen3, and a C++11 compiler
- Currently only supports linux; tested on multiple distributions and platforms
- Use correct units in sensor-msgs::Imu
- Deal with time going backwards in replays
- Contributors: Alexander Carballo, Dima Garbuzov, Roy Rinberg, alexandrx, amc-nu, hooic, rafficm, rrinberg
Wiki Tutorials
This package does not provide any links to tutorials in it's rosindex metadata.
You can check on the ROS Wiki Tutorials page for the package.
Package Dependencies
| Deps | Name |
|---|---|
| roscpp | |
| message_generation | |
| std_msgs | |
| sensor_msgs | |
| pcl_ros | |
| pcl_conversions | |
| catkin | |
| message_runtime |
System Dependencies
No direct system dependencies.
Dependant Packages
No known dependants.
Launch files
- launch/os1.launch
- -*- mode: XML -*-
-
- lidar_address [default: 192.168.0.100] — hostname or IP address in dotted decimal form of the Ouster sensor
- pc_address [default: 192.168.0.1] — hostname or IP address of the computer (PC) where the sensor will send data packets
- lidar_port [default: 7502] — port to which the sensor should send lidar data
- imu_port [default: 7503] — port to which the sensor should send imu data
- replay [default: false] — when true, the node will listen on ~/lidar_packets and ~/imu_packets for data instead of attempting to connect to a sensor
- scan_dur_ns [default: 100000000] — nanoseconds to batch lidar packets before publishing a cloud
- pointcloud_mode [default: XYZIR] — Point cloud mode, supported modes: NATIVE, XYZ, XYZI, XYZIR, XYZIF, XYZIRF, XYZIFN, XYZIRFN (I=intensity, R=ring (in ascending order), F=reflectivity, N=ambient noise). NATIVE is XYZIRFt where t=point timestamp and ring follows Ouster's original descending order.
- lidar_frame_name [default: velodyne] — Frame name for lidar output message
- lidar_topic_name [default: /points_raw] — Topic name for lidar output message
- imu_frame_name [default: imu] — Frame name for IMU output message
- imu_topic_name [default: /imu_raw] — Topic name for IMU output message
- operation_mode [default: 1024x10] — Supported operation modes: 512x10, 1024x10, 2048x10, 512x20, 1024x20 (horizontal resolution x scan rate)
- pulse_mode [default: STANDARD] — Laser pulse width, available modes: STANDARD and NARROW
- window_rejection [default: true] — Window (short range) rejection enable
Messages
Services
No service files found
Plugins
No plugins found.
Recent questions tagged ouster_driver at Robotics Stack Exchange
No version for distro noetic showing kinetic. Known supported distros are highlighted in the buttons above.
|
|
ouster_driver package from ouster repoouster_driver |
ROS Distro
|
Package Summary
| Tags | No category tags. |
| Version | 0.1.7 |
| License | Apache 2 |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/CPFL/ouster.git |
| VCS Type | git |
| VCS Version | autoware_branch |
| Last Updated | 2019-03-28 |
| 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
OS1 ROS client
Additional Links
No additional links.
Maintainers
- Alexander Carballo
- Abraham Monrroy
Authors
- ouster developers
README
No README found.
No README in repository either.
CHANGELOG
Changelog for package ouster
0.1.7 (2019-03-28)
- Sensor model and firmware version validation
- Added sensor model and firmware version validation. The driver currently only works for OS-1-64 and on firmware version 1.10 some configuration parameters disappeared.
- Parameter validation and new pointcloud types
- Added parameter validation to avoid reinitializing the LiDAR. Added new pointcloud types XYZIRF and XYZIRFN. Changed pulse_mode parameter from integer to string for readability. Updated the readme file.
- Contributors: Alexander Carballo, alexandrx
0.1.6 (2019-03-13)
- Renamed ouster_ros to ouster_driver
0.1.5 (2019-03-13)
- updated package.xml
0.1.4 (2019-03-13)
- Updated project name to follow ros standards
0.1.3 (2019-03-06)
- Updated LICENSE
0.1.2 (2019-03-06)
- Changed operation mode from integer to string to ease reading.
- New pointcloud mode format added
- Improved parameter documentation
- removed the old bool pointcloud_mode_xyzir parameter (to match Velodyne's mode) and replaced with a way to specify the desired pointcloud format, several options added including Ouster's native pointcloud format.
- Added install commands
- run CI on kinetic and melodic only
- Fixed launch file to deal with hidden parameters, fixed readme.md to update the TODO, fixed os1_node.cpp to reduce by half the scan duration variable in case of 20Hz operation.
- Updated the driver to support advanced parameter configuration (lidar-mode, pulse-mode and window-rejection-enable)
- Eliminated the ouster-ros static library
- Updated readme.md incorrect info for lidar address configuration.
- Switched to industrial-ci
- First commit for Autoware version branch. Modified the original Ouster ROS code to suit Autoware needs. Code structure is more simple, only ROS driver code is kept, and the readme.md file has more details on how to configure the sensor and use this driver. To further ease Autoware integration, Velodyne compatibility options were added and tested with nd-_matching, ray-ground-filter and euclidean-cluster nodes.
- Improve positional argument parsing in viz
- Use allocate-shared for Eigen compatibility
- Support building visualizer with newer VTK
- Readme tweaks and new example data
- Update readme.md
- updated the readme to include viz in the contents
- Initial commit of the example visualizer
- Uses VTK6 to display point clouds and range/intensity/noise images
- No dependencies other than VTK6, Eigen3, and a C++11 compiler
- Currently only supports linux; tested on multiple distributions and platforms
- Use correct units in sensor-msgs::Imu
- Deal with time going backwards in replays
- Contributors: Alexander Carballo, Dima Garbuzov, Roy Rinberg, alexandrx, amc-nu, hooic, rafficm, rrinberg
Wiki Tutorials
This package does not provide any links to tutorials in it's rosindex metadata.
You can check on the ROS Wiki Tutorials page for the package.
Package Dependencies
| Deps | Name |
|---|---|
| roscpp | |
| message_generation | |
| std_msgs | |
| sensor_msgs | |
| pcl_ros | |
| pcl_conversions | |
| catkin | |
| message_runtime |
System Dependencies
No direct system dependencies.
Dependant Packages
No known dependants.
Launch files
- launch/os1.launch
- -*- mode: XML -*-
-
- lidar_address [default: 192.168.0.100] — hostname or IP address in dotted decimal form of the Ouster sensor
- pc_address [default: 192.168.0.1] — hostname or IP address of the computer (PC) where the sensor will send data packets
- lidar_port [default: 7502] — port to which the sensor should send lidar data
- imu_port [default: 7503] — port to which the sensor should send imu data
- replay [default: false] — when true, the node will listen on ~/lidar_packets and ~/imu_packets for data instead of attempting to connect to a sensor
- scan_dur_ns [default: 100000000] — nanoseconds to batch lidar packets before publishing a cloud
- pointcloud_mode [default: XYZIR] — Point cloud mode, supported modes: NATIVE, XYZ, XYZI, XYZIR, XYZIF, XYZIRF, XYZIFN, XYZIRFN (I=intensity, R=ring (in ascending order), F=reflectivity, N=ambient noise). NATIVE is XYZIRFt where t=point timestamp and ring follows Ouster's original descending order.
- lidar_frame_name [default: velodyne] — Frame name for lidar output message
- lidar_topic_name [default: /points_raw] — Topic name for lidar output message
- imu_frame_name [default: imu] — Frame name for IMU output message
- imu_topic_name [default: /imu_raw] — Topic name for IMU output message
- operation_mode [default: 1024x10] — Supported operation modes: 512x10, 1024x10, 2048x10, 512x20, 1024x20 (horizontal resolution x scan rate)
- pulse_mode [default: STANDARD] — Laser pulse width, available modes: STANDARD and NARROW
- window_rejection [default: true] — Window (short range) rejection enable
Messages
Services
No service files found
Plugins
No plugins found.