PDA

View Full Version : How do you log misfires in COS5?



onfire
July 11th, 2007, 12:55 PM
TIA. I've logged in the GM OS, but can't get COS5 to show misfires.

onfire
July 12th, 2007, 03:16 AM
cricket, cricket, cricket.....

joecar
July 12th, 2007, 03:27 AM
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
July 12th, 2007, 04:09 AM
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
July 12th, 2007, 09:39 PM
i never got it to work either :( You NEED to be able to see misfires

onfire
July 13th, 2007, 12:31 AM
I logged all the misfire pids yesterday.....nothing :(

onfire
July 13th, 2007, 02:55 PM
I sent a pm to Paul and Ross to see it they can help us out.

Cablebandit
July 14th, 2007, 05:46 AM
I think I already contacted Paul about it with no answers...I dont think it can be done as is

GMPX
July 14th, 2007, 12:08 PM
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
July 14th, 2007, 12:30 PM
Ok, I'll check.

onfire
July 14th, 2007, 01:15 PM
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


Thanks for checking in Ross:cheers:

The misfire pids validate....but they do not report anything except for the caserl,mfcstat,mfcylidx1,msload and msrpm....those pids report but the misfire history and misfire per cylinder do not.

This is OLSD COS5 .....no 02's

Thanks for any help that you can provide.

2002_z28_six_speed
July 14th, 2007, 01:18 PM
Listening in..

squealingtires
July 19th, 2007, 12:16 PM
I'm hoping for something here too. I'm showing feedback AFR's of 18+:1 at idle from the LM-1 and I'm not getting any misfire signals using COS#5.

joecar
July 19th, 2007, 01:20 PM
Ok, I see ASPARK working (it sometimes goes to 99%)... is there a way of making it go "more"...?

joecar
July 19th, 2007, 01:20 PM
I'm going to find my MAF and install/enable it to see if misfire counts work.

joecar
August 17th, 2007, 03:46 AM
I found my MAF and installed it, and un-failed it in my COS5 tune...

now I see misfire counts being logged (and I can see increased count rates when I run bad leads)...

Is there a way to run SD without failing the MAF...?

It seems to me that failing the MAF inhibits certain functions like misfire detection
(and others which I am not sure about, possibly to do with the trans.).

onfire
August 17th, 2007, 07:13 AM
I found my MAF and installed it, and un-failed it in my COS5 tune...

now I see misfire counts being logged (and I can see increased count rates when I run bad leads)...

Is there a way to run SD without failing the MAF...?

It seems to me that failing the MAF inhibits certain functions like misfire detection
(and others which I am not sure about, possibly to do with the trans.).


That's pretty good detective work! Now we know why it doesn't work. Could EFI develop a work-a-round?

DrX
August 17th, 2009, 07:39 AM
Was this ever worked out? I'm running COS3 with O misfire counts logged.

joecar
August 17th, 2009, 08:15 AM
No, with MAF failed the PCM seems to not process misfires...

Some people at HPT claim they can do SD without failing the MAF... but I'm not sure how...?