Map yaw rate and sideslip to steering and speed

Generated from content/lms/vehicle-dynamics-ii-theory/02-steady-state-handling-balance/04-steady-state-yaw-rate-and-sideslip-response.md; edit the source file, not this page.

Source path: content/lms/vehicle-dynamics-ii-theory/02-steady-state-handling-balance/04-steady-state-yaw-rate-and-sideslip-response.md

Course: Read the forces that steer the car

Module: Balance the car with forces and moments

Estimated duration: 45 minutes

Principle - steady-state handling is a map, not a single feeling. You are trying to connect two things you command, speed and steering, to several things the car does in response: path curvature, yaw angular speed, lateral acceleration, and sideslip at the center of gravity. Dixon frames these as the basic independent variables of steady-state handling theory and notes that, for a given speed and path curvature, yaw angular speed and lateral acceleration are tied to the same circular motion. The practical point is simple: in a trimmed corner, any two of the four response variables are enough to locate the rest of the steady-state condition. For the driver, the useful working pair is usually speed plus one response measure, because the actual controls are the accelerator and steering wheel. That is why this lesson does not start with a setup part. It starts with a question: for this speed and this steering, how much path, rotation, lateral acceleration, and sideslip did the car produce? Map that, and balance stops being a vague word. It becomes a repeatable response pattern. Scope - this lesson sits between the force-balance lesson and the understeer-gradient calculation lesson. You are not deriving the bicycle model here, and you are not calculating understeer gradient from tire and geometry data. You are learning to read the outputs those calculations are trying to predict. You should finish able to watch or log a steady corner and say whether a change in yaw rate came from speed, steering, or vehicle balance; whether sideslip is consistent with low-speed geometry or high-speed tire slip; and whether the car is getting more responsive, less responsive, or unstable as speed rises. Keep the sibling lessons for the math behind axle side-force balance, understeer-gradient calculation, and the speed where balance becomes a boundary. Here you are building the driver-and-engineer translation layer. The four-variable map - begin with path curvature. Curvature is the tightness of the path. A larger curvature means a smaller radius; a smaller curvature means a wider radius. Yaw angular speed, or yaw rate, is how fast the vehicle body is rotating about its vertical axis while it follows that path. Lateral acceleration is the side acceleration required by that curved path at that speed. Speed connects all of them. At a fixed path curvature, adding speed increases the demand on the tires and changes the yaw-rate and lateral-acceleration values. At a fixed speed, adding curvature tightens the path and changes the same response variables. This is why a steady-state test must always keep track of speed. If you compare two steering inputs without speed, you are not comparing balance; you are mixing command and operating point. If you compare two yaw-rate traces without steering angle, you do not know whether the car became more responsive or whether you simply asked for more rotation. The skill is to always pair the response with the control. The control pair is speed and steering. The response pair you choose can be path curvature and yaw rate, yaw rate and lateral acceleration, or lateral acceleration and sideslip, depending on what your car or your body can read. Steering gain - Dixon defines gain as the sensitivity of a response measure to steer angle at a particular trim state. That phrase matters. Gain is not the raw number by itself. It is the response per steering command at a trimmed speed and condition. Path-curvature gain asks how much curvature the car produces for a given steer angle. Yaw-velocity gain asks how much yaw angular speed the car produces for a given steer angle. Lateral-acceleration gain asks how much lateral acceleration the car produces for a given steer angle. The same steering-wheel angle can feel reasonable at one speed and lazy or nervous at another, because the gain changes with speed and with balance. Your first job is not to label the car. Your first job is to observe the gain. If a small steering change gives a large yaw-rate change, the yaw-velocity gain is high. If more steering produces little extra yaw, the gain is low or saturating. If the same steering angle gives different curvature at different speeds, you are watching speed move the operating point. That is the core map. Yaw rate - yaw rate tells you how quickly the car is rotating, but it does not by itself tell you whether the car is following the line cleanly. Gillespie separates the yaw-velocity gain behavior by balance type. For a neutral-steer vehicle, yaw-velocity gain is proportional to velocity. For an understeer vehicle, yaw velocity increases with speed up to the characteristic speed and then begins to decrease. Gillespie gives the key interpretation: the characteristic speed is the speed at which the vehicle is most responsive in yaw. For an oversteer vehicle, yaw-velocity gain becomes infinite at critical speed; another chunk notes that a vehicle with a critical speed becomes unstable above it. You do not need to calculate those speeds in this lesson. You do need to recognize the signatures. Neutral behavior feels like the car gives you more yaw response as speed rises in a clean, proportional way. Understeer behavior can feel helpful at first, then duller as speed rises beyond the most responsive point. Oversteer behavior can feel increasingly sharp as speed rises, until the steering-to-yaw relationship becomes the wrong kind of efficient: too much rotation for the input and not enough stable margin. Sideslip - sideslip is the missing half of the story. Yaw rate tells how fast the car is rotating; sideslip tells how the car body is oriented relative to the local velocity vector at the center of gravity. Gillespie defines the low-speed turn case with the direction of travel oriented clockwise from the longitudinal axis under the SAE convention, and then notes that at high speed the rear-wheel slip angle can make the sideslip angle at the CG become negative. The driver version is this: in a slow, tight, geometric turn, the body and velocity vector do not line up the same way they do in a high-speed corner where tire slip angles dominate. Therefore you should not treat every sideslip sign or every small body angle as oversteer. You must ask what speed range and tire-slip regime you are in. At low speed, geometry can produce a sideslip sign that is normal for the maneuver. At higher speed, rear slip angle can move the CG sideslip the other way. That transition is one of the reasons steady-state response is a map instead of a single sensation. If you only feel rotation, you can miss translation. If you only feel the car drifting sideways, you can miss whether yaw rate is increasing, flattening, or declining for the steering input. Pair them. What steering does - steering is the command that asks the front tires to create a path curvature. The steering wheel angle is often reduced through steering gearing to a reference steer angle in the analysis, but as a driver you still work at the steering wheel. A larger steering input is not automatically better, and a smaller steering input is not automatically faster. The meaningful question is response per input. If you add steering and the yaw rate and curvature rise in a stable, proportionate way, the car is still answering the command. If you add steering and the car mainly adds tire slip without much extra curvature, the front axle may be asking for more slip angle to maintain lateral force and the front may plough out. Gillespie describes that as understeer when the front tires have to assume a greater slip angle and the front ploughs out. If the rear is the axle that slips out, the vehicle oversteers. The steering wheel is therefore not a truth source by itself. It is the driver request. The yaw rate, path, lateral acceleration, and sideslip are the answer. What speed does - speed changes the demand and the gain. At the same path curvature, higher speed means a different steady-state condition. At the same steering input, higher speed can make the yaw response grow, peak, fade, or become unstable depending on the balance. That is why a car can feel eager in one speed band and reluctant in another without any setup change between corners. Gillespie makes that explicit for the understeer case: yaw velocity rises with speed up to characteristic speed, then decreases after it. This is a powerful calibration cue for track driving. If a medium-speed corner takes a set crisply but the faster version of the same radius needs more steering and gives less yaw response per degree of wheel, do not assume your hands got lazy. You may be past the car's yaw-responsiveness peak for that balance. Likewise, if response sharpens rapidly with speed, do not celebrate the smaller steering angle until you check sideslip and stability margin. A high yaw-rate gain can be useful below the boundary and dangerous as the critical-speed behavior approaches. Technique - the practical technique is to hold one variable steady long enough to read the others. You do not learn this skill during a messy trail-brake release, throttle catch, or avoidance maneuver. Those are transient problems. Steady-state means the cornering state is trimmed enough that speed, steering, yaw rate, and lateral acceleration have settled. In a real HPDE session you may only get brief windows of this, but the method is still the same. Pick a corner or a skidpad exercise where you can hold a clean arc. Enter below the limit. Set the speed. Set the steering. Let the car take a set. Now observe the path, the rotation rate, and the body angle. Then change only one thing. If you add speed, try not to add steering at the same time until you know what the original response was. If you add steering, keep speed as constant as practical. The cleaner the one-variable change, the more useful the response map. Sub-skill 1, separating command from response - drivers often describe handling in blended language. The car wanted more wheel. The car rotated. The car washed. Those can be useful phrases in a paddock debrief, but for this lesson you split them. Steering angle is command. Speed is operating point. Path curvature, yaw rate, lateral acceleration, and sideslip are response. If the car needed more steering to hold the same path at the same speed, that is a command-response change. If the car produced more yaw rate at the same speed with the same steering, that is a gain change. If the car produced the same yaw rate but more sideslip, it may be rotating similarly while translating differently. This split prevents the classic mistake of treating hand position as handling balance. Sub-skill 2, reading yaw gain instead of raw yaw - a car can have a high yaw rate simply because it is going fast around a tight path. That is not the same as being responsive. Responsiveness is yaw response relative to steer angle at that trim state. Dixon's gain language is useful because it forces the comparison to include steering. On a constant-radius exercise, yaw rate will be tied to speed, so the better question is how steering changes as speed rises. On a constant-speed exercise, yaw rate and curvature should change with steering, so the better question is how much response each added steering increment creates. If the first increment of steering gives a clear curvature change and the next increment mostly adds slip, you have found the front end's diminishing answer. If small steering reductions create a large change in yaw or sideslip, you may be near an over-responsive region. Sub-skill 3, pairing yaw with sideslip - yaw rate can look good while sideslip is poor. A car can rotate quickly but still be sliding across the path in a way that forces a later correction. Conversely, a car can show sideslip while yaw rate is not excessive, especially as the sign and source of sideslip change between low-speed and high-speed cornering. Gillespie's low-speed and high-speed sideslip discussion is the reason you do not use a single mental picture for every corner. In low-speed geometry, the relationship between the longitudinal axis and the local velocity vector can have one sign. At high speed, rear tire slip angle can move CG sideslip negative. So the useful question is not simply whether the car is sideways. The useful question is whether the body angle matches the yaw-rate response and the speed band you are in. Sub-skill 4, recognizing the understeer speed signature - in the understeer case, yaw response increases with speed only up to characteristic speed and then decreases. You can feel this as the car being eager through the lower part of a speed build, then requiring more steering effort or more steering angle for less additional path tightening as speed rises. This does not mean the car has no grip. It means the yaw response per steering input is no longer increasing. The track-side correction is not automatically more steering. More steering may only ask the front tires for more slip angle. The first correction is diagnostic: reduce the number of variables, confirm speed, confirm path, and see whether easing the speed slightly restores yaw response. Sub-skill 5, recognizing the oversteer speed signature - in the oversteer case, yaw-velocity gain can climb toward critical speed. Near that region, the car may seem impressively willing because little steering produces a lot of yaw. The danger is that this apparent efficiency is also the loss of stable margin. If yaw rate grows faster than your steering request and sideslip begins to build from the rear, you are no longer just enjoying a responsive car. You are approaching the condition Gillespie identifies as critical-speed behavior. The correction is to stop feeding the state: reduce the demand smoothly, avoid adding steering that tightens the path further, and return to a lower-gain operating point. Sub-skill 6, knowing where setup enters - multiple vehicle-design factors influence the cornering forces developed in lateral acceleration. Gillespie names suspension and steering as primary sources, and the provided chunks also point to roll steer, compliance steer, camber attitudes, aligning effects, tractive-force effects, and the need for the suspension to keep the wheels in the proper steer and camber attitudes while reacting tire forces and keeping tires in contact with low load variation. For this lesson, that means you should not jump from a response map to a single-cause setup claim. A lazy yaw response at speed may be tire cornering stiffness balance, roll moment distribution, compliance steer, camber behavior, steering system behavior, or another force-dependent effect. Your job as the driver is to describe the response cleanly enough that the setup lesson can use it. Calibration cues - good improvement has a few signatures. First, your descriptions become two-variable descriptions. Instead of saying the car pushed, you can say the same steering at higher speed produced less yaw response and more front slip feel. Instead of saying the car rotated well, you can say a small steering input produced a large yaw-rate response and sideslip started to build from the rear. Second, your steady-state windows get cleaner. You can hold a speed and steering input long enough to judge whether the car is trimmed or still in a transient. Third, you stop treating every corner as the same balance test. A low-speed turn may show a sideslip sign that belongs to geometry; a high-speed corner may show the high-speed rear-slip sideslip behavior Gillespie describes. Fourth, your debriefs identify the speed band. The phrase at 55 mph it was neutral, at 75 mph it started needing more steering is much more useful than it understeered everywhere. Telemetry signatures, if you have the channels - with steering, speed, yaw rate, and lateral acceleration available, the map becomes visual. For a constant-speed steering sweep, plot or compare steering angle to yaw rate and lateral acceleration. You are looking for the response per steering input. For a constant-radius speed build, compare speed to required steering and yaw rate. Dixon notes that speed, angular speed, and lateral acceleration may be measured in testing, and that lateral acceleration is generally used in graphical results. Use that logic without overcomplicating it. You do not need a full professional test rig to think correctly. You need to avoid comparing apples to moving apples. Keep speed and steering tied to the response. When the traces are steady, learn from them. When the traces are changing rapidly, call it transient and save that for another lesson. Failure modes - the first failure mode is raw-yaw worship. You feel or see a big yaw rate and assume the car is good. But yaw rate without sideslip and steering input is incomplete. The car may be rotating because it is responsive, because it is over-responsive, or because the path and speed demand it. The second failure mode is hand-angle judgment. You look at how much steering you used and call that balance. But steering is only the request. Without speed and path, the same hand angle can mean different things. The third failure mode is steady-state contamination. You try to read balance while still releasing the brake, adding throttle, correcting a slide, or dealing with a disturbance. Those are useful driving problems, but they are not the trimmed state this lesson is about. The fourth failure mode is single-axle blame. Gillespie is clear that design factors across suspension and steering influence cornering force. If the front ploughs, that describes the outcome; it does not by itself prove which design factor caused it. The fifth failure mode is ignoring speed bands. Understeer and oversteer response are speed-dependent in the gain sense. A balance report without speed is an unfinished report. Recovery logic - if the response map is going dull, remove demand before adding command. In an understeer-like signature, more steering can deepen the front tires' slip-angle demand without tightening the path. Ease the speed or unwind slightly enough to get the front tires answering again, then rebuild. If the response map is going sharp, do not chase the car into higher yaw gain. Reduce the operating demand smoothly and let the sideslip settle. If the sideslip story and yaw-rate story disagree, do not force a conclusion. Repeat the observation in a cleaner steady-state window. This restraint is not academic caution. It is how you avoid changing the wrong part of the car or practicing the wrong driver response. Cross-references - when you want to know why the axle forces balance the way they do, go to the bicycle-model lesson. When you want the mathematical link from tire and geometry data to understeer gradient, go to the understeer-gradient lesson. When you want to calculate the speed where balance becomes a boundary, go to the characteristic-speed and critical-speed lesson. This lesson gives you the map-reading skill those lessons need. If you cannot describe yaw rate, sideslip, steering, and speed cleanly, the equations will still be true, but your diagnosis will be noisy.

Worked example: constant-radius speed build

Use a large, controlled circle or a corner segment that behaves like one. The point is not to set a lap time. The point is to hold path curvature nearly fixed while speed changes. Begin at a low speed where the car is comfortably below the limit. Set the circle, settle the steering, and notice the yaw rate and lateral acceleration if you can measure them. Now increase speed in small steps while trying to keep the same path. Because path curvature is fixed, speed is the variable that moves the steady-state condition. In a neutral-like response, yaw-velocity gain grows with velocity in the straightforward way Gillespie describes. In an understeer-like response, the car becomes more yaw responsive up to a point, then the extra speed gives less yaw response per steering command and asks for more steering to hold the same circle. That point is the driver-facing clue behind characteristic speed. If the car instead becomes sharply more responsive with speed, with the rear beginning to build sideslip, treat that as an oversteer-like signature and stop the build. The success of the exercise is not speed. Success is being able to say what changed first: steering demand, yaw response, lateral acceleration, or sideslip.

Worked example: constant-speed steering sweep

Now hold speed and change steering. This is the other clean half of the map. Choose a safe, open, controlled section where you can make a gentle constant-speed arc, then increase steering in small, patient increments. Dixon's gain idea is the tool: you are observing response sensitivity to steer angle at a trim state. At the first increment, the car should increase curvature and yaw rate. At later increments, the answer may remain proportional, flatten, or become unstable. If steering increases but curvature and yaw rate do not rise much, the front tires may be taking more slip angle without giving much more useful path change. If a small steering increment produces a large yaw-rate jump and sideslip starts to build from the rear, the gain is high enough that you should reduce demand. This example deliberately avoids deriving the understeer gradient. You are learning the shape of the response before calculating the number.

Worked example: low-speed turn versus high-speed cornering

Gillespie's sideslip discussion is easy to misuse unless you separate speed regimes. In a low-speed turn, the sideslip angle at the center of gravity is defined positive for the illustrated case because the local velocity vector is oriented clockwise from the vehicle longitudinal axis in SAE convention. At high speed, rear-wheel slip angle can make the CG sideslip become negative. Translate that into driving judgment: do not carry one low-speed mental picture into every high-speed corner. A tight paddock-speed arc, a slow autocross-style element, and a fast track corner can all show different body-to-velocity relationships without meaning the same handling fault. In the slow case, geometry is a large part of the picture. In the fast case, tire slip angles are the story. The lesson is to pair sideslip with speed and yaw rate before naming the balance.

Worked example: disturbance and path tendency

The corpus points to Olley's definitions for understeer and oversteer with an oversteer path and a disturbance force. Use that as a mental test, not as a stunt. Imagine the car is in a trimmed steady corner and something disturbs it. If the disturbance produces a path tendency that requires more stabilizing correction because the rear is slipping out, you are seeing the oversteer side of the map. If the front ploughs and the car does not take the intended curvature for the steering request, you are seeing the understeer side. In both cases, the useful driver report is not just the label. It is the sequence: speed, steering state, yaw response, sideslip direction, and whether the path opened or tightened. That sequence gives the engineer something grounded in the same variables as the steady-state model.

Common mistakes

Mistake 1: calling steering angle the balance. Good looks like separating the command from the response: at this speed and this steering, the car produced this yaw rate and this sideslip. Mistake 2: calling every extra steering input understeer. Good looks like checking whether the path actually failed to tighten and whether front slip-angle demand is the likely symptom. Mistake 3: treating yaw rate alone as rotation quality. Good looks like pairing yaw rate with sideslip at the center of gravity so you know whether the car is rotating cleanly or also translating across the path. Mistake 4: comparing different speeds as if they were the same test. Good looks like naming the speed band and remembering that yaw-velocity gain changes with speed, including the characteristic-speed behavior of understeer and the critical-speed behavior of oversteer. Mistake 5: reading transient corners as steady-state data. Good looks like waiting for a trimmed window, then observing. Mistake 6: jumping straight to setup. Good looks like first describing the response pattern, because suspension and steering factors can influence the cornering forces in several ways.

Drill: two-variable steady-state map

Run this only in a controlled HPDE, test day, skidpad, or other approved environment. Count: three runs for the constant-radius half and three runs for the constant-speed half. Duration: each run should be long enough to settle the car, observe the response, and exit cleanly; do not extend the run if tires, traffic, or safety margins are degrading. Step 1: choose a safe arc and drive it below the limit. Record or write down speed, approximate steering, yaw feel, lateral acceleration if available, and sideslip feel. Step 2: repeat the same path with a modest speed increase, then again with one more modest speed increase. Your success criterion is that you can identify whether yaw response per steering input rose, flattened, or fell as speed increased. Step 3: at one comfortable speed, repeat the arc with small steering changes. Your success criterion is that you can identify whether each added steering input produced proportional path and yaw response or mostly added slip. Step 4: write the debrief in the same order every time: speed, steering command, path response, yaw response, sideslip response, and label. If you cannot fill those fields, the run was not clean enough to diagnose.

When the principle breaks down

The principle breaks down when the car is not in a steady-state trim. Heavy brake release, throttle pickup, sudden steering, bumps, and disturbance response belong to transient handling. Dixon's text separates steady-state handling from unsteady-state handling, including yaw and sideslip behavior, steer response, power steering, and disturbance response. That separation matters. A transient slide can teach car control, but it is not the clean place to measure yaw-velocity gain. The principle also breaks down when you ask the bond for more precision than it provides. The chunks here support the response-map logic, speed dependence, gains, sideslip sign behavior, and understeer or oversteer outcomes, but they do not provide a complete displayed equation set or numerical vehicle data. Use this lesson to read the map; use the sibling lessons and a fuller vehicle model to calculate it.

Author Review

No quiz questions are attached to this lesson.

Sources

#	Document	Chunk	Pages	Score	Collection
1	Tires Suspension and Handling Second Edition Dixon John C	916feb6c-c8b6-7086-c853-0ffb1e21fe5d	349	1	uio_books_raw_v1
2	Fundamentals of vehicle dynamics Gillespie T. D. Thomas D.	9b1b906d-e2e5-e7e7-7beb-dcc8343daf88	138	1	uio_books_raw_v1
3	Fundamentals of vehicle dynamics Gillespie T. D. Thomas D.	88cbdbfe-237b-b2ed-0f8b-09605b9839e3	139	1	uio_books_raw_v1
4	Tires Suspension and Handling Second Edition Dixon John C	016130a8-fbf8-2bd4-1c39-807954a587b4	512	1	uio_books_raw_v1
5	Fundamentals of vehicle dynamics Gillespie T. D. Thomas D.	1c0f4276-b013-e968-0df0-135783d05f49	212	1	uio_books_raw_v1
6	Fundamentals of vehicle dynamics Gillespie T. D. Thomas D.	783c9b6f-00c0-fbbc-c938-5d8da61bcdb5	12	1	uio_books_raw_v1
7	Fundamentals of vehicle dynamics Gillespie T. D. Thomas D.	ae1b0ba3-4369-e30a-2e18-7abfed5791f4	153	1	uio_books_raw_v1
8	Tires Suspension and Handling Second Edition Dixon John C	560ef1be-06ef-28ac-b58d-977984b068f2	511	1	uio_books_raw_v1
9	Tires Suspension and Handling Second Edition Dixon John C	1c80aab5-0b3d-be93-e678-120497031a2c	642	1	uio_books_raw_v1
10	Fundamentals of vehicle dynamics Gillespie T. D. Thomas D.	d6ed3070-411f-ea1b-763f-f8e83c2046fb	2	1	uio_books_raw_v1
11	Tires Suspension and Handling Second Edition Dixon John C	bba93109-e3f1-a488-3ba7-9f3118eddb35	3	1	uio_books_raw_v1