Package Summary

Tags No category tags.
Version 1.0.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-07-25
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

Autoware v2x messages package.

Additional Links

No additional links.

Maintainers

  • Takagi, Isamu
  • Ryohsuke Mitsudome
  • Yukihiro Saito

Authors

No additional 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.

virtual-gate-nodes

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
No CHANGELOG found.

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.

Dependant Packages

No known dependants.

Launch files

No launch files found

Services

No service files found

Plugins

No plugins found.

Recent questions tagged autoware_v2x_msgs at Robotics Stack Exchange

No version for distro iron. Known supported distros are highlighted in the buttons above.

Package Summary

Tags No category tags.
Version 1.0.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-07-25
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

Autoware v2x messages package.

Additional Links

No additional links.

Maintainers

  • Takagi, Isamu
  • Ryohsuke Mitsudome
  • Yukihiro Saito

Authors

No additional 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.

virtual-gate-nodes

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
No CHANGELOG found.

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.

Dependant Packages

No known dependants.

Launch files

No launch files found

Services

No service files found

Plugins

No plugins found.

Recent questions tagged autoware_v2x_msgs at Robotics Stack Exchange

Package Summary

Tags No category tags.
Version 1.0.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-07-25
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

Autoware v2x messages package.

Additional Links

No additional links.

Maintainers

  • Takagi, Isamu
  • Ryohsuke Mitsudome
  • Yukihiro Saito

Authors

No additional 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.

virtual-gate-nodes

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
No CHANGELOG found.

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.

Dependant Packages

No known dependants.

Launch files

No launch files found

Services

No service files found

Plugins

No plugins found.

Recent questions tagged autoware_v2x_msgs at Robotics Stack Exchange

No version for distro noetic. Known supported distros are highlighted in the buttons above.
No version for distro ardent. Known supported distros are highlighted in the buttons above.
No version for distro bouncy. Known supported distros are highlighted in the buttons above.
No version for distro crystal. Known supported distros are highlighted in the buttons above.
No version for distro eloquent. Known supported distros are highlighted in the buttons above.
No version for distro dashing. Known supported distros are highlighted in the buttons above.
No version for distro galactic. Known supported distros are highlighted in the buttons above.
No version for distro foxy. Known supported distros are highlighted in the buttons above.
No version for distro lunar. Known supported distros are highlighted in the buttons above.
No version for distro jade. Known supported distros are highlighted in the buttons above.
No version for distro indigo. Known supported distros are highlighted in the buttons above.
No version for distro hydro. Known supported distros are highlighted in the buttons above.
No version for distro kinetic. Known supported distros are highlighted in the buttons above.
No version for distro melodic. Known supported distros are highlighted in the buttons above.