Package Summary
Tags | No category tags. |
Version | 0.46.0 |
License | Apache License 2.0 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | |
Checkout URI | https://github.com/autowarefoundation/autoware_universe.git |
VCS Type | git |
VCS Version | main |
Last Updated | 2025-07-31 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | planner ros calibration self-driving-car autonomous-driving autonomous-vehicles ros2 3d-map autoware |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Fumihito Ito
- Junya Sasaki
Authors
autoware_velodyne_monitor
Purpose
This node monitors the status of Velodyne LiDARs. The result of the status is published as diagnostics. Take care not to use this diagnostics to decide the lidar error. Please read Assumptions / Known limits for the detail reason.
Inner-workings / Algorithms
The status of Velodyne LiDAR can be retrieved from http://[ip_address]/cgi/{info, settings, status, diag}.json
.
The types of abnormal status and corresponding diagnostics status are following.
Abnormal status | Diagnostic status |
---|---|
No abnormality | OK |
Top board temperature is too cold | ERROR |
Top board temperature is cold | WARN |
Top board temperature is too hot | ERROR |
Top board temperature is hot | WARN |
Bottom board temperature is too cold | ERROR |
Bottom board temperature is cold | WARN |
Bottom board temperature is too hot | ERROR |
Bottom board temperature is hot | WARN |
Rpm(Rotations per minute) of the motor is too low | ERROR |
Rpm(Rotations per minute) of the motor is low | WARN |
Connection error (cannot get Velodyne LiDAR status) | ERROR |
Inputs / Outputs
Input
None
Output
Name | Type | Description |
---|---|---|
/diagnostics |
diagnostic_msgs/DiagnosticArray |
Diagnostics outputs |
Parameters
Node Parameters
Name | Type | Default Value | Description |
---|---|---|---|
timeout |
double | 0.5 | Timeout for HTTP request to get Velodyne LiDAR status [s] |
Core Parameters
Name | Type | Default Value | Description |
---|---|---|---|
ip_address |
string | “192.168.1.201” | IP address of target Velodyne LiDAR |
temp_cold_warn |
double | -5.0 | If the temperature of Velodyne LiDAR is lower than this value, the diagnostics status becomes WARN [°C] |
temp_cold_error |
double | -10.0 | If the temperature of Velodyne LiDAR is lower than this value, the diagnostics status becomes ERROR [°C] |
temp_hot_warn |
double | 75.0 | If the temperature of Velodyne LiDAR is higher than this value, the diagnostics status becomes WARN [°C] |
temp_hot_error |
double | 80.0 | If the temperature of Velodyne LiDAR is higher than this value, the diagnostics status becomes ERROR [°C] |
rpm_ratio_warn |
double | 0.80 | If the rpm rate of the motor (= current rpm / default rpm) is lower than this value, the diagnostics status becomes WARN |
rpm_ratio_error |
double | 0.70 | If the rpm rate of the motor (= current rpm / default rpm) is lower than this value, the diagnostics status becomes ERROR |
Config files
Config files for several velodyne models are prepared.
The temp_***
parameters are set with reference to the operational temperature from each datasheet.
Moreover, the temp_hot_***
of each model are set highly as 20 from operational temperature.
Now, VLP-16.param.yaml
is used as default argument because it is lowest spec.
Model Name | Config name | Operational Temperature [℃] |
---|---|---|
VLP-16 | VLP-16.param.yaml | -10 to 60 |
VLP-32C | VLP-32C.param.yaml | -20 to 60 |
VLS-128 | VLS-128.param.yaml | -20 to 60 |
Velarray M1600 | Velarray_M1600.param.yaml | -40 to 85 |
HDL-32E | HDL-32E.param.yaml | -10 to 60 |
Assumptions / Known limits
This node uses the http_client and request results by GET method. It takes a few seconds to get results, or generate a timeout exception if it does not succeed the GET request. This occurs frequently and the diagnostics aggregator output STALE. Therefore I recommend to stop using this results to decide the lidar error, and only monitor it to confirm lidar status.
Changelog for package autoware_velodyne_monitor
0.46.0 (2025-06-20)
0.45.0 (2025-05-22)
0.44.2 (2025-06-10)
0.44.1 (2025-05-01)
0.44.0 (2025-04-18)
0.43.0 (2025-03-21)
- Merge remote-tracking branch 'origin/main' into chore/bump-version-0.43
- chore: rename from [autoware.universe]{.title-ref} to [autoware_universe]{.title-ref} (#10306)
- Contributors: Hayato Mizushima, Yutaka Kondo
0.42.0 (2025-03-03)
0.41.2 (2025-02-19)
- chore: bump version to 0.41.1 (#10088)
- Contributors: Ryohsuke Mitsudome
0.41.1 (2025-02-10)
0.41.0 (2025-01-29)
- Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
- feat: apply [autoware_]{.title-ref} prefix for [velodyne_monitor]{.title-ref} (#9976)
- Contributors: Fumiya Watanabe, Junya Sasaki
0.40.0 (2024-12-12)
-
Revert "chore(package.xml): bump version to 0.39.0 (#9587)" This reverts commit c9f0f2688c57b0f657f5c1f28f036a970682e7f5.
-
fix: fix ticket links in CHANGELOG.rst (#9588)
-
chore(package.xml): bump version to 0.39.0 (#9587)
- chore(package.xml): bump version to 0.39.0
- fix: fix ticket links in CHANGELOG.rst
* fix: remove unnecessary diff ---------Co-authored-by: Yutaka Kondo <<yutaka.kondo@youtalk.jp>>
-
fix: fix ticket links in CHANGELOG.rst (#9588)
-
0.39.0
-
update changelog
-
fix: fix ticket links to point to https://github.com/autowarefoundation/autoware_universe (#9304)
-
fix: fix ticket links to point to https://github.com/autowarefoundation/autoware_universe (#9304)
-
chore(package.xml): bump version to 0.38.0 (#9266) (#9284)
- unify package.xml version to 0.37.0
- remove system_monitor/CHANGELOG.rst
- add changelog
* 0.38.0
-
Contributors: Esteve Fernandez, Fumiya Watanabe, Ryohsuke Mitsudome, Yutaka Kondo
0.39.0 (2024-11-25)
- fix: fix ticket links to point to https://github.com/autowarefoundation/autoware_universe (#9304)
- fix: fix ticket links to point to https://github.com/autowarefoundation/autoware_universe (#9304)
- chore(package.xml): bump version to 0.38.0
(#9266)
(#9284)
- unify package.xml version to 0.37.0
- remove system_monitor/CHANGELOG.rst
- add changelog
File truncated at 100 lines see the full file
Package Dependencies
Deps | Name |
---|---|
ament_cmake_auto | |
autoware_cmake | |
ament_lint_auto | |
autoware_lint_common | |
diagnostic_msgs | |
diagnostic_updater | |
rclcpp | |
rclcpp_components | |
std_msgs |
System Dependencies
Name |
---|
crypto++ |
fmt |
libcpprest-dev |
Dependant Packages
Launch files
- launch/velodyne_monitor.launch.xml
-
- velodyne_monitor_param_file [default: $(find-pkg-share autoware_velodyne_monitor)/config/VLP-16.param.yaml]
- ip_address [default: 192.168.1.201]
Messages
Services
Plugins
Recent questions tagged autoware_velodyne_monitor at Robotics Stack Exchange
Package Summary
Tags | No category tags. |
Version | 0.46.0 |
License | Apache License 2.0 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | |
Checkout URI | https://github.com/autowarefoundation/autoware_universe.git |
VCS Type | git |
VCS Version | main |
Last Updated | 2025-07-31 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | planner ros calibration self-driving-car autonomous-driving autonomous-vehicles ros2 3d-map autoware |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Fumihito Ito
- Junya Sasaki
Authors
autoware_velodyne_monitor
Purpose
This node monitors the status of Velodyne LiDARs. The result of the status is published as diagnostics. Take care not to use this diagnostics to decide the lidar error. Please read Assumptions / Known limits for the detail reason.
Inner-workings / Algorithms
The status of Velodyne LiDAR can be retrieved from http://[ip_address]/cgi/{info, settings, status, diag}.json
.
The types of abnormal status and corresponding diagnostics status are following.
Abnormal status | Diagnostic status |
---|---|
No abnormality | OK |
Top board temperature is too cold | ERROR |
Top board temperature is cold | WARN |
Top board temperature is too hot | ERROR |
Top board temperature is hot | WARN |
Bottom board temperature is too cold | ERROR |
Bottom board temperature is cold | WARN |
Bottom board temperature is too hot | ERROR |
Bottom board temperature is hot | WARN |
Rpm(Rotations per minute) of the motor is too low | ERROR |
Rpm(Rotations per minute) of the motor is low | WARN |
Connection error (cannot get Velodyne LiDAR status) | ERROR |
Inputs / Outputs
Input
None
Output
Name | Type | Description |
---|---|---|
/diagnostics |
diagnostic_msgs/DiagnosticArray |
Diagnostics outputs |
Parameters
Node Parameters
Name | Type | Default Value | Description |
---|---|---|---|
timeout |
double | 0.5 | Timeout for HTTP request to get Velodyne LiDAR status [s] |
Core Parameters
Name | Type | Default Value | Description |
---|---|---|---|
ip_address |
string | “192.168.1.201” | IP address of target Velodyne LiDAR |
temp_cold_warn |
double | -5.0 | If the temperature of Velodyne LiDAR is lower than this value, the diagnostics status becomes WARN [°C] |
temp_cold_error |
double | -10.0 | If the temperature of Velodyne LiDAR is lower than this value, the diagnostics status becomes ERROR [°C] |
temp_hot_warn |
double | 75.0 | If the temperature of Velodyne LiDAR is higher than this value, the diagnostics status becomes WARN [°C] |
temp_hot_error |
double | 80.0 | If the temperature of Velodyne LiDAR is higher than this value, the diagnostics status becomes ERROR [°C] |
rpm_ratio_warn |
double | 0.80 | If the rpm rate of the motor (= current rpm / default rpm) is lower than this value, the diagnostics status becomes WARN |
rpm_ratio_error |
double | 0.70 | If the rpm rate of the motor (= current rpm / default rpm) is lower than this value, the diagnostics status becomes ERROR |
Config files
Config files for several velodyne models are prepared.
The temp_***
parameters are set with reference to the operational temperature from each datasheet.
Moreover, the temp_hot_***
of each model are set highly as 20 from operational temperature.
Now, VLP-16.param.yaml
is used as default argument because it is lowest spec.
Model Name | Config name | Operational Temperature [℃] |
---|---|---|
VLP-16 | VLP-16.param.yaml | -10 to 60 |
VLP-32C | VLP-32C.param.yaml | -20 to 60 |
VLS-128 | VLS-128.param.yaml | -20 to 60 |
Velarray M1600 | Velarray_M1600.param.yaml | -40 to 85 |
HDL-32E | HDL-32E.param.yaml | -10 to 60 |
Assumptions / Known limits
This node uses the http_client and request results by GET method. It takes a few seconds to get results, or generate a timeout exception if it does not succeed the GET request. This occurs frequently and the diagnostics aggregator output STALE. Therefore I recommend to stop using this results to decide the lidar error, and only monitor it to confirm lidar status.
Changelog for package autoware_velodyne_monitor
0.46.0 (2025-06-20)
0.45.0 (2025-05-22)
0.44.2 (2025-06-10)
0.44.1 (2025-05-01)
0.44.0 (2025-04-18)
0.43.0 (2025-03-21)
- Merge remote-tracking branch 'origin/main' into chore/bump-version-0.43
- chore: rename from [autoware.universe]{.title-ref} to [autoware_universe]{.title-ref} (#10306)
- Contributors: Hayato Mizushima, Yutaka Kondo
0.42.0 (2025-03-03)
0.41.2 (2025-02-19)
- chore: bump version to 0.41.1 (#10088)
- Contributors: Ryohsuke Mitsudome
0.41.1 (2025-02-10)
0.41.0 (2025-01-29)
- Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
- feat: apply [autoware_]{.title-ref} prefix for [velodyne_monitor]{.title-ref} (#9976)
- Contributors: Fumiya Watanabe, Junya Sasaki
0.40.0 (2024-12-12)
-
Revert "chore(package.xml): bump version to 0.39.0 (#9587)" This reverts commit c9f0f2688c57b0f657f5c1f28f036a970682e7f5.
-
fix: fix ticket links in CHANGELOG.rst (#9588)
-
chore(package.xml): bump version to 0.39.0 (#9587)
- chore(package.xml): bump version to 0.39.0
- fix: fix ticket links in CHANGELOG.rst
* fix: remove unnecessary diff ---------Co-authored-by: Yutaka Kondo <<yutaka.kondo@youtalk.jp>>
-
fix: fix ticket links in CHANGELOG.rst (#9588)
-
0.39.0
-
update changelog
-
fix: fix ticket links to point to https://github.com/autowarefoundation/autoware_universe (#9304)
-
fix: fix ticket links to point to https://github.com/autowarefoundation/autoware_universe (#9304)
-
chore(package.xml): bump version to 0.38.0 (#9266) (#9284)
- unify package.xml version to 0.37.0
- remove system_monitor/CHANGELOG.rst
- add changelog
* 0.38.0
-
Contributors: Esteve Fernandez, Fumiya Watanabe, Ryohsuke Mitsudome, Yutaka Kondo
0.39.0 (2024-11-25)
- fix: fix ticket links to point to https://github.com/autowarefoundation/autoware_universe (#9304)
- fix: fix ticket links to point to https://github.com/autowarefoundation/autoware_universe (#9304)
- chore(package.xml): bump version to 0.38.0
(#9266)
(#9284)
- unify package.xml version to 0.37.0
- remove system_monitor/CHANGELOG.rst
- add changelog
File truncated at 100 lines see the full file
Package Dependencies
Deps | Name |
---|---|
ament_cmake_auto | |
autoware_cmake | |
ament_lint_auto | |
autoware_lint_common | |
diagnostic_msgs | |
diagnostic_updater | |
rclcpp | |
rclcpp_components | |
std_msgs |
System Dependencies
Name |
---|
crypto++ |
fmt |
libcpprest-dev |
Dependant Packages
Launch files
- launch/velodyne_monitor.launch.xml
-
- velodyne_monitor_param_file [default: $(find-pkg-share autoware_velodyne_monitor)/config/VLP-16.param.yaml]
- ip_address [default: 192.168.1.201]
Messages
Services
Plugins
Recent questions tagged autoware_velodyne_monitor at Robotics Stack Exchange
Package Summary
Tags | No category tags. |
Version | 0.46.0 |
License | Apache License 2.0 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | |
Checkout URI | https://github.com/autowarefoundation/autoware_universe.git |
VCS Type | git |
VCS Version | main |
Last Updated | 2025-07-31 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | planner ros calibration self-driving-car autonomous-driving autonomous-vehicles ros2 3d-map autoware |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Fumihito Ito
- Junya Sasaki
Authors
autoware_velodyne_monitor
Purpose
This node monitors the status of Velodyne LiDARs. The result of the status is published as diagnostics. Take care not to use this diagnostics to decide the lidar error. Please read Assumptions / Known limits for the detail reason.
Inner-workings / Algorithms
The status of Velodyne LiDAR can be retrieved from http://[ip_address]/cgi/{info, settings, status, diag}.json
.
The types of abnormal status and corresponding diagnostics status are following.
Abnormal status | Diagnostic status |
---|---|
No abnormality | OK |
Top board temperature is too cold | ERROR |
Top board temperature is cold | WARN |
Top board temperature is too hot | ERROR |
Top board temperature is hot | WARN |
Bottom board temperature is too cold | ERROR |
Bottom board temperature is cold | WARN |
Bottom board temperature is too hot | ERROR |
Bottom board temperature is hot | WARN |
Rpm(Rotations per minute) of the motor is too low | ERROR |
Rpm(Rotations per minute) of the motor is low | WARN |
Connection error (cannot get Velodyne LiDAR status) | ERROR |
Inputs / Outputs
Input
None
Output
Name | Type | Description |
---|---|---|
/diagnostics |
diagnostic_msgs/DiagnosticArray |
Diagnostics outputs |
Parameters
Node Parameters
Name | Type | Default Value | Description |
---|---|---|---|
timeout |
double | 0.5 | Timeout for HTTP request to get Velodyne LiDAR status [s] |
Core Parameters
Name | Type | Default Value | Description |
---|---|---|---|
ip_address |
string | “192.168.1.201” | IP address of target Velodyne LiDAR |
temp_cold_warn |
double | -5.0 | If the temperature of Velodyne LiDAR is lower than this value, the diagnostics status becomes WARN [°C] |
temp_cold_error |
double | -10.0 | If the temperature of Velodyne LiDAR is lower than this value, the diagnostics status becomes ERROR [°C] |
temp_hot_warn |
double | 75.0 | If the temperature of Velodyne LiDAR is higher than this value, the diagnostics status becomes WARN [°C] |
temp_hot_error |
double | 80.0 | If the temperature of Velodyne LiDAR is higher than this value, the diagnostics status becomes ERROR [°C] |
rpm_ratio_warn |
double | 0.80 | If the rpm rate of the motor (= current rpm / default rpm) is lower than this value, the diagnostics status becomes WARN |
rpm_ratio_error |
double | 0.70 | If the rpm rate of the motor (= current rpm / default rpm) is lower than this value, the diagnostics status becomes ERROR |
Config files
Config files for several velodyne models are prepared.
The temp_***
parameters are set with reference to the operational temperature from each datasheet.
Moreover, the temp_hot_***
of each model are set highly as 20 from operational temperature.
Now, VLP-16.param.yaml
is used as default argument because it is lowest spec.
Model Name | Config name | Operational Temperature [℃] |
---|---|---|
VLP-16 | VLP-16.param.yaml | -10 to 60 |
VLP-32C | VLP-32C.param.yaml | -20 to 60 |
VLS-128 | VLS-128.param.yaml | -20 to 60 |
Velarray M1600 | Velarray_M1600.param.yaml | -40 to 85 |
HDL-32E | HDL-32E.param.yaml | -10 to 60 |
Assumptions / Known limits
This node uses the http_client and request results by GET method. It takes a few seconds to get results, or generate a timeout exception if it does not succeed the GET request. This occurs frequently and the diagnostics aggregator output STALE. Therefore I recommend to stop using this results to decide the lidar error, and only monitor it to confirm lidar status.
Changelog for package autoware_velodyne_monitor
0.46.0 (2025-06-20)
0.45.0 (2025-05-22)
0.44.2 (2025-06-10)
0.44.1 (2025-05-01)
0.44.0 (2025-04-18)
0.43.0 (2025-03-21)
- Merge remote-tracking branch 'origin/main' into chore/bump-version-0.43
- chore: rename from [autoware.universe]{.title-ref} to [autoware_universe]{.title-ref} (#10306)
- Contributors: Hayato Mizushima, Yutaka Kondo
0.42.0 (2025-03-03)
0.41.2 (2025-02-19)
- chore: bump version to 0.41.1 (#10088)
- Contributors: Ryohsuke Mitsudome
0.41.1 (2025-02-10)
0.41.0 (2025-01-29)
- Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
- feat: apply [autoware_]{.title-ref} prefix for [velodyne_monitor]{.title-ref} (#9976)
- Contributors: Fumiya Watanabe, Junya Sasaki
0.40.0 (2024-12-12)
-
Revert "chore(package.xml): bump version to 0.39.0 (#9587)" This reverts commit c9f0f2688c57b0f657f5c1f28f036a970682e7f5.
-
fix: fix ticket links in CHANGELOG.rst (#9588)
-
chore(package.xml): bump version to 0.39.0 (#9587)
- chore(package.xml): bump version to 0.39.0
- fix: fix ticket links in CHANGELOG.rst
* fix: remove unnecessary diff ---------Co-authored-by: Yutaka Kondo <<yutaka.kondo@youtalk.jp>>
-
fix: fix ticket links in CHANGELOG.rst (#9588)
-
0.39.0
-
update changelog
-
fix: fix ticket links to point to https://github.com/autowarefoundation/autoware_universe (#9304)
-
fix: fix ticket links to point to https://github.com/autowarefoundation/autoware_universe (#9304)
-
chore(package.xml): bump version to 0.38.0 (#9266) (#9284)
- unify package.xml version to 0.37.0
- remove system_monitor/CHANGELOG.rst
- add changelog
* 0.38.0
-
Contributors: Esteve Fernandez, Fumiya Watanabe, Ryohsuke Mitsudome, Yutaka Kondo
0.39.0 (2024-11-25)
- fix: fix ticket links to point to https://github.com/autowarefoundation/autoware_universe (#9304)
- fix: fix ticket links to point to https://github.com/autowarefoundation/autoware_universe (#9304)
- chore(package.xml): bump version to 0.38.0
(#9266)
(#9284)
- unify package.xml version to 0.37.0
- remove system_monitor/CHANGELOG.rst
- add changelog
File truncated at 100 lines see the full file
Package Dependencies
Deps | Name |
---|---|
ament_cmake_auto | |
autoware_cmake | |
ament_lint_auto | |
autoware_lint_common | |
diagnostic_msgs | |
diagnostic_updater | |
rclcpp | |
rclcpp_components | |
std_msgs |
System Dependencies
Name |
---|
crypto++ |
fmt |
libcpprest-dev |
Dependant Packages
Launch files
- launch/velodyne_monitor.launch.xml
-
- velodyne_monitor_param_file [default: $(find-pkg-share autoware_velodyne_monitor)/config/VLP-16.param.yaml]
- ip_address [default: 192.168.1.201]
Messages
Services
Plugins
Recent questions tagged autoware_velodyne_monitor at Robotics Stack Exchange
Package Summary
Tags | No category tags. |
Version | 0.46.0 |
License | Apache License 2.0 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | |
Checkout URI | https://github.com/autowarefoundation/autoware_universe.git |
VCS Type | git |
VCS Version | main |
Last Updated | 2025-07-31 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | planner ros calibration self-driving-car autonomous-driving autonomous-vehicles ros2 3d-map autoware |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Fumihito Ito
- Junya Sasaki
Authors
autoware_velodyne_monitor
Purpose
This node monitors the status of Velodyne LiDARs. The result of the status is published as diagnostics. Take care not to use this diagnostics to decide the lidar error. Please read Assumptions / Known limits for the detail reason.
Inner-workings / Algorithms
The status of Velodyne LiDAR can be retrieved from http://[ip_address]/cgi/{info, settings, status, diag}.json
.
The types of abnormal status and corresponding diagnostics status are following.
Abnormal status | Diagnostic status |
---|---|
No abnormality | OK |
Top board temperature is too cold | ERROR |
Top board temperature is cold | WARN |
Top board temperature is too hot | ERROR |
Top board temperature is hot | WARN |
Bottom board temperature is too cold | ERROR |
Bottom board temperature is cold | WARN |
Bottom board temperature is too hot | ERROR |
Bottom board temperature is hot | WARN |
Rpm(Rotations per minute) of the motor is too low | ERROR |
Rpm(Rotations per minute) of the motor is low | WARN |
Connection error (cannot get Velodyne LiDAR status) | ERROR |
Inputs / Outputs
Input
None
Output
Name | Type | Description |
---|---|---|
/diagnostics |
diagnostic_msgs/DiagnosticArray |
Diagnostics outputs |
Parameters
Node Parameters
Name | Type | Default Value | Description |
---|---|---|---|
timeout |
double | 0.5 | Timeout for HTTP request to get Velodyne LiDAR status [s] |
Core Parameters
Name | Type | Default Value | Description |
---|---|---|---|
ip_address |
string | “192.168.1.201” | IP address of target Velodyne LiDAR |
temp_cold_warn |
double | -5.0 | If the temperature of Velodyne LiDAR is lower than this value, the diagnostics status becomes WARN [°C] |
temp_cold_error |
double | -10.0 | If the temperature of Velodyne LiDAR is lower than this value, the diagnostics status becomes ERROR [°C] |
temp_hot_warn |
double | 75.0 | If the temperature of Velodyne LiDAR is higher than this value, the diagnostics status becomes WARN [°C] |
temp_hot_error |
double | 80.0 | If the temperature of Velodyne LiDAR is higher than this value, the diagnostics status becomes ERROR [°C] |
rpm_ratio_warn |
double | 0.80 | If the rpm rate of the motor (= current rpm / default rpm) is lower than this value, the diagnostics status becomes WARN |
rpm_ratio_error |
double | 0.70 | If the rpm rate of the motor (= current rpm / default rpm) is lower than this value, the diagnostics status becomes ERROR |
Config files
Config files for several velodyne models are prepared.
The temp_***
parameters are set with reference to the operational temperature from each datasheet.
Moreover, the temp_hot_***
of each model are set highly as 20 from operational temperature.
Now, VLP-16.param.yaml
is used as default argument because it is lowest spec.
Model Name | Config name | Operational Temperature [℃] |
---|---|---|
VLP-16 | VLP-16.param.yaml | -10 to 60 |
VLP-32C | VLP-32C.param.yaml | -20 to 60 |
VLS-128 | VLS-128.param.yaml | -20 to 60 |
Velarray M1600 | Velarray_M1600.param.yaml | -40 to 85 |
HDL-32E | HDL-32E.param.yaml | -10 to 60 |
Assumptions / Known limits
This node uses the http_client and request results by GET method. It takes a few seconds to get results, or generate a timeout exception if it does not succeed the GET request. This occurs frequently and the diagnostics aggregator output STALE. Therefore I recommend to stop using this results to decide the lidar error, and only monitor it to confirm lidar status.
Changelog for package autoware_velodyne_monitor
0.46.0 (2025-06-20)
0.45.0 (2025-05-22)
0.44.2 (2025-06-10)
0.44.1 (2025-05-01)
0.44.0 (2025-04-18)
0.43.0 (2025-03-21)
- Merge remote-tracking branch 'origin/main' into chore/bump-version-0.43
- chore: rename from [autoware.universe]{.title-ref} to [autoware_universe]{.title-ref} (#10306)
- Contributors: Hayato Mizushima, Yutaka Kondo
0.42.0 (2025-03-03)
0.41.2 (2025-02-19)
- chore: bump version to 0.41.1 (#10088)
- Contributors: Ryohsuke Mitsudome
0.41.1 (2025-02-10)
0.41.0 (2025-01-29)
- Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
- feat: apply [autoware_]{.title-ref} prefix for [velodyne_monitor]{.title-ref} (#9976)
- Contributors: Fumiya Watanabe, Junya Sasaki
0.40.0 (2024-12-12)
-
Revert "chore(package.xml): bump version to 0.39.0 (#9587)" This reverts commit c9f0f2688c57b0f657f5c1f28f036a970682e7f5.
-
fix: fix ticket links in CHANGELOG.rst (#9588)
-
chore(package.xml): bump version to 0.39.0 (#9587)
- chore(package.xml): bump version to 0.39.0
- fix: fix ticket links in CHANGELOG.rst
* fix: remove unnecessary diff ---------Co-authored-by: Yutaka Kondo <<yutaka.kondo@youtalk.jp>>
-
fix: fix ticket links in CHANGELOG.rst (#9588)
-
0.39.0
-
update changelog
-
fix: fix ticket links to point to https://github.com/autowarefoundation/autoware_universe (#9304)
-
fix: fix ticket links to point to https://github.com/autowarefoundation/autoware_universe (#9304)
-
chore(package.xml): bump version to 0.38.0 (#9266) (#9284)
- unify package.xml version to 0.37.0
- remove system_monitor/CHANGELOG.rst
- add changelog
* 0.38.0
-
Contributors: Esteve Fernandez, Fumiya Watanabe, Ryohsuke Mitsudome, Yutaka Kondo
0.39.0 (2024-11-25)
- fix: fix ticket links to point to https://github.com/autowarefoundation/autoware_universe (#9304)
- fix: fix ticket links to point to https://github.com/autowarefoundation/autoware_universe (#9304)
- chore(package.xml): bump version to 0.38.0
(#9266)
(#9284)
- unify package.xml version to 0.37.0
- remove system_monitor/CHANGELOG.rst
- add changelog
File truncated at 100 lines see the full file
Package Dependencies
Deps | Name |
---|---|
ament_cmake_auto | |
autoware_cmake | |
ament_lint_auto | |
autoware_lint_common | |
diagnostic_msgs | |
diagnostic_updater | |
rclcpp | |
rclcpp_components | |
std_msgs |
System Dependencies
Name |
---|
crypto++ |
fmt |
libcpprest-dev |
Dependant Packages
Launch files
- launch/velodyne_monitor.launch.xml
-
- velodyne_monitor_param_file [default: $(find-pkg-share autoware_velodyne_monitor)/config/VLP-16.param.yaml]
- ip_address [default: 192.168.1.201]
Messages
Services
Plugins
Recent questions tagged autoware_velodyne_monitor at Robotics Stack Exchange
Package Summary
Tags | No category tags. |
Version | 0.46.0 |
License | Apache License 2.0 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | |
Checkout URI | https://github.com/autowarefoundation/autoware_universe.git |
VCS Type | git |
VCS Version | main |
Last Updated | 2025-07-31 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | planner ros calibration self-driving-car autonomous-driving autonomous-vehicles ros2 3d-map autoware |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Fumihito Ito
- Junya Sasaki
Authors
autoware_velodyne_monitor
Purpose
This node monitors the status of Velodyne LiDARs. The result of the status is published as diagnostics. Take care not to use this diagnostics to decide the lidar error. Please read Assumptions / Known limits for the detail reason.
Inner-workings / Algorithms
The status of Velodyne LiDAR can be retrieved from http://[ip_address]/cgi/{info, settings, status, diag}.json
.
The types of abnormal status and corresponding diagnostics status are following.
Abnormal status | Diagnostic status |
---|---|
No abnormality | OK |
Top board temperature is too cold | ERROR |
Top board temperature is cold | WARN |
Top board temperature is too hot | ERROR |
Top board temperature is hot | WARN |
Bottom board temperature is too cold | ERROR |
Bottom board temperature is cold | WARN |
Bottom board temperature is too hot | ERROR |
Bottom board temperature is hot | WARN |
Rpm(Rotations per minute) of the motor is too low | ERROR |
Rpm(Rotations per minute) of the motor is low | WARN |
Connection error (cannot get Velodyne LiDAR status) | ERROR |
Inputs / Outputs
Input
None
Output
Name | Type | Description |
---|---|---|
/diagnostics |
diagnostic_msgs/DiagnosticArray |
Diagnostics outputs |
Parameters
Node Parameters
Name | Type | Default Value | Description |
---|---|---|---|
timeout |
double | 0.5 | Timeout for HTTP request to get Velodyne LiDAR status [s] |
Core Parameters
Name | Type | Default Value | Description |
---|---|---|---|
ip_address |
string | “192.168.1.201” | IP address of target Velodyne LiDAR |
temp_cold_warn |
double | -5.0 | If the temperature of Velodyne LiDAR is lower than this value, the diagnostics status becomes WARN [°C] |
temp_cold_error |
double | -10.0 | If the temperature of Velodyne LiDAR is lower than this value, the diagnostics status becomes ERROR [°C] |
temp_hot_warn |
double | 75.0 | If the temperature of Velodyne LiDAR is higher than this value, the diagnostics status becomes WARN [°C] |
temp_hot_error |
double | 80.0 | If the temperature of Velodyne LiDAR is higher than this value, the diagnostics status becomes ERROR [°C] |
rpm_ratio_warn |
double | 0.80 | If the rpm rate of the motor (= current rpm / default rpm) is lower than this value, the diagnostics status becomes WARN |
rpm_ratio_error |
double | 0.70 | If the rpm rate of the motor (= current rpm / default rpm) is lower than this value, the diagnostics status becomes ERROR |
Config files
Config files for several velodyne models are prepared.
The temp_***
parameters are set with reference to the operational temperature from each datasheet.
Moreover, the temp_hot_***
of each model are set highly as 20 from operational temperature.
Now, VLP-16.param.yaml
is used as default argument because it is lowest spec.
Model Name | Config name | Operational Temperature [℃] |
---|---|---|
VLP-16 | VLP-16.param.yaml | -10 to 60 |
VLP-32C | VLP-32C.param.yaml | -20 to 60 |
VLS-128 | VLS-128.param.yaml | -20 to 60 |
Velarray M1600 | Velarray_M1600.param.yaml | -40 to 85 |
HDL-32E | HDL-32E.param.yaml | -10 to 60 |
Assumptions / Known limits
This node uses the http_client and request results by GET method. It takes a few seconds to get results, or generate a timeout exception if it does not succeed the GET request. This occurs frequently and the diagnostics aggregator output STALE. Therefore I recommend to stop using this results to decide the lidar error, and only monitor it to confirm lidar status.
Changelog for package autoware_velodyne_monitor
0.46.0 (2025-06-20)
0.45.0 (2025-05-22)
0.44.2 (2025-06-10)
0.44.1 (2025-05-01)
0.44.0 (2025-04-18)
0.43.0 (2025-03-21)
- Merge remote-tracking branch 'origin/main' into chore/bump-version-0.43
- chore: rename from [autoware.universe]{.title-ref} to [autoware_universe]{.title-ref} (#10306)
- Contributors: Hayato Mizushima, Yutaka Kondo
0.42.0 (2025-03-03)
0.41.2 (2025-02-19)
- chore: bump version to 0.41.1 (#10088)
- Contributors: Ryohsuke Mitsudome
0.41.1 (2025-02-10)
0.41.0 (2025-01-29)
- Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
- feat: apply [autoware_]{.title-ref} prefix for [velodyne_monitor]{.title-ref} (#9976)
- Contributors: Fumiya Watanabe, Junya Sasaki
0.40.0 (2024-12-12)
-
Revert "chore(package.xml): bump version to 0.39.0 (#9587)" This reverts commit c9f0f2688c57b0f657f5c1f28f036a970682e7f5.
-
fix: fix ticket links in CHANGELOG.rst (#9588)
-
chore(package.xml): bump version to 0.39.0 (#9587)
- chore(package.xml): bump version to 0.39.0
- fix: fix ticket links in CHANGELOG.rst
* fix: remove unnecessary diff ---------Co-authored-by: Yutaka Kondo <<yutaka.kondo@youtalk.jp>>
-
fix: fix ticket links in CHANGELOG.rst (#9588)
-
0.39.0
-
update changelog
-
fix: fix ticket links to point to https://github.com/autowarefoundation/autoware_universe (#9304)
-
fix: fix ticket links to point to https://github.com/autowarefoundation/autoware_universe (#9304)
-
chore(package.xml): bump version to 0.38.0 (#9266) (#9284)
- unify package.xml version to 0.37.0
- remove system_monitor/CHANGELOG.rst
- add changelog
* 0.38.0
-
Contributors: Esteve Fernandez, Fumiya Watanabe, Ryohsuke Mitsudome, Yutaka Kondo
0.39.0 (2024-11-25)
- fix: fix ticket links to point to https://github.com/autowarefoundation/autoware_universe (#9304)
- fix: fix ticket links to point to https://github.com/autowarefoundation/autoware_universe (#9304)
- chore(package.xml): bump version to 0.38.0
(#9266)
(#9284)
- unify package.xml version to 0.37.0
- remove system_monitor/CHANGELOG.rst
- add changelog
File truncated at 100 lines see the full file
Package Dependencies
Deps | Name |
---|---|
ament_cmake_auto | |
autoware_cmake | |
ament_lint_auto | |
autoware_lint_common | |
diagnostic_msgs | |
diagnostic_updater | |
rclcpp | |
rclcpp_components | |
std_msgs |
System Dependencies
Name |
---|
crypto++ |
fmt |
libcpprest-dev |
Dependant Packages
Launch files
- launch/velodyne_monitor.launch.xml
-
- velodyne_monitor_param_file [default: $(find-pkg-share autoware_velodyne_monitor)/config/VLP-16.param.yaml]
- ip_address [default: 192.168.1.201]
Messages
Services
Plugins
Recent questions tagged autoware_velodyne_monitor at Robotics Stack Exchange
Package Summary
Tags | No category tags. |
Version | 0.46.0 |
License | Apache License 2.0 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | |
Checkout URI | https://github.com/autowarefoundation/autoware_universe.git |
VCS Type | git |
VCS Version | main |
Last Updated | 2025-07-31 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | planner ros calibration self-driving-car autonomous-driving autonomous-vehicles ros2 3d-map autoware |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Fumihito Ito
- Junya Sasaki
Authors
autoware_velodyne_monitor
Purpose
This node monitors the status of Velodyne LiDARs. The result of the status is published as diagnostics. Take care not to use this diagnostics to decide the lidar error. Please read Assumptions / Known limits for the detail reason.
Inner-workings / Algorithms
The status of Velodyne LiDAR can be retrieved from http://[ip_address]/cgi/{info, settings, status, diag}.json
.
The types of abnormal status and corresponding diagnostics status are following.
Abnormal status | Diagnostic status |
---|---|
No abnormality | OK |
Top board temperature is too cold | ERROR |
Top board temperature is cold | WARN |
Top board temperature is too hot | ERROR |
Top board temperature is hot | WARN |
Bottom board temperature is too cold | ERROR |
Bottom board temperature is cold | WARN |
Bottom board temperature is too hot | ERROR |
Bottom board temperature is hot | WARN |
Rpm(Rotations per minute) of the motor is too low | ERROR |
Rpm(Rotations per minute) of the motor is low | WARN |
Connection error (cannot get Velodyne LiDAR status) | ERROR |
Inputs / Outputs
Input
None
Output
Name | Type | Description |
---|---|---|
/diagnostics |
diagnostic_msgs/DiagnosticArray |
Diagnostics outputs |
Parameters
Node Parameters
Name | Type | Default Value | Description |
---|---|---|---|
timeout |
double | 0.5 | Timeout for HTTP request to get Velodyne LiDAR status [s] |
Core Parameters
Name | Type | Default Value | Description |
---|---|---|---|
ip_address |
string | “192.168.1.201” | IP address of target Velodyne LiDAR |
temp_cold_warn |
double | -5.0 | If the temperature of Velodyne LiDAR is lower than this value, the diagnostics status becomes WARN [°C] |
temp_cold_error |
double | -10.0 | If the temperature of Velodyne LiDAR is lower than this value, the diagnostics status becomes ERROR [°C] |
temp_hot_warn |
double | 75.0 | If the temperature of Velodyne LiDAR is higher than this value, the diagnostics status becomes WARN [°C] |
temp_hot_error |
double | 80.0 | If the temperature of Velodyne LiDAR is higher than this value, the diagnostics status becomes ERROR [°C] |
rpm_ratio_warn |
double | 0.80 | If the rpm rate of the motor (= current rpm / default rpm) is lower than this value, the diagnostics status becomes WARN |
rpm_ratio_error |
double | 0.70 | If the rpm rate of the motor (= current rpm / default rpm) is lower than this value, the diagnostics status becomes ERROR |
Config files
Config files for several velodyne models are prepared.
The temp_***
parameters are set with reference to the operational temperature from each datasheet.
Moreover, the temp_hot_***
of each model are set highly as 20 from operational temperature.
Now, VLP-16.param.yaml
is used as default argument because it is lowest spec.
Model Name | Config name | Operational Temperature [℃] |
---|---|---|
VLP-16 | VLP-16.param.yaml | -10 to 60 |
VLP-32C | VLP-32C.param.yaml | -20 to 60 |
VLS-128 | VLS-128.param.yaml | -20 to 60 |
Velarray M1600 | Velarray_M1600.param.yaml | -40 to 85 |
HDL-32E | HDL-32E.param.yaml | -10 to 60 |
Assumptions / Known limits
This node uses the http_client and request results by GET method. It takes a few seconds to get results, or generate a timeout exception if it does not succeed the GET request. This occurs frequently and the diagnostics aggregator output STALE. Therefore I recommend to stop using this results to decide the lidar error, and only monitor it to confirm lidar status.
Changelog for package autoware_velodyne_monitor
0.46.0 (2025-06-20)
0.45.0 (2025-05-22)
0.44.2 (2025-06-10)
0.44.1 (2025-05-01)
0.44.0 (2025-04-18)
0.43.0 (2025-03-21)
- Merge remote-tracking branch 'origin/main' into chore/bump-version-0.43
- chore: rename from [autoware.universe]{.title-ref} to [autoware_universe]{.title-ref} (#10306)
- Contributors: Hayato Mizushima, Yutaka Kondo
0.42.0 (2025-03-03)
0.41.2 (2025-02-19)
- chore: bump version to 0.41.1 (#10088)
- Contributors: Ryohsuke Mitsudome
0.41.1 (2025-02-10)
0.41.0 (2025-01-29)
- Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
- feat: apply [autoware_]{.title-ref} prefix for [velodyne_monitor]{.title-ref} (#9976)
- Contributors: Fumiya Watanabe, Junya Sasaki
0.40.0 (2024-12-12)
-
Revert "chore(package.xml): bump version to 0.39.0 (#9587)" This reverts commit c9f0f2688c57b0f657f5c1f28f036a970682e7f5.
-
fix: fix ticket links in CHANGELOG.rst (#9588)
-
chore(package.xml): bump version to 0.39.0 (#9587)
- chore(package.xml): bump version to 0.39.0
- fix: fix ticket links in CHANGELOG.rst
* fix: remove unnecessary diff ---------Co-authored-by: Yutaka Kondo <<yutaka.kondo@youtalk.jp>>
-
fix: fix ticket links in CHANGELOG.rst (#9588)
-
0.39.0
-
update changelog
-
fix: fix ticket links to point to https://github.com/autowarefoundation/autoware_universe (#9304)
-
fix: fix ticket links to point to https://github.com/autowarefoundation/autoware_universe (#9304)
-
chore(package.xml): bump version to 0.38.0 (#9266) (#9284)
- unify package.xml version to 0.37.0
- remove system_monitor/CHANGELOG.rst
- add changelog
* 0.38.0
-
Contributors: Esteve Fernandez, Fumiya Watanabe, Ryohsuke Mitsudome, Yutaka Kondo
0.39.0 (2024-11-25)
- fix: fix ticket links to point to https://github.com/autowarefoundation/autoware_universe (#9304)
- fix: fix ticket links to point to https://github.com/autowarefoundation/autoware_universe (#9304)
- chore(package.xml): bump version to 0.38.0
(#9266)
(#9284)
- unify package.xml version to 0.37.0
- remove system_monitor/CHANGELOG.rst
- add changelog
File truncated at 100 lines see the full file
Package Dependencies
Deps | Name |
---|---|
ament_cmake_auto | |
autoware_cmake | |
ament_lint_auto | |
autoware_lint_common | |
diagnostic_msgs | |
diagnostic_updater | |
rclcpp | |
rclcpp_components | |
std_msgs |
System Dependencies
Name |
---|
crypto++ |
fmt |
libcpprest-dev |
Dependant Packages
Launch files
- launch/velodyne_monitor.launch.xml
-
- velodyne_monitor_param_file [default: $(find-pkg-share autoware_velodyne_monitor)/config/VLP-16.param.yaml]
- ip_address [default: 192.168.1.201]
Messages
Services
Plugins
Recent questions tagged autoware_velodyne_monitor at Robotics Stack Exchange
Package Summary
Tags | No category tags. |
Version | 0.46.0 |
License | Apache License 2.0 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | |
Checkout URI | https://github.com/autowarefoundation/autoware_universe.git |
VCS Type | git |
VCS Version | main |
Last Updated | 2025-07-31 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | planner ros calibration self-driving-car autonomous-driving autonomous-vehicles ros2 3d-map autoware |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Fumihito Ito
- Junya Sasaki
Authors
autoware_velodyne_monitor
Purpose
This node monitors the status of Velodyne LiDARs. The result of the status is published as diagnostics. Take care not to use this diagnostics to decide the lidar error. Please read Assumptions / Known limits for the detail reason.
Inner-workings / Algorithms
The status of Velodyne LiDAR can be retrieved from http://[ip_address]/cgi/{info, settings, status, diag}.json
.
The types of abnormal status and corresponding diagnostics status are following.
Abnormal status | Diagnostic status |
---|---|
No abnormality | OK |
Top board temperature is too cold | ERROR |
Top board temperature is cold | WARN |
Top board temperature is too hot | ERROR |
Top board temperature is hot | WARN |
Bottom board temperature is too cold | ERROR |
Bottom board temperature is cold | WARN |
Bottom board temperature is too hot | ERROR |
Bottom board temperature is hot | WARN |
Rpm(Rotations per minute) of the motor is too low | ERROR |
Rpm(Rotations per minute) of the motor is low | WARN |
Connection error (cannot get Velodyne LiDAR status) | ERROR |
Inputs / Outputs
Input
None
Output
Name | Type | Description |
---|---|---|
/diagnostics |
diagnostic_msgs/DiagnosticArray |
Diagnostics outputs |
Parameters
Node Parameters
Name | Type | Default Value | Description |
---|---|---|---|
timeout |
double | 0.5 | Timeout for HTTP request to get Velodyne LiDAR status [s] |
Core Parameters
Name | Type | Default Value | Description |
---|---|---|---|
ip_address |
string | “192.168.1.201” | IP address of target Velodyne LiDAR |
temp_cold_warn |
double | -5.0 | If the temperature of Velodyne LiDAR is lower than this value, the diagnostics status becomes WARN [°C] |
temp_cold_error |
double | -10.0 | If the temperature of Velodyne LiDAR is lower than this value, the diagnostics status becomes ERROR [°C] |
temp_hot_warn |
double | 75.0 | If the temperature of Velodyne LiDAR is higher than this value, the diagnostics status becomes WARN [°C] |
temp_hot_error |
double | 80.0 | If the temperature of Velodyne LiDAR is higher than this value, the diagnostics status becomes ERROR [°C] |
rpm_ratio_warn |
double | 0.80 | If the rpm rate of the motor (= current rpm / default rpm) is lower than this value, the diagnostics status becomes WARN |
rpm_ratio_error |
double | 0.70 | If the rpm rate of the motor (= current rpm / default rpm) is lower than this value, the diagnostics status becomes ERROR |
Config files
Config files for several velodyne models are prepared.
The temp_***
parameters are set with reference to the operational temperature from each datasheet.
Moreover, the temp_hot_***
of each model are set highly as 20 from operational temperature.
Now, VLP-16.param.yaml
is used as default argument because it is lowest spec.
Model Name | Config name | Operational Temperature [℃] |
---|---|---|
VLP-16 | VLP-16.param.yaml | -10 to 60 |
VLP-32C | VLP-32C.param.yaml | -20 to 60 |
VLS-128 | VLS-128.param.yaml | -20 to 60 |
Velarray M1600 | Velarray_M1600.param.yaml | -40 to 85 |
HDL-32E | HDL-32E.param.yaml | -10 to 60 |
Assumptions / Known limits
This node uses the http_client and request results by GET method. It takes a few seconds to get results, or generate a timeout exception if it does not succeed the GET request. This occurs frequently and the diagnostics aggregator output STALE. Therefore I recommend to stop using this results to decide the lidar error, and only monitor it to confirm lidar status.
Changelog for package autoware_velodyne_monitor
0.46.0 (2025-06-20)
0.45.0 (2025-05-22)
0.44.2 (2025-06-10)
0.44.1 (2025-05-01)
0.44.0 (2025-04-18)
0.43.0 (2025-03-21)
- Merge remote-tracking branch 'origin/main' into chore/bump-version-0.43
- chore: rename from [autoware.universe]{.title-ref} to [autoware_universe]{.title-ref} (#10306)
- Contributors: Hayato Mizushima, Yutaka Kondo
0.42.0 (2025-03-03)
0.41.2 (2025-02-19)
- chore: bump version to 0.41.1 (#10088)
- Contributors: Ryohsuke Mitsudome
0.41.1 (2025-02-10)
0.41.0 (2025-01-29)
- Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
- feat: apply [autoware_]{.title-ref} prefix for [velodyne_monitor]{.title-ref} (#9976)
- Contributors: Fumiya Watanabe, Junya Sasaki
0.40.0 (2024-12-12)
-
Revert "chore(package.xml): bump version to 0.39.0 (#9587)" This reverts commit c9f0f2688c57b0f657f5c1f28f036a970682e7f5.
-
fix: fix ticket links in CHANGELOG.rst (#9588)
-
chore(package.xml): bump version to 0.39.0 (#9587)
- chore(package.xml): bump version to 0.39.0
- fix: fix ticket links in CHANGELOG.rst
* fix: remove unnecessary diff ---------Co-authored-by: Yutaka Kondo <<yutaka.kondo@youtalk.jp>>
-
fix: fix ticket links in CHANGELOG.rst (#9588)
-
0.39.0
-
update changelog
-
fix: fix ticket links to point to https://github.com/autowarefoundation/autoware_universe (#9304)
-
fix: fix ticket links to point to https://github.com/autowarefoundation/autoware_universe (#9304)
-
chore(package.xml): bump version to 0.38.0 (#9266) (#9284)
- unify package.xml version to 0.37.0
- remove system_monitor/CHANGELOG.rst
- add changelog
* 0.38.0
-
Contributors: Esteve Fernandez, Fumiya Watanabe, Ryohsuke Mitsudome, Yutaka Kondo
0.39.0 (2024-11-25)
- fix: fix ticket links to point to https://github.com/autowarefoundation/autoware_universe (#9304)
- fix: fix ticket links to point to https://github.com/autowarefoundation/autoware_universe (#9304)
- chore(package.xml): bump version to 0.38.0
(#9266)
(#9284)
- unify package.xml version to 0.37.0
- remove system_monitor/CHANGELOG.rst
- add changelog
File truncated at 100 lines see the full file
Package Dependencies
Deps | Name |
---|---|
ament_cmake_auto | |
autoware_cmake | |
ament_lint_auto | |
autoware_lint_common | |
diagnostic_msgs | |
diagnostic_updater | |
rclcpp | |
rclcpp_components | |
std_msgs |
System Dependencies
Name |
---|
crypto++ |
fmt |
libcpprest-dev |
Dependant Packages
Launch files
- launch/velodyne_monitor.launch.xml
-
- velodyne_monitor_param_file [default: $(find-pkg-share autoware_velodyne_monitor)/config/VLP-16.param.yaml]
- ip_address [default: 192.168.1.201]
Messages
Services
Plugins
Recent questions tagged autoware_velodyne_monitor at Robotics Stack Exchange
Package Summary
Tags | No category tags. |
Version | 0.46.0 |
License | Apache License 2.0 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | |
Checkout URI | https://github.com/autowarefoundation/autoware_universe.git |
VCS Type | git |
VCS Version | main |
Last Updated | 2025-07-31 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | planner ros calibration self-driving-car autonomous-driving autonomous-vehicles ros2 3d-map autoware |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Fumihito Ito
- Junya Sasaki
Authors
autoware_velodyne_monitor
Purpose
This node monitors the status of Velodyne LiDARs. The result of the status is published as diagnostics. Take care not to use this diagnostics to decide the lidar error. Please read Assumptions / Known limits for the detail reason.
Inner-workings / Algorithms
The status of Velodyne LiDAR can be retrieved from http://[ip_address]/cgi/{info, settings, status, diag}.json
.
The types of abnormal status and corresponding diagnostics status are following.
Abnormal status | Diagnostic status |
---|---|
No abnormality | OK |
Top board temperature is too cold | ERROR |
Top board temperature is cold | WARN |
Top board temperature is too hot | ERROR |
Top board temperature is hot | WARN |
Bottom board temperature is too cold | ERROR |
Bottom board temperature is cold | WARN |
Bottom board temperature is too hot | ERROR |
Bottom board temperature is hot | WARN |
Rpm(Rotations per minute) of the motor is too low | ERROR |
Rpm(Rotations per minute) of the motor is low | WARN |
Connection error (cannot get Velodyne LiDAR status) | ERROR |
Inputs / Outputs
Input
None
Output
Name | Type | Description |
---|---|---|
/diagnostics |
diagnostic_msgs/DiagnosticArray |
Diagnostics outputs |
Parameters
Node Parameters
Name | Type | Default Value | Description |
---|---|---|---|
timeout |
double | 0.5 | Timeout for HTTP request to get Velodyne LiDAR status [s] |
Core Parameters
Name | Type | Default Value | Description |
---|---|---|---|
ip_address |
string | “192.168.1.201” | IP address of target Velodyne LiDAR |
temp_cold_warn |
double | -5.0 | If the temperature of Velodyne LiDAR is lower than this value, the diagnostics status becomes WARN [°C] |
temp_cold_error |
double | -10.0 | If the temperature of Velodyne LiDAR is lower than this value, the diagnostics status becomes ERROR [°C] |
temp_hot_warn |
double | 75.0 | If the temperature of Velodyne LiDAR is higher than this value, the diagnostics status becomes WARN [°C] |
temp_hot_error |
double | 80.0 | If the temperature of Velodyne LiDAR is higher than this value, the diagnostics status becomes ERROR [°C] |
rpm_ratio_warn |
double | 0.80 | If the rpm rate of the motor (= current rpm / default rpm) is lower than this value, the diagnostics status becomes WARN |
rpm_ratio_error |
double | 0.70 | If the rpm rate of the motor (= current rpm / default rpm) is lower than this value, the diagnostics status becomes ERROR |
Config files
Config files for several velodyne models are prepared.
The temp_***
parameters are set with reference to the operational temperature from each datasheet.
Moreover, the temp_hot_***
of each model are set highly as 20 from operational temperature.
Now, VLP-16.param.yaml
is used as default argument because it is lowest spec.
Model Name | Config name | Operational Temperature [℃] |
---|---|---|
VLP-16 | VLP-16.param.yaml | -10 to 60 |
VLP-32C | VLP-32C.param.yaml | -20 to 60 |
VLS-128 | VLS-128.param.yaml | -20 to 60 |
Velarray M1600 | Velarray_M1600.param.yaml | -40 to 85 |
HDL-32E | HDL-32E.param.yaml | -10 to 60 |
Assumptions / Known limits
This node uses the http_client and request results by GET method. It takes a few seconds to get results, or generate a timeout exception if it does not succeed the GET request. This occurs frequently and the diagnostics aggregator output STALE. Therefore I recommend to stop using this results to decide the lidar error, and only monitor it to confirm lidar status.
Changelog for package autoware_velodyne_monitor
0.46.0 (2025-06-20)
0.45.0 (2025-05-22)
0.44.2 (2025-06-10)
0.44.1 (2025-05-01)
0.44.0 (2025-04-18)
0.43.0 (2025-03-21)
- Merge remote-tracking branch 'origin/main' into chore/bump-version-0.43
- chore: rename from [autoware.universe]{.title-ref} to [autoware_universe]{.title-ref} (#10306)
- Contributors: Hayato Mizushima, Yutaka Kondo
0.42.0 (2025-03-03)
0.41.2 (2025-02-19)
- chore: bump version to 0.41.1 (#10088)
- Contributors: Ryohsuke Mitsudome
0.41.1 (2025-02-10)
0.41.0 (2025-01-29)
- Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
- feat: apply [autoware_]{.title-ref} prefix for [velodyne_monitor]{.title-ref} (#9976)
- Contributors: Fumiya Watanabe, Junya Sasaki
0.40.0 (2024-12-12)
-
Revert "chore(package.xml): bump version to 0.39.0 (#9587)" This reverts commit c9f0f2688c57b0f657f5c1f28f036a970682e7f5.
-
fix: fix ticket links in CHANGELOG.rst (#9588)
-
chore(package.xml): bump version to 0.39.0 (#9587)
- chore(package.xml): bump version to 0.39.0
- fix: fix ticket links in CHANGELOG.rst
* fix: remove unnecessary diff ---------Co-authored-by: Yutaka Kondo <<yutaka.kondo@youtalk.jp>>
-
fix: fix ticket links in CHANGELOG.rst (#9588)
-
0.39.0
-
update changelog
-
fix: fix ticket links to point to https://github.com/autowarefoundation/autoware_universe (#9304)
-
fix: fix ticket links to point to https://github.com/autowarefoundation/autoware_universe (#9304)
-
chore(package.xml): bump version to 0.38.0 (#9266) (#9284)
- unify package.xml version to 0.37.0
- remove system_monitor/CHANGELOG.rst
- add changelog
* 0.38.0
-
Contributors: Esteve Fernandez, Fumiya Watanabe, Ryohsuke Mitsudome, Yutaka Kondo
0.39.0 (2024-11-25)
- fix: fix ticket links to point to https://github.com/autowarefoundation/autoware_universe (#9304)
- fix: fix ticket links to point to https://github.com/autowarefoundation/autoware_universe (#9304)
- chore(package.xml): bump version to 0.38.0
(#9266)
(#9284)
- unify package.xml version to 0.37.0
- remove system_monitor/CHANGELOG.rst
- add changelog
File truncated at 100 lines see the full file
Package Dependencies
Deps | Name |
---|---|
ament_cmake_auto | |
autoware_cmake | |
ament_lint_auto | |
autoware_lint_common | |
diagnostic_msgs | |
diagnostic_updater | |
rclcpp | |
rclcpp_components | |
std_msgs |
System Dependencies
Name |
---|
crypto++ |
fmt |
libcpprest-dev |
Dependant Packages
Launch files
- launch/velodyne_monitor.launch.xml
-
- velodyne_monitor_param_file [default: $(find-pkg-share autoware_velodyne_monitor)/config/VLP-16.param.yaml]
- ip_address [default: 192.168.1.201]
Messages
Services
Plugins
Recent questions tagged autoware_velodyne_monitor at Robotics Stack Exchange
Package Summary
Tags | No category tags. |
Version | 0.46.0 |
License | Apache License 2.0 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Description | |
Checkout URI | https://github.com/autowarefoundation/autoware_universe.git |
VCS Type | git |
VCS Version | main |
Last Updated | 2025-07-31 |
Dev Status | UNKNOWN |
Released | UNRELEASED |
Tags | planner ros calibration self-driving-car autonomous-driving autonomous-vehicles ros2 3d-map autoware |
Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Fumihito Ito
- Junya Sasaki
Authors
autoware_velodyne_monitor
Purpose
This node monitors the status of Velodyne LiDARs. The result of the status is published as diagnostics. Take care not to use this diagnostics to decide the lidar error. Please read Assumptions / Known limits for the detail reason.
Inner-workings / Algorithms
The status of Velodyne LiDAR can be retrieved from http://[ip_address]/cgi/{info, settings, status, diag}.json
.
The types of abnormal status and corresponding diagnostics status are following.
Abnormal status | Diagnostic status |
---|---|
No abnormality | OK |
Top board temperature is too cold | ERROR |
Top board temperature is cold | WARN |
Top board temperature is too hot | ERROR |
Top board temperature is hot | WARN |
Bottom board temperature is too cold | ERROR |
Bottom board temperature is cold | WARN |
Bottom board temperature is too hot | ERROR |
Bottom board temperature is hot | WARN |
Rpm(Rotations per minute) of the motor is too low | ERROR |
Rpm(Rotations per minute) of the motor is low | WARN |
Connection error (cannot get Velodyne LiDAR status) | ERROR |
Inputs / Outputs
Input
None
Output
Name | Type | Description |
---|---|---|
/diagnostics |
diagnostic_msgs/DiagnosticArray |
Diagnostics outputs |
Parameters
Node Parameters
Name | Type | Default Value | Description |
---|---|---|---|
timeout |
double | 0.5 | Timeout for HTTP request to get Velodyne LiDAR status [s] |
Core Parameters
Name | Type | Default Value | Description |
---|---|---|---|
ip_address |
string | “192.168.1.201” | IP address of target Velodyne LiDAR |
temp_cold_warn |
double | -5.0 | If the temperature of Velodyne LiDAR is lower than this value, the diagnostics status becomes WARN [°C] |
temp_cold_error |
double | -10.0 | If the temperature of Velodyne LiDAR is lower than this value, the diagnostics status becomes ERROR [°C] |
temp_hot_warn |
double | 75.0 | If the temperature of Velodyne LiDAR is higher than this value, the diagnostics status becomes WARN [°C] |
temp_hot_error |
double | 80.0 | If the temperature of Velodyne LiDAR is higher than this value, the diagnostics status becomes ERROR [°C] |
rpm_ratio_warn |
double | 0.80 | If the rpm rate of the motor (= current rpm / default rpm) is lower than this value, the diagnostics status becomes WARN |
rpm_ratio_error |
double | 0.70 | If the rpm rate of the motor (= current rpm / default rpm) is lower than this value, the diagnostics status becomes ERROR |
Config files
Config files for several velodyne models are prepared.
The temp_***
parameters are set with reference to the operational temperature from each datasheet.
Moreover, the temp_hot_***
of each model are set highly as 20 from operational temperature.
Now, VLP-16.param.yaml
is used as default argument because it is lowest spec.
Model Name | Config name | Operational Temperature [℃] |
---|---|---|
VLP-16 | VLP-16.param.yaml | -10 to 60 |
VLP-32C | VLP-32C.param.yaml | -20 to 60 |
VLS-128 | VLS-128.param.yaml | -20 to 60 |
Velarray M1600 | Velarray_M1600.param.yaml | -40 to 85 |
HDL-32E | HDL-32E.param.yaml | -10 to 60 |
Assumptions / Known limits
This node uses the http_client and request results by GET method. It takes a few seconds to get results, or generate a timeout exception if it does not succeed the GET request. This occurs frequently and the diagnostics aggregator output STALE. Therefore I recommend to stop using this results to decide the lidar error, and only monitor it to confirm lidar status.
Changelog for package autoware_velodyne_monitor
0.46.0 (2025-06-20)
0.45.0 (2025-05-22)
0.44.2 (2025-06-10)
0.44.1 (2025-05-01)
0.44.0 (2025-04-18)
0.43.0 (2025-03-21)
- Merge remote-tracking branch 'origin/main' into chore/bump-version-0.43
- chore: rename from [autoware.universe]{.title-ref} to [autoware_universe]{.title-ref} (#10306)
- Contributors: Hayato Mizushima, Yutaka Kondo
0.42.0 (2025-03-03)
0.41.2 (2025-02-19)
- chore: bump version to 0.41.1 (#10088)
- Contributors: Ryohsuke Mitsudome
0.41.1 (2025-02-10)
0.41.0 (2025-01-29)
- Merge remote-tracking branch 'origin/main' into tmp/bot/bump_version_base
- feat: apply [autoware_]{.title-ref} prefix for [velodyne_monitor]{.title-ref} (#9976)
- Contributors: Fumiya Watanabe, Junya Sasaki
0.40.0 (2024-12-12)
-
Revert "chore(package.xml): bump version to 0.39.0 (#9587)" This reverts commit c9f0f2688c57b0f657f5c1f28f036a970682e7f5.
-
fix: fix ticket links in CHANGELOG.rst (#9588)
-
chore(package.xml): bump version to 0.39.0 (#9587)
- chore(package.xml): bump version to 0.39.0
- fix: fix ticket links in CHANGELOG.rst
* fix: remove unnecessary diff ---------Co-authored-by: Yutaka Kondo <<yutaka.kondo@youtalk.jp>>
-
fix: fix ticket links in CHANGELOG.rst (#9588)
-
0.39.0
-
update changelog
-
fix: fix ticket links to point to https://github.com/autowarefoundation/autoware_universe (#9304)
-
fix: fix ticket links to point to https://github.com/autowarefoundation/autoware_universe (#9304)
-
chore(package.xml): bump version to 0.38.0 (#9266) (#9284)
- unify package.xml version to 0.37.0
- remove system_monitor/CHANGELOG.rst
- add changelog
* 0.38.0
-
Contributors: Esteve Fernandez, Fumiya Watanabe, Ryohsuke Mitsudome, Yutaka Kondo
0.39.0 (2024-11-25)
- fix: fix ticket links to point to https://github.com/autowarefoundation/autoware_universe (#9304)
- fix: fix ticket links to point to https://github.com/autowarefoundation/autoware_universe (#9304)
- chore(package.xml): bump version to 0.38.0
(#9266)
(#9284)
- unify package.xml version to 0.37.0
- remove system_monitor/CHANGELOG.rst
- add changelog
File truncated at 100 lines see the full file
Package Dependencies
Deps | Name |
---|---|
ament_cmake_auto | |
autoware_cmake | |
ament_lint_auto | |
autoware_lint_common | |
diagnostic_msgs | |
diagnostic_updater | |
rclcpp | |
rclcpp_components | |
std_msgs |
System Dependencies
Name |
---|
crypto++ |
fmt |
libcpprest-dev |
Dependant Packages
Launch files
- launch/velodyne_monitor.launch.xml
-
- velodyne_monitor_param_file [default: $(find-pkg-share autoware_velodyne_monitor)/config/VLP-16.param.yaml]
- ip_address [default: 192.168.1.201]