Circle of Forces¶
Represent a tire contact patch's combined longitudinal and lateral force capacity as a friction-circle or friction-ellipse envelope, so braking, driving, and cornering consume one coupled traction budget.
Core Idea¶
The circle of forces is a vehicle-dynamics diagram and constraint model for a tire-road contact patch. It plots longitudinal tire force \(F_x\)—driving or braking—against lateral force \(F_y\)—cornering—and encloses the combinations the contact can sustain under a stated vertical load and operating condition. A force request inside the boundary is feasible in the model; one outside exceeds available combined traction.[1][2]
The central insight is coupling. A tire near its maximum braking force has less remaining lateral capacity, and a tire near maximum cornering has less remaining drive or braking capacity. The ideal boundary may be drawn as a circle; real data and models often use an ellipse or a more irregular combined-slip envelope.[3]
It is therefore a shared traction-budget representation, not a claim that every tire has a perfect circular Coulomb-friction limit.
Structural Signature¶
The recognition roles are:
- Tire-road contact patch: the physical interface producing horizontal force.
- Declared coordinates: longitudinal and lateral axes relative to tire or vehicle.
- Longitudinal force \(F_x\): braking or drive contribution.
- Lateral force \(F_y\): cornering contribution.
- Vertical load \(F_z\): operating load influencing the envelope's scale and shape.
- Road/tire condition: friction, temperature, wear, pressure, speed, and surface state frame capacity.
- Combined-slip interaction: simultaneous slip ratio and slip angle compete for force generation.
- Boundary or envelope: circle, ellipse, normalized norm, or empirical contour limits admissible pairs.
- Force vector: requested or realized \((F_x,F_y)\) is plotted against the envelope.
- Interior: modeled combinations remain within available traction.
- Boundary: saturation where an additional component requires reducing another.
- Exterior: infeasible request, leading to saturation or altered slip rather than the commanded force.
The invariant is: longitudinal and lateral tire forces share one bounded combined-traction envelope at a specified contact condition.
What It Is Not¶
It is not a free-body diagram of every vehicle force. The node concerns horizontal force capacity at a tire-road contact.
It is not the equations of motion. Those propagate forces into vehicle acceleration and yaw; the circle constrains which tire forces are available.
It is not a literal geometric circle in all cases. An ellipse or measured contour can preserve the abstraction.
It is not the friction coefficient alone. \(\mu\) helps scale an ideal envelope but does not encode combined-slip shape, load sensitivity, transients, temperature, or tire construction.
It is not a g-g diagram, although a vehicle-level acceleration envelope is related.
It is not a traction-control or stability-control algorithm; those systems may use or approximate the constraint.
Scope of Application¶
Circle of Forces applies to passenger-car and motorcycle dynamics, racing-line analysis, braking while cornering, acceleration out of a turn, tire testing, chassis setup, torque allocation, anti-lock braking, traction control, electronic stability control, and model-predictive vehicle control.
It can describe one tire, one axle, or an aggregated vehicle envelope only when the level is declared. Load transfer means four tire-level circles do not combine into one fixed circle by simple addition.
The representation is most useful as a quasi-steady limit. Relaxation length, thermal evolution, road transients, suspension motion, aerodynamics, and actuator delays require dynamic models beyond the static envelope.
Clarity¶
An ideal isotropic friction circle may be written
An anisotropic ellipse may use
These formulas are approximations. Exponents other than two, asymmetric limits, or lookup-table contours can fit data better. The membership test is not “looks circular”; it is whether a combined-force envelope allocates longitudinal and lateral capacity at one contact.
Specify signs, axes, \(F_z\), surface, tire state, and whether values are commanded, estimated, or measured. A point on an outdated dry-road circle may lie outside the current wet-road envelope.
Manages Complexity¶
The diagram compresses a nonlinear tire model into an operational feasibility map. A driver, controller, or analyst can see immediately why adding brake changes cornering reserve without solving the full contact mechanics.
It also creates a common language for maneuvers. Straight-line braking occupies the longitudinal axis; steady cornering the lateral axis; trail braking and powered corner exit occupy quadrants between them.
The same picture makes reserve visible: distance from a normalized boundary summarizes how much disturbance or additional command the approximation can still absorb.
For control allocation, the envelope turns “generate these forces” into a constrained optimization problem. Requests can be scaled, redistributed among tires, or prioritized before saturation destabilizes the vehicle.
Abstract Reasoning¶
Let \(\mathcal F(q)\subset\mathbb R^2\) be the admissible horizontal-force set for operating state \(q\), which includes load, friction, slips, temperature, and tire condition. A request \(f=(F_x,F_y)\) is feasible when \(f\in\mathcal F(q)\).
For a normalized ellipse, define utilization
Then \(u<1\) denotes reserve, \(u=1\) saturation, and \(u>1\) an infeasible request under the approximation. Increasing \(|F_x|\) near the boundary predicts a required decrease in available \(|F_y|\).
Because \(\mathcal F\) varies with \(q\), feasibility is conditional. Increased normal load often increases absolute capacity but tires are load-sensitive, so capacity need not scale linearly with \(F_z\).
Knowledge Transfer¶
Literal transfer occurs across tires and maneuvers whenever combined longitudinal/lateral capacity is represented as one contact envelope. Circle, ellipse, and empirical contour are variants.
The portable residue is a coupled feasibility constraint: multiple outputs draw from a shared bounded capacity. Live prime:constraint supplies the generic restriction. Circle of Forces adds tire forces, contact friction, slip, normal load, and vehicle control.
Resource-budget diagrams outside tire dynamics are analogies unless they represent this force interface.
Examples¶
Straight-line braking. \(F_y\approx0\); the tire can approach the negative-longitudinal edge.
Steady cornering. \(F_x\approx0\); lateral force uses most of the envelope.
Trail braking. Both braking and lateral force are nonzero. As steering demand grows, braking must be released to remain inside the boundary.
Powered corner exit. Drive force increases while lateral demand decreases as steering unwinds.
Wet patch. Lower effective friction shrinks the envelope; a formerly feasible pair becomes exterior.
Negative—engine torque map. Available powertrain torque does not describe tire lateral capacity.
Negative—vehicle acceleration plot without contact-force allocation. Related performance data may not instantiate the tire-level abstraction.
Structural Tensions¶
T1: Simplicity versus tire realism. A circle communicates coupling; empirical envelopes capture asymmetry and load dependence.
T2: Longitudinal demand versus lateral reserve. Braking or driving consumes cornering capacity.
T3: Static limit versus transient response. The envelope gives attainable force, not how quickly it develops.
T4: Tire-level truth versus vehicle-level aggregation. Load transfer and control allocation complicate summation.
T5: Conservative safety margin versus performance utilization. Remaining interior increases robustness; boundary operation maximizes maneuvering.
Structural–Framed Character¶
Circle of Forces is structural as a coupled feasible set. Axes, force vector, boundary, utilization, and saturation yield explicit diagnostics.
It is framed by tire, road, load, temperature, speed, pressure, wear, transient state, and model fidelity. These determine the particular envelope while leaving the shared-capacity architecture intact.
Structural Core vs. Domain Accent¶
The core is a bounded multiaxial constraint: components share capacity and trade against one another near a feasibility boundary.
The domain accent is tire-road contact, longitudinal and lateral forces, slip ratio, slip angle, friction, normal load, vehicle maneuver, and control allocation. Removing these gives generic Constraint.
Instantiates / Related Primes¶
The minimal prospective placement is a strict composition/instantiates edge to live prime:constraint. The circle or ellipse is a concrete feasible-set constraint on tire-force components, not a subtype of the abstract concept.
Tradeoff, boundary, saturation, capacity, and optimization are related. Frozen domain_specific:equations_of_motion is false coverage because propagation equations do not supply the contact limit.
Relationships to Other Abstractions¶
Current abstraction Circle of Forces Domain-specific
Parents (1) — more general patterns this builds on
-
Circle of Forces is a kind of Constraint Prime
The minimal prospective placement is a strict
composition/instantiatesedge to liveprime:constraint.The circle or ellipse is a concrete feasible-set constraint on tire-force components, not a subtype of the abstract concept. Tradeoff, boundary, saturation, capacity, and optimization are related. Frozendomain_specific:equations_of_motionis false coverage because propagation equations do not supply the contact limit.
Hierarchy path (1) — routes to 1 parentless root
- Circle of Forces → Constraint
Neighborhood in Abstraction Space¶
Circle of Forces sits in a sparse region of the domain-specific corpus (91st percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely.
Family — Unclustered & Miscellaneous (1565 abstractions)
Nearest neighbors
- Ziggurat Algorithm — 0.81
- Intrinsic Equation of a Curve — 0.78
- Primitive Equations — 0.78
- Microscopic traffic flow model — 0.78
- Traction (mechanics) — 0.77
Computed from structural-signature embeddings · 2026-09-08
Not to Be Confused With¶
Friction circle / traction circle: direct aliases in vehicle dynamics.
Friction ellipse: noncircular implementation of the same combined-force envelope.
G-g diagram: vehicle-level acceleration envelope.
Friction coefficient: scalar input or summary, not the full combined-slip map.
Tire model: richer mapping of slips and states to forces.
Equations of motion: vehicle response to forces.
References¶
[1] Pacejka, Hans B. Tire and Vehicle Dynamics, 3rd ed. Butterworth-Heinemann, 2012. Combined tire forces and friction-circle concepts. https://doi.org/10.1016/C2010-0-68548-8. registry ↩
[2] Gillespie, Thomas D. Fundamentals of Vehicle Dynamics. SAE International, 1992. Tire-road friction and vehicle handling limits. https://doi.org/10.4271/R-114. registry ↩
[3] Rajamani, Rajesh. Vehicle Dynamics and Control, 2nd ed. Springer, 2012. Tire-force constraints in vehicle control. https://doi.org/10.1007/978-1-4614-1433-9. registry ↩