You will need to flash FEM to write car VIN to it, and then I believe there is an alignment procedure in ISTA to align FEM to car DME.

 

How to flash FEM with car VIN ? With E-sys ?

Alignment procedure is in ISTA/P or ISTA/D ? Is alignment procedure is possible with ICOM emulator ?
Where to find this procedure in ISTA ?

Is the car configuration stored in DME ?

 

See here regarding Flashing FEM:

http://www.bimmerfest.com/forums/showthread.php?p=8737326#post8737326

The alignment procedure is in ISTA/P, "EWS/DDE calibration" tab, and it synchronizes EWS and DME control modules. So, maybe it is needed only if DME is replaced, and not if FEM (CAS) is replaced.

Configuration is not stored in DME. It is in ZGW and FEM (CAS).

 

Shawn thanks for the info.

So I need to flash FEM by this guide from link You provided.
I have few more questions.
1. if FEM is dependand from other module do I need to flash all of dependand modules ?
2. in step 3 "Connection via Gateway URL". This is important ? My new FEM has different VIN from my car so if during flashing procedure VIN in FEM changes this may interrupt rest of process.
3. in step 5 "Read and save FA". When I read FA I get only 12 modules (probably from car donor of the FEM module). My original FEM after read FA shows 21 modules. Is it important, or this correct number of modules will appear after flashing procedure ?
4. in step 8 "Create an SVT Target:". How to choose I-step target ? Is it possible to flash with I-step target with the same value like I-step shipment ? Or is this depends from pszdata version ?
5. in step 13 I read VIN from FA or insert VIN by myself ?

One general question.
Where is stored information about car keys ?
When I installed used FEM in the car my key won't work. The car shows that key is not in the car. So the car won't start.

 

1. I would flash all other ECU's with Dependency as well.
2. I would flash with Connection via VIN.
3. Try Read ECU instead of Read SVT. It is important they all show else you may not be able to flash ones with dependency.
4. I-Step target is not selectable, as it is fixed based on yoru current PSdZData version.
5. Read VIN from FA.

Key information is stored in FEM (CAS).

 

1. I would flash all other ECU's with Dependency as well.

OK.

2. I would flash with Connection via VIN.

Is it correct, even when during flashing FEM the VIN will change ?

3. Try Read ECU instead of Read SVT. It is important they all show else you may not be able to flash ones with dependency.

Ok, so unless all modules shows up I don't go further with flashing ?

4. I-Step target is not selectable, as it is fixed based on yoru current PSdZData version.

For flashing should I use latest available version of PSdZData ?

5. Read VIN from FA.

What if this will give me VIN from car donor of FEM module ?

Key information is stored in FEM (CAS).

After FEM replacement do I need to add my key to new FEM?
How to do it ?

 

Shawn thanks for all the info.
Will try to flash FEM in couple of days.

 

Ok. Good luck with it.

 

FEM and DME are EWS4 - so both have a VIN specific code. There is no alignment as in the earlier EWS systems. The used FEM will not work using these methods. There is also a risk to the DME with an incorrectly coded FEM.

 

So this method will not work with used FEM ?

How to code used FEM ?

 

I have read both, that Immobilizer (EWS4) is an issue for FEM, and that it is not. For sure it is an issue for DME replacement. I don't think attempting to flash FEM would do anything to DME. Worst case is FEM takes VIN, and still won't sync / decrypt key with DME.

 

I still have the actual FEM from my car.
Is after flashing the "used FEM" I will be still able to use the original FEM from my car ?

With FEM from my car is something wrong, I can't open the car with key fob, dash button and CA. Thats why I need new FEM. I already checked all fuses and wiring. So the failure of FEM modul is only explanation.

Is this procedure with replacement FEM will be easier with new empty FEM ?

 

If the method with flashing used FEM will not work, it will be possible to get back to original FEM from my car ?

I still have this original FEM.

 

If the method with flashing used FEM will not work, it will be possible to get back to original FEM from my car ?

I still have this original FEM.

Flashing used FEM will have no affect on your original one.

 

This two options in E-sys should be enabled only when I want to write VIN to module ?

What charger is good for flashing to avoid interruption during process ?

 

This two options in E-sys should be enabled only when I want to write VIN to module ?
View attachment 489259

What charger is good for flashing to avoid interruption during process ?

No, these have nothing to do with writing VIN to module. VIN is written to module during flash, either taken from FA or manually specified on the TAL screen.

Use any charger good for 50 amp minimum.

 

I have never replaced FEM but on other modules VIN changes according to FA when you just code the module. You can check the VIN by reading coding data from a module, it is shown in SVT-tree after reading.

 

how much time takes flashing module process ?

 

It depends on the module. I have no idea on FEM. My guess will be around 20 - 30 minutes.

 

I would say that FEM takes maybe ten minutes, but I have not flashed it separately. NBT takes 25 minutes, and it has much more data (though it has ethernet, but so does FEM).

 

Iv'e seen CIC take 45 minutes, which is why I guessed 30 minutes for FEM given its size. Time depends too on how old the current firmware is relative to the new firmware, and how many firmware files actually need updating.

 

FEM is usually the last module to be flashed. GW gets flashed first and then then rest, then last one is FEM.

The multiple times I have flashed it, has taken me about 5-10 Min. MAX. Mine is a F30, not sure about the other models

 

during flashing car engine should be running ?

 

No, it should not be running. You need power supply with 13-15 volts and 50 amps. Other option is to use another car with engine running and jump start cables.

 

what if during flashing proces ignition will switch off ?
what damages to the car this may do?

 

It won't turn off after the flashing has started.

 

I was trying update FEM, but ended with this error:
TAL execution started.
VCM Update: VCM-Update is deactivated. VCM will not be updated. [C197]
[Exception - UNKNOWN] FA must not be null when trying to execute a TAL containing coding transactions
Fatal error while executing tal!
Asynchrone programming failed! [C049]
FA must not be null when trying to execute a TAL containing coding transactions [1358]

In E-sys settings I have unchecked this "Update VCM after TAL execution".

 

At top of TAL Processing screen, did you hit the Read FA button before executing TAL?

 

Yes. I hit "Read FA"
In the near field shows up filename: FA_aus_VCM.xml.

In the ECU list there are two ECU with text FEM (FEM_BODY, FEM_GW).
What the difference between them ?

 

That is normal. FEM_GW is the part that is Central Gateway module, and FEM_BODY is the rest of FEM (FRM, CAS and JBE).

 

VCM is located in FEM, so you must first go to VCM-module in esys expert mode, and copy VCM backup from backup to master.

 

How to do it, step by step ?

And when, just before flashing ? or later ?

 

I have never done it but I suppose you just select restore data. If it doesn't work, then do: read data (backup), maybe restore data, write data (master). There is a "help" function in esys

 

need more help.

after installation of new fem in car I cant flash it.
errors in E-sys:

I need assistance by teamviewer.

i tryed to code FEM_BODY but it resulted with error:

Caf's suchen
Tal wird generiert
Abarbeitung wird gestartet

TAL execution started.
VCM Update: VCM-Update is deactivated. VCM will not be updated. [C197]
ExecutionID=2015/02/14-16:34:49.824
[] prepareTALExecution started
MCDDiagService<id=410649, job=com.bmw.psdz.jobs.common.MCD3_PrepareTALExecution, service=RC_STEUERN_RESET_ACT_LINE - RoutineControl SteuernResetActivationline, description=error: negative response : requestOutOfRange, link=FEM_GW_10_ETHERNET>
MCDDiagService<id=410600, job=com.bmw.psdz.jobs.common.MCD3_PrepareTALExecution, service=RC_STEUERN_RESET_ACT_LINE, description=error: negative response, link=#RtGen_MultipleEcuJob_LogicalLink>
MCDDiagService<id=36900, job=com.bmw.psdz.jobs.common.MCD3_PrepareTALExecution, service=RDBI_ADS - ReadDataByIdentifier ActiveDiagnosticSession, description=error: timeout, link=Physical request to ECU with address 0x78>
MCDDiagService<id=36900, job=com.bmw.psdz.jobs.common.MCD3_PrepareTALExecution, service=RDBI_ADS - ReadDataByIdentifier ActiveDiagnosticSession, description=error: timeout, link=Physical request to ECU with address 0x78>
MCDDiagService<id=36900, job=com.bmw.psdz.jobs.common.MCD3_PrepareTALExecution, service=RDBI_ADS - ReadDataByIdentifier ActiveDiagnosticSession, description=error: timeout, link=Physical request to ECU with address 0x78>
[] prepareTALExecution finished
[] prepareVehicleForCoding started
[] prepareVehicleForCoding finished
[FEM_BODY - 40] prepareECUforCoding started
[FEM_BODY - 40] prepareECUforCoding error
[FEM_BODY - 40] There was an error during TAL execution, please check the log files.
[FEM_BODY - 40] finalizeECUCoding started
[Exception - FEM_BODY - 40] SVK-Ist does not match expected SGBMIDs for ecu ECUId:FEM_BODY_0x40. Excpected: [hwel_00000792-000_004_008, hwap_00000f26-255_255_255, hwap_00000f29-255_255_255, hwap_00000f2b-255_255_255, hwap_00000f2c-255_255_255, hwap_00000f2d-255_255_255, hwap_00000f2e-255_255_255, hwap_00000f30-255_255_255, hwap_00000f32-255_255_255, hwap_00001263-255_255_255, btld_00001556-003_101_010, swfl_0000155e-004_102_040, swfl_0000155f-000_003_029], Actual: [hwel_00000792-000_004_010, hwap_00000f26-255_255_255, hwap_00000f28-255_255_255, hwap_00000f29-255_255_255, hwap_00000f2b-255_255_255, hwap_00000f2c-255_255_255, hwap_00000f2d-255_255_255, hwap_00000f2e-255_255_255, hwap_00000f30-255_255_255, hwap_00000f32-255_255_255, hwap_00001263-255_255_255, btld_00001556-003_101_010, swfl_0000155e-004_104_040, swfl_0000155f-000_003_029, cafd_00000794-004_228_010]
[FEM_BODY - 40] finalizeECUCoding finished
[] finalizeVehicleCoding started
[] finalizeVehicleCoding finished
[] finalizeTALExecution started
[] finalizeTALExecution finished
TAL execution finished
TAL-Execution finished with status: "FinishedWithErrorInTransaction". [C207]
TAL execution finished. Duration: "18s". [C206]
Abarbeitung beendet

 

need more help.

after installation of new fem in car I cant flash it.
errors in E-sys:
...
[Exception - FEM_BODY - 40] SVK-Ist does not match expected SGBMIDs for ecu...

This "SVK-Ist does not match expected SGBMIDs for ecu..." means you have chosen an improper I-Step Shipment when you made your SVT Target (SVT_soll). The problem is that this ECU is not original. So it came with a different I-Step Shipment then your car's actual I-Step Shipment, and you have no way of knowing what the right I-Step Shipment is for this ECU.

So, redo flash, but this time after you calculate SVT Target (SVT_soll), check the box that says "HW-IDs from SVTactual" and then Save it.

If it still does not work, the only thing you can do is try different I-Step Shipment dates until hopefully one works. This is simply Trial and Error.