Page 5 of 5

Re: OBD logging/display issues in Android

Posted: Mon Aug 08, 2016 6:09 pm
by Harry
aaronc7 wrote:Any desciption of the new adaptive vs aggressive vs conservative setting?
Generally speaking, "Aggressive" means LapTimer will extrapolate OBD fixes more often, and "Conservative" means it applies extrapolation seldom. The measure for extrapolation aggressiveness is the relation between the time distance between two OBD fixes used as the extrapolation basis, and the time distance from the last base point to the extrapolation position. As an example, if the two fixes are 1 second apart and the requested position in time is further 2 seconds away, the measure is 2. Aggressive means extrapolations are allows up to this factor, while conservative uses a factor of 0.5. For the later, two fixes 1 second apart will get extrapolated a max of half a second forward. "Adaptive" means the factor is calculated dynamically based on the sensor update rate. A 8 Hz sensor (or faster) will get a max factor of 0.5 while a 2 Hz Sensor (and below) will get a factor 2.0. Any update rate in-between will get a value between 0.5 and 2.0.

O.k., I'm aware that facts in high dose can be toxic... :-)
I try to rephrase it:

Adaptive should work around spikes for high update rate sensors but not produce stepped OBD values for low rate adapters. Only in case you face either steps or spikes when using "Adaptive", select "Aggressive" for stepped results and "Conservative" for spiked results. Any change of the setting will have an effect on new recordings, existing recordings are unchanged.

- Harry

Re: OBD logging/display issues in Android

Posted: Thu Sep 08, 2016 6:59 am
by Willi87
Hello,
I just want to give a small feedback. I have had the same problems, which are described in this post.
But now everything seems to be fine!

Thank you very much for fixing this issue!

Here is my new lap from the 06.09.2016 on the Nordschleife:
[youtube]https://www.youtube.com/watch?v=Cl4JohFRFG8[/youtube]

Kind regards,
Willi