How to Retrofit a Bluetooth TCU to your car

Originally Posted by stuartjohn24

Hi Jeff,

Ahh I see what your getting at!

Yes the car was manufactured in October 2001. The production date of the new MMI is 19/06 WW/YY.

Is the manufacture date an editable option in the FA write menu of NCS expert? I will have a look tonight and see, I hope changing it wont completely mess the car up!

Could there be a safer way? I notice in the daten folder, find the file E65AT, open it with a text editor and near the top the #1001 is shown along with what appear to be other production codes, it appears to reference modules and their coding level index which I presume is what is telling NCS what its expecting to see.

Could an edit here be an option? I dont see any MMI references in the whole file but as you say the MMI is not an option so may not have the parameters in this file.

Although fisters profile allows you to choose which code level file to use it dosent work, could always be an issue with the profile I guess.

I have decoded the VO Paper has posted for reference, but I agree nothing appears to relate directly to the MMI.

#0903
$1CA - Selection of CO2 (Conformity of Production)
$202 - Steptronic, line is needed for PPP's
$216 - Servotronic
$226 - Sports suspension
$229 - Active roll stabilisation
$245 - Electric steering column adjustment
$255 - Sports leather steering wheel
$302 - Alarm: DWA with interior protection and emergency siren
$316 - Automatic Boot Lid
$319 - Integrated universal remote control
$323 - Soft Close Automatic with child protection
$330 - Sport package with sport suspension
$358 - Climate comfort windscreen (IR-coated glass plate)
$403 - Sliding glass sunroof
$415 - Electric rear window sunshade
$416 - 0415 as including electric side window sunshade
$423 - Front and rear velor mats
$430 - Interior and exterior auto dimming mirrors
$431 - Mirror control
$438 - Fine-wood trim Ash Grain dark
$441 - Smoking package
$442 - Front and rear cup holders
$449 -
$466 - Roof bar in body color
$470 - ISO-FIX child seat attachment
$481 - Sports seats
$488 - Electric lumbar support
$502 - Headlight washers
$508 - Park distance control (PDC)
$521 - Rain sensor from 09/05 series for all 6 and 8-cylinder (not for E67)
$522 - Bi-xenon headlights
$524 - Adaptive Light Control
$534 - Automatic air conditioning, "High" + Cooled storage compartment in center console
$541 - Adaptive Cruise Control II
$596 - LM-E65-wheel sport package
$609 - Navigation system without TV, new production use in conjunction with LA802 03/06
$620 - Voice control for navigation, telephone and radio
$645 - Radio control U.S.
$672 - Audio-CD changer for 6 CDs and MP3 from MT
$677 - HIFI system professional (Logic 7)
$691 - CD Mount
$693 - Preparing For U.S. satellite tuner types (GL63, GN63, GN83) from 09
$760 - Individual high-gloss Shadow Line
$785 - Individual "white flashing lights"
$845 - Audible seatbelt warning
$850 - Additional Export tank filling
$853 - English language
$925 - Shipping Protection Package
$992 - Control plate mounting
%0472
&V7SW
*GN63
-LEDE

I couldnt find $449, I may be translating from an old file....

Stuart

Stuart, I haven't had a chance to try what I'm suggesting. I don't see how temporarily removing and adding a new production date for the purpose of coding our MMI would cause any damage, but check around to see if anyone has had issues doing so.

I don't think you can edit that file directly but I may be wrong. I feel strongly at this point that this is our next course of action. Hopefully one of us will be brave and try this to see if it moves us ahead.

Read this PDF for editing VO using NCS expert: http://www.m5board.com/vbulletin/att...ng-20ncs-1.pdf

If you look at step 12 you will see the production date #0905 at the top of the list. I believe you need to highlight that line (in your case it would be #1001) and hit the delete button. Not sure if you should add the new VO first or after the removal. But this is where our next test needs to take place.

Jeff

Have you guys tried putting your old MMI in & reading it with NCS ?
I would try that before trying to edit the production date of your car .

Sent from my GT-I9100 using Bimmer App

Originally Posted by PAPER

Have you guys tried putting your old MMI in & reading it with NCS ?
I would try that before trying to edit the production date of your car .

Sent from my GT-I9100 using Bimmer App

Paper, I had no issues coding my old MMI. Never got an error trying to read the MMI ECU. I also still have a backup of the trace file from my old MMI.

Since the coding index of the old MMI was 02 and the new MMI has a coding index of 04, I assume this has to at least be part of the problem. I didn't write it to the CAS or LMA, but I was able to remove my production VO (#0503), but when I tried to add (#0906) I got an error (forgot what the error message said). When I kept my VO production AND also tried to add the #0906 to the VO, I got an error saying that $216 wasn't valid for my VO. Again since I never coded the newer production VO (#0906) I don't know if I would have been able to read the MMI ECU. I pulled back to get more info.

Might have to hook my MMI up to a 750 code my options and preferences and then re-install it in my car. At least then I would have my Navigation and iPod list showing up rather than CD 1 through CD 6.

Anyone else making headway?

Jeff

Hi guys,

Just tried changing the date in the VO....

BIG MISTAKE!

The CAS was happy but the LM has thrown its toys out, it has now gone into failsafe and I only get headlights, no other lights work! the lights come on automatically with the ignition.

I have tried writing the original FA code back but its not having it, error is:

COAPI-2060: coding faulty
LM_60,FA_AUFTRAG: ERROR_ECU_SUBFUNCTION_NOT_SUPPORTED_INVALID_FORMAT

when taking backups from the car it was LM_E65.C06, it now thinks its a .C05 I guess thats the problem, when trying to code the unit i get:

COAPI-2041: wrong ecu coding index
A_E65LM: CODIERINDEX = FFh

Im annoyed this looks to have bricked the LM module, trying to read information from it using tool32 throws errors.

Does anybody have any ideas how to get myself out of this mess? I would be most greatful!

Originally Posted by stuartjohn24

Hi guys,

Just tried changing the date in the VO....

BIG MISTAKE!

The CAS was happy but the LM has thrown its toys out, it has now gone into failsafe and I only get headlights, no other lights work! the lights come on automatically with the ignition.

I have tried writing the original FA code back but its not having it, error is:

COAPI-2060: coding faulty
LM_60,FA_AUFTRAG: ERROR_ECU_SUBFUNCTION_NOT_SUPPORTED_INVALID_FORMAT

when taking backups from the car it was LM_E65.C06, it now thinks its a .C05 I guess thats the problem, when trying to code the unit i get:

COAPI-2041: wrong ecu coding index
A_E65LM: CODIERINDEX = FFh

Im annoyed this looks to have bricked the LM module, trying to read information from it using tool32 throws errors.

Does anybody have any ideas how to get myself out of this mess? I would be most greatful!

Did you change the VO in your CAS & LMA ?
If you only did the CAS then that's why your getting the LMA error

Sent from my GT-I9100 using Bimmer App

Hi Paper,

Yes the CAS took the new FA/VO number but when i went to program it to the LMA it gave that error and I now cannot write or read the FA number, I cant read the coding file either.

Tool32 does talk to the unit and it gets the information etc... but actually trying to get values back like the VIN, FA etc... all return errors.

I will try and re-flash the unit using WinKFP and try and treat it as a new unit and hope that works.

All I done was change the 1001 code to 0903 to see if that worked.

When i try coding it back to 1001 it wont code it.

This is turning into a nightmare!

Originally Posted by stuartjohn24

Hi Paper,

Yes the CAS took the new FA/VO number but when i went to program it to the LMA it gave that error and I now cannot write or read the FA number, I cant read the coding file either.

Tool32 does talk to the unit and it gets the information etc... but actually trying to get values back like the VIN, FA etc... all return errors.

I will try and re-flash the unit using WinKFP and try and treat it as a new unit and hope that works.

All I done was change the 1001 code to 0903 to see if that worked.

When i try coding it back to 1001 it wont code it.

This is turning into a nightmare!

Stuart, I'm really sorry that I suggested the production date change. I wish I had a quick fix for the crapstorm this has unleashed. I hope that you're able to get this resolved quickly.

Jeff

Hi Jeff,

No worries! I can see where it was progressing and I convinced myself this is the correct way to go, on the E90 forum they also change the production date in the VO to retrofit the CIC kits.

I did read the LMA unit can be sensitive, I followed instructions in a pdf, guess i was unlucky! I will have a go tomorrow and try to code the unit using WinFKP hopefully I can revive it, otherwise its looking like an excuse to do an LM2 retrofit so I can enable welcome lights!

Will keep you lot posted, looks like it may be easier to program this MMI in another car! what a pain!

I still think the production date change in the VO is the correct route, i was just unlucky!

One thing i was going to ask, is dashsoft able to code the MMI when its in this situation?

Cheers!

Originally Posted by stuartjohn24

Hi Paper,

Yes the CAS took the new FA/VO number but when i went to program it to the LMA it gave that error and I now cannot write or read the FA number, I cant read the coding file either.

Tool32 does talk to the unit and it gets the information etc... but actually trying to get values back like the VIN, FA etc... all return errors.

I will try and re-flash the unit using WinKFP and try and treat it as a new unit and hope that works.

All I done was change the 1001 code to 0903 to see if that worked.

When i try coding it back to 1001 it wont code it.

This is turning into a nightmare!

try using the expert profile , it should set everything back to
how it was before .

Any news on our issue? Would love to hear from someone who has successfully used NCS Expert to code a facelift MMI.

Stuart, Did Paper's suggestion get you back to where you were before trying to update the production date?

Jeff

Hi Jeff and Paper,

no, I had already tried the expert profile, that's what I used in the first place. INPA will not communicate with the module either it's looking like its dead.

To re-cap I cannot update the FA using any profiles, I cannot read or code the LMA. Tool32 and INPA are unable to communicate.

The only thing left is WinFKP, I am having trouble setting this up, I haven't allowed enough space on my virtual machine (as I'm coding the car using my MacBook) so will do a fresh xp install later tonight when the kids are in bed and start from scratch.

Jeff I have seen on other forums that you can fool NCS into thinking you have a different production date. Go and read the FA from the CAS like normal, click enter FA and change the hash bit with the date click ok but DON'T CODE IT TO THE CAS! you will notice now in NCS under FA that the code has changed. Try reading the MMI again now. It might work.

However I have noticed my LMA is throwing an error about the coding index is wrong I would guess the MMI would be doing this of it was the case?

Let me know how you get on! Remember don't actually code it, or you may end up like me!

Stuart

Originally Posted by stuartjohn24

Hi Jeff and Paper,

no, I had already tried the expert profile, that's what I used in the first place. INPA will not communicate with the module either it's looking like its dead.

To re-cap I cannot update the FA using any profiles, I cannot read or code the LMA. Tool32 and INPA are unable to communicate.

The only thing left is WinFKP, I am having trouble setting this up, I haven't allowed enough space on my virtual machine (as I'm coding the car using my MacBook) so will do a fresh xp install later tonight when the kids are in bed and start from scratch.

Jeff I have seen on other forums that you can fool NCS into thinking you have a different production date. Go and read the FA from the CAS like normal, click enter FA and change the hash bit with the date click ok but DON'T CODE IT TO THE CAS! you will notice now in NCS under FA that the code has changed. Try reading the MMI again now. It might work.

However I have noticed my LMA is throwing an error about the coding index is wrong I would guess the MMI would be doing this of it was the case?

Let me know how you get on! Remember don't actually code it, or you may end up like me!

Stuart

Stuart, Thanks for the tip. I will try it late tonight or tomorrow. I definitely won't write anything to the CAS or LMA.

Originally Posted by stuartjohn24

Hi Jeff and Paper,

no, I had already tried the expert profile, that's what I used in the first place. INPA will not communicate with the module either it's looking like its dead.

To re-cap I cannot update the FA using any profiles, I cannot read or code the LMA. Tool32 and INPA are unable to communicate.

The only thing left is WinFKP, I am having trouble setting this up, I haven't allowed enough space on my virtual machine (as I'm coding the car using my MacBook) so will do a fresh xp install later tonight when the kids are in bed and start from scratch.

Jeff I have seen on other forums that you can fool NCS into thinking you have a different production date. Go and read the FA from the CAS like normal, click enter FA and change the hash bit with the date click ok but DON'T CODE IT TO THE CAS! you will notice now in NCS under FA that the code has changed. Try reading the MMI again now. It might work.

However I have noticed my LMA is throwing an error about the coding index is wrong I would guess the MMI would be doing this of it was the case?

Let me know how you get on! Remember don't actually code it, or you may end up like me!

Stuart

on what other forums ? Do you happen to have a link ?

sorry to see your still having trouble . I did a little research
But didn't find much on your problem with the LMA beside
people saying to work with the VO to get it back .
I will keep looking for you .

Originally Posted by stuartjohn24

Hi Jeff and Paper,

no, I had already tried the expert profile, that's what I used in the first place. INPA will not communicate with the module either it's looking like its dead.

To re-cap I cannot update the FA using any profiles, I cannot read or code the LMA. Tool32 and INPA are unable to communicate.

The only thing left is WinFKP, I am having trouble setting this up, I haven't allowed enough space on my virtual machine (as I'm coding the car using my MacBook) so will do a fresh xp install later tonight when the kids are in bed and start from scratch.

Jeff I have seen on other forums that you can fool NCS into thinking you have a different production date. Go and read the FA from the CAS like normal, click enter FA and change the hash bit with the date click ok but DON'T CODE IT TO THE CAS! you will notice now in NCS under FA that the code has changed. Try reading the MMI again now. It might work.

However I have noticed my LMA is throwing an error about the coding index is wrong I would guess the MMI would be doing this of it was the case?

Let me know how you get on! Remember don't actually code it, or you may end up like me!

Stuart

ok found something interesting , it is said our car will
not take any production date over 2004 . I was told
to have you try this .




READ IN EXPERTMODE ( VERY IMPORTANT )
1) delete the entry starting with a # (eg # 0101)
(Del key on the keyboard)

2) Add a new entry: # 0904 ( DO NOT WRITE TO CAR )
After you changed the FA you click on the "back" button so that it takes the changes

# Xxxx is the way the production date. There are perhaps other
values ***8203;***8203;as # 0904 but with this it worked in my VFL. So take that!
When I was # 0101 in, although my car is from 01/2002, so it
can be that there are only certain values, where there has been
a "restructuring" of the control devices. Maybe start with the
program as # 1004 # 0904 instead of nothing.

Hi Paper,

Thanks for looking, I haven't found much on sorting the LMA out, only retrofits in the E60 etc...

If you look in the folder DATEN\ and find file E65AT.000 make a copy and open it with notepad or something, in the top third of the file is what look like the production dates #1001, etc

I think if you choose one from this list you should be ok. You will also see lists of files for each date. This looks to be the .C0x coding levels it's expecting to see for that particular production date.

My guess is the LMA module has been replaced in the past and I'm now using the wrong files.

I will dig out the link but there is a reference to it here:

Using latest tips from 4711, I "simulated" change of ZK from #0606 (which my E91 has) to #0307 in NCS-EXPERT. In the ECU-list FRM then changed to NFRM and I was able to do proper coding.

This is where a newer FRM module was upgraded on an E90.

Have you tried coding the MMI with the edited production date?

Originally Posted by PAPER

ok found something interesting , it is said our car will
not take any production date over 2004 . I was told
to have you try this .




READ IN EXPERTMODE ( VERY IMPORTANT )
1) delete the entry starting with a # (eg # 0101)
(Del key on the keyboard)

2) Add a new entry: # 0904 ( DO NOT WRITE TO CAR )
After you changed the FA you click on the "back" button so that it takes the changes

# Xxxx is the way the production date. There are perhaps other
values ***8203;***8203;as # 0904 but with this it worked in my VFL. So take that!
When I was # 0101 in, although my car is from 01/2002, so it
can be that there are only certain values, where there has been
a "restructuring" of the control devices. Maybe start with the
program as # 1004 # 0904 instead of nothing.

Paper, I don't understand how if I change the production date to #0904 and my facelift MMI is built in 2006 I would be in any better shape than with the #0503 (5/28/2003) that my car was actually manufactured? Any of the facelift MMI's we are using will have a production date of 3/2005 or later so this applies to all of us.

Jeff

Originally Posted by stuartjohn24

Hi Paper,

Thanks for looking, I haven't found much on sorting the LMA out, only retrofits in the E60 etc...

If you look in the folder DATEN\ and find file E65AT.000 make a copy and open it with notepad or something, in the top third of the file is what look like the production dates #1001, etc

I think if you choose one from this list you should be ok. You will also see lists of files for each date. This looks to be the .C0x coding levels it's expecting to see for that particular production date.

My guess is the LMA module has been replaced in the past and I'm now using the wrong files.

I will dig out the link but there is a reference to it here:

Using latest tips from 4711, I "simulated" change of ZK from #0606 (which my E91 has) to #0307 in NCS-EXPERT. In the ECU-list FRM then changed to NFRM and I was able to do proper coding.

This is where a newer FRM module was upgraded on an E90.

Have you tried coding the MMI with the edited production date?

Stuart, I haven't tried editing the production date as of yet. I'm still unsure about changing the production date unless I get more information about what dates are valid. I don't want to put in any date that is earlier than the actual production date of my facelift MMI or at the very least later than 3/2005 (That's when they first started with the facelift MMI's). I forgot to ask, but why did you use the date of #0903 when you coded the CAS and LMA?

Originally Posted by JML6278

Paper, I don't understand how if I change the production date to #0904 and my facelift MMI is built in 2006 I would be in any better shape than with the #0503 (5/28/2003) that my car was actually manufactured? Any of the facelift MMI's we are using will have a production date of 3/2005 or later so this applies to all of us.

Jeff

I can confirm it works, you have to play with the month & use 04 as the year.

Sent from my GT-N7000 using Bimmer App

Originally Posted by stuartjohn24

Hi Paper,

Thanks for looking, I haven't found much on sorting the LMA out, only retrofits in the E60 etc...

If you look in the folder DATEN\ and find file E65AT.000 make a copy and open it with notepad or something, in the top third of the file is what look like the production dates #1001, etc

I think if you choose one from this list you should be ok. You will also see lists of files for each date. This looks to be the .C0x coding levels it's expecting to see for that particular production date.

My guess is the LMA module has been replaced in the past and I'm now using the wrong files.

I will dig out the link but there is a reference to it here:

Using latest tips from 4711, I "simulated" change of ZK from #0606 (which my E91 has) to #0307 in NCS-EXPERT. In the ECU-list FRM then changed to NFRM and I was able to do proper coding.

This is where a newer FRM module was upgraded on an E90.

Have you tried coding the MMI with the edited production date?

Its 4:39 am here I have been sitting in my car for hours toying with this. Call me & Will fix your car. I Will pm you my # right now

Sent from my GT-N7000 using Bimmer App

Ok I'm going to bed! !!

Sent from my GT-N7000 using Bimmer App

Just want to say that the willingness to help each other out everyone is showing here is impressing the h*ll out of me!

I'll probably be needing to call someone when I have swapped TCUs and coding bricked the engine

Originally Posted by PAPER

Its 4:39 am here I have been sitting in my car for hours toying with this. Call me & Will fix your car. I Will pm you my # right now

Sent from my GT-N7000 using Bimmer App

Paper, Have you been able to code the new MMI? Not sure if you went to sleep, so I didn't want to call if you did.

Thanks,

Jeff

Originally Posted by jml6278

paper, have you been able to code the new mmi? Not sure if you went to sleep, so i didn't want to call if you did.

Thanks,

jeff

YES I HAVE
call me now

Hey guys! I hear you have solved it!? What production date did you use??

Originally Posted by stuartjohn24

hey guys! I hear you have solved it!? What production date did you use??

03 / 04 ( #0304 )