After looking many detailed InputTrigger/TriggerLog logs, I think it would be possible to tune ignition advance with free-revving

This means without

Actually, this is a kind of GenBoard/LoggerIntegration/DedicatedLogger/VirtualDyno.

This eliminates the problem associated with

high RPMdot problem

This uses the own theta of the engine, measuring the change in RPM precisely. InputTrigger/TriggerLog shows that even energy of individual events can be measured in

Timing from predetermined tooth - or simple "coil type" trigger

This is a standard method. GenBoard firmware is migrating to the superior "timing from the last possible tooth" method (AdvancedIgnition).

Without "timing from the last possible tooth", if the ignition is tuned by free reving it'll probably end up with a lot of advance. The reason for this is that the engine has already became faster, but it still uses the higher period data from the times of lower RPM, so the ignadv will be faster.

Low frequency of calculations

This would effect tuning, but not as badly as the timing from predetermined tooth. This would also result in slightly (really small effect) higher ignadv values in most of the map. Reason: the engine uses the ignadv from a lower RPM applied to a higher RPM, so the bigger advance will get into the lower RPM loadsite of the map.

Travelling across the map

Of course only those loadsites can be tuned, that are met.


Software to: