Hmm, warning light came on

[fallingman]

Ok got the scanner and what an excellent bit of kit; plug in, switch on, turn on ignition, read error codes, erase error codes, done. Thirty secs max and no yellow light.
The only code thrown up was PO420 which I've yet to find it's meaning, but after the reset it's yet to return so fingers crossed it was a one off.

My warning light came on the other day too, so I sent off for the same unit (the 2012 version of the D900). Problem is it won't connect to my Zed. The screen lights up, it asks me what brand of car I've got, I hit 'New Scan' and then it cycles through all the different protocols a few times before giving up and telling me it cannot connect to my vehicle. Anyone got any ideas why it's not working?

 

[Lillywhite]

I hit 'New Scan' and then it cycles through all the different protocols a few times before giving up and telling me it cannot connect to my vehicle. Anyone got any ideas why it's not working?

Make sure you switch the ignition on to position 2 (dashboard lights on) and it should work. :wink:

 

[fallingman]

Make sure you switch the ignition on to position 2 (dashboard lights on) and it should work. :wink:

Yeah, did that. No joy.

 

[fallingman]

My warning light came on the other day too, so I sent off for the same unit (the 2012 version of the D900). Problem is it won't connect to my Zed. The screen lights up, it asks me what brand of car I've got, I hit 'New Scan' and then it cycles through all the different protocols a few times before giving up and telling me it cannot connect to my vehicle. Anyone got any ideas why it's not working?

So my D900 mystery deepens. I contacted the vendor and they asked me to try the unit on another car to check whether it was faulty. So I tried it on my wife's S-Max and it worked first time!

As you can imagine, that was infuriating. :x So in a sulk I stomped back to my Zed to try one last time... and this time it worked!

So I cleared my error code (P0420 in case you were wondering, going to see whether it comes back again before I worry too much). Obviously I wanted to run a scan again to check everything had wiped okay - and of course the bloody thing wasn't working again.

So I ran back to the S-Max, ran a successful scan, came back to the Zed and, hey presto, working in the Zed again. Seems my D900 unit will only communicate with my Zed after it has spoken to my wife's car first. What does that tell you?!

But seriously, why what could be causing that??? :?

 

[Georgio]

I don't know if it's because I didn't get any instructions, but I found the scanner only connected if I actually had the engine running.
What I did was connect the scanner with engine and scanner both off, then turn over the engine then turn on the scanner, select BMW, wait for the handshake and options then take it from there.
By having the engine running you can also see all the live data which is nice.

Ok got the scanner and what an excellent bit of kit; plug in, switch on, turn on ignition, read error codes, erase error codes, done. Thirty secs max and no yellow light.
The only code thrown up was PO420 which I've yet to find it's meaning, but after the reset it's yet to return so fingers crossed it was a one off.

My warning light came on the other day too, so I sent off for the same unit (the 2012 version of the D900). Problem is it won't connect to my Zed. The screen lights up, it asks me what brand of car I've got, I hit 'New Scan' and then it cycles through all the different protocols a few times before giving up and telling me it cannot connect to my vehicle. Anyone got any ideas why it's not working?

 

[Georgio]

Not to suck eggs, but are you making sure the plug to the obd socket is really pushed in tight?
Either that or you have the female D900 that obviously has to be sweet talked by your wife's car before it comes out to play.
If you can't resolve it, best bet is to send the unit back asap and get another, if it's still happening then, then you have a stubborn zed.... :wink:
Btw was the code you got PO4020? If so then that's the same code I got.

My warning light came on the other day too, so I sent off for the same unit (the 2012 version of the D900). Problem is it won't connect to my Zed. The screen lights up, it asks me what brand of car I've got, I hit 'New Scan' and then it cycles through all the different protocols a few times before giving up and telling me it cannot connect to my vehicle. Anyone got any ideas why it's not working?

So my D900 mystery deepens. I contacted the vendor and they asked me to try the unit on another car to check whether it was faulty. So I tried it on my wife's S-Max and it worked first time!

As you can imagine, that was infuriating. :x So in a sulk I stomped back to my Zed to try one last time... and this time it worked!

So I cleared my error code (P0420 in case you were wondering, going to see whether it comes back again before I worry too much). Obviously I wanted to run a scan again to check everything had wiped okay - and of course the bloody thing wasn't working again.

So I ran back to the S-Max, ran a successful scan, came back to the Zed and, hey presto, working in the Zed again. Seems my D900 unit will only communicate with my Zed after it has spoken to my wife's car first. What does that tell you?!

But seriously, why what could be causing that??? :?

 

[Lillywhite]

Nice to see that the Code Reader now works. :wink:

Also it's interesting that all three of us have the Fault Code P0420 and guess what we all have the 2.0i model!

Now I have had this code from time to time but not for well over a month and I recently put in a can of BG44K fuel cleaner in a full tank of petrol hoping that this might clean out any carbon build up in the system. I'm hoping that this will solve the problem. My car is due for it's MOT in four weeks time so it will have an emissions test.

 

[Georgio]

Yup it's a nice bit of kit; I keep mine in the boot with all the other 'emergency' stuff.
I haven't had the light return since clearing it so more than happy that it was a one off due to a Sainsbury's fill-up that was unavoidable.
Fingers crossed on the MOT; I'm sure your exhaust will be ok.

Nice to see that the Code Reader now works. :wink:

Also it's interesting that all three of us have the Fault Code P0420 and guess what we all have the 2.0i model!

Now I have had this code from time to time but not for well over a month and I recently put in a can of BG44K fuel cleaner in a full tank of petrol hoping that this might clean out any carbon build up in the system. I'm hoping that this will solve the problem. My car is due for it's MOT in four weeks time so it will have an emissions test.

 

[Lillywhite]

Yup it's a nice bit of kit; I keep mine in the boot with all the other 'emergency' stuff.

Fingers crossed on the MOT; I'm sure your exhaust will be ok.

I also keep mine with the 'emergency' stuff. I was encouraged when you advised that your Cat was very clean and as regards to my forthcoming MOT I'm hopeful since the previous owner spent a fair bit of money last July, replacing tyres, rear springs, front brake discs and pads etc. I think this MIL light must be very sensitive.
I've emailed you the D900 manual for your information. :wink:

 

[fallingman]

Nice to see that the Code Reader now works. :wink:

Also it's interesting that all three of us have the Fault Code P0420 and guess what we all have the 2.0i model!

Hmm, yes, coincidence?! :roll: My warning light hasn't come back on yet - though I have only driven about 30 miles since I turned it off!

Yup it's a nice bit of kit; I keep mine in the boot with all the other 'emergency' stuff.

Not much use me keeping mine with the emergency stuff, unless I can also squeeze my wife's S-Max in there! :wink:

 

[rajen44]

Hi guys,

Sorry to bring this thread back up. Did anyone manage to sort out the p0420 code in the end as I have this issue on my 2.0?

Thanks.

 

[Jfgoldfish]

Did anyone manage to sort out the p0420 code in the end as I have this issue on my 2.0?

It is quite common for this code to be thrown for no reason at all!
First step is to clear it and see if it comes back. Occasionally it can come up due to contaminated fuel, too much idling, too much gentle driving or sometimes if the wind is blowing in the wrong direction.

I replaced both mixture control O2 sensors on mine, they were old and slow to respond, that seemed to stop the code returning. I highly doubt the O2 sensors are always to blame but worth checking they both function as expected.

 

[tug]

Have had my 2.0i for 6 years now and i found that the light comes on randomly when in wet (pi$$ing down) conditions and having to drive "carefully"

I just pull out the scanner and turn the light out, its always the P040 code so not concerned. I have had all 4 lambda sensors changed & me manifold welded over the time ive had her. So i just put it down to the 2.0 gremlins.

I have found that the N46 loves to be thrashed regularly & that keeps the light away.

Cheers, tug