Automatic parking basics: from space to maneuver
Connect space detection, path planning and low-speed vehicle control.
- Explain how a parking space is assessed
- Distinguish planning from vehicle control
- Describe why obstacle monitoring continues during a maneuver
Find and assess a space
Parking assistance can use ultrasonic sensors and cameras to observe the nearby environment. The system assesses whether an available space suits the vehicle and the maneuver. A visible gap alone is not enough: the car needs room to enter, turn and finish in a usable position.
The animation scans beside parked cars and highlights a space. The highlighted rectangle represents a candidate area for parking.
Remember: Space detection is the start of the maneuver, not the complete solution.
Plan a path the vehicle can follow
A car cannot slide sideways into a parking space. Its steering geometry and turning limits constrain how it can move. Planning searches for a path that changes position and heading while allowing clearance around obstacles. A dashed route in the demo represents the intended motion, not proof that every real-world constraint has been solved.
The illustrated car reverses along a curved path and gradually aligns with the parking bay. Its heading changes as it moves.
Remember: A parking path must account for how a vehicle turns.
Turn the plan into movement
After the appropriate driver confirmation, assistance can manage steering and, depending on the vehicle, speed, braking and other actions. Control is the process of following the plan using updated information about the car. The planned path and the actual motion are related but are not the same thing.
The dashed path is the intention; the moving car is the response. If the car does not follow the intended route, a controller needs to respond rather than assume perfect motion.
Remember: Planning chooses a route; control works to follow it.
Keep checking the surroundings
An area that was clear during planning may change while the car is moving. Sensors must keep observing the surroundings so the maneuver can pause or be adjusted when needed. Driver supervision and the vehicle’s instructions still matter. The animation includes an obstacle option to make this continuing check visible.
Enable “Add an obstacle”. The car stops before completing the illustrated path instead of proceeding simply because a route was already planned.
Remember: A valid earlier plan does not remove the need to monitor new obstacles.
Engineering notes: architecture, limitations and efficiency
What the system can and cannot do
Automatic parking combines space detection, vehicle localisation, path planning, low-speed motion control and continuous obstacle monitoring. Depending on the vehicle, steering may be automated while the driver manages speed, or the system may also control braking and propulsion inside a tightly defined operating envelope.
Known limitations
- A detected space may be geometrically feasible but unsuitable because of kerbs, potholes, unusual objects, traffic or poor surface assumptions.
- The vehicle model, wheelbase, steering limits and sensor placement constrain which spaces and paths are possible.
- The driver remains responsible for supervision, confirmation and intervention; the system is not a guarantee of contact-free parking.
When problems can occur
- Ultrasonic reflections, camera blockage, rain, snow, low obstacles and sensor calibration errors can corrupt the local map.
- A moving pedestrian, bicycle or vehicle can invalidate a previously safe path.
- Unexpected driver input, wheel slip, a slope or an obstacle outside sensor coverage can cause the actual trajectory to differ from the plan.
Automatic parking is not designed as a fuel-saving system. It may reduce repeated searching and corrections, but low-speed manoeuvres are usually short and fuel differences are small. The relevant benefits are consistency, convenience and reduced collision risk, not a dependable economy percentage.
- Implement a bicycle-model parking simulator
- Compare open-loop paths with closed-loop tracking
- Test obstacle insertion and emergency-stop latency
Connect the lesson to the animation.
Watch the reverse maneuver once, then enable “Add an obstacle”. Compare the planned route with the point where the car pauses.
Revisit the parking demoApply what you learned.
Answer all three questions correctly to complete this basic lesson. You can review the explanations and retry as often as you like.
Continue into engineering.
Build on these basics with implementation, experiments and validation. More detailed engineering material is being developed.
Preview future technical topics
- Build a vehicle kinematics model
- Plan feasible parking paths
- Test closed-loop tracking and obstacle handling