[Vinobien]

Has the limp mode event happened to anyone with a map OTHER THAN the v1.45?

[e.n335]

Information about what is stored in my car's ECU will be available tomorrow morning - FYI.

[A. Hansen]

I looked at my bill but nothing was related to the sensor. ......sorry

They also placed new tires (Michelin) unfortunatly they were not under warranty.

[e.n335]

Originally Posted by Fortbimmer

Happened to me yesterday. I was letting a friend test drive my car and he wasn't too use to a manual. He was in 5th and probably should have been down a gear. Once he hit it, the 1/2 engine light came on. The first time this has happened. It was hot, 90 degrees and the AC was on.

XEDE'd or PROcede'd ?

[e.n335]

Originally Posted by Vinobien

Has the limp mode event happened to anyone with a map OTHER THAN the v1.45?

Happened with XEDE and PROcede. Not sure if it happened without a piggyback. I also want to know why Terry335 sold his AA Xede. Terry, where are you ?

[Terry335]

Originally Posted by eugen.niederreiter

Happened with XEDE and PROcede. Not sure if it happened without a piggyback. I also want to know why Terry335 sold his AA Xede. Terry, where are you ?

This error did not happen on my Xede, that error was a startup check on the tmap sensor. At altiutude If you have too much resistance in the circuit without attenuating it slightly at 0rpm, it fails a startup test. I think they fixed it in the software.

I sold the Xede because I knew I could make almost as much power with my own setup.

[e.n335]

Originally Posted by Terry335

This error did not happen on my Xede, that error was a startup check on the tmap sensor. At altiutude If you have too much resistance in the circuit without attenuating it slightly at 0rpm, it fails a startup test. I think they fixed it in the software.

I sold the Xede because I knew I could make almost as much power with my own setup.

Hi Terry,

Thank you for feedback. Good luck with your own setup !

Cheers
Eugen

[sflgator]

Originally Posted by Vinobien

Has the limp mode event happened to anyone with a map OTHER THAN the v1.45?

PROcede v1.4 here.

[e.n335]

Let's wait for the results. I hope we are close to know what the ECU causes to behave like this and I'm very interested about the results. The v1.45 steptronic map works perfect, the car runs smoother than stock, not hotter at all and pretty economic while cruising.

Approaching the market with v2 will be quite a challenge for Vishnu having a v1.45 steptronic map already rolled out

[Fortbimmer]

Originally Posted by eugen.niederreiter

XEDE'd or PROcede'd ?

Proceed

Not real sure on the map, whatever was delivered with the big shipment in April. It's v1.45 or the one right before.

[Terry335]

Originally Posted by eugen.niederreiter

Let's wait for the results. I hope we are close to know what the ECU causes to behave like this and I'm very interested about the results. The v1.45 steptronic map works perfect, the car runs smoother than stock, not hotter at all and pretty economic while cruising.

Approaching the market with v2 will be quite a challenge for Vishnu having a v1.45 steptronic map already rolled out

We know what causes it. Map sensor reports less boost than the ECU was expecting given the rpm, tps, etc. It's a software issue, although rumor has it BMW is getting smarter about these plausibility checks to keep piggyback systems in check.

[e.n335]

Originally Posted by Terry335

We know what causes it. Map sensor reports less boost than the ECU was expecting given the rpm, tps, etc. It's a software issue, although rumor has it BMW is getting smarter about these plausibility checks to keep piggyback systems in check.

No, you were wrong.

[e.n335]

Hi,

Have been at a dealership and I am pretty sure the problem is identified now. I will send the informations to Shiv directly rather than posting them here on the forum. As I have been informed it's clear why this error occurs that randomly. Once Shiv has got the detailed diagnostics I am sure he will inform us ( his PROcede customers ) how he will proceed and solve the problem. In the meantime don't worry it's nothing that will harm our engines.

Cheers
Eugen

[RiXst3r]

Originally Posted by eugen.niederreiter

Hi,

Have been at a dealership and I am pretty sure the problem is identified now. I will send the informations to Shiv directly rather than posting them here on the forum. As I have been informed it's clear why this error occurs that randomly. Once Shiv has got the detailed diagnostics I am sure he will inform us ( his PROcede customers ) how he will proceed and solve the problem. In the meantime don't worry it's nothing that will harm our engines.

Cheers
Eugen

So is it something that dealers see stored in the DME, and then they know that you have had a PROcede installed... because the Creader cant clear the stored code?

[e.n335]

Originally Posted by RiXst3r

So is it something that dealers see stored in the DME, and then they know that you have had a PROcede installed... because the Creader cant clear the stored code?

They see a lot of things, you can be sure ... I got explained it today. But what they see allows no conclusion that a PROcede / Xede is in the car. Creader: read post #49, I explained it there.

[max boost]

Originally Posted by eugen.niederreiter

Hi,

Have been at a dealership and I am pretty sure the problem is identified now. I will send the informations to Shiv directly rather than posting them here on the forum. As I have been informed it's clear why this error occurs that randomly. Once Shiv has got the detailed diagnostics I am sure he will inform us ( his PROcede customers ) how he will proceed and solve the problem. In the meantime don't worry it's nothing that will harm our engines.

Cheers
Eugen

fair enough....strange why its so random though????????
if it was some sort of sensor malfuction i woulnt think it be so random...hrmmm or unless the is needs to send code so many times in a key cycle.......

[e.n335]

Originally Posted by max boost

fair enough....strange why its so random though????????
if it was some sort of sensor malfuction i woulnt think it be so random...hrmmm or unless the is needs to send code so many times in a key cycle.......

A couple of errors may occur on bone stock cars as well. There is a "logistic-counter" which determines whether an occured error should be triggered or not. Nothing rocket-science

[RiXst3r]

What about this...

I was able to access all the diagnostic functions with the PROCEDE installed that the dealer would need to access.
However, if you have a driveability complaint, do remove the PROCEDE prior to bringing it to the dealer. Drive it without the PROCEDE installed, and make sure the problem is still there.
The reason i'm stating this, is like with any control modules, there can be glitches that can cause driveability complaints, as does happen with BMW modules on occasion.
Also, with the PROCEDE installed, you get a fault in the DME(ECU), for a Short Circuit on the Boost Sensor, which will be normal with the procede as it does give you more Boost.
Without taking out the PROCEDE prior to bringing the vehicle in for a "Driveability Complaint", the technician might start trying to repair that boost pressure "problem" as indicated by the diagnostic computer.

And This...

Originally Posted by ac2

+1
The following is what stored in my DME. ... with ProCede only.

$error locationNr: 11757
$error locationtext: 2DED power management, standby current control
Error: 1(1) No.: 11757 2DED power management, standby current control frequency: 2
error type: 8 (4286 ) standby current violation
readines Flag: (16 ) Test conditions fulfilled
error status: (32 ) failure presently not available, OBDon-board diagnosis not debounced
MIL - Status: (48) failure does not cause warning lamp show light (MIL)
P-Code: P160F Powermanagement No-Load Current Error F_LZ: 40
ambient text / entry at 84xx km(2.) 84xx km(1.)
time with idle current 80 - 200 mA 0.00 min 3091.20 min
time with idle current 200 - 1000 mA 0.00 min 74.67 min
time with idle current larger than 1000 mA 0.00 min 0.00 min
voltage Kl. 87 0.00 V 11.98 V

Obviously there is stuff that the PROcede isnt dealing with correctly, and it causes stored info in the DME, which could eventually be traced back to being a signiture for having a procede installed.

[e.n335]

^ for what you have quoted secondly I'll come up with a solution soon. Probably Shiv should fix this with v2 ...

[RiXst3r]

Originally Posted by eugen.niederreiter

^ for what you have quoted secondly I'll come up with a solution soon. Propably Shiv should fix this with v2 ...

Wont your little automatic relay bypass plug thingies fix some of this?

[e.n335]

Originally Posted by RiXst3r

Wont your little automatic relay bypass plug thingies fix some of this?

They will not be needed.

[Park2670]

Those faults are the same one mine stored. I didnt go into it, thinking they were stored from the PROcede always being powered.