So, while chasing a smooth idle, I have been trying all sorts of things. I can get the car to idle nicely, but it will disrupt itself (missfire) after a bit, and start to hunt. When settings are in a sweet spot, it will immediately recover, until it misses again. Recently I have been following andy whittles advice on youtube, and watching for consistent injector pulse width. After chasing "spikes" in the pulse width toward 0ms, I decided to flatten all of my maps, crank up the data sampling rate, disconnect the IAC, turn off all ego correction, all idle control, all acceleration enrichment, and everything else I could find. This resulted in the following images:
In the chart you are seeing commanded pulse widths under 2 ms. They always are focused around 900rpm, but not always the same #. I have not found a reference to 900rpm in any settings. In the line graph bellow you see the full data set. The green trace is PW, and is highly unstable.
Here is another example with Red = PW, Green = RPM, and White = VE
:
You can see that even with a stable VE, and relatively stable rpm, the PW is unstable. Another interesting note, the PW is only unstable at idle, and usually around 900rpm.
Next I took some tooth logs. The standard tooth logs did not show anything unusual on the crank trigger, but on the composite logs we see less stable behavior:
This is not the best example, but you can see there are simultaneous high and low data points on the crank trigger at multiple points, and the cam signal is too close to one of the crank pulses. Elsewhere in the log there are gaps where there is no missing tooth, and multiple simultaneous data points.
This seems significant. The disruptions are not enough to show up as sync loss. My thoughts are that the disorganized data from the crank wheel causes a momentary sync loss, where injector pulse width falls toward 0, causing a missfire. Or, there is a mechanical issue causing a random missfire that is causing disorganized crank trigger readings. raising the software filtering on the triggers does not seem to have an effect.
More investigation to come.
Edit: During this process I found why my VE values are so high. I finally started logging Gamma Enrichment, only to find it at 51% when warm.... After correcting the coolant temp based enrichment map to end at 100% instead of 51%, I divided the whole VE table by 2. Now the numbers are far more realistic. Unfortunately this did not effect the above issue.