02 sensor reset on montster 4.8is 2007

[ake53]

hi everyone.

does anyone know how would i reset the check engine light on a 2007 4.8is
using DIS or Inpa or carsoft maybe..?

thank you

[TerminatorX5]

any of those would do... INPA has the clear/erase error memory function...

but.. did you say 2007 4.8iS? the latest iS was made in September of 0'6 for euro market, still designated as '06 models... maybe, you meant 4.8i, which E70?

Not that it matters for the light reset... still the same thing, just need to choose E70 in INPA, instead of E53...

[ake53]

Originally Posted by TerminatorX5

any of those would do... INPA has the clear/erase error memory function...

but.. did you say 2007 4.8iS? the latest iS was made in September of 0'6 for euro market, still designated as '06 models... maybe, you meant 4.8i, which E70?

Not that it matters for the light reset... still the same thing, just need to choose E70 in INPA, instead of E53...

thanks, I never used inpa before. It lookd all in german and i didnt see e70 on it...
and yeah its 2007 x5 4.8i

[ard]

More important question is WHY the cel came on, what CODE was shown, and how the underlying issue was fixed....

[ake53]

Originally Posted by ard

More important question is WHY the cel came on, what CODE was shown, and how the underlying issue was fixed....

Yeah yeah.... it was an 02 sensor. the guy bought OEM sensors and got a shop to replace them. Shop never cleared code and it doesnt go away from simple driving...

[TerminatorX5]

you do have the OBD cable? connect to the car, fire up the sw, see if you can clear the codes.. if INPA doesn't help, move to the next sw that you have... eventually you will get it...

[ake53]

Originally Posted by TerminatorX5

you do have the OBD cable? connect to the car, fire up the sw, see if you can clear the codes.. if INPA doesn't help, move to the next sw that you have... eventually you will get it...

On my E53 dis works like a charm but with the e70 its a little different.
i go into ediabus file, launch if32 tool. -
than I launch BMWHEAD32 tool - to connect the obd cable

than i launch dis in vmware. on the connection bar i have almost all bars besides the last bar...

On dis i go to diag. pick vehicle. turn car on and run quick tests. than go into dde module and try reading the codes...

what could i be doing wrong?

[ard]

Originally Posted by alex77ae

Yeah yeah.... it was an 02 sensor. the guy bought OEM sensors and got a shop to replace them. Shop never cleared code and it doesnt go away from simple driving...

Yeah, yeah...in my experience, an "O2 sensor code" can mean 'bad sensor' OR it can mean 'bad air/fuel ratio due to air leak, etc, that is fooling the DME into thinking it is a bad sensor'.

The way OBDs work, if the O2 sensor was bad and it was replaced, the CEL should eventually clear once there are enough cold starts without an error present.

Just saying...

Any cheap OBD readers should be able to reset the codes/CEL. If the CEL comes back immediately, you'll know it wasnt an O2 sensor.

A

[ake53]

Originally Posted by ard

Yeah, yeah...in my experience, an "O2 sensor code" can mean 'bad sensor' OR it can mean 'bad air/fuel ratio due to air leak, etc, that is fooling the DME into thinking it is a bad sensor'.

The way OBDs work, if the O2 sensor was bad and it was replaced, the CEL should eventually clear once there are enough cold starts without an error present.

Just saying...

Any cheap OBD readers should be able to reset the codes/CEL. If the CEL comes back immediately, you'll know it wasnt an O2 sensor.

A

yea I know. thats why Dis shows you exactly what is wrong...
and I dont think that plain obd scanners clear bmw codes

[TerminatorX5]

i had an OBD logger that logged the travel info, that could clear codes on E39...