When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
Stock Problems/IssuesDiscussions related to warranty related issues and repairs, or other problems with the OEM parts and software for MINI Cooper (R50), Cabrio (R52), and Cooper S (R53) MINIs.
I have a 2006 R50 auto (CVT) and I am trying to clear the adaptations, but having a problem. I am using a iCarsoft i910-II tool. After I choose "clear adaptations" and it instructs me to turn the ignition on then off, I get the following screen....
EF, 00, 10, 31, No Found!
EF, 00, 10, 32, No Found!
EF, 00, 10, 33, No Found!
EF, 00, 10, 34, No Found!
EF, 00, 10, 35, No Found!
EF, 00, 10, 36, No Found!
EF, 00, 10, 37, No Found!
EF, 00, 10, 38, No Found!
EF, 00, 10, 39, No Found!
If I click on one of them it will take me through a few steps like I am clearing the adaptations. I have done this on all of them, but the car never goes into X mode (learning mode).
I know almost nothing about clearing adaptations. Are you sure that it didn't do the job and then it reported back that it can't find the adaptation files.
Well, the "X" is not displayed on the shift indicator (which indicates the vehicle is in learn mode after adaptations are cleared) So, I did go through the process of re-learning the adaptations and still no success.
I disconnected the Electronic Control Unit, which generated a EP code. No worries, when I reattached the code was cleared. After reviewing information on the ECU, the only programming involved will consist of reseting the adaptations, (back to the original problem)
Also when attempting to communicate to the CVT controller my scanner will not communicate with it. I assuming that this is where our problem may lie. Now to find it.
According to research, These are the following things that will effect the EGS/ECU;
DME Digital Motor Electronics
DSC (including the ABS "already corrected" / ASC)
Instrument Cluster
docsigns
Last edited by Docsigns; May 20, 2018 at 06:36 PM.
Update:
This is from the AAMCO repair manual... It looks like additional evidence to support my theory on replacing the CVT control module. Because we are having problems communicating to the CVT Controller (due to the lack of trouble codes) the information above further strikes my interest in moving forward with the replacement of the Transmission Control Module / CVT Controller.
Transmission fixed. After extensive troubleshooting I found the output rotation speed sensor was bad. After removing it, I examined the actual wiring and noticed that protective sheathing of the wiring was split exposing all the internal wiring. Of course the copper was exposed and some of it was corroded. I then ordered the new sensor. Now installed the Cooper is ready for inspection and registration.
That's a good news story! Thanks for sharing...I too have a 2006 R50 and we currently have around 154K...I've changed the fluid in the CVT every 25 - 30K (give or take) and have never had any problems.
Make sure you change the tranny fluid every 30,000 miles or so.
I also have a R 50 2006 LOVE IT !!!!!
I also wait about 5 seconds ( I count to 5) before I put my foot on the gas when changing gears. Like P to R then D....... This helps the CVT and prevents damage.
It takes a few seconds to " catch" in gear. This is one of the reasons the CVT tranny had /has issues.
Most people when they back out.....put the car into D while its rolling back !!!!!!
I've seen numerous people do this. My friend with his Honda. I do not think it has a CVT
@evano I have the exact same issue using the exact same iCarSoft i910-II on my 2006 R52 Sport Mini Cooper (See photos). Thanks for posting this.
EF, 00, 10, 31, No Found!
EF, 00, 10, 32, No Found!
EF, 00, 10, 33, No Found!
EF, 00, 10, 34, No Found!
EF, 00, 10, 35, No Found!
EF, 00, 10, 36, No Found!
EF, 00, 10, 37, No Found!
EF, 00, 10, 38, No Found!
EF, 00, 10, 39, No Found!
In addition, I had error codes regarding the ABS sensors and DTC convertible top voltage errors:
29 Switch, convertible-top locked, voltage 2.5V
CODE: 2321005B no description!
30 Switch, hard top, voltage undefined
CODE: 2321005B no description!
I haven't began to sort this out yet....
@Docsigns I've included my errors from pages 1 & 2 when attempting to reset CVT adaptations. This led me to check if there were any errrors from the DTC page, as seen in photo 3.
1611 Serial communication connection, gearbox control unit (research discloses this is a supply sensor voltage 1 and 2 out of range)
1613 Smooth running controller (research discloses this as microprocessor failure RTI2)
p0700 Transmission Control System Malfunction
1661 Timeout, EWS telegram
With the help of thePDFat MiniCarParts.net
(https://www.google.com/url?sa=t&source=web&rct=j&url=https://www.minicarparts.net/PDF/MR5EMXToolMANUAL0825-234V1.pdf&ved=2ahUKEwi1tOq8obLhAhXQJTQIHdjRBZQQFjA AegQIARAB&usg=AOvVaw0uVCnBeojD6BswzQZYnK6U), my conclusion there-for is:
A - The transmission control module (TCM) located underneath the steering wheel is either not connecting or has gone bad or,
B - The rotational speed sensor is either not connecting or has gone bad.
I've unplugged the TCM, cleaned the male and female connections and applied a bit of aerosol dielectric grease in addition to replacing both left and right ABS sensors (part number 34526756384). There was absolutely no change to the TCM errors. The ABS error code are now of course gone.
When I have a moment, possibly tonight, I'll do the same (clean, inspect, treat and verify a good connection) with the rotational speed sensor and all other connectors to the transmission.
I will provide an update when this basic maintenance is completed. In the meanwhile I've already ordered a new "rotational speed sensor" (part number 24357518732) and O2 sensors (part number 11780872674) just in case.
Errors of page 1 attempting to reset CVT adaptations Errors of page 2 attempting to reset CVT adaptations Errors from DTC page which led me to believe that either the rotational speed sensor was either not connecting or has gone bad.