Fist I like to relate to this video. And yes it works well with 50% PWM DC/AC this way but it’s not the reality as we use a hall sensor one pulse per crank rotation (not 50% PWM) so we get no RPM reading @ all while the engine runs. Only @ start-up we get some RPM spikes and it hold the last RPM reading as well even when no signal is fed into the data logger.
https://www.youtube.com/watch?v=12Z9JbnwTUs
We had the MK1 data logger working well on the RPM reading before we upgraded the new firmware and now have the same problems as with the MK2 types. Suggest to jump back on older type of soft/firmware as this was working well.
This is how the data logger reads RPM. On the left the RPM the ECU reads and on the right it should display the crank RPM from the data logger. Also fast medium or slow timer speed makes no sense as it changes the reading or freaks the reading out totally.
https://www.youtube.com/watch?v=50SeI3J ... e=youtu.be
RPM problems on all type of data loggers with new firmware
Moderators: JeffC, rdoherty, stieg, brentp
Yes the RPM reading is better with 2.7.9 firmware so that’s an improvement.
@ brentp. I can sent you load of pictures of signals we us for testing but this is not the problem. The triggering is OK.
The data logger is unable to interpolate or calculate RPM with low speed resolution.
Also the thing called timer speed worries me as it looks like you swiping the dust under the carpet and al do you do not see the dust it’s still there. Please revise you speed calculation and avarice things out over an X amount of trigger points not only using time base calculation divide by the amount of trigger points.
@ brentp. I can sent you load of pictures of signals we us for testing but this is not the problem. The triggering is OK.
The data logger is unable to interpolate or calculate RPM with low speed resolution.
Also the thing called timer speed worries me as it looks like you swiping the dust under the carpet and al do you do not see the dust it’s still there. Please revise you speed calculation and avarice things out over an X amount of trigger points not only using time base calculation divide by the amount of trigger points.
Hi,
Thanks for the follow up.
The "slow / medium / fast" is simply a re-labeling of the previous timer speed settings we had in the Race Analyzer app where we used the terms "Timer MCK / 64, Timer MCK / 128 ... etc" This was very confusing for people, so we simplified the names.
It does exactly the same as before: it selects the low to high frequency range for the timer used for measuring RPM or frequency. The Medium speed is best in most cases for measuring RPM ranges.
Thanks for the follow up.
The "slow / medium / fast" is simply a re-labeling of the previous timer speed settings we had in the Race Analyzer app where we used the terms "Timer MCK / 64, Timer MCK / 128 ... etc" This was very confusing for people, so we simplified the names.
It does exactly the same as before: it selects the low to high frequency range for the timer used for measuring RPM or frequency. The Medium speed is best in most cases for measuring RPM ranges.