(Apologies to the mods as I've also posted this in ICE forum as it falls into both categories.)
Could really do with some advice from those in the know about the BMW coding procedures.
I retrofitted the OEM handsfree kit in my car
Harness, bluetooth aerial, mic, centre console snap-in, and MULF2 (Low Basis). Followed the BMW instructions to the letter and researched this for months before even ordering the kit.
Booked my baby into my local BMW dealership to get coded. Dropped her of this morning at 8:15, collected my courtesy car and went about my day.
Got a call at 11:15 from the service department accusing me of having no bluetooth equipment in the car and insisting they had checked the part number of the kit I had bought from them a month ago. This, they were admant, was just the "part that goes under your armrest" .
After a lengthy 'black is white' type argument, and having been advised that the coding guy had "removed my radio and couldn't find the cable he expected to see" I insisted on talking to the guy myself. Eventually after checking the parts list for the kit I bought he realised this was different to what he was used to coding, apologised and went back to the car.
4 hours later I got a call from the uppity receptionist cheerfully telling me the car was coded and ready to collect so I pulled up at the dealer, paid the bill and collected my car. Turned her on, hit the menu button on the radio. No Bluetooth option.
Back into the service department, then! Confused receptionist gets the coding wizard back on the phone, at which point he advises her there was an fault but the car had been coded. Again I insisted on speaking to the bloke in person. He graciously came out to meet me and explained, as best he could, what had happened. It became increasingly obvious during the conversation that he had never done one of these before and hadn't bothered to cal BMW for advice.
To cut a long story slightly shorter I was advised of the following points:
The software he was using (I assume this was Progman) identified the new module immediately and began the retrofit. At one point though it spat out a fault message of some sort. He reckoned the coding still 'completed' ok though. The info on the print out I got is below:
System version:2.23.10 Data version: 2.23.1
Fault Description - A fault in the Bluetooth aerial (open circuit) is detected during start-up of the control unit.
Condition of fault identification - System voltage greater than 9 volts. Terminal 15 is on.
Condition of fault memory entry - Control unit start-up.
Action in service -
Check bluetooth aerial (which he didn't do)
Check lines and plug connections between control unit and Bluetooth aerial. (He checked the MULF end only. I checked the areial end tonight.)
Check control unit. (Got the impression he was in over his head at this point.)
The other sheet seems to be a summary of the module's status:
ULF-SBX part number: 9149656
Bluetooth device name:
Bluetooth status: switched off
a) Would the bluetooth areial issue prevent the retrofit being enabled (i.e. availbale as a menu item)
b) The MULF summary sheet above seems to indicate he never actually turned Bluetooth on in the system. Would I be right in thinking this?
c) What is your collective expert opinions on the above?
Points of note:
My gut feeeling was that he didn't have the knowledge or experience to carry this through.
He never identified any issues with the MULF unit but didn't discount it. Basically was very non-commital bordering on intentionally vague.
Module was not brand new and not bought from dealer.
All other kit was bought from dealer.
I fitted all myself in line with the BMW instructions.
Software version on the radio hidden menu still says 2006.
Basically I'm waiting to hear back from the manager as I'm not happy with the level of service. What do you guys think?
I would really, REALLY appreciate your comments / opinions on this