[OpenFlash]

Originally Posted by Rossifumi

Just to make sure... When you press the accelerator and get the sound that indicates that it reads the code, you also get an message on the iDrive window stating "Engine malfunction, service engine soon" or something like that?

Yep.. it is accompanied with the little "ding" sound The light goes away by itself in 30 sec or so. Or when you press the throttle on/off for the second time (during the code clearing process).

Shiv

[boxter]

Hi Shiv!

I´ve just read the DME codes after "update" to firmware123, I saw two codes:
11379 Lambda probe behind catalytic converter, signal Often triggered during the firmware update process… normal. Just clear the code.
11380 Lambda probe behind catalytic converter 2, signal Often triggered during the firmware update process… normal. Just clear the code.


Thank a lot

[OpenFlash]

Originally Posted by boxter

Hi Shiv!

I´ve just read the DME codes after "update" to firmware123, I saw two codes:
11379 Lambda probe behind catalytic converter, signal Often triggered during the firmware update process… normal. Just clear the code.
11380 Lambda probe behind catalytic converter 2, signal Often triggered during the firmware update process… normal. Just clear the code.


Thank a lot

If you go back and forth between Doomsday and nonDoomsday maps, there will be some adaptation required since both maps run different fuel rail pressures. Any roughness with the DD map should go away within a few on-boost pulls. But seeing that you have a Rev.2 (which can read/clear codes), why are you running the Doomsday map? You should run the nonDD map.

I don't know what to tell you with respect to valet mode. It's the same as its always been. I'll look at it today though...

shiv

[boxter]

Originally Posted by shiv@vishnu

If you go back and forth between Doomsday and nonDoomsday maps, there will be some adaptation required since both maps run different fuel rail pressures. Any roughness with the DD map should go away within a few on-boost pulls. But seeing that you have a Rev.2 (which can read/clear codes), why are you running the Doomsday map? You should run the nonDD map.

I don't know what to tell you with respect to valet mode. It's the same as its always been. I'll look at it today though...

shiv

Hi Shiv!

I only want to learn all and you are who can help me!!

Then I always will run nonDD map OK!!

Thank you Shiv

[Glowin]

Shiv, any idea why?

Originally Posted by Slidewayz

Does not (yet) clear the airbag code, but hopefully you will get to this soon (please-please-please)...

[OpenFlash]

Originally Posted by Glowin

Shiv, any idea why?

Yes... Because the airbag diagnostic system isn't powertrain related. And the PROcede, as it stands, only reads/clears powertrain related data. We can certainly extend the feature to clear airbag codes in the future. But we have a few things to do first.

Shiv

[jonm42]

Originally Posted by cn555ic

Thank you so much! The low pressure sensor cost me $63 and looks like an easy installation....the high pressure sensor cost 70 bucks and needed to be ordered...THe service rep told me 9 out of 10 times is the low pressure sensor.....so I am hoping that you come back with that part number...Also would you happen to know the code they found for this sensor that was changed out?? Thnaks

Yup, it was the low pressure sensor: 13-53-7-547-883 (13509953?) -- the invoice is hard to read. Code was 29F3.

[edo]

Does someone know what codes 11322 and 11326 mean?

[Glowin]

Originally Posted by edo

Does someone know what codes 11322 and 11326 mean?

Just go here:

http://www.easycalculation.com/decimal-converter.php

It's 2C3A and 2C3E. Now you can look these up in the forum and see what they mean. Hopefully they're there!

[edo]

Originally Posted by Glowin

Hopefully they're there!

No, they aren't...

[Sparky66]

Time to get Bavarian Technic Tool.

[edo]

Damn.
I used to get limp modes because of misfires in cylinder #5 and 6. Swapped the spark plug coils (in order to see if bad coils were the reason) this weekend and I haven't got a limp mode since. However, I'm getting error 11326 every time when I read the codes with Vishnu software (after driving, obviously).

[edo]

Originally Posted by edo

Does someone know what codes 11322 and 11326 mean?

Anyone?

[lawdude]

I assume it's not listed on that code sheet Shiv has posted somewhere.

[edo]

Originally Posted by lawdude

I assume it's not listed on that code sheet Shiv has posted somewhere.

Yep, not on the list.

[OpenFlash]

Originally Posted by edo

Yep, not on the list.

Yep.. it's some obscure code I've seen seen or been able to induce myself. I did a quick search on the forum and no mention of it either. So the best bet is to go get it read by the dealership. I suspect it will explain the cause of your issues (boost oscillation).

Shiv

[edo]

Originally Posted by shiv@vishnu

Yep.. it's some obscure code I've seen seen or been able to induce myself. I did a quick search on the forum and no mention of it either. So the best bet is to go get it read by the dealership. I suspect it will explain the cause of your issues (boost oscillation).

Shiv

Well, no boost oscillation with the new maps. At least I didn't feel it (like previous time when I was logging the runs). Didn't log this time.

I got the same code again (11326). Read the errors with my code reader. It appeared to be P112D error. I found the definition on e90post:

P112D: O2 sensor negative current or positive current control open circuit (bank 2 sensor 1).

[packinDSS]

Guys am I doing this right?

I connect the proceed software and see it say connected.

I made sure the guages were on and press the accelator to the floor...i get the ding and see the "engine malfucntion message on Idrive" but the CanBus DME codes never change....it says 65535 which converts to FFFF.

Help have to bring car to dealer...

[packinDSS]

Originally Posted by packinDSS

Guys am I doing this right?

I connect the proceed software and see it say connected.

I made sure the guages were on and press the accelator to the floor...i get the ding and see the "engine malfucntion message on Idrive" but the CanBus DME codes never change....it says 65535 which converts to FFFF.

Help have to bring car to dealer...

I am connected because I see the throttle value go to 100 when I press the accelator to the floor. I did get a code pop about a month ago that went away after I restarted the car.

[Glowin]

Originally Posted by packinDSS

Guys am I doing this right?

I connect the proceed software and see it say connected.

I made sure the guages were on and press the accelator to the floor...i get the ding and see the "engine malfucntion message on Idrive" but the CanBus DME codes never change....it says 65535 which converts to FFFF.

Help have to bring car to dealer...

Hmmm.... that's suspiciously the same value as the max when you go to the properties of some of the channels... Wonder if you're doing it right.

[packinDSS]

Originally Posted by packinDSS

Guys am I doing this right?

I connect the proceed software and see it say connected.

I made sure the guages were on and press the accelator to the floor...i get the ding and see the "engine malfucntion message on Idrive" but the CanBus DME codes never change....it says 65535 which converts to FFFF. I am connected because I see the throttle value go to 100 when I press the accelator to the floor. I did get a code pop about a month ago that went away after I restarted the car.

Help have to bring car to dealer...

I still have this problem. I am wondering what happens if your car has no codes to clear? When you press the gas to the floor what does the Procede software show if there are no codes and what does iDrive or the dash dispaly if there are no codes...etc..?

I have not had anyword from Shiv for the last week on this via PM. Is he away?

[jpsimon]

packin, i'll test out what happens when there are no codes and get back to you this afternoon