autoware_operation_mode_transition_manager

Note

The state management functionality of this package is currently being moved to the command_mode_decider package. When used with the command_mode_decider package, this package is only responsible for determining transition conditions. Also, the data status, in_autoware_control, and in_transition contained in the debug topic is not available, so use the /system/command_mode_decider/debug topic instead.

• in_autoware_control: True when the current command mode is manual mode (default value 1000).
• in_transition: See the is_in_transition function in the command_mode_decider package.
• status:
  • If in_autoware_control, DISENGAGE (autoware mode = curr_mode)
  • Else if in_transition, curr_mode (in transition from prev_mode)
  • Else curr_mode
  • Note: curr_mode = current operation mode and prev_mode = last operation mode

Purpose / Use cases

This module is responsible for managing the different modes of operation for the Autoware system. The possible modes are:

• Autonomous: the vehicle is fully controlled by the autonomous driving system
• Local: the vehicle is controlled by a physically connected control system such as a joy stick
• Remote: the vehicle is controlled by a remote controller
• Stop: the vehicle is stopped and there is no active control system.

There is also an In Transition state that occurs during each mode transitions. During this state, the transition to the new operator is not yet complete, and the previous operator is still responsible for controlling the system until the transition is complete. Some actions may be restricted during the In Transition state, such as sudden braking or steering. (This is restricted by the vehicle_cmd_gate).

Features

• Transit mode between Autonomous, Local, Remote and Stop based on the indication command.
• Check whether the each transition is available (safe or not).
• Limit some sudden motion control in In Transition mode (this is done with vehicle_cmd_gate feature).

• Check whether the transition is completed.

• Transition between the Autonomous, Local, Remote, and Stop modes based on the indicated command.
• Determine whether each transition is safe to execute.
• Restrict certain sudden motion controls during the In Transition mode (using the vehicle_cmd_gate feature).
• Verify that the transition is complete.

Design

A rough design of the relationship between autoware_operation_mode_transition_manager` and the other nodes is shown below.

A more detailed structure is below.

Here we see that autoware_operation_mode_transition_manager has multiple state transitions as follows

• AUTOWARE ENABLED <—> DISABLED
  • ENABLED: the vehicle is controlled by Autoware.
  • DISABLED: the vehicle is out of Autoware control, expecting the e.g. manual driving.
• AUTOWARE ENABLED <—> AUTO/LOCAL/REMOTE/NONE
  • AUTO: the vehicle is controlled by Autoware, with the autonomous control command calculated by the planning/control component.
  • LOCAL: the vehicle is controlled by Autoware, with the locally connected operator, e.g. joystick controller.
  • REMOTE: the vehicle is controlled by Autoware, with the remotely connected operator.
  • NONE: the vehicle is not controlled by any operator.
• IN TRANSITION <—> COMPLETED
  • IN TRANSITION: the mode listed above is in the transition process, expecting the former operator to have a responsibility to confirm the transition is completed.
  • COMPLETED: the mode transition is completed.

Inputs / Outputs / API

Inputs

For the mode transition:

• /system/operation_mode/change_autoware_control [autoware_system_msgs/srv/ChangeAutowareControl]: change operation mode to Autonomous
• /system/operation_mode/change_operation_mode [autoware_system_msgs/srv/ChangeOperationMode]: change operation mode

For the transition availability/completion check:

• /control/command/control_cmd [autoware_control_msgs/msg/Control]: vehicle control signal
• /localization/kinematic_state [nav_msgs/msg/Odometry]: ego vehicle state
• /planning/trajectory [autoware_planning_msgs/msg/Trajectory]: planning trajectory
• /vehicle/status/control_mode [autoware_vehicle_msgs/msg/ControlModeReport]: vehicle control mode (autonomous/manual)
• /control/vehicle_cmd_gate/operation_mode [autoware_adapi_v1_msgs/msg/OperationModeState]: the operation mode in the vehicle_cmd_gate. (To be removed)

For the backward compatibility (to be removed):

• /api/autoware/get/engage [autoware_vehicle_msgs/msg/Engage]
• /control/current_gate_mode [tier4_control_msgs/msg/GateMode]
• /control/external_cmd_selector/current_selector_mode [tier4_control_msgs/msg/ExternalCommandSelectorMode]

Outputs

• /system/operation_mode/state [autoware_adapi_v1_msgs/msg/OperationModeState]: to inform the current operation mode

• /control/autoware_operation_mode_transition_manager/debug_info [autoware_operation_mode_transition_manager/msg/OperationModeTransitionManagerDebug]: detailed information about the operation mode transition

• /control/gate_mode_cmd [tier4_control_msgs/msg/GateMode]: to change the vehicle_cmd_gate state to use its features (to be removed)

• /autoware/engage [autoware_vehicle_msgs/msg/Engage]:

• /control/control_mode_request [autoware_vehicle_msgs/srv/ControlModeCommand]: to change the vehicle control mode (autonomous/manual)
• /control/external_cmd_selector/select_external_command [tier4_control_msgs/srv/ExternalCommandSelect]:

Parameters

{{ json_to_markdown(“control/autoware_operation_mode_transition_manager/schema/operation_mode_transition_manager.schema.json”) }}

File truncated at 100 lines see the full file

Changelog for package autoware_operation_mode_transition_manager

0.47.0 (2025-08-11)

• feat: change planning output topic name to /planning/trajectory (#11135)

  • change planning output topic name to /planning/trajectory

  * style(pre-commit): autofix ---------Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>

• fix(operation_mode_transition_manager): modify the engage condition (#11097)

  • check engage on driving before check engage condition

  * fix

• Contributors: Yukihiro Saito, Zhi Wang

0.46.0 (2025-06-20)

• Merge remote-tracking branch 'upstream/main' into tmp/TaikiYamada/bump_version_base

• feat!: replace tier4_system_msgs with autoware_system_msgs for services (#10842)

  • feat!: replace tier4_system_msgs with autoware_system_msgs for services

  * style(pre-commit): autofix ---------Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>

• feat(operaton_mode_transition_manager): add flag node (#10828)

  • feat(operaton_mode_transition_manager): add flag node

  * rename node ---------

• fix(operation_mode_transition_manager): fix mode change without route (#10749)

• Contributors: Ryohsuke Mitsudome, TaikiYamada4, Takagi, Isamu

0.45.0 (2025-05-22)

• Merge remote-tracking branch 'origin/main' into tmp/notbot/bump_version_base

• feat(operation_mode_transition_manager): add timeout of the input (#10457) fix(operation_mode_transition_manager): add timeout for the input

• refactor(operation_mode_transition_manager): less member variable (#10453)

  • refactor(operatoin_mode_transition_manager): remove unnecessary member variable
  • implement InputData
  • fix
  • fix
  • resolve the reviews

  * add maintainer ---------

• Contributors: TaikiYamada4, Takayuki Murooka

0.44.2 (2025-06-10)

0.44.1 (2025-05-01)

0.44.0 (2025-04-18)

• Merge remote-tracking branch 'origin/main' into humble
• fix(control): apply THROTTLE to frequent log (#10418)
  • fix(control): apply THROTTLE to frequent log
  • fix
  • fix
  • fix

  * fix

• Contributors: Ryohsuke Mitsudome, Takayuki Murooka

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

File truncated at 100 lines see the full file