Previous value is not updated and causes a Rate too high error in the next round

[vol907]

Issue

Hi,
I am using v16.0.0. Post-processing is set to check max rate > 0,05 (default?).
I get "Rate too high" errors, although the data recognition seems to work perfectly and the max rates are not exceeded. Here an extract of the data (which I also fully enclose):

2025-06-22T04:27:23+0200,main,00005.1987,5.0987,5.0987,0.000160,0.0008,no error,0.0,0.0,0.0,0.0,5.0,1.0,9.0,8.8,7.8
2025-06-22T04:32:23+0200,main,00005.2345,,5.0987,,0.0000,Rate too high - Read: 5.2345 - Pre: 5.0987 - Rate: 0.1358,0.0,0.0,0.0,0.0,5.0,2.0,3.0,4.5,5.2

My interpretation is that at 04:27:23 the new previous value has not been updated in spite of a perfect reading. Consequently, at 04:32:23 the raw value is compared to the previous value, which in this case is not the last but last last value. And this results in a "Rate too high" error.

Is this interpretation correct? Why is the previous value not updated? Are there other solutions or workarounds other than disabling the max rate control, which I think is needed?

Thanks in advance!
David

data_2025-06-22.csv

[SybexX]

CheckDigitIncreaseConsistency activated? Then deactivate it.
https://jomjol.github.io/AI-on-the-edge-device-docs/Parameters/#parameter-checkdigitincreaseconsistency

[vol907]

Ok, it was enabled and I have disabled it right now. Let's see how it behaves.

Thank you for the hint!

[vol907]

Works perfect now, thanks!