2 ms·
> how exactly the suspension compresses during breaking The entire graph of suspension vs time should be well below the frequency range. It doesn't matter whet
by kazinator 3y ago
> how exactly the suspension compresses during breaking
The entire graph of suspension vs time should be well below the frequency range. It doesn't matter whether we are looking for frequency domain features or time domain features.
(Like someone said upthread, it's probably 4000 events per second as an aggregate from numerous sensors, mutiplexed into one sqlite. Or maybe even a total across the three sqlites.)
- magicalhippo 3y agoI found this page[1] which mentions dynoing shocks at 3 inches per second, as that what one could see in the pits. If you want some spatial-temporal resolution for that then you'll want a fairly decent sample rate, no? Maybe not quite 4kSps is needed but for vibration and such it'd make sense to me. But sure, could very well be an aggregate rate. [1]: https://www.speedwaymotors.com/the-toolbox/general-sprint-car-shock-technology/30975 https://www.speedwaymotors.com/the-toolbox/general-sprint-ca...
- kazinator 3y ago3 inches per second is very slow. I think shocks compress quite a bit faster when you hit a speedbump in a parking lot. The sample rate you need to reconstruct the motion of shocks is entirely determined by Nyquist, just like sampling audio or any other signal. You need some 2.2x the highest frequency you want to capture, and make sure you filter out anything above that (if it exists). If there is nothing above 20 Hz in the suspension's movement, or nothing you're interested in, then you need a 44 Hz sample rate. (More if you implement oversampling, but not 10 times more let alone 100.)