This place would make a woodpecker's head hurt. It's a two cylinder, wobble fire tractor motor.
.3 sec response time has nothing to do with sample rate, It has everything to do with matching up the data packets and filtering data.
Andy
Please explain to us how you match it up to a two cylinder, wobble fire tractor motor operating above 1000 RPM. Since you have 8.333 exhaust pulses per cylinder at 1000 RPM and you can only get 3.333 samples what are you reading? What is being missed and what is real? It surely isn't what each firing cycle is doing.
So if response time has nothing to do with sample rate please explain how you can get an accurate reading faster than the sensor is capable of reading. Also explain how you filter something you do not have.
In steady state conditions you have the following:
1000 RPM you have missed ~ 40% of the firing events and the reading your getting is some average with reversion mixed in.
6000 RPM you have missed ~ 94% of the firing events!
Now lets look at a normal set of conditions when riding the bike. You let the clutch out at 1000 RPM and accelerate the engine to 4000 and shift. The engine is not in a steady state condition, and you have no idea when your samples are taken with many aftermarket Broad Band systems. So end end up with some randomly taken samples at best.
I have no problem using a broad band or narrow band system but you must understand the limitations of ANY system to make good use of it.