When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
So I always had at least one cyl showing a higher misfire count then all the rest. I had this for the whole life of the car and I had it a LOOONG time. Now, this is seen in HP scanner and never had any codes. So I mentioned it when I was getting my car tuned SD for my SC and when I got home I never see any misfire count move from zero. So I figured my tuner went in an raised some of the misfire tables, BUT all tables are completely stock...So is there any other parameter that would make the misfire count from registering? I cannot seem to figure it out....
Probably because failed MAF mode was designed to be a fallback/safety limp mode kinda thing. I didn't realize misfire detection didnt work in SD either, but good to know. My misfire limit tables were maxed out when I got a cam, I was thinking about going back and start bringing them back to sane values, but it would have been a wasted effort.
One time I did attempt to monitor misfires on my Aeroforce gauge and it was 0 across the board, I figured the thing didn't work but it was probably because of the SD tune. learn something new every day.
Probably because failed MAF mode was designed to be a fallback/safety limp mode kinda thing. I didn't realize misfire detection didnt work in SD either, but good to know. My misfire limit tables were maxed out when I got a cam, I was thinking about going back and start bringing them back to sane values, but it would have been a wasted effort.
One time I did attempt to monitor misfires on my Aeroforce gauge and it was 0 across the board, I figured the thing didn't work but it was probably because of the SD tune. learn something new every day.
agreed...wish it had the ability to read the misfires