Knowledge base on Peake codes for E39 M5 - Page 28

Polynova · 9th June 2009, 07:26

With the exhaust CPS replaced, all codes went away except for the following:

8F - E-Fan Box, and
AA (it did go away at the instance right after the CPS replacement, but came back again the next day, probably due to a cold start)

If the latter eventually disappears I would try to look into factors that could be the triggering magic. Wishful thinking but at least I don't have SES warnings to deal with.

Thanks again.

chowdah · 9th June 2009, 18:04

There is a DIY e-box fan replacement post somewhere, though it's not the easiest thing to reach if I remember correctly.

wilsodh · 9th June 2009, 19:25

Quote:

Originally Posted by Polynova

With the exhaust CPS replaced, all codes went away except for the following:

8F - E-Fan Box, and
AA (it did go away at the instance right after the CPS replacement, but came back again the next day, probably due to a cold start)

Sounds ominous. Do a few resets, and if you really do have full carbon occlusion of the SAS, you'll see the AA code come back every 2nd or 3rd cold start.

That's a drag!

Dave

vixpix · 11th June 2009, 21:55

Hi - have a quick question on these codes.
Just recently replaced the MAF sensors and have driven approx 100 miles. Recently started the car (already warm after a short drive to my indy shop) and the SES came on. Just purchased a Peake today and am looking at:-
69 - Engine coolant temp - plausability
AE - Air-fuel adaption, bank 1
AF - Air-fuel adaption, bank 2

Could the new MAFS (Bosch) cause the AE & AF?
Not sure about 69...I had been driving slowly (under 45MPH) and the coolant level is normal.

The beast is a stock MY2000 with 71K miles

Thanks

chowdah · 12th June 2009, 22:43

100mi seems like enough to let the DME adapt to new MAFS. You can run a "secret menu" test from member DavidS to confirm their performance.

AE and AF are not very specific. With all Peake codes, note them, reset them, and wait for them to come back (if at all). 69 is a pretty common code. Do a search with the error code words; "69" is too small for the search engine here.

vixpix · 13th June 2009, 01:38

Thanks for the reply. I reset the codes today and will wait and see.
After I posted I found all of the thermostat related discussion on "69"
Monitored the K Temp yesterday and it never got above 78C...it was 75F outside and I drove it on the freeway and back roads. The temp needle never got to the 12 o'clock position always just to the left of center.

chowdah · 13th June 2009, 06:07

You mean "below" not "above," right? Typically it's easier to expose a worsening thermostat condition in colder ambient conditions. Your needle position is normal.

vixpix · 13th June 2009, 19:40

It varied between 75C and 78C after warming up. I had read that it should be >79C for optimal coolant temp. Just wondering if this was enough to trigger the SES.

Kleintje · 22nd June 2009, 21:09

After my engine start shaking (cas was shaking from left to right (or other way arround)) I did some research;

18 Ignition Coil Cyl #4
54 Secondairy air control circuit
46 Misfire detected, catalyst damaging, Cyl #8
4A Misfire detected, catalyst damaging, Cyl #12 (12? Thought I had a V8)
71 Camshaft position sensor, Cyl #1-4
29 Air mass sensor
51 Secondary air system, cyl #5-8
39 Misfire, Cyl#2
4D Air contaiment valve, shrouded injectors, Cyl 5-8
D1 Misfire during warm-up, Cyl #5
D2 Knock sensor, Cyl 1-2
D3 Knock sensor, Cyl 3-4
D4 Knock sensor, Cyl 5-6
D5 Knock sensor, Cyl 6-8
95 Misfire w/empty fuel tack (tank?)
C8 Misfire w/fuel cutoff, Cyl #5
C9 Misfire w/fuel cutoff, Cyl #6
CA Fault code memory error
CC Idle speed increase -CAN Bus
CE Knock control test pulse
91 Fuel control, Cyl #4-6

It seems I'm reading also old errors.?

Before I put the car away (its in my garage sinds 16th of April) I did a hard reset on the car. I removed the battery and put the + and - cable together (not from the battery....but from the car). Sinds then I did a battery recovery and its on a slow (smart) charger...

Time for a new car?

chowdah · 22nd June 2009, 21:27

Only you can find out if they are old errors - by resetting the codes and seeing which return.