- Location
- MilkyWay Galaxy
I disagree.
96 OBD-II also indicates cylinder missfires using the same technique. But in this case it gave the wrong code because it never completed the emissions monitors lock in (relearn process initiated after replacing a bad O2 sensor) process because of the miss fire. This same 96 OBD-II rig did report missfires properly 4 years ago when the heads cracked.
I actually reported this HERE on
after discovering how it worked on this 96 rig, 5 years ago when the heads cracked:
"The ECU uses the master timing signal from the CPS to determine which cylinders aren't contributing as much power as they should (and thus which point in the rotation the crankshaft slows down at) and then sets codes for that."
The problem I ran into had nothing to do with CPU power, it was a buggy logic algorithm in the ECU that not been tested enough IMHO.
96 OBD-II also indicates cylinder missfires using the same technique. But in this case it gave the wrong code because it never completed the emissions monitors lock in (relearn process initiated after replacing a bad O2 sensor) process because of the miss fire. This same 96 OBD-II rig did report missfires properly 4 years ago when the heads cracked.
I actually reported this HERE on

"The ECU uses the master timing signal from the CPS to determine which cylinders aren't contributing as much power as they should (and thus which point in the rotation the crankshaft slows down at) and then sets codes for that."
The problem I ran into had nothing to do with CPU power, it was a buggy logic algorithm in the ECU that not been tested enough IMHO.