2006 E90 320D - Dealer Coding Hassles

Notices
 

Thread: 2006 E90 320D - Dealer Coding Hassles

Reply to Thread
Results 1 to 9 of 9
  1. 2006 E90 320D - Dealer Coding Hassles 
    #1
    Bimmer Fan
    Car Details
    jack69hoops's Car Details
    Model of Car:
    320d SE
    Year of Manufacture:
    2006
    Transmission Type:
    Manual
    Car Body Type:
    Saloon

    Join Date
    Nov 2010
    Location
    Scotland
    Posts
    15
    Thanks
    3
    Thanked 3 Times in 3 Posts
    Hi folks.

    (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

    Bluetooth device name:
    Bluetooth passkey:
    Bluetooth status: switched off

    So...

    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
     
     

  2. Remove Advertisements
    BimmerForums.co.uk
    Advertisements
     

  3.  
    #2
    Bimmer Fan
    Join Date
    Jul 2008
    Location
    Middlesex
    Posts
    11
    Thanks
    1,817
    Thanked 7,115 Times in 5,338 Posts
    Looks like you went to a dealer not experienced in BT coding. The DIS system has step by step menus for coding and checks each stage. My guess is the programmer started skipping stages.
     
     

  4.  
    #3
    Bimmer Fan
    Car Details
    jack69hoops's Car Details
    Model of Car:
    320d SE
    Year of Manufacture:
    2006
    Transmission Type:
    Manual
    Car Body Type:
    Saloon

    Join Date
    Nov 2010
    Location
    Scotland
    Posts
    15
    Thanks
    3
    Thanked 3 Times in 3 Posts
    Neal, It certainly seemed like they don't have the experience. I had to explain to him how the Bluetooth kit is wired to the car and where the module could be found etc. Didn't fill me with confidence.

    I think 've got my head around the section called Condition for fault indentification. Would I be right in saying it's just a description of the car's electrical status during the procedure;
    'Terminal 15 on' = Ignition on, engine off
    and
    'System voltage greater than 9v' = system voltage normal?

    Really can't figure out the open circuit error for the bluetooth aerial. I think the aerial is just a metal plate inside the plastic cover?
     
     

  5. Remove Advertisements
    BimmerForums.co.uk
    Advertisements
     

  6.  
    #4
    Bimmer Fan
    Car Details
    jack69hoops's Car Details
    Model of Car:
    320d SE
    Year of Manufacture:
    2006
    Transmission Type:
    Manual
    Car Body Type:
    Saloon

    Join Date
    Nov 2010
    Location
    Scotland
    Posts
    15
    Thanks
    3
    Thanked 3 Times in 3 Posts
    Hmmmm, found a silmilar coding error in google, but on a skoda site

    http://briskoda.net/forums/topic/171...e-fault-codes/

    Turns out in his case he was coding it with the wrong option

    Could the tech at my dealer have been using the wrong coding? Is that even possible with their software?
    Last edited by jack69hoops; 26-02-2011 at 14:09.
     
     

  7.  
    #5
    Bimmer Fan
    Join Date
    Jul 2008
    Location
    Middlesex
    Posts
    11
    Thanks
    1,817
    Thanked 7,115 Times in 5,338 Posts
    Maybe you need to find an indy/audio specialist with Autologic, because it is much easier to activate items on there with a straight forward menu.
     
     

  8. The Following User Says Thank You to xXNealXx For This Useful Post:

    jack69hoops (28-02-2011)

  9.  
    #6
    Bimmer Fan
    Car Details
    jack69hoops's Car Details
    Model of Car:
    320d SE
    Year of Manufacture:
    2006
    Transmission Type:
    Manual
    Car Body Type:
    Saloon

    Join Date
    Nov 2010
    Location
    Scotland
    Posts
    15
    Thanks
    3
    Thanked 3 Times in 3 Posts
    Advice taken.

    Car booked in with a BMW Autologic Independent this saturday morning. Guy seemed very confident in doing this and appeared to be familiar with the kit I've fitted. What's more he said "If we can't code it we won't charge you!" What a change from Harry Fairbairn's attitude this morning
     
     

  10. The Following User Says Thank You to jack69hoops For This Useful Post:

    steve23002 (28-02-2011)

  11.  
    #7
    Bimmer Fan
    Car Details
    jack69hoops's Car Details
    Model of Car:
    320d SE
    Year of Manufacture:
    2006
    Transmission Type:
    Manual
    Car Body Type:
    Saloon

    Join Date
    Nov 2010
    Location
    Scotland
    Posts
    15
    Thanks
    3
    Thanked 3 Times in 3 Posts
    Right. Been to see the Autologic guy in Glasgow. Car isn't coded yet but he was great. Actually took me out to the car and talked through everything he was doing, printed out a screenshot showing me the Vehicle Order, which confirms SA644A is not in the V/O (despite waht the Harry Fairbairn coder said) and also showed me that none of the modules have been updated including the MULF, (which he could read from and see status of through Autologic).

    Basically he reckons Harry Fairbairn have done the square root of zilch to my car and charged me for the pleasure. Seemed really peed off at that.

    As it is saturday they do not have Autologic support on hand to provide the updates etc. that he needs to do the job. So he took the details from the car so he can send them the logs and get the software back to do the job. I'm booked back in for next saturday and no charge for today

    Think I might have found my new garage. B4BMW, Clydebank.
     
     

  12. The Following User Says Thank You to jack69hoops For This Useful Post:

    Ronnie (05-03-2011)

  13.  
    #8
    BMW Guru
    Car Details
    Ronnie's Car Details
    Model of Car:
    See above
    Year of Manufacture:
    Never too old, never too new
    Transmission Type:
    Always manual
    Car Body Type:
    Usually 5 doors
    Ronnie's Avatar
    Join Date
    Dec 2007
    Location
    Bournemouth, Dorset.
    Posts
    20,394
    Thanks
    6,198
    Thanked 7,051 Times in 5,322 Posts
    Great result Jack, thanks for the update.
     
     

  14.  
    #9
    Bimmer Fan
    Car Details
    jack69hoops's Car Details
    Model of Car:
    320d SE
    Year of Manufacture:
    2006
    Transmission Type:
    Manual
    Car Body Type:
    Saloon

    Join Date
    Nov 2010
    Location
    Scotland
    Posts
    15
    Thanks
    3
    Thanked 3 Times in 3 Posts
    OK. This week's installment in the saga...

    B4BMW have coded the car for Bluetooth, or at least they have coded all the necessary modules successfully; with the exception of the MULF module itself, which failed with an error code right at the end. They are going to send the logs to Autologic again, but basically I need to try to get the car in with them during the week so they can troubleshoot with Autologic's assistance. Could be a simple coding fix or, as I'm starting to suspect, there may be a problem with part of the ebay module.

    However at least now the Radio has the 'TEL' softkey displayed, albeit I cannot access it, so I'm now at the stage where the car knows it has the option fitted. If there is a problem with the module it should just be a straight swap for another used one and it should work fine.

    Best thing is, despite having spent 3 hours on my car so far, B4BMW have been very attentive, helpful and refuse to take one thin dime for the work until the job is finished.
     
     

  15. The Following User Says Thank You to jack69hoops For This Useful Post:

    Ronnie (14-03-2011)

Tags for this Thread

View Tag Cloud

Posting Permissions
  • You may post new threads
  • You may post replies
  • You may not post attachments
  • You may not edit your posts