How did I miss this thread......
I've noticed the same issue when using a timing analyzer and comparing the reading to what tuner pro shows.
For what it's worth, because I am running a C3 ecm, I don't put much faith in the tunerpro timing reading. I do know that the different analyzers I've tried are accurate.
I have 3 different analyzers:
- All-Test 3800, digital readout using a magnetic pickup in conjunction with the inductive clamp on the number one plug wire.
- Kal-Equip 3821, digital readout using a magnetic pickup in conjunction with the pulse coming from the coil.
- Kal-Equip 4020, analog meter using a magnetic pickup in conjunction with the inductive clamp on the number one plug wire.
- I also have an Equus 5568 timing light that has the "advance" function on it.
All three work and all three accurately read the mechanical timing properly, but, as I recall, the timing reading in TunerPro was always different, although I don't remember how much.
I finally realized that the readings in TunerPro for timing did not really matter, because what did matter, was knock counts and where it was occurring.
I've questioned the purpose of the spark latency table and the best understanding of it that I've gotten, (may not be entirely correct r complete), is that it's function is to correct to frequency and duration of the reluctor pulse at different RPM's. This table varies in values based on things such as distributor size for example.
If you google "gm spark latency table", you will find some "white papers" that discuss this further.
This is my two cents, YMMV.
Edit to add video: (note that the timing in tunerpro is off by 3 degrees or so, and, I believe that the reason for that is that the analyzer is more "real-time" than what TunerPro is showing due to the 160 baud rate of the ECM I'm using.
Bookmarks