@colin62 cheers, this is a learning experience and I dont mind being educated. I wont apologise for how I speak or type though..theres many members here who write in a weird frame and you have to gloss over these things. I am what I am.
Back to sensors, I think the crux I am trying to get to is, ok, we have ways of detecting what is going on, but I'm stubborn in that (as I have typed a few times) it isnt reliable enough to throw a fault code. Just because a wheel is deemed to be reading a bit odd..The wiki page for the second type of pressure sensor even says this....
Without going hyper-local, the cars are used all over the world in snowy conditions, sandy areas..not just Parktown, Jhb. To consistently enough read one wheel different (half a percent? one percent?) and to them use this as gospel data to put a car in limp mode still doesnt strike me as a sane idea.
If it snows in Seattle, as it does, or Moscow, or Sweden, and every sensor is consistently producing weird results....it just doesnt stack up that BMW (or any other automaker) will use that data to the point of limp moding the car. An ecu code you can read with a scanner sure...same as a cylinder intermittent misfire. But activating limp mode...I'm still unconvinced.
In fact, I doubt I would buy a car that does that. The only choice I can see is if all sensors are out (based on their neighbour) then suspend any decision until such time as sensors calm down.
My original question was how do we make a program based on the sensor readings that detects one tyre has 5000km more wear than the other. Its been covered that you cant directly use the data produced (I hope we can all see the large range of variables that you just simply cannot rely 100% on), but perhaps you can fuzzy it over a few days to work out "something" (we can leave what that is for a later day), and now we have to decide if that "something" is worth limp moding (as the garage said) (do we have faith in our conclusions enough to justify taking the car to a dealer and inconveniencing our client) or just throw a code for the service techs to check at the regular service interval.
And to throw this into the mix, the OP's car a pair of tyres replaced, as it is normal to do
So if we take this to our x6 car (the poster mentioned they replaced both tyres too), we can see that our theoretical system has to rely only on an axle, not on 4 wheels. The x6 mentioned above has two new tyres, and two worn tyres. And isnt throwing a code.
So back to the drawing board. Our system can only use a pair of wheels, one of which may naturally be going a different speed due to corners, or bumps in the road, (concave or convex, that tyre goes a further distance), pressure differences or weight, road conditions etc (yeah, picky..but we're trying to reliably measure 0.5% difference in one wheel) and our data has to be solid enough to activate limp mode. And apparently, this system is in use in a bmw x6 right now. So lets work it out.
The much more glaringly obvious answer is that bmw cleared the code for a transmission/diff/speed sensor/abs ring, put on two new tyres and spun a story. And the code hasnt returned.
Those are our two choices.