Skip to content

feat(nav_msgs): add COLLISION_APPROACH_ACTIVE reason (#34) #23

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
skunal3318 merged 1 commit into from
Oct 9, 2026
Merged

feat(nav_msgs): add COLLISION_APPROACH_ACTIVE reason (#34) #23

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions compatibility/jazzy.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -251,6 +251,10 @@
"type": "uint16",
"value": 9004
},
"msg/COLLISION_APPROACH_ACTIVE": {
"type": "uint16",
"value": 6008
},
"msg/COLLISION_LAYER_INACTIVE": {
"type": "uint16",
"value": 6001
Expand Down
1 change: 1 addition & 0 deletions ros2/openamr_nav_msgs/msg/NavigationStatus.msg
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -80,6 +80,7 @@ uint16 PROTECTION_STATE_UNKNOWN=6004
uint16 SPEED_LIMIT_ACTIVE=6005
uint16 REVERSE_SPEED_LIMITED=6006
uint16 MOTION_SOURCE_PARTIALLY_PROTECTED=6007 # PARTIAL collision-monitor coverage, distinct from fully UNPROTECTED
uint16 COLLISION_APPROACH_ACTIVE=6008 # collision_monitor's "approach" polygon has triggered

# docking
uint16 DOCK_ENGAGEMENT_UNKNOWN=7001
Expand Down
Loading