ROS Index
|
|
Package Summary
| Tags | No category tags. |
| Version | 1.3.0 |
| License | Apache License 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/autowarefoundation/autoware_msgs.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2024-11-26 |
| Dev Status | DEVELOPED |
| CI status | No Continuous Integration |
| Released | RELEASED |
| Tags | No category tags. |
| Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Takagi, Isamu
- Ryohsuke Mitsudome
- Yukihiro Saito
Authors
autoware_v2x_msgs
Virtual gate messages
Overview
This message represents the status of the virtual gate for passing through the area managed by the facility. The virtual gate treats area entry permission as a shared resource and controls vehicles by acquiring and releasing locks. Each facility may support different protocols, but Autoware V2X component converts each protocol and this message. This allows Autoware to handle facilities with different protocols with a unified message.
Sequence
Because there is a time lag before commands are reflected, the vehicle must wait until it receives the status of the same sequence as the command it sent. Until the vehicle receives the status, treat it as if it were unlocked.
Gates
Specify the entrance and exit gate IDs. This is used to check if vehicles can pass simultaneously when multiple routes are possible within an area. If omitted, it is treated as a lock for the entire area.
Vehicle ID
This message does not include the vehicle ID, so add it in the V2X component if required by the communication protocol. And if facilities publish multiple vehicle statuses, filter to only status for own vehicle.
Changelog for package autoware_v2x_msgs
1.3.0 (2024-11-25)
1.2.0 (2024-10-01)
- feat(autoware_v2x_msgs): add virtual gate messages (#77)
- Contributors: Takagi, Isamu
1.1.0 (2024-05-10)
Wiki Tutorials
Package Dependencies
| Deps | Name |
|---|---|
| rosidl_default_generators | |
| ament_cmake_auto | |
| rosidl_default_runtime | |
| ament_lint_auto | |
| ament_lint_common | |
| builtin_interfaces | |
| geometry_msgs |
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged autoware_v2x_msgs at Robotics Stack Exchange
|
|
Package Summary
| Tags | No category tags. |
| Version | 1.3.0 |
| License | Apache License 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/autowarefoundation/autoware_msgs.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2024-11-26 |
| Dev Status | DEVELOPED |
| CI status | No Continuous Integration |
| Released | RELEASED |
| Tags | No category tags. |
| Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Takagi, Isamu
- Ryohsuke Mitsudome
- Yukihiro Saito
Authors
autoware_v2x_msgs
Virtual gate messages
Overview
This message represents the status of the virtual gate for passing through the area managed by the facility. The virtual gate treats area entry permission as a shared resource and controls vehicles by acquiring and releasing locks. Each facility may support different protocols, but Autoware V2X component converts each protocol and this message. This allows Autoware to handle facilities with different protocols with a unified message.
Sequence
Because there is a time lag before commands are reflected, the vehicle must wait until it receives the status of the same sequence as the command it sent. Until the vehicle receives the status, treat it as if it were unlocked.
Gates
Specify the entrance and exit gate IDs. This is used to check if vehicles can pass simultaneously when multiple routes are possible within an area. If omitted, it is treated as a lock for the entire area.
Vehicle ID
This message does not include the vehicle ID, so add it in the V2X component if required by the communication protocol. And if facilities publish multiple vehicle statuses, filter to only status for own vehicle.
Changelog for package autoware_v2x_msgs
1.3.0 (2024-11-25)
1.2.0 (2024-10-01)
- feat(autoware_v2x_msgs): add virtual gate messages (#77)
- Contributors: Takagi, Isamu
1.1.0 (2024-05-10)
Wiki Tutorials
Package Dependencies
| Deps | Name |
|---|---|
| rosidl_default_generators | |
| ament_cmake_auto | |
| rosidl_default_runtime | |
| ament_lint_auto | |
| ament_lint_common | |
| builtin_interfaces | |
| geometry_msgs |
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged autoware_v2x_msgs at Robotics Stack Exchange
|
|
Package Summary
| Tags | No category tags. |
| Version | 1.3.0 |
| License | Apache License 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/autowarefoundation/autoware_msgs.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2024-11-26 |
| Dev Status | DEVELOPED |
| CI status | No Continuous Integration |
| Released | RELEASED |
| Tags | No category tags. |
| Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Takagi, Isamu
- Ryohsuke Mitsudome
- Yukihiro Saito
Authors
autoware_v2x_msgs
Virtual gate messages
Overview
This message represents the status of the virtual gate for passing through the area managed by the facility. The virtual gate treats area entry permission as a shared resource and controls vehicles by acquiring and releasing locks. Each facility may support different protocols, but Autoware V2X component converts each protocol and this message. This allows Autoware to handle facilities with different protocols with a unified message.
Sequence
Because there is a time lag before commands are reflected, the vehicle must wait until it receives the status of the same sequence as the command it sent. Until the vehicle receives the status, treat it as if it were unlocked.
Gates
Specify the entrance and exit gate IDs. This is used to check if vehicles can pass simultaneously when multiple routes are possible within an area. If omitted, it is treated as a lock for the entire area.
Vehicle ID
This message does not include the vehicle ID, so add it in the V2X component if required by the communication protocol. And if facilities publish multiple vehicle statuses, filter to only status for own vehicle.
Changelog for package autoware_v2x_msgs
1.3.0 (2024-11-25)
1.2.0 (2024-10-01)
- feat(autoware_v2x_msgs): add virtual gate messages (#77)
- Contributors: Takagi, Isamu
1.1.0 (2024-05-10)
Wiki Tutorials
Package Dependencies
| Deps | Name |
|---|---|
| rosidl_default_generators | |
| ament_cmake_auto | |
| rosidl_default_runtime | |
| ament_lint_auto | |
| ament_lint_common | |
| builtin_interfaces | |
| geometry_msgs |