BMW Forum - BimmerFest BMW Forums banner

F45/F46/F48/F55/F56 Coding Thread

3 reading
387K views 737 replies 150 participants last post by  Mistaf46  
#1 · (Edited)
Hello,
i propose to open One master threads to regroup the information about the coding of theses car as they have the same architecture .

i already found a coding sheat for mini :

https://docs.google.com/spreadsheets/d/1eO-4KXfxkksCIBP_xKjMXcIwlgAyWVxFLcla5lzibnw/edit#gid=0

and i've already VO code the 6NS option to my car with this procedure !

1) Just Add 6NS to FA and VO Code HU_ENTRYNAV

2) You will not get Voice Control without an FSC Code, but you can still code EBT.

3) No. Just add 6NS to FA, Save FA, Load FA in Coding Module, Activate FA, and VO Code HU_ENTRYNAV.
owners of F45/F46/F48/F55/F56 any stuff we can share, we can do it here.

READ IMPORTANT NOTES:

1) NEVER click "Code Default Values" it can reset important stuff and car might not start and need to get towed to the dealer to fix the software
2) Make sure you click "Code FDL" and not "Code" (clicking code will reset the car to the factory setting erasing all the FDL coding for the selected ECU)
3) Always code with the car running or with a commercial grade charger connected to it, else voltage might drop during coding and you could get unexpected errors. (if you are codding the DME ECU you can't have the car running so you will need a charger)
4) Launcher note: E-Sys Launcher Car Series MUST be set to exactly match the car's chassis type you are coding (e.g. F01, F06, F07, F10, F12, F15, F25, F30, F82, F83, etc.). If after install it defaults to F999 and it cannot be changed, change PC Date ahead 4 days, then change E-Sys Launcher Car Series, then change PC Date back to current date. DO NOT create .EST Token and PIN with PC Date advanced 4 days as the Validity Start Date for the token will be 4 days in the future."

What's Needed for coding?
Enet Cable search on ebay http://www.ebay.com/sch/i.html?_trk...S&_nkw=OBD2+ENET+Ethernet+Cable+for+BMW+F-Series+Coding+ESYS&_sacat=0&_from=R40
E-sys software (ask here http://www.bimmerfest.com/forums/showthread.php?t=638188&page=121)
NEW: Free universal token option http://www.bimmerfest.com/forums/showthread.php?t=805745
NCD CAFD tool http://www.bimmerfest.com/forums/showthread.php?t=749668

Whatever you do never ever ever press "Code Default Values" ... you have been warned :)

Coding 101 video

How to VO code
Connect => Read FA => Activate FA => Read SVT (VCM) => Right-Click on ECU you want to code i.e. HU_NBT (the ECU itself not the underlying CAFD) => Select CODE.

Corrupted CAFD
Just inject new CAFD into ECU, and VO Code it.

Connect => Read FA (VO) => Activate FA (VO) => Read SVT (VCM) => Left-Click on desired ECU => Click on "Detect CAF for SWE" => Select the CAFD from latest I-Level shown => Select OK => Right-Click on ECU (the ECU itself not the underlying CAFD) => Select CODE.

Read I-Level
To determine your I-Level, go to VCM Module => VCM Master Tab => click Read under I-Steps

Targets:
F001 psdzdata covers the F01/F02/F03/F04/F07 (5-Series GT is an F07 NOT an F10)
F010 psdzdata covers the F06/F10/F11/F12/F13/F18
F020 psdzdata covers the F20/F21/F22/F23/F30/F31/F32/F33/F34/F35/F36/F80/F82/F83 (There is no Z4 F-chassis yet)
F025 psdzdata covers the F15/F16/F25/F26/F48/F85/F86
F056 psdzdata covers the F45/F46/F48(BMW)F64/F55 F56 (Cooper Mini's)
I001 psdzdata covers the i3/i8
 

Attachments

#276 ·
Hello, everybody!

My car (mini F-series) have some issue into BMW serves then they updated my cars software. A lot of coding be changed to default.

i was coding my setting almost done. But have one item not work.

GWF_SBR_WARNDAUER ,i tried coding the value its didn't work, the item only "aktiv /Werte=01" "nicht_aktiv /Werte=00" "UNKNOW /Werte=03"

Its can be coding before i updated the software. (GWF_SBR_WARNDAUER=1E)

Any ideal ? thanks.
 
#277 ·
Hello, everybody!

My car (mini F-series) have some issue into BMW serves then they updated my cars software. A lot of coding be changed to default.

i was coding my setting almost done. But have one item not work.

GWF_SBR_WARNDAUER ,i tried coding the value its didn't work, the item only "aktiv /Werte=01" "nicht_aktiv /Werte=00" "UNKNOW /Werte=03"

Its can be coding before i updated the software. (GWF_SBR_WARNDAUER=1E)

Any ideal ? thanks.
 
#278 · (Edited)
Hi guys,

I have a Mini Cooper S F55 from 2015 and retrofitted the oem backup camera on my car. Used the following wiring diagram:

https://www.newtis.info/tisv2/a/en/...t/wiring-functional-info/supply/supply-trsvc-all-round-vision-camera/1VnXhE6RKE

NBT: 21 23 24
Terminal: 9 22 13
Power: Fusebox F55 (tapped from existing pdc)
Ground: Trunk

All wiring from the trunk to the terminal and power except NBT I measured and it all works. I have 14.5v on the camera socket and 9 22 13 short circuited to see if they are connected and all works.

Now I should have ICAM2 visible on my ECU tree in Esys but it does not come. I added 3AG to my VO and coded it to all ECU's by mistake instead of all relevant ecu's. This should not affect anything though. So if i put the car in reverse I can see the camera options now but still have no picture.

Main issue according to the seller is that ICAM2 is not visible on the ECU tree. Should this be visible? Should I code something to make it visible? I think I am doing something wrong with the coding, since the wiring all seems to be fine. Any help is appreciated. Thanks in advance.
 
#279 ·
I seem to have used CAN2 instead of CAN3. But strangly there is no CAN3 connection at the trunk of my car. ETK shows the CAN3 terminal. So that means i need to pull the cables to the bdc in the front and connect it directly. But the seller says we need to use a terminal because of the resistance it provides. Connecting directly will not work he is saying...

Image


So now i need a new can terminal to connect the camera on and this should be connected to the bdc... after that the camera ecu should be visible in ESYS.
 
#281 ·
Jep the seller is going to send me one. If i would buy the same set from the dealer it would cost me around 50 euro.

When it arrives I have to solder/connect the K_CAN3_H (3) and K_CAN_L (16) from the new terminal resistor to bdc A258*8B K_CAN3_H (44) and K_CAN_L (43). 26 from terminal resistor to ground in the trunk. Camera K_CAN3_H (7) and K_CAN_L (8) and ground 3 to terminal resistor K_CAN3_H (9) and K_CAN_L (22) ground 3. This should make the camera visible in esys and codable to the car.
 

Attachments

#283 ·
Hello, i need help with mapping front LED DRL function in Mini F56.

What is the name for that half circle in the headlight? Tagfarhlicht or standlicht?

I removed the front foglights from the Cooper S, and i would like the upper DRL in the headlight to behave like the JCW version, which has no lower foglight.

On the lights switch I have Auto, 0, position lights (maybe called parking lamps, anyway the first click after 0), and low beam.

My headlights behave like this:

0= DRL hard on, low beam off
position= DRL off, low beam off
low beam= DRL soft on, low beam on

I want them to behave like this:
0= DRL hard on, low beam off
position= DRL soft on, low beam off
low beam= DRL soft on, low beam on



And also, how to set the low beam or high beam to be part of the welcome lights when you open the car?

I understood everything is part of the various 'mapping' folders in BDC body, but i'm really struggling to understand which is the correct line to change and the correct value to assign.



Thank you so much
 
#287 ·
@emiliof56

Thats the same i want to do.
I want to Remove my foglights sitting in the bumper.
The Problem is, that in the foglights is also the light named in german ***8222;Standlicht***8220; or maybe in englisch parking lights.

NOW i want Following:

Light switch position from left to right:

Position Auto= Daydriving lights hard on.
If its getting darker: daydriving lights soft on (as german ***8222;Standlicht***8220;) + low beam.

Position 0= all lights off (everything off).

Next Position= ***8222;Standlicht***8220; daydriving lights soft on

Next Position= Low Beam light on + daydriving lights soft on as ***8222;Standlicht***8220;.

I Hope i didnt forget anything.

THE NAME FOR THE CIRCLE IN HEADLIGHT IS TAGFAHRLICHT.

My question: is everything we Need for coding in BDC Body?

Hello, i need help with mapping front LED DRL function in Mini F56.

What is the name for that half circle in the headlight? Tagfarhlicht or standlicht?

I removed the front foglights from the Cooper S, and i would like the upper DRL in the headlight to behave like the JCW version, which has no lower foglight.

On the lights switch I have Auto, 0, position lights (maybe called parking lamps, anyway the first click after 0), and low beam.

My headlights behave like this:

0= DRL hard on, low beam off
position= DRL off, low beam off
low beam= DRL soft on, low beam on

I want them to behave like this:
0= DRL hard on, low beam off
position= DRL soft on, low beam off
low beam= DRL soft on, low beam on

And also, how to set the low beam or high beam to be part of the welcome lights when you open the car?

I understood everything is part of the various 'mapping' folders in BDC body, but i'm really struggling to understand which is the correct line to change and the correct value to assign.

Thank you so much
 
#296 ·
Hi everyone i have a question if someone can help me. I was trying coding bmw f45 2015 and while i was trying to update a navigation system the screen went blink and dosent show anything and i don't know how to make it work again it seems like its out of system if anyone had this issue please let me know how to fix it
 
#298 · (Edited)
I've been trying for some time to code SLI in the car with Kafas, nbt evo, kombi basisc and the fsc loaded but there's no way. I have read that with my kombi you can not but I found this image that says the opposite, does anyone know what is to be codified?

Image


Image


In my car f45, i have:

FA SALAPA:

1CA,1CB,205,216,230,235,249,255,2FX,2PA,2VB,2VG,313,316,423,441,470,473,493,4FD,4FS,507,520,521,534,544,548,575,5A4,5AV,650,698,6AC,6AE,6FW,6NS,6UP,7LC,856,883,8KA,8S3,8TD,8TF

I can not put 8th, error when calculating FA


FSC:

--> Read the state from "3" ECU(s) <--

EPS[DiagAddress=48(0x30)]
WBA2C11020V342358
RootCertStatus not available
SWSigStatus accepted
SWTApplications
----------
AppID 189(0xBD)
UpgradeIndex 1(0x01)
SWTType SWTclassic light
FSCStatus accepted
FSCCertStatus not available

HU_NBT2[DiagAddress=99(0x63)]
WBA1H11030V233209
RootCertStatus not available
SWSigStatus accepted
SWTApplications
----------
AppID 158(0x9E)
UpgradeIndex 1(0x01)
SWTType SWTclassic light
FSCStatus accepted
FSCCertStatus not available
----------
AppID 160(0xA0)
UpgradeIndex 1(0x01)
SWTType SWTclassic light
FSCStatus accepted
FSCCertStatus not available
----------
AppID 240(0xF0)
UpgradeIndex 1(0x01)
SWTType SWTclassic light
FSCStatus accepted
FSCCertStatus not available
----------
AppID 111(0x6F)
UpgradeIndex 1(0x01)
SWTType SWTclassic light
FSCStatus accepted
FSCCertStatus not available
----------
AppID 159(0x9F)
UpgradeIndex 1(0x01)
SWTType SWTclassic light
FSCStatus accepted
FSCCertStatus not available
----------
AppID 156(0x9C)
UpgradeIndex 1(0x01)
SWTType SWTclassic light
FSCStatus accepted
FSCCertStatus not available
----------
AppID 229(0xE5)
UpgradeIndex 1(0x01)
SWTType SWTclassic light
FSCStatus accepted
FSCCertStatus not available
----------
AppID 241(0xF1)
UpgradeIndex 37(0x25)
SWTType SWTshort
FSCStatus accepted
FSCCertStatus not available

KAFAS2[DiagAddress=93(0x5D)]
WBA8Y91030G618285
RootCertStatus not available
SWSigStatus accepted
SWTApplications
----------
AppID 126(0x7E)
UpgradeIndex 1(0x01)
SWTType SWTclassic light
FSCStatus accepted
FSCCertStatus not available
----------
AppID 190(0xBE)
UpgradeIndex 1(0x01)
SWTType SWTclassic light
FSCStatus accepted
FSCCertStatus not available
----------
AppID 191(0xBF)
UpgradeIndex 1(0x01)
SWTType SWTclassic light
FSCStatus accepted
FSCCertStatus not available

Coding Vo to 8TD

<<< CAFD_000017BE.caf.005_031_147 (BDC_01) >>>
BDC_01 > PfSarahMaster 3420 > UEBERNAHME_GESCHWINDIGKEIT_ISA = nicht_aktiv [Default]

<<< CAFD_00001F86.caf.002_022_004 (SAS) >>>
SAS > FAS 3000 > LDM_ISA_vorhanden = false [Default]
SAS > TRW 3002 > UNBELEGT = initwert [Default]

<<< CAFD_00001148.caf.000_024_001 (Kafas2) >>>
Kafas2 > SLI_CODING 3010 > NPI_ON_OFF = all_others [Default]
Kafas2 > SLI_CODING 3010 > SLI_ON_OFF = all_others [Default]

<<< CAFD_00000760.caf.007_001_103 (KOMBI L7_BASIS) >>>
KOMBI L7_BASIS > FZG_Ausstattung 3003 > LDM_ISA_ENABLE = nicht_aktiv [Default]

<<< CAFD_00001EF6.caf.006_011_025 (HU_NBT_EVO) >>>
HU_NBT_EVO > SARAH 300A > AUTOLIMITER = nicht_aktiv [Default]
 
#305 ·
Hello everyone

I have F46 m sport XDrive, I did LDW fdl coding by ESYS

Parameter:

FEM_BODY (CAFD_00000794_011_033_013) 3420 PfSarahMaster, 0E => SPURVERLASSENS_WARNUNG => aktiv = 01 (default: "nicht_aktiv = 00"; required, otherwise check control error "Front camera based assistance systems failed" - not really sure about the exact English wording, my car is German )

KAFAS2 (CAFD_00001148_000_021_002) 3020 TLC_CODING, 0B => SEND_MSG_345 => message_on_F020_F030_F025 = 01 (default: "message_off =00"; required, otherwise no warning signal will be sent to the steering wheel) 3020 TLC_CODING, 0B => SEND_MSG_327 => message_on = 01 (default: "message_off =00"; required, otherwise lane detection won't be displayed) 3020 TLC_CODING, 0B => TLC_ON_OFF => TLC_on_F020_F030_F025 = 01 (default: "TLC_off = 00"; required, otherwise the system will be inactive entirely) 3040 TLC_ACTUATOR_PARAM, 14 => ACTUATOR_ON_OFF => vib_warn_on_F20_F30_F25 = 01 (default: "all_others = 00"; required, otherwise vibration for camera based systems will be disabled at all)

KOMBI (CAFD_000009C8_006_000_031) 3003 FZG_Ausstattung, 10 => TLC_VERBAUT => aktiv = 01 (default: "nicht_aktiv = 00"; required, otherwise the system won't be displayed in the KOMBI)

KAFAS2 (CAFD_00001148_000_021_002) 3020 TLC_CODING, 0B => TLC_START_VERSION => 01 = UNKNOWN (default: "PIA_mode = 03"; required to engage the system permanently if switch not existent)

FEM_BODY (CAFD_00000794_011_033_013) 3003 ComAdapterNetworkDtc, 90 => ComAdapterPdu_327_ Status_Spurverlassenswarnsystem => aktiv = 01 (default: "nicht_aktiv = 00")

HU_NBT (CAFD_00000DED_003_009_015) 3001 EXBOX, 97 => LANE_DEPARTURE_WARNING => aktiv = 01 (default: "nicht_aktiv = 00

KAFAS2 (CAFD_00001148_000_021_002) 3020 TLC_CODING, 0B => DISPLAY_VARIANT
This is by default set to "lanes_if_system_is_on,_arrows_side_dependant_on_ availability = 04

I have steering wheel vibration motor installed with control unit.

The problem is ldw work for 10 seconds and goes off, ISTA+ fault code E07C15 in Kafas2 camera.

Fault Code Description:

The receiving control unit logs the fault when an expected message from the transmitting control unit is not received.
These types of faults are usually caused by interference on the bus connection between the affected control units (physical link).

Fault Code Conditions:

General Conditions Supply voltage between 9 and 16 volts.
Terminal Condition Terminal 15
on

Terminal Condition: PWF status: Driving

Terminal Condition: PWF status: Residing

Driving Conditions

Note: The designations of terminal status or PWF status apply according to the vehicle electrical system of the vehicle.

Fault Time Condition:

The fault code is entered after starting the control unit after a maximum of 10 seconds.
Service Plan

Run the "System analysis message missing" test module.In this test module, all "Message not present" fault code entries from all control units are analysed. This makes it possible to localise the fault to a specific area (most likely fault cause).In many cases, the faults only occur sporadically. To determine the precise fault cause, additional measurements based on the results of the analysis routine need to be carried out (voltage supply, short circuit, contact problems).

If it proves impossible to identify a clear and unambiguous fault cause and the fault pattern continues to appear repeatedly (repeat repairs), then it may be necessary to replace the related wiring, plug connections or the control unit.

Attention:
If the fault only appears sporadically (no repeat repair) and if no customer complaints concerning the problem have been received, then replacement of the related control unit is neither approved nor logical.

Note:
These faults usually appear in large numbers. If only a single fault related to a missing message has been entered and no problems related to the function of the control unit are present, then the fault can be ignored.

Does anyone have any idea how to solve this issue?

Thanks
 
#306 ·
Hello everyone

I have F46 m sport XDrive, I did LDW fdl coding by ESYS

Parameter:

FEM_BODY (CAFD_00000794_011_033_013) 3420 PfSarahMaster, 0E => SPURVERLASSENS_WARNUNG => aktiv = 01 (default: "nicht_aktiv = 00"; required, otherwise check control error "Front camera based assistance systems failed" - not really sure about the exact English wording, my car is German )

KAFAS2 (CAFD_00001148_000_021_002) 3020 TLC_CODING, 0B => SEND_MSG_345 => message_on_F020_F030_F025 = 01 (default: "message_off =00"; required, otherwise no warning signal will be sent to the steering wheel) 3020 TLC_CODING, 0B => SEND_MSG_327 => message_on = 01 (default: "message_off =00"; required, otherwise lane detection won't be displayed) 3020 TLC_CODING, 0B => TLC_ON_OFF => TLC_on_F020_F030_F025 = 01 (default: "TLC_off = 00"; required, otherwise the system will be inactive entirely) 3040 TLC_ACTUATOR_PARAM, 14 => ACTUATOR_ON_OFF => vib_warn_on_F20_F30_F25 = 01 (default: "all_others = 00"; required, otherwise vibration for camera based systems will be disabled at all)

KOMBI (CAFD_000009C8_006_000_031) 3003 FZG_Ausstattung, 10 => TLC_VERBAUT => aktiv = 01 (default: "nicht_aktiv = 00"; required, otherwise the system won't be displayed in the KOMBI)

KAFAS2 (CAFD_00001148_000_021_002) 3020 TLC_CODING, 0B => TLC_START_VERSION => 01 = UNKNOWN (default: "PIA_mode = 03"; required to engage the system permanently if switch not existent)

FEM_BODY (CAFD_00000794_011_033_013) 3003 ComAdapterNetworkDtc, 90 => ComAdapterPdu_327_ Status_Spurverlassenswarnsystem => aktiv = 01 (default: "nicht_aktiv = 00")

HU_NBT (CAFD_00000DED_003_009_015) 3001 EXBOX, 97 => LANE_DEPARTURE_WARNING => aktiv = 01 (default: "nicht_aktiv = 00

KAFAS2 (CAFD_00001148_000_021_002) 3020 TLC_CODING, 0B => DISPLAY_VARIANT
This is by default set to "lanes_if_system_is_on,_arrows_side_dependant_on_ availability = 04

I have steering wheel vibration motor installed with control unit.

The problem is ldw work for 10 seconds and goes off, ISTA+ fault code E07C15 in Kafas2 camera.

Fault Code Description:

The receiving control unit logs the fault when an expected message from the transmitting control unit is not received.
These types of faults are usually caused by interference on the bus connection between the affected control units (physical link).

Fault Code Conditions:

General Conditions Supply voltage between 9 and 16 volts.
Terminal Condition Terminal 15
on

Terminal Condition: PWF status: Driving

Terminal Condition: PWF status: Residing

Driving Conditions

Note: The designations of terminal status or PWF status apply according to the vehicle electrical system of the vehicle.

Fault Time Condition:

The fault code is entered after starting the control unit after a maximum of 10 seconds.
Service Plan

Run the "System analysis message missing" test module.In this test module, all "Message not present" fault code entries from all control units are analysed. This makes it possible to localise the fault to a specific area (most likely fault cause).In many cases, the faults only occur sporadically. To determine the precise fault cause, additional measurements based on the results of the analysis routine need to be carried out (voltage supply, short circuit, contact problems).

If it proves impossible to identify a clear and unambiguous fault cause and the fault pattern continues to appear repeatedly (repeat repairs), then it may be necessary to replace the related wiring, plug connections or the control unit.

Attention:
If the fault only appears sporadically (no repeat repair) and if no customer complaints concerning the problem have been received, then replacement of the related control unit is neither approved nor logical.

Note:
These faults usually appear in large numbers. If only a single fault related to a missing message has been entered and no problems related to the function of the control unit are present, then the fault can be ignored.

Does anyone have any idea how to solve this issue?

Thanks
Maybe you should check the wiring. Since you installed a new control unit, there may be a chance KCAN or LIN or whatever interface you connected may have wrong wiring.
 
#312 · (Edited)
I already have FCW from factory and INTELLIGENT SAFETY BUTTON both works. Today I successfully coded LDW in my F45

SEND_MGS_345 do not active if you get error. In my case it has been replaced by SEND_MSG_18A

Start with Kombi module step by step

1- KOMBI:
TLC_VERBAUT > aktiv
ST_TLC_TIMEOUT > aktiv
ST_TLC_ALIVE > aktiv
ST_TLC_APPL > aktiv

2- HU_NBT:
LANE_DEPARTURE_WARNING > aktiv

3- BDC_BODY: ( maybe different in FEM_BODY)
ComAdapterPdu_18A_Steurung_Vibration_Lenkrad > aktiv
ComAdapterPdu_327_Status_Spurverlassens_Spurverlassenswarnsystem > aktiv
PIA_DEFAULT_SPURVERLASSENS_WARNUNG > aktiv
SPURVERLASSENS_WARNUNG > aktiv
If you are installed steering wheel Control Unit with Vibration Actuator Motor then code:
LIN_VARIANTE_LRE > lre_tlc
LRE_VERBAUT > aktiv

4- KAFAS2:
TLC_START_VERSION --> Aktiv
TLC_ON_OFF --> aktiv
SEND_MSG_327 --> aktiv
SEND_MSG_345 --> nicht_aktiv (if error)
DT_LNDT_SEND: messages_activated
ACTUATOR_ON_OFF > aktiv
SEND_MSG_18A > aktiv
TLC_ON_OFF > aktiv
TLC_START_VERSION > aktiv

This fdl coding I did in BMW F46 and 100% works


Malik
 

Attachments

#313 ·
I already have FCW from factory and INTELLIGENT SAFETY BUTTON both works. Today I successfully coded LDW in my F45

SEND_MGS_345 do not active if you get error. In my case it has been replaced by SEND_MSG_18A

Start with Kombi module step by step

1- KOMBI:
TLC_VERBAUT > aktiv
ST_TLC_TIMEOUT > aktiv
ST_TLC_ALIVE > aktiv
ST_TLC_APPL > aktiv

2- HU_NBT:
LANE_DEPARTURE_WARNING > aktiv

3- BDC_BODY: ( maybe different in FEM_BODY)
ComAdapterPdu_18A_Steurung_Vibration_Lenkrad > aktiv
ComAdapterPdu_327_Status_Spurverlassens_Spurverlassenswarnsystem > aktiv
PIA_DEFAULT_SPURVERLASSENS_WARNUNG > aktiv
SPURVERLASSENS_WARNUNG > aktiv
If you are installed steering wheel Control Unit with Vibration Actuator Motor then code:
LIN_VARIANTE_LRE > lre_tlc
LRE_VERBAUT > aktiv

4- KAFAS2:
TLC_START_VERSION --> Aktiv
TLC_ON_OFF --> aktiv
SEND_MSG_327 --> aktiv
SEND_MSG_345 --> nicht_aktiv (if error)
DT_LNDT_SEND: messages_activated
ACTUATOR_ON_OFF > aktiv
SEND_MSG_18A > aktiv
TLC_ON_OFF > aktiv
TLC_START_VERSION > aktiv

This fdl coding I did in BMW F46 and 100% works

Malik
Perfect guide! Thank you and congratulations on your new toy :)
 
#314 · (Edited)
Hi All,

This is my first post and I need some emergency help. I tried to do some diagnostics on my F30 using ISTA+ 4.15 via ENET and must have accidentally started a software update which was aborted when I disconnected ENET. So now my ZGW (ZGM?) module is in a programming abort state and the car is semi-bricked.

Can anyone please help me sort this out? I'm willing to pay but need this done this weekend as I'm leaving overseas Sunday night. I don't really have a power supply other than a 30AMP schumacher battery charger. Note I had no intention of doing any flashing or programming as I thought the ISTA+ was same as ISTA-D, which I understood was only for diagnostics.

UPDATE: sorry wrong forum!
 
#315 ·
Hi All,

This is my first post and I need some emergency help. I tried to do some diagnostics on my F30 using ISTA+ 4.15 via ENET and must have accidentally started a software update which was aborted when I disconnected ENET. So now my ZGW (ZGM?) module is in a programming abort state and the car is semi-bricked.

Can anyone please help me sort this out? I'm willing to pay but need this done this weekend as I'm leaving overseas Sunday night. I don't really have a power supply other than a 30AMP schumacher battery charger. Note I had no intention of doing any flashing or programming as I thought the ISTA+ was same as ISTA-D, which I understood was only for diagnostics.
Make sure car is not stuck in Transport Mode:

Connect to vehicle with E-Sys
Read FA
Activate FA
Read SVT
go to external applications
double click the transmitter
click the connect button
double click 31 01 0f 0c 00;setenergymodedefault.