Control the car through forces and moments

Generated from content/lms/vehicle-dynamics-ii-theory/07-klomp-theory-module/02-driver-as-force-moment-controller.md; edit the source file, not this page.

Source path: content/lms/vehicle-dynamics-ii-theory/07-klomp-theory-module/02-driver-as-force-moment-controller.md

Course: Read the forces that steer the car

Module: Apply Klomp's unified force-moment framework

Estimated duration: 45 minutes

You are not a steering-wheel operator. You are a force and moment controller.

That distinction sounds theoretical until you use it in the car. The steering wheel, brake pedal, throttle pedal, chassis setup, and aero package are not the things that move the car directly. They are commands into a system. The car actually changes speed, direction, attitude, and path because external forces act on it. The useful force sources in this lesson are the tire-road contact, gravity, and the atmosphere. For most handling work, the tire forces dominate, while aerodynamics is usually a secondary handling influence unless the car and speed range make it large enough to matter.

The intermediate-driver mistake is to treat the control as the input itself. You add steering and expect path. You add brake and expect speed reduction. You add throttle and expect acceleration. That works at grocery-store demand levels, but it is too shallow for track driving. At track demand levels the car is always asking a deeper question: which force are you asking for, through which tires, in which direction, and what moment will that create about the car?

This lesson gives you that operating language. The sibling lessons in this module teach Klomp diagrams as balance maps and extend them into transient maneuvers. This lesson sits underneath those. Before a balance map means anything to you, you need to understand yourself as the controller that commands the forces and moments the map is trying to organize.

Principle: control the outcome, not the control position

Control means action by the driver intended to influence the motion of the car. The target is not a steering angle, a brake pressure, or a throttle percentage. The target is the car's vector velocity and path. In plain driver language, you are trying to decide where the car is going, how fast it is going there, and how its body is rotating while it does it.

That is why pure position thinking is misleading. A position-control test can specify a ramp, a step, or a sinusoidal steering input. That can be useful in engineering because it makes the input repeatable. But you do not drive a lap by trying to reproduce an arbitrary control trace. You drive by asking the car for a motion outcome, watching whether the car gives you that outcome, and changing the command when it does not.

A force and moment view gives you a cleaner loop. First, decide the motion you want. You may want less forward speed, more lateral path curvature, a stable straight-line attitude, or acceleration out of a corner. Second, identify which force source can create that motion. On track, that usually means the tires, with gravity and aerodynamics also present. Third, recognize that the force will not act through an abstract point in space. It acts through contact patches and through the suspension into the chassis. Because those forces are offset from the car's center of mass, they can create moments: yaw, pitch, and roll. Fourth, feel the response and correct the command.

This is the driver version of vehicle dynamics. Vehicle dynamics studies acceleration, braking, ride, and turning, and it asks what forces are produced by the tires, gravity, and aerodynamics for a given maneuver and trim condition. You do not need to solve the equations in the car. You do need to think in the same direction as the equations: the car responds to forces, and the force locations create moments.

Mechanism: where your commands become real

The tires are the main actuator you have. A tire can produce longitudinal force for acceleration and braking. It can produce lateral force for cornering. The suspension's job is not just to hold the wheels near the body. It must keep the wheels in useful steer and camber attitudes, react to tire control forces and braking or driving torques, and keep the tires in contact with the road with minimal load variation. That means a good driver input is one the tire can produce and the suspension can transmit without the platform becoming confusing.

Steering is therefore not path by itself. Steering asks the front tires to create cornering force. If the car changes path, it is because the tire-road forces generated a lateral acceleration and a yaw response. If the car refuses to change path, the important question is not whether you turned the wheel. The question is whether the tires produced enough usable lateral force at that moment, and whether the resulting moment about the car was the one you needed.

Brake pedal is not just slowing down. Braking asks the tires for longitudinal force, and the chassis responds with a pitch attitude and changed axle loading. That brake force also has to be reacted by the suspension and the tire contact. If you ask for braking while you are also asking for path change, you are still operating one physical system, not two independent systems. The tire-road contact is where the commands become real.

Throttle is the same kind of command. At low speed, maximum acceleration may be limited by traction at the drive wheels. At higher speed, the engine's available power may become the limit. The control position can feel similar, but the governing limit is different. In the traction-limited case, your throttle foot is mostly managing tire force. In the power-limited case, the tire may be ready for more than the engine can supply. The right driver question changes with the speed range.

Aerodynamics belongs in the same mental model, but you should not let it crowd out the tires unless the evidence says it matters. The vehicle can be influenced by forces from the road, atmosphere, and gravity. The atmosphere can apply forces and moments to the body. In many practical handling cases the tires are dominant and aerodynamic effects are secondary. On a faster car or faster part of the track, aero may become a meaningful part of the moment balance, but it is still a force-and-moment problem rather than a magic grip source.

Gravity is always present. On grades, crests, compressions, and lateral slopes, gravity changes the load state the tires must work within. This bond does not give a crest or camber-worked example, so the lesson will not invent one. The important principle still holds: if the car's response changes when the road surface changes, you are looking at a changed force environment, not a personality change in the car.

Sub-skill 1: name the force you are asking for

Before a session, pick a few corners and ask a simple question for each phase: which force am I mainly asking for here? On the straight before the brake zone, you are asking for drive force until you lift or brake. In the brake zone, you are asking for longitudinal deceleration force. In the cornering phase, you are asking for lateral force. On exit, you are trading back toward longitudinal drive force while still holding enough lateral force to finish the path.

This naming habit prevents a common intermediate muddle. Many drivers describe a corner only by controls: brake here, turn here, throttle here. The controls matter, but that description hides the real work. A force description is clearer: slow the car through tire braking force, turn the car through tire cornering force and yaw moment, then accelerate through drive force while the car finishes unwinding.

Do not overcomplicate this into equations while driving. The goal is not to calculate forces in the cockpit. The goal is to keep your commands honest. If you cannot say what force you are asking for, you probably cannot diagnose why the car did not answer.

Sub-skill 2: separate force from moment

A force changes translation. A moment changes rotation. On a car, the two are tied together because the forces act at contact patches, suspension links, the body, and pressure centers rather than at one ideal point.

When you brake, the force is longitudinal deceleration at the tire-road contact. The car's attitude response includes pitch. When you corner, lateral tire forces change the car's path and create yaw response. Body roll is part of the chassis and suspension response to lateral force. When aerodynamic side force or lift acts away from the center of mass, it can create yawing, pitching, or rolling moments. The exact calculation is for the engineering lesson. The driver skill is noticing that a car can have enough force but the wrong moment, or a promising moment but not enough sustainable force.

Think about a car that initially rotates but then cannot hold the chosen path. That is not the same problem as a car that never begins to rotate. One is a moment-and-sustain problem. The other is a force-generation or balance problem. The bonded corpus does not give enough understeer or oversteer detail to make this a full balance lesson, and the sibling Klomp lessons cover balance mapping. Here, stay with the controller question: did my command create the force and rotation I intended, and did the tire and suspension system maintain it?

Sub-skill 3: respect the suspension as the force path

The suspension is not just comfort hardware. In vehicle-dynamics terms it has to maintain wheel attitudes, react longitudinal and lateral control forces, react braking and driving torques, and keep the tires in contact with the road with minimal load variation. For a driver, that means your smoothest, cleverest input is only useful if the tire contact and suspension force path can make it real.

This matters when you compare cars. A modern passenger car, a race car with outboard suspension, and a push-rod or pull-rod car may all answer the same basic driver commands, but the way forces and moments transmit through their suspensions can differ. Carroll Smith's race-car modeling discussion notes that steady-state calculations may need iterative techniques, and push- or pull-rod suspensions can require many more iterations because bell-crank rotation changes motion ratio. You do not need to compute that. You need to remember that the car's response is a mechanical system response, not a direct cable from your hands to the path.

It also matters when the chassis itself participates. A torsionally soft chassis region near a suspension can effectively reduce that suspension's roll stiffness. That means the driver may feel a balance change that is not just spring, bar, or tire. The force path includes the structure. If the structure yields, the moment distribution you think you commanded is not the one the tire actually sees.

Sub-skill 4: use feel as evidence, not as folklore

The bonded multibody-systems text makes a useful point for drivers: deciding whether a vehicle has good or bad handling is often partly human judgement based on response, feel, and how easy the vehicle is to drive through maneuvers. Manufacturers still rely on track measurements and experienced test engineers' instincts. That does not mean feelings are mystical. It means the car's force and moment response has to be interpreted by a human in motion.

Use feel as evidence when it is tied to a specific force question. The car takes a set and follows the intended path. The car needs less correction to hold the same radius. The car accelerates cleanly when you ask for drive force at low speed. The car requires a different amount of steering effort or correction when speed moves into a range where aerodynamic moments are plausible. Those are useful observations because they are attached to the mechanism.

Do not use feel as a vague verdict. The car feels bad is not a diagnosis. Better is: when I ask for lateral force after the brake release, the front of the car does not build the path change I asked for. Or: when I add throttle at low speed, the acceleration limit feels tire-based rather than power-based. The better your force language, the more useful your feel becomes.

Sub-skill 5: know what the model is leaving out

A model is a tool, not the car. The supplied Carroll Smith material is explicit that steady-state handling equations can model steady-state behavior while ignoring tire and bushing compliance and linearizing roll resistance per degree. That may be reasonable for road-racing vehicles in that modeling context, but it is still a simplification.

For the driver, the caution is practical. Do not take a clean diagram or equation and assume it fully predicts a messy track input. Transient maneuvers, compliance, load variation, chassis stiffness, suspension kinematics, aero forces, and driver timing all enter the real response. This lesson is not telling you to distrust theory. It is telling you to use theory as a clean map of the force and moment problem, then compare it against the car's felt and measured behavior.

This is especially important in this module. Klomp-style balance diagrams can help you reason about handling balance, but the diagram is not the corner. You still have to ask how the forces are generated, how the moments develop, and whether your driver input is asking the physical system for something it can actually produce.

Technique: the four-question control loop

Use this loop in the car and in the debrief.

First, what motion outcome do I want? State the desired result in car terms: less speed before entry, more path curvature, stable body attitude, clean drive off the corner, or a smaller correction burden. Avoid starting with the input. If your first sentence is more steering, earlier throttle, or later brake, you may already be skipping the mechanism.

Second, which force source can create that outcome? If the answer is braking or acceleration, you are mostly thinking longitudinal tire force. If the answer is path curvature, you are thinking lateral tire force and yaw moment. If the answer changes with speed on a fast section, aerodynamic forces and moments may be part of the evidence, but the tires still have to turn those loads into useful road forces.

Third, what moment will that force create or disturb? Ask what will happen to yaw, pitch, or roll. A braking request is not neutral to pitch. A cornering request is not neutral to roll and yaw. A suspension or chassis that changes effective stiffness changes how those moments are reacted. A control input that looks small at the steering wheel can be large in moment effect if it arrives at the wrong time.

Fourth, what did the car actually do? This is where driver feel becomes disciplined. Did the car follow the path? Did it need a second correction? Did it feel easy or difficult to drive through the maneuver? Did a change in speed range change the response in a way that points toward traction limit, power limit, or aero contribution? Write the answer in force-and-moment language immediately after the session.

Calibration cues: signs that the skill is improving

You are improving when your debrief stops sounding like a list of controls and starts sounding like a causal chain. Instead of saying you turned too late, you can say the car did not build the lateral response early enough for the path you chose. Instead of saying the car was lazy, you can say the requested tire force arrived without the yaw moment you expected. Instead of saying it needed more throttle, you can say the exit was still traction-limited and the tire could not accept the drive force you asked for.

You are improving when your mid-session correction becomes smaller. The goal is not to avoid all correction. A track car is a dynamic system, and the driver is part of the control loop. The cue is that your correction addresses the right level of the system. If the problem is tire force, you do not answer only with steering position. If the problem is power limit, you do not blame drive-tire traction. If the problem is a force path through suspension or chassis, you do not treat the control as a direct path command.

You are improving when you can distinguish low-speed acceleration from high-speed acceleration. At low speed the limit may be drive-wheel traction. At high speed engine power may account for the limit. A driver who understands force control changes the question as the speed range changes. The same throttle position does not mean the same physical limitation.

You are improving when theory and feel start to check each other. A diagram or model may predict a balance tendency, but your track note should say how the car felt through the maneuver and whether the response was easy to drive. A felt response should be translated back into tire force, aero force, gravity, suspension reaction, or chassis force path. Neither side is enough by itself.

Failure modes: what wrong looks like

The first failure mode is input worship. This is the belief that because you turned the wheel, braked, or went to throttle, you made the car do the job. The correction is to ask whether the external force was actually produced. If the path did not change, steering position alone was not the answer. If the car did not accelerate, throttle position alone was not the answer. The car only responds when the tire-road, gravity, and atmospheric force environment produces the needed response.

The second failure mode is one-channel thinking. A driver says brake problem, steering problem, or throttle problem as though the channels are isolated. Vehicle dynamics does not isolate them that neatly. The car's dynamic behavior includes acceleration, braking, ride, and turning. Suspension must react longitudinal forces, lateral forces, and torques. A good debrief recognizes which channel was primary without pretending the other channels disappeared.

The third failure mode is aero overreach. Because aerodynamic forces and moments sound sophisticated, drivers may blame aero before they have explained the tire force problem. The corpus gives the proper hierarchy for most practical handling cases: tire forces are dominant, aerodynamics secondary. If you are not in a speed range or car type where aero evidence is credible, start with the tires and force path.

The fourth failure mode is model literalism. A steady-state model can teach balance, but it may ignore compliance and simplify roll behavior. If you use it as a complete description of a transient corner entry or exit, you will overclaim. The correction is to keep the model's job narrow: it helps you think about force and moment balance, then the car's real response tells you what the model missed.

The fifth failure mode is structure blindness. If a soft chassis region effectively reduces suspension roll stiffness, the driver may chase springs, bars, or tire pressures without recognizing that the force path is not as stiff as assumed. The driver does not need to redesign the chassis during a session, but the driver should know when the response feels like a system compliance problem rather than a single input mistake.

How this lesson connects to the Klomp module

When you read a Klomp handling diagram in the sibling lessons, treat it as a balance map of forces and moments, not as a decorative setup chart. The diagram can show how the car tends to distribute handling demand, but the driver still has to command the car through real tire forces, suspension reactions, chassis stiffness, gravity, and atmospheric forces.

That is the through-line of this module. Diagrams help you see balance. Transient lessons help you see how balance changes during the maneuver. This lesson helps you become the person who asks the car for the right physical response in the first place.

Worked example: low-speed exit versus high-speed acceleration

Imagine reviewing two acceleration complaints from the same car. In the first, the car is slow leaving a low-speed corner. In the second, the car is slow near the end of a straight. The control input may look similar because the driver is asking for throttle in both places, but the governing limit may not be the same.

The bonded acceleration-performance material gives the split: maximum longitudinal acceleration can be limited by engine power or by traction at the drive wheels, and which limit prevails may depend on speed. At low speed, tire traction may be the limiting factor. At high speed, engine power may account for the limit.

As the driver-controller, you diagnose those two complaints differently. On the low-speed exit, ask whether the drive tires can accept the requested longitudinal force. If the car does not accelerate cleanly when throttle is added, the first question is whether the tire force request is too large for the tire-road contact in that state. More throttle position may only make the force request less achievable.

Near the end of the straight, the same full-throttle command can be power-limited. The tires may be capable of transmitting the force available, but the engine and drivetrain cannot keep increasing acceleration at the same rate. The lesson is not that one limit is good and the other bad. The lesson is that the control position is not the diagnosis. You identify the force source and the active limit before you decide what to change.

Worked example: steady-state circle as a control-language test

A steady-state circular test is useful as a thought experiment even if you never run one formally. The driver tries to hold a repeated path while the car produces lateral force. The clean engineering version is attractive because the maneuver is simplified. The supplied material also cautions that steady-state equations can ignore compliance and linearize roll resistance, which means the clean model is not the whole car.

Use the situation to test your language. If the car will not hold the circle at the chosen speed, do not begin with steering position. Begin with the physical request. You are asking the tires for lateral force, the chassis for a yaw response that matches the path, and the suspension for a stable force path while maintaining contact with the road. If the response changes as speed builds, you ask whether the tire force, suspension reaction, body motion, or aerodynamic contribution changed enough to matter.

This is exactly why the skill belongs before the Klomp diagram lessons. A diagram can help organize steady-state balance, but the driver must still understand what is being balanced: road forces, moments, and the car's response to them.

Worked example: suspension force path and the misleading input

Take a driver who says the car needs more steering because it does not follow the intended path. A force-and-moment controller hears a different question. The front tire request may be too large, but the suspension also has to hold the wheel in the right attitude, react the lateral force, and transmit the moment into the chassis. If a region of the chassis near a suspension is not torsionally stiff, the effective roll stiffness at that suspension can be reduced.

That means the same steering command can produce a different path result than the driver expects, not because the steering wheel failed, but because the force path did not behave like the driver assumed. In a more complex race-car suspension, changing motion ratio through bell-crank rotation can also make the mechanical response less linear than a simple input story suggests.

The practical correction is humility and specificity. Do not say the wheel needs more angle until you have asked whether the tire force and force path can support the request. The driver's control input is only the start of the event. The chassis response is the evidence.

Drill: force-and-moment callout, three sessions

Run this over your next three sessions, using four corners that are safe and familiar enough that you are not adding cognitive overload. The drill is not to drive faster. The drill is to force your debrief language to match the physics.

Session one is the naming pass. For each chosen corner, write one sentence after the session naming the main force request in entry, middle, and exit. Keep it simple: braking force, lateral force, drive force, gravity or road attitude if the surface obviously changes, and aero only if the speed and car make that plausible. Success criterion: twelve phase notes across the four corners with no sentence that only names a control input.

Session two is the moment pass. For the same four corners, add what rotation or attitude response you expected from the force request. You are not solving the car. You are building the habit of saying yaw, pitch, and roll response in driver language. Success criterion: for each corner, one note that separates force from moment. For example, the brake request slowed the car but also changed pitch attitude, or the lateral-force request produced path but required extra correction in yaw.

Session three is the correction pass. Pick one corner where the response was not what you expected. Make only one deliberate driving change, then debrief whether the change addressed the force source, the moment response, or the force path through the suspension and chassis. Success criterion: your post-session note must include the intended physical change, the felt response, and whether the car became easier to drive through the maneuver. If your note only says earlier, later, more, or less, repeat the drill.

Common mistakes

Mistake one is describing the lap as control positions. Bad language is brake later, turn more, throttle earlier with no mechanism attached. Good language names the physical job: create deceleration force, create lateral force and yaw response, then ask for drive force when the tire can accept it.

Mistake two is treating tire force and chassis response as separate worlds. The tires create the control forces, but the suspension must react those forces and keep the tires in contact with the road. Good driving notes include both the tire request and the platform response.

Mistake three is blaming aerodynamics because it sounds advanced. The bonded handling introduction is clear that for most practical cases, tire forces dominate while aerodynamics is secondary. Good practice is to start with tire force and only bring aero into the diagnosis when speed range, car type, and evidence justify it.

Mistake four is using theory as a verdict instead of a lens. Steady-state equations and handling diagrams can be accurate within their assumptions, yet still ignore compliance and simplify roll behavior. Good practice is to use the model to form a better question, then use the car's response to test that question.

Mistake five is confusing ease with slowness. A car that is easy to drive through a maneuver may be giving the driver a cleaner force-and-moment response, not merely feeling soft or slow. The useful question is whether the response helps the car follow the intended path with fewer corrections and clearer limits.

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	40339bca-e933-200f-6899-89d001869049	21	1	uio_books_raw_v1
2	Fundamentals of vehicle dynamics Gillespie T. D. Thomas D.	02d46cc3-2e67-5d17-d657-2abb5e25e5ef	23	1	uio_books_raw_v1
3	Fundamentals of vehicle dynamics Gillespie T. D. Thomas D.	ae1b0ba3-4369-e30a-2e18-7abfed5791f4	153	1	uio_books_raw_v1
4	The Multibody Systems Approach to Vehicle Dynamics Michael Blundell Damian Harty	8550dbd1-52c8-0157-ef98-6ae489af1436	12	1	uio_books_raw_v1
5	Tires Suspension and Handling Second Edition Dixon John C	b176fc90-8e3e-3ce1-0012-574fc7240c6a	70	1	uio_books_raw_v1
6	Fundamentals of vehicle dynamics Gillespie T. D. Thomas D.	12ef28f0-7f24-1ff0-ced6-3bf57a946f65	36	1	uio_books_raw_v1
7	Racing Chassis and Suspension Design Carroll Smith	1ac1a126-b9d2-24ff-6133-1843c3554108	213	1	uio_books_raw_v1
8	Racing Chassis and Suspension Design Carroll Smith	d05ed1e9-ad15-b224-c461-110eb40e5478	128	1	uio_books_raw_v1
9	Fundamentals of vehicle dynamics Gillespie T. D. Thomas D.	02084087-6941-7db5-e124-e81b4c867480	79	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