Vehicle makers: tyre forces and track data models cannot explain
Why vehicle dynamics models disagree with track data, why tyre forces stay unknown, and how to check what can be estimated from existing signals.
Book a free 30-minute callControl and optimisation since 2007: CERN helium cooling · IAV wind turbines · SkySails airborne wind
Tyre forces are unknown, so safety margins stay wide
What happens. Every driving-dynamics function depends on how much force the tyre can transmit now. Nobody measures that. Grip changes with road surface, wetness, temperature and wear, and the control works with a conservative assumption.
What it costs. Stability and braking functions that intervene too early in good conditions, comfort and sportiness given up for safety, and little room for functions that need to know the limit.
Why the usual fix fails. A tyre sensor adds cost and does not tell what the road does. Fixed tables for dry and wet are crude. A function that reacts after the tyre has started to slide has no time left to prevent it.
How a fixed-price remote diagnosis checks it. From vehicle signals you already record (wheel speeds, accelerations, yaw rate, steering angle, brake and drive torque) I look at how well the tyre forces can be estimated and under which conditions the estimate fails. The fixed-price remote diagnosis tells you whether a computed tyre force can let the margins shrink, and what it takes.
Background: Computing unmeasured states for control
Vehicle dynamics models do not match track data
What happens. A vehicle dynamics model is built from design data and simulation. On the track, with real tyres and real set-ups, the car behaves differently. The team compares simulation with measured data, finds gaps, and corrects parameters one by one.
What it costs. Set-up and control decisions made on a model that is off, track days used for finding out what the model gets wrong, and engineers busy with correlation instead of development.
Why the usual fix fails. Adjusting parameters by hand until one lap fits breaks the next one. A more detailed model brings more parameters to fit. Data from different days, tyres and temperatures blur each other.
How a fixed-price remote diagnosis checks it. From track recordings and the current model I look at which parameters the data really identify, and where the model structure itself is missing something. The fixed-price remote diagnosis tells you whether identification against the data can give a model that holds across conditions.
More problems that concern this industry
These problems are described on the page of the industry where they matter most:
- Vehicle battery cooling follows thresholds, not the route (Battery system makers)
- Charge and health estimates in vehicles drift (Battery system makers)
- Fast charging is limited conservatively (Battery system makers)
- More sensors per vehicle add cost (Automotive suppliers)
- On-board diagnosis requirements are hard to meet (Automotive suppliers)
- Control functions are specified loosely and reworked late (Automotive suppliers)
- Functions move to central computers and hit real-time limits (Automotive suppliers)
- Suspension has to trade comfort against handling (Automotive suppliers)
- Chassis control is developed model-based but confirmed in road tests (Automotive suppliers)
- Control functions for combustion, hybrid and electric powertrains pile up (Automotive suppliers)
Check it on your plant first: a fixed-price remote diagnosis
EUR 4,500 net · 5 working days · remote · availability on request · freelance or through temporary agency work
Within a fixed scope and at a fixed price, I review your data, control structure and measurements remotely and tell you whether the problem on this page is behind your symptoms and what fixing it would take. You get a short summary for decision-makers and a technical report for your engineers.