Skip to content

Vehicle get stuck in multi-level parking lot #12528

@VRichardJP

Description

@VRichardJP

Checklist

  • I've read the contribution guidelines.
  • I've searched other issues and no duplicate issues were found.
  • I'm convinced that this is not my fault but a bug.

Description

I have created the following lanelet2 map representing a multi-level parking lot:

Image

dual_spiral_parking.osm.txt

In the planning simulator, I set vehicle pose and goal so that the vehicle has to drive through the whole "building". However, Autoware always stop right before the first curve:

Image

Video demo:

2026-05-01.154613.mp4

The logs does not tell much about what is going on:

[component_container_mt-33] [INFO 1777618057.671877034] [control.autoware_operation_mode_transition_manager]: Engage unavailable: enable_engage_on_driving is false, and the vehicle is not stationary. (isModeChangeAvailable() at /workspace/src/universe/autoware_universe/control/autoware_operation_mode_transition_manager/src/state.cpp:230)
[component_container_mt-33] [INFO 1777618060.771716487] [control.autoware_operation_mode_transition_manager]: Engage unavailable: enable_engage_on_driving is false, and the vehicle is not stationary. (isModeChangeAvailable() at /workspace/src/universe/autoware_universe/control/autoware_operation_mode_transition_manager/src/state.cpp:230)
[component_container_mt-33] [INFO 1777618063.771958951] [control.autoware_operation_mode_transition_manager]: Engage unavailable: enable_engage_on_driving is false, and the vehicle is not stationary. (isModeChangeAvailable() at /workspace/src/universe/autoware_universe/control/autoware_operation_mode_transition_manager/src/state.cpp:230)
^[[B[component_container_mt-33] [INFO 1777618066.871803203] [control.autoware_operation_mode_transition_manager]: Engage unavailable: enable_engage_on_driving is false, and the vehicle is not stationary. (isModeChangeAvailable() at /workspace/src/universe/autoware_universe/control/autoware_operation_mode_transition_manager/src/state.cpp:230)
[autoware_mrm_handler_node-13] [INFO 1777618068.684115830] [system.mrm_handler]: MRM State changed: NORMAL -> MRM_OPERATING (transitionTo() at /workspace/src/universe/autoware_universe/system/autoware_mrm_handler/src/mrm_handler/mrm_handler_core.cpp:410)
[autoware_mrm_handler_node-13] [WARN 1777618068.684449952] [system.mrm_handler]: EMERGENCY_STOP is operated. (requestMrmBehavior() at /workspace/src/universe/autoware_universe/system/autoware_mrm_handler/src/mrm_handler/mrm_handler_core.cpp:300)
[component_container_mt-33] [WARN 1777618068.696096218] [control.vehicle_cmd_gate]: Emergency! (publishControlCommands() at /workspace/src/universe/autoware_universe/control/autoware_vehicle_cmd_gate/src/vehicle_cmd_gate.cpp:594)
[logging_node-15] [WARN 1777618068.706610164] [logging_diag_graph]: The target mode is not available for the following reasons:
[logging_node-15] - /autoware/modes/autonomous ERROR
[logging_node-15]     - /autoware/localization ERROR
[logging_node-15]         - /autoware/localization/state STALE
[logging_node-15]  (on_timer() at /workspace/src/universe/autoware_universe/system/autoware_diagnostic_graph_utils/src/node/logging.cpp:70)
[autoware_mrm_handler_node-13] [INFO 1777618068.784370253] [system.mrm_handler]: MRM State changed: MRM_OPERATING -> NORMAL (transitionTo() at /workspace/src/universe/autoware_universe/system/autoware_mrm_handler/src/mrm_handler/mrm_handler_core.cpp:410)
[autoware_mrm_handler_node-13] [WARN 1777618068.784871629] [system.mrm_handler]: EMERGENCY_STOP is canceled. (requestMrmBehavior() at /workspace/src/universe/autoware_universe/system/autoware_mrm_handler/src/mrm_handler/mrm_handler_core.cpp:300)
[logging_node-15] [INFO 1777618068.806539200] [logging_diag_graph]: The target mode is available now. (on_timer() at /workspace/src/universe/autoware_universe/system/autoware_diagnostic_graph_utils/src/node/logging.cpp:94)

However the blue lines supposed to indicate the left and right of the drivable area are suspicious:

Image

You can also clearly see in the video the vehicle stops immediately after a new lanelet from the bottom floor is added to the local path planning.

Expected behavior

Can drive through the map

Actual behavior

Stops before the first curve

Steps to reproduce

dual_spiral_parking.osm.txt

See video

Versions

  • Ubuntu 22.04 (docker)
  • ros2 humble
  • release/1.7.1

Possible causes

having multiple lanelets overlapping vertically may cause some trouble.

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    component:planningRoute planning, decision-making, and navigation. (auto-assigned)type:bugSoftware flaws or errors.

    Type

    No type

    Projects

    Status

    To Triage

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions