Engine Light Came on - No Fault on IDrive though???

[Raz0s]

Hey,

I hope I am not doubling up on a thread, although I had a strange issue with my 135i this afternoon. The engine light came on after approx 2 minutes of the car running ... but the IDrive system says 'No Faults'.

I 'Did not' have reduced power or any car symptoms, just and engine light on.

Turning the car on and off didn't help so i used my Procede to clear the faults and then test to see if it came back. Drove it around for 10 minutes and car seems fine. Anyone else had this issue?

[RaihaX]

do you have catless downpipe?

your CEL will come on if your procede autoclear setting is not on?

[Raz0s]

Only other mods are cat less mid pipes and a diff back exhaust, which has been on the car for over a year and had no issues.

Nothing has changed with the car for some time now.

[RaihaX]

did you check for any error using your procede?

[Raz0s]

Nah, cleared before I had a chance. Wasn't close to home and sorta got impatient as I didn't like seeing the light on the dash :P.

Im curious though if anyone else has had this issue. I thought if the car throws a fault it 'should' prompt you on Idrive...?

I may just need to wait for it to come back.

[RaihaX]

Probably best - some code only triggers a CEL but doesn't give you limp mode.

ps. You should keep a little netbook in your glove box with a car charger that is what I did when I had the procede haha....

[BMW86]

The only way you will ever know is by reading the codes. The symptoms are too common so it could be a range of things.

[Raz0s]

If the error only throws a CEL and not limp mode... I am assuming its not a major issue? I understand that is a vague question... but should I be concerned from peoples experience? or simply drive until it comes back?

[BMW86]

Originally Posted by Raz0s

If the error only throws a CEL and not limp mode... I am assuming its not a major issue? I understand that is a vague question... but should I be concerned from peoples experience? or simply drive until it comes back?

Usually if you throw a CEL and/or LIMP it disappears after you re-start the car. Not everything breaks the first time so this could be the beginning of the end of something. Reading the codes is the only way to know.

[pavo335]

Well that's it then your cars fucked. Lol I didn't like the light so I cleared it!

[TimMc]

I've had this happen twice. Both times on track & both went away after restarting the car. Codes said that 1st was rear brakes overheating & 2nd was a misfire in cylinder 1.

[Pretz]

I had a situation last week where the car developed a misfire, then went into limp mode (with associated warning lights), but didn't log an error. Was all fine after I left it for half an hour or so but took it to dealer anyway as it is under used car warranty still. Dealer (admittedly Merc) said no fault logged. Is this common? I would have thought if it's serious enough to trigger warning light it should be serious enough to log.

[RaihaX]

Originally Posted by Pretz

I had a situation last week where the car developed a misfire, then went into limp mode (with associated warning lights), but didn't log an error. Was all fine after I left it for half an hour or so but took it to dealer anyway as it is under used car warranty still. Dealer (admittedly Merc) said no fault logged. Is this common? I would have thought if it's serious enough to trigger warning light it should be serious enough to log.

If it misfired to my understanding it should have a misfire cylinder x error code.

Everytime I misfire there is always a error code that comes up.

[luster]

ive noted that each time I get a CEL it is normally directly related to emissions related events.

errors on idrive tend to be everything else!

(this is only my own personal experience)

[Raz0s]

Thanks for the response guys.

Ok soo the light came back on during the drive to work today. I was close enough to Canterbury BMW so I swung past and the code was checked out. Looks like the oxygen sensor has gone.

Anyone else had this issue?

[BMW86]

Originally Posted by Raz0s

Thanks for the response guys.

Ok soo the light came back on during the drive to work today. I was close enough to Canterbury BMW so I swung past and the code was checked out. Looks like the oxygen sensor has gone.

Anyone else had this issue?

What is the code? And did they clear it?

[drjekl]

So I had a CEL come on this afternoon whilst toodling along driving home. I have only just recently started driving the car after being overseas for 2 weeks (the car was on a battery tender whilst not in use)

I didn't notice a drop in power and giving it a slight squirt in 2nd where i could in traffic it didn't misfire.

I'm running a procede Rev 2.5, with AR DP's and an ams fmic and AA CP installed by advan just before xmas....

Restarting the car this evening it still came back on, and i happen to notice that cranking was a split second longer then normal (or i may just be imagining things thinking its the HPFP) how do I check the codes?

Please bear in mind I'm a total noob, but I'm guessing download the procede software to my laptop and then plug it into the procede and perform some type of diagnostic check?

The car had a fresh set of plugs installed in march 2012 (about 8k kays ago by memory) and it seems to be driving fine so far.

[Ian///M]

Originally Posted by drjekl

So I had a CEL come on this afternoon whilst toodling along driving home. I have only just recently started driving the car after being overseas for 2 weeks (the car was on a battery tender whilst not in use)

I didn't notice a drop in power and giving it a slight squirt in 2nd where i could in traffic it didn't misfire.

I'm running a procede Rev 2.5, with AR DP's and an ams fmic and AA CP installed by advan just before xmas....

Restarting the car this evening it still came back on, and i happen to notice that cranking was a split second longer then normal (or i may just be imagining things thinking its the HPFP) how do I check the codes?

Please bear in mind I'm a total noob, but I'm guessing download the procede software to my laptop and then plug it into the procede and perform some type of diagnostic check?

The car had a fresh set of plugs installed in march 2012 (about 8k kays ago by memory) and it seems to be driving fine so far.

Procede can read fault codes. Hook your laptop up to OBD2 port

[drjekl]

Originally Posted by Ian///M

Procede can read fault codes. Hook your laptop up to OBD2 port

Thanks mate I will do some searching on all of this!

You wouldn't believe it but the warranty expired 18 days ago.....

[drjekl]

Originally Posted by drjekl

So I had a CEL come on this afternoon whilst toodling along driving home. I have only just recently started driving the car after being overseas for 2 weeks (the car was on a battery tender whilst not in use)

I didn't notice a drop in power and giving it a slight squirt in 2nd where i could in traffic it didn't misfire.

I'm running a procede Rev 2.5, with AR DP's and an ams fmic and AA CP installed by advan just before xmas....

Restarting the car this evening it still came back on, and i happen to notice that cranking was a split second longer then normal (or i may just be imagining things thinking its the HPFP) how do I check the codes?

Please bear in mind I'm a total noob, but I'm guessing download the procede software to my laptop and then plug it into the procede and perform some type of diagnostic check?

The car had a fresh set of plugs installed in march 2012 (about 8k kays ago by memory) and it seems to be driving fine so far.

I had some time off over easter and hadnt driven my 335i in almost 2 weeks, and upon starting this week it wasn't running right as it was idling rough and at suburban speeds it was jerky and hesitating. Once oil temp hit 100 deg C, I gunned it & it had no power at all and misfired.

That night when I drove it again upon WOT it went into limp mode and had a engine light illuminated on the dash. I hooked my pc up to the procede ecu but no error codes were logged.

The next morning the same thing occured, once the oil temp hit 100 degrees i gave it some and bam straight away the engine light came up and it started misfiring badly (limp mode). I didn't have time to hook the procede up to it as i was arriving at work, i thought I will deal with it when I go to leave work that afternoon.

When I went to leave that day the car started up fine and the engine light no longer stayed on, but I noticed the idrive screen switched off and was blank the idrive controller was locked tight and then a few minutes later a SOS picture came up on the dash screen with a picture of a phone with a slash through it. Eventually the idrive screen came back on and the date and time popped back up as per normal along with sound through the stereo.

Since then the car is back to normal and gets full boost in 1st and 2nd gear and hauls arse really, but at 60 km/h in 4th gear it still hestitates slightly....

So I dont think its the hpfp as i dont have long cranks, and atm its pulling hard to redline in 1st and 2nd gear, the spark plugs are 12 months old with about 5k kays use so they should be ok perhaps its a coil or an injector....

Steve (Drawn05) dropped by today and hooked up his scanner and pulled the following codes:

DME: 2C3E 2C2E

DSC: 5DA3 5D93

Looking online the dme code is:

Lambda probe in front of catalytic converter 2, control failure or cable transmission failure

& the DSC code 5DA3 is:

5DA3/C0 - Wheel speed sensor front right start recognition v_comparison.
5D93/C0 - Wheel speed sensor front left start recognition v_comparison

Whilst searching google for these codes a guy with a m5 complained of jerky acceleration like the trac is kicking in and he stated it was the throttle positioning sensor....

Any ideas guys on what action should be taken with these codes? (its interesting how when i let the car rest for a few weeks i get an engine light when i go to drive it - the car was on a battery tender whilst not in use)