DB9 Misfire Monitor

DB9 Misfire Monitor

Author
Discussion

NoGrip

Original Poster:

36 posts

22 months

Sunday 6th October 2019
quotequote all
I inherited my Father's 05 DB9 last year with only 16500 miles on the clock. The engine had a terrible misfire / hesitation which I reckoned was failing coils. Reading on this forum, I suspected the misfire monitor hadn't been enabled, so I took her out and managed to enable on the second rundown using a Foxwell NT520pro. This let the dash light up with the emmisions warning and let me see that three cylinders had a large number of misfires.

Roll on a few months, with 12 new Beru coil packs, NGK plugs, PCV valves & air filters, the engine is running very well. However, I can feel some popping at idle from the N/S exhaust, but no matter what I have tried I cannot get the misfire monitor to enable again. I have disconnected the battery twice and then cleared all fault codes, but still after about six attempts at the rundown sequence, the misfire monitor will still not enable. The rundown sequence that I am using is:

No aircon, infact whole air system set to off.
6th gear in Drive
Not in Sport mode
Cruise at 70+ and dropping to 20mph (no brakes / straight line)
Repeat another 4 times

Is there something else that I could be overlooking? Or do I just ignore, drive on and enjoy the experience smile. Any help much appreciated!

Ken Figenus

4,842 posts

75 months

Sunday 6th October 2019
quotequote all
Misfire fuel hitting the manifold cats could be a big worry so I would bite the bullet and take it to an indie that has the AMDS system to diagnose.

NoGrip

Original Poster:

36 posts

22 months

Sunday 6th October 2019
quotequote all
Hi Ken, I totally agree about the cats and that's what has me wound up.

I'm feeling a bit confused (maybe because I was up in the middle of the night trying to relearn the parameters) but I have just been searching through the OBDII reader and found a parameter '36-1 profile learned' and it says YES. A quick Google of that says that this is the misfire profile, but it is definitely not the same 'misfire corrections' parameter that we watched change to 'enabled' during the first rundown sequence which immediately activated the emmision warnings for the first time ever.

I can now see the misfires per cylinder and #10 stands out with a high misfire rate. It is worse when cold but still only ~0.6% misfire dropping to the 0.0X% range when at normal temperature. Hopefully if it does go above the 1.4% threshold it will light the dash up. No biggy stripping the engine down again but I need to figure out which component is at fault.

Ken Figenus

4,842 posts

75 months

Sunday 6th October 2019
quotequote all
I have a Foxwell too - good to know it is so capable as I'm around the scheduled time for plugs and coils, but she runs sweet as a nut so no need yet to do plugs at 50,000 miles - 20,000 left in 'em!

NoGrip

Original Poster:

36 posts

22 months

Sunday 6th October 2019
quotequote all
The thing that threw me this time was I was looking at the parameter 'Misfire Monitor' which was stuck at 'Not Enabled'. I'm 95% sure that this was the one that changed to 'Enabled' during the pre-coil change but now will not change to 'Enabled'. Very possibly during the coast down procedures the '36-1 profile learned' parameter had updated without me knowing and let me read the misfire counts. The '36-1' just didn't register as being the one banghead

NoGrip

Original Poster:

36 posts

22 months

Monday 7th October 2019
quotequote all
I have spent today going through the OBDII reader and hopefully this will be a useful summary for whoever may need it.

Firstly, using the Aston Martin software on the Foxwell NT520pro, screen by screen, to check that the Misfire Corrections have been learned using the 'coast down' procedure.






This is where I appeared to go wrong. Watching for the 'Misfire Monitor' to become enabled. It never did!





Then I found this parameter!




Success!




Now the misfire readings are unlocked smile


Checking the misfire readings using the generic OBDII read function:









$80 Test / TOTAL engine misfire and catalyst damage rate (updated every 200 revs?)



$81 Test / TOTAL engine misfire and emission threshold rate (updated every 1000 revs?)



$82 Test / HIGHEST engine catalyst damage misfire and catalyst damage misfire rate



$83 Test / HIGHEST engine emission threshold misfire and emission threshold misfire rate

I can't explain why this is zero, unless is it calculated using a different sample rateconfused



$84 Test / Inferred catalyst mid-bed temperature



You can also look at individual cylinders. #9 for example:



EWMA - Misfire counts (average) for last 10 drive cycles. 0.00% in this case (sorry, no screen shot!)


Misfire Counts Last / Misfires on this cylinder during last drive cycle (3 miles)




$80 Test / Cylinder misfire rate and catalyst damage rate



$81 Test / Cylinder misfire rate and emission threshold rate



So the new coils and plugs appear to be doing the trick and are well under the misfire thresholds. However, with these readings I can still feel some popping from the exhausts at idle.

Hopefully I have pulled the information together correctly for this, but please do tell me if I have anything wrong.

Gavin

gaussianmist

37 posts

27 months

Monday 7th October 2019
quotequote all
You might want to communicate these findings to Aston1936 who is the DB9 and Foxwell maven.

PetersAston

5 posts

84 months

Thursday 20th August
quotequote all
Thank you for an extremely useful post - I used a Foxwell NY510 to check the misfire learning had taken place on my DBS following a battery change - It hadn’t but trying again was successful. Wonderful to be guided through checking the missfire count on each cylinder.

Peter

Archimedou

34 posts

37 months

Tuesday 25th August
quotequote all
Hello,
I cannot see the images anymore. Would it be possible to have them back?
Many thanks

LTP

265 posts

70 months

Tuesday 25th August
quotequote all
Archimedou said:
Hello,
I cannot see the images anymore. Would it be possible to have them back?
Many thanks
I see them fine - the problem may be your end

N7GTX

4,673 posts

101 months

Tuesday 25th August
quotequote all
Using either the Aston menu or the OBD one, are you able to see the lambda sensor output readings for all the sensors? On a hot engine, i.e. with the cats 'lit' (300c) and idling the fronts - upstream - should be switching between 0.1v and 0.8v roughly once a second or so. The after cat ones - downstream - should be fairly stable around 0.6v.
Is the coolant temp reading good e.g. if the cooling fans are cutting in and out then you don't want to see 20c, it should be around 92-95c. Follow the coolant temp live reading from cold and make sure it is smooth all the way to the fans running.
Chasing a misfire is more than just checking for a misfire code. With saying the problem appears better as it warms up may point to an injector issue or the increased load when cold may be an HT problem. Check for tracking marks on the ceramic part of the plugs.

Edited by N7GTX on Tuesday 25th August 18:23