2002 MINI Cooper Limp-In Mode
Hey guys I got a MINI Cooper that is giving me some trouble. Originally Customer brought vehicle to us wanting a DME replacement or DME update. We talked him into doing some diag first. Customer has loaded the parts cannon all the way to the top on his own and came to the conclusion through google and youtube that he needed a DME software update or replacement. Customer concern is if the engine is revved over 2500RPM then it goes into Limp-In mode until the codes are cleared. I confirmed the customers concern.
Originally the codes that i pulled were P0036, P0340 and P0130. So i started with the CMP sensor as the likely cause of Limp-In mode. CMP Sensor was new, power and grounds to it were good but had a steady 5v signal. So we replaced the CMP Sensor and now the 5v is a square wave. I clear codes and test drive. The car goes into Limp-In mode but it acts different than the first Limp-In Mode(RPM's were limited to 2000RPM and Engine power was reduced). Where now it acts like a throttle body code with very limited throttle opening. Check Engine Light came on again with a P0036 and an additional code P1689- Electronic throttle monitoring , level ⅔, torque calculation - error.
So I replaced the Throttle Body with a VDO brand and performed the adaption. The Throttle Body on the car looked pretty new, was clean and was also a VDO.
I drove the vehicle several times and it never went into Limp-In Mode but it has a surge above 2500RPM while cruising.
The customer is now stating that he replaced the Throttle Body and the problem stayed away for a few days before coming back.
He also gave us more information on the situation. He bought the car with a crank no start condition. He replaced many sensors and repaired the MAP Sensor wiring and then it would start but had this Limp-In Mode concern that he brought to us for.
So I guess my question is should I try to update this DME first before doing any additional diag to appease the customer? or should I go with my gut and do some more testing first?
That sounds like a can of worms. It's a long shot but the early R50s did have issues with throttle body connections. We used to replace the looms under warranty. Have a good look at the connection. Also check the fuel pressure and flow. It's not monitored by the DME.
Yep I remember doing those harnesses as well. Check around the front corner edge of the cylinder head over the transmission side. The harness makes a sharp bend around the head with the sharp corner edge of the cylinder head. Was a common chafe spot. For P1689, check fuel pressure AND volume (Cannot stress this enough). Pressure should be around 55psi, give or take, Key On Engine Off and should…
When a vehicle has performed for the last 20 years with no issues it is highly unlikely that software will fix anything.
If this is supercharged? The throttle body code is due to crank pulley slipping causing low supercharger output
I've got a little farther on this thing but its still giving me fits. I tried a software update through ISTP/A and it pulls this up as a Supercharged S Model W11 Engine. I believe this is most of the problem I just don't have a solution yet. We told the customer and he showed up with another used DME the very next morning(suspiciously fast if you ask me), that was supposed to be for the exact…
Yes the DME you tried to program is NOT original. Last 7 of the VIN are different from what you posted (Look at upper left hand corner of ISTA/P, middle picture). Someone has tried to swap a DME, for what reason is unknown. If the DME/EWS will not align with the original module, try to do a 1 hour battery reset. If that still will not work, Verify that all the modules on the car have matching…
i did reinstall the original dme that was in the car and it did successfully realign the dme with the ews. i still don't know how the autel or the snap on pulled up the correct vin. the first picture makes it appear that the EWS and/or the KOMBI are the suspected modules with the wrong vin? i'm mainly just trying to figure out in one fell swoop which module(s) need to be replaced.