- Tue Jun 09, 2015 3:26 am
#931
Once you've got the latest code on (Assuming it works for you), then I'll be interested to see a similar log. I just remembered that there was a fix go in recently to the duty cycle calculation in TunerStudio, the values being shown were too low. This didn't affect the pulsewidth itself, purely the DC% calculation on the gauge/log.
As I mentioned on IRC, there is a known problem occurring once DC% goes above about 85% that can cause some very strange behaviour. The simple solution here is to cap the DC at 85%, which would prevent the possible missed firings etc, but does means that the pulsewidth will not be increasing beyond that 85% DC mark.
As I mentioned on IRC, there is a known problem occurring once DC% goes above about 85% that can cause some very strange behaviour. The simple solution here is to cap the DC at 85%, which would prevent the possible missed firings etc, but does means that the pulsewidth will not be increasing beyond that 85% DC mark.