mr2guru

iTrader: (16)

So I periodically open up my "misfiredetect.cfg" config in my scanner... and check for real misfires or if one cyl is misfiring more than the others down low.

I have "current misfire" #1-8 in the PIDs and I've logged them before. I've got a TRex cam so of course I get plenty of "misfires" at idle and they would disappear when revved up.

So I go to do this today and nothing.... it won't log current misfire. Everything else I have setup in that config will log but misfires don't.

So the only changes I've made since the last time I've done this is switching to an SD tune and upgrading to 2.017.

I am leaning towards the upgrade? but all my other custom configs work fine.

But then again one thing I've noticed is I haven't had to clear a general misfire code in a while. So I am also thinking the PCM isn't even looking for misfires anymore? Is this an SD thing?

Hrmmm confuzzled.....

GuitsBoy

iTrader: (4)

I also noticed that it didnt look at misfires with teh MAF unplugged.

mr2guru

iTrader: (16)

Nice (in a way) At least I know its in the PCM side of things. I wonder if it is a maf plugged in thing only... Say I keep my table zeroed out (SD) plug maf back in, or if it is an SD mode thing?

I wonder if 1bar SD enhanced fixes this OS issue?