An autonomous race car must sense the track, decide what to do, and command steering, braking, and throttle while moving at very high speed. Latency is the time delay between an event in the world and the car's physical response to it. In racing, even a delay of a few milliseconds can shift the car by centimeters or meters before the controller reacts.
Understanding latency helps engineers design safer, faster systems that can handle sharp corners and sudden changes in grip.
The full decision loop includes sensor exposure, data transfer, perception, planning, control computation, actuator response, and tire force buildup. Each step adds delay, so engineers measure end-to-end latency rather than only computer processing time. A control system must predict where the car will be when the command takes effect, not where it was when the camera or LiDAR first measured the scene.
Low latency, accurate prediction, and high update rates allow the car to stay near the racing line while avoiding instability.
Key Facts
- Distance traveled during delay: d = vΔt
- At 60 m/s, a 50 ms delay means d = 3.0 m of travel before response.
- Control loop frequency: f = 1/T, where T is the loop period.
- Total latency = sensor delay + compute delay + communication delay + actuator delay.
- For circular cornering, lateral acceleration is a = v^2/r.
- Prediction compensates delay by estimating future state: x_future = x_now + vΔt for simple straight-line motion.
Vocabulary
- Latency
- Latency is the time delay between sensing an event and the vehicle responding to it.
- Control loop
- A control loop is the repeated process of measuring the car's state, computing a command, and applying that command.
- Perception
- Perception is the software process that turns sensor data into useful information about lanes, obstacles, track edges, and vehicle motion.
- Actuator
- An actuator is a device that converts a control command into physical action, such as steering angle, brake pressure, or motor torque.
- Racing line
- The racing line is the path through a corner that helps maximize speed while staying within the track and grip limits.
Common Mistakes to Avoid
- Ignoring actuator delay is wrong because steering, braking, and throttle systems take time to physically change the car's motion after the computer sends a command.
- Using speed in km/h directly in d = vΔt is wrong because the formula requires consistent units, usually meters per second and seconds.
- Assuming a faster processor removes all delay is wrong because sensors, communication, filtering, and tire response also contribute to end-to-end latency.
- Treating delayed sensor data as the current position is wrong because a race car may have moved a significant distance by the time the data is processed.
Practice Questions
- 1 A race car travels at 72 m/s and has an end-to-end latency of 40 ms. How far does it travel before a command begins to affect the car?
- 2 A control system updates every 10 ms. What is its update frequency in hertz, and how many updates occur in 1 second?
- 3 Explain why an autonomous race car entering a sharp corner must predict its future position rather than steering only from its most recent sensor measurement.