BMW Forum - BimmerFest BMW Forums banner
Status
Not open for further replies.

iDrive controller not working - SOLUTION FOUND

43K views 18 replies 7 participants last post by  HerbP  
#1 ·
Hi all,

I'm hoping someone might be able to help with an iDrive controller question.

My CCC died a few weeks back and I ended up shipping the unit off to be fixed. It's come back working, playing music, etc - but the iDrive controller is now not working (turning or clicking down have no effect). The company that repaired my CCC state that they have tested the unit complete with amp/screen/controller and all aspects were functional before it left the shop. I tend to believe them as they have been extremely helpful to date.

I've checked all the connections round the back of the CCC unit - everything looks fine. So my question is where do I go next? Where does the iDrive controller get its power from? I can't find anything in the fuse diagrams; and it kinda feels like it's not only the controller that is suffering as the 'menu' and 'voice' buttons behind the knob also don't work and they are not part of the controller unit.

I wouldn't know where to start with diagnosing this. I don't think that the controller is at fault and am certainly not going to spend over £400 on a new one unless I know 100% it's faulty. Any tips, or things I can check?

My gut feeling is that this is power related - hence my question about where the controller power comes from.

Thanks in advance,

TD.
 
#2 ·
A46 in the rear fuse panel supplies the power to the controller. If they possibly sent you a different CCC from another car, you might need to have it programmed to the car? It would be hard to say without using ISTA to run the diagnostics to what the problem might be?
 
#3 ·
Hi Herb.

I'm assuming you meant A64 as I can't see a no. 46 on the fuse diagram. I'd already checked 64 - that seems to control power to the main part of the CCC unit. The fuse is fine though. I've checked all relevant fuses (from what I can see on the fuse diagram) and they all seem fine.

I ran ista, and ran the MOST bus diagnostics. No problems detected there. I've also tried taking the CD changer and my bluetooth kit out of the MOST loop using an optical fibre loop. Again, no change. But I don't think that the controller knob is part of the MOST loop.

CCC unit is definitely from my car. No coding required. All functions with the exception of the controller knob and the two buttons behind it are working fine. My uninformed guess is that there seems to be a breakdown in comms/power to the controller knob - but I have no idea how to test for this :(
 
#4 ·
If you are using ISTA, go into the module on the control tree, & test the components inside of the module. This possibly sounds like a loose wire somewhere, or ISTA should pop up the fault. If you use the text search under vehicle management, you can see the wiring diagrams starting with SSP. Type CCC & you will see the wiring schematic.
 
#5 ·
Hi Herb. So, I used the ista component triggering for the CON module earlier. All triggers worked fine - rotate (left/right), button press, button slide (up, down, left, right); and also the menu and voice command button presses all register correctly. The motor tests also work (controller spins itself left/right) - so that rules out any power-related issues. ...but still nothing registeriing with the CCC unit itself.

As you suggested, I found the circuit diagram for the SSP "K-CAN-system bus" and I can see the controller and the CCC unit on there - unfortunately I haven't the faintest idea what the symbols/numbers actually mean so I'm fast reaching the point where I'll need to take it to an expert :(

Thinking about it logically though: The cables at the controller end were never touched during the removal of the CCC unit; so it's far more likely that there is a cable issue at the CCC end (maybe going into the quadlock connector) or perhaps with the CCC unit itself (although I think the latter is less likely). Would you agree with that logic?
 
#6 ·
I would suspect a cable problem would probably be the problem, but ISTA should reveal the problem. Mulchman updated his CCC to a CIC recently, so he might have a better clue to what might be the problem. There are a lot of DIY's on the net with the CCC & CIC, so there should be some help there. Roseng is our IDrive specialist, as he has done quite a few. What symbols are you referring to that might not be understood? It is also possible that the wiring schematic in ISTA might not be the correct one, & the search might need to be more specific. If you have INPA loaded, run the info on the link below, just to make sure your vin number is correct on the CCC.

 
#7 ·
Hi Herb. Apologies for the delay - been away on a few days holiday.

VIN numbers are correct for all modules (had already checked that). I'm waiting for a spell of decent weather now so that I can take out the center console (handbrake surround etc) and get a proper look at the wiring. I might ping Roseng to see if he has any ideas, or areas to check.

I'll report back any findings/solutions.
 
#8 ·
SOLUTION FOUND! Happy Days!

Thanks to the ever-present HerbP and roseng.

The issue was that whilst my CCC unit was being repaired they had upgraded the firmware of all of the CCC modules (CC6260, CC3F60, CC4760, CC6360 & CCA060) to the latest firmware revision. The problem is that the latest revision of the Gateway module (CC6260) had been updated to a revision that didn't work with my old-skool i-Drive controller - as roseng pointed out to me, there are more than one type of i-drive controller.

So, for anyone who has the same issue - the steps to fix are:-

  • Open Winkfp
  • Choose 'comfort mode'
  • Choose 'Choose ZUSB' (Not 'Update ZUSB' - you need to select a particular revision!)
  • In 'ECU Family' select "CC6260' (which, I believe, is the CCC gateway module)
  • In 'ZB-Number' select revision 9185627 (the most recent revision - 9185636 - is likely what is causing your issue)
  • Click 'Enter VIN' and put in the last part of your VIN code (for me this was a letter 'B' followed by 6 numbers. You can get this from the 'User Information Field' information in INPA)
  • Click 'Done'
  • Click 'Program'

NOTE: Just in case you need to update any of the other CCC modules afterwards, my understanding is that the CCC modules must be upgraded in the order that I listed them above - so starting with CC8260 and ending with CCA060). All of my other CCC modules are upgraded to the latest firmware revision and work fine. It's only CC6260 that you need to be aware of.

I sincerely hope that this helps someone else who's had CCC modules upgraded past the hardware capabilities of their car.
 
#12 ·
hello to all.i have a similar problem, somehow.
i have e61 touring 2005.
it had ccc with nagi, big screen, which died(famous restart loop and black screen and so on)
i have now m ask and small screen.
my problems are:
1.idrive controller does not behave as it shoult. it spins relatively freely, not much resistance( when i had ccc it had resistance and it stopped rotating when you cannnot scroll anymore)
i have full funcionality in climate basic control - and in obc menu,but otherwise it does not work as expected.
when it is in idrive menu, the one that opens when you start the car, i can rotate the knob. i do not know if this is normal.
2.sound is not the same with mask - had vo and fa 640 and 677 written in the car, and i have 2 subwoofers under the seats.i have some crackle,and the right side is not as loud as the left side.
3. i have mask module and most gw with different numbers, i suspect different vin in modules.i have tried to code them with winkfp but i failed big time, i cannot find mostgw - sgbd mcgw60 and zb 6983847 , and also mmi/ccc with zb 6983833.
i have succesfully coded zbe with my own car's vin, with winkfp - i forgot to take out the key and the car had thrown all kinds of christmas tree errors on the dash, my cid restartet, but otherwise good.i have checked in inpa and now zbe module is with the same vin as the rest of them, except mostgw with addr 62, and mmi/ccc with addr 63.
4.i had a mulf module, which i think died, and i coded that out from vo order, i deleted 640 from vo order, and disconnected the connector and applied most bypass.

any help is greatly appreciated.
thanks in advance.
 
#18 ·
I checked my settings they are the same. I’m trying to follow this post. https://www.bimmerfest.com/threads/idrive-controller-not-working-solution-found.1415612/ But cannot get the ECU: CC6260 ZUSB: 9185627 I only see: 9185571 Any suggestions. The issue was that whilst my CCC unit was being repaired they had upgraded the firmware of all of the CCC modules (CC6260, CC3F60, CC4760, CC6360 & CCA060) to the latest firmware revision. The problem is that the latest revision of the Gateway module (CC6260) had been updated to a revision that didn't work with my old-skool i-Drive controller - as roseng pointed out to me, there are more than one type of i-drive controller. So, for anyone who has the same issue - the steps to fix are:-
  • Open Winkfp
  • Choose 'comfort mode'
  • Choose 'Choose ZUSB' (Not 'Update ZUSB' - you need to select a particular revision!)
  • In 'ECU Family' select "CC6260' (which, I believe, is the CCC gateway module)
  • In 'ZB-Number' select revision 9185627 (the most recent revision - 9185636 - is likely what is causing your issue)
  • Click 'Enter VIN' and put in the last part of your VIN code (for me this was a letter 'B' followed by 6 numbers. You can get this from the 'User Information Field' information in INPA)
  • Click 'Done'
  • Click 'Program'
NOTE: Just in case you need to update any of the other CCC modules afterwards, my understanding is that the CCC modules must be upgraded in the order that I listed them above - so starting with CC8260 and ending with CCA060). All of my other CCC modules are upgraded to the latest firmware revision and work fine. It's only CC6260 that you need to be aware of.
 
#19 ·
Does your IDrive have 2 buttons, or 6 buttons on it? The newer controller usually comes with a CIC, but not always. I know the programming order for the CIC programming, but not the CCC. I would try with what you have above. The CIC requires an ICOM with the ICOM B fiber connecter, I would think the CCC requires the same for programming? You could try to code all of the modules on the CCC, & IDrive controller itself, to a default programming mode. Anytime a module is programmed, the same module will need coding with NCSExpert.
 
Status
Not open for further replies.
You have insufficient privileges to reply here.