Wheel Speed Sensor Resolution
Made a bracket to bolt in a wheel speed sensor to my front wheels to be able to run traction control
Made it so wheel speed sensor picks up one the inner ring of bolts (5), or the outer ring that holds the rotor (8)
Does anyone know of minimum resolution to accurately run traction control from front and rear wheel speed differences?
And what would happen if I ran 5 or 8 as appose to making or getting something off the shelf to work with a higher resolution like 20+?
I was planning on only using it 10~15 mph +
the resolution can be debatable. if you get really high resolution the computer can see it fine but can it control your power fast enough? it will end up spending a lot of time waiting for the next ignition event to retard or cut. thats where running real high rpm can help too, you can make power changes quicker.
<trigger warning, ev talk>
one of the things that fascinated me about the tesla plaid i had was how fast it could control power delivery. i suspect it was controlling the motors at kz kind of update rates* and could see slip extremely quickly. it was fast enough even in the rain at wot you could feel it working to stay stuck, but it felt like it was doing it with only a few degrees of wheel slip at a time. a gas/ice engine simply cant change its power output that fast regardless of how many teeth you have on your wheels.
*this made me curious so i briefly looked at some vesc (bldc controller used in electric skateboards and similar stuff) info and they seem to be in the 100s of hz ranges of control.
That is interesting indeed, I'll have to check mine out when I get mine set up
Still winter and non driving conditions here. And I still don't have the car set up and ready yet
But excited for first start








