How do you log misfires in COS5?

[onfire]

TIA. I've logged in the GM OS, but can't get COS5 to show misfires.

[onfire]

cricket, cricket, cricket.....

[joecar]

I noted same thing: zero misfire counts (I'll go back to 12212156/12202088 to compare).

And also I noted: ASPARK seems to stay at 100% always (even with prolonged pinging).

[onfire]

I noted same thing: zero misfire counts (I'll go back to 12212156/12202088 to compare).

And also I noted: ASPARK seems to stay at 100% always (even with prolonged pinging).

I'm going to try a couple of different pid selections today and see if any work. I'm getting all 0's too. Misfire per cylinder is a great tool when it works....we need to figure out a solution.

[Cablebandit]

i never got it to work either :( You NEED to be able to see misfires

[onfire]

I logged all the misfire pids yesterday.....nothing :(

[onfire]

I sent a pm to Paul and Ross to see it they can help us out.

[Cablebandit]

I think I already contacted Paul about it with no answers...I dont think it can be done as is

[GMPX]

If the problem exists in V5 it will be there in V3 as well. Might be to do with them not really running in full closed loop I'm not sure, or, is it the PID's will not validate?
Joe, with ASPARK stuck at 100% just check that A0000 is not accidently set to Enable and A0001 at 100%.

Cheers,
Ross

[joecar]

Ok, I'll check.