generated from tier4/ros2-project-template
-
Notifications
You must be signed in to change notification settings - Fork 53
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix(velodyne_hw_monitor): allow max cloud angle of 360 degrees
Signed-off-by: David Wong <[email protected]>
- Loading branch information
Showing
2 changed files
with
8 additions
and
23 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,25 +1,10 @@ | ||
#nebula_velodyne_hw_interface: | ||
#nebula_velodyne_hw_monitor: | ||
/**: | ||
ros__parameters: | ||
sensor_model: "VLP32" # See readme for supported models | ||
sensor_ip: "192.168.1.201" # Lidar Sensor IP | ||
host_ip: "255.255.255.255" # Broadcast IP from Sensor | ||
sensor_model: "VLP32" | ||
sensor_ip: "192.168.1.201" | ||
host_ip: "255.255.255.255" | ||
frame_id: "velodyne" | ||
data_port: 2368 # LiDAR Data Port | ||
gnss_port: 2369 # LiDAR GNSS Port | ||
return_mode: "Dual" # See readme for supported return modes | ||
scan_phase: 0.0 # Angle where scans begin (degrees, [0.,360.] | ||
packet_mtu_size: 1500 # Packet MTU size | ||
rotation_speed: 600 # Motor RPM, the sensor's internal spin rate. | ||
cloud_min_angle: 0 # Field of View, start degrees. | ||
cloud_max_angle: 359 # Field of View, end degrees. | ||
diag_span: 1000 # milliseconds | ||
advanced_diagnostics: False # original diag | ||
min_range: 0.3 | ||
max_range: 300.0 | ||
view_width: 360.0 | ||
calibration_file: "./install/nebula_decoders/share/nebula_decoders/calibration/velodyne/VLP32.yaml" | ||
data_port: 2368 | ||
gnss_port: 2369 | ||
setup_sensor: True | ||
|
||
online: True |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters