MYBLKSS

iTrader: (1)

Converter lock-up is unpredicable after cam install. Which has led me to do some research and there seems to be two different ways to solove the problem.

1. Set the Misfire detection temp between 139-140
or
2. Move the values in the idle by cycle & low rpm by cycle tables to 32000

Which technique works the best?

NoGo

iTrader: (2)

Turning the code off works best. Rather turning the TEST off works best. Set the P0300 test to Type X.

<small>[ March 06, 2003, 07:10 PM: Message edited by: NoGo ]</small>

MYBLKSS

iTrader: (1)

So I should set the values in the misfire detection table to 139 and 140.

gojo

iTrader: (12)

</font><blockquote><font size="1" face="Verdana, Helvetica, sans-serif">quote:</font><hr /><font size="2" face="Verdana, Helvetica, sans-serif"> 2. Move the values in the idle by cycle & low rpm by cycle tables to 32000 </font><hr /></blockquote><font size="2" face="Verdana, Helvetica, sans-serif">Try this way first. If it works it's the best way, since completely turning off the tests means you will not detect true misfire.

<small>[ March 06, 2003, 11:08 PM: Message edited by: gojo ]</small>

MYBLKSS

iTrader: (1)

what do the values (32000) represent. Does it represent the total number of misfires? Last night I autotapped the car and most of the time the car kept misfires per cylinder in the single digits, but when I came to a stop some cylinders jumped up as high as 26.

Sonny

iTrader: (1)

</font><blockquote><font size="1" face="Verdana, Helvetica, sans-serif">quote:</font><hr /><font size="2" face="Verdana, Helvetica, sans-serif">Originally posted by MYBLKSS:
<strong> what do the values (32000) represent. Does it represent the total number of misfires? </strong></font><hr /></blockquote><font size="2" face="Verdana, Helvetica, sans-serif">it is a time interval (I think it is in millisecond) that PCM checks for misfires.
</font><blockquote><font size="1" face="Verdana, Helvetica, sans-serif">quote:</font><hr /><font size="2" face="Verdana, Helvetica, sans-serif"> when I came to a stop some cylinders jumped up as high as 26. [/QB]</font><hr /></blockquote><font size="2" face="Verdana, Helvetica, sans-serif">This is reason you want to set the low rpm tables to 32000.

Good luck,

MYBLKSS

iTrader: (1)

Thanks sonny called my tuner today hope to get it fixed soon, but at least I know whats wrong with it now.

RPM WS6

iTrader: (3)

</font><blockquote><font size="1" face="Verdana, Helvetica, sans-serif">quote:</font><hr /><font size="2" face="Verdana, Helvetica, sans-serif">Originally posted by NoGo:
<strong> Turning the code off works best. Rather turning the TEST off works best. Set the P0300 test to Type X. </strong></font><hr /></blockquote><font size="2" face="Verdana, Helvetica, sans-serif">IIRC, The test is either toggled on or off. The "Type X" is what you want to set the field for that asks "Does error set SES?". Type X = turned off, but that just keeps the DTC from being stored and the MIL from being commanded on from what I understand. The diagnostic test and the SES type are separate toggle fields.

I found that even with the test and the SES off, I still lock-up issues until I maxed out the misfire tables in the idle and low rpm ranges. I set them all to 32,767 or whatever the max is, now I get lockup every time. <img border="0" title="" alt="[Smile]" src="gr_stretch.gif" />

02BlackWS6

RPM WS6,

You're correct...Turning the P0300 code off will not help with the lock-up issue. I have EDIT and a Vig3600 converter and the only way to get consistant converter lock-up is to set both values to 150, which is max. Because even though the code is turned off, if the PCM sees misfires it will cause lock-up issues, even though a SES light isn't set or a code isn't stored.