[squidlyboy]

Sorry if this has been covered somewhere, but i tried searching on the the error file name i'm seeing with no luck. Here's my situation:

2014 F30, using E-Sys 3.26.1 w/ E-Sys Launcher Premium 1.07 and v.54.1_PSdZData_Lite. As a first code attempt, i successfully coded ASD to change from F30 to F82. No problems.

My next code attempt was trying to code out error code after switch parking lights from halogen to LED. I made the mistake of leaving my car off, and as luck would have it, right in the middle of the "Code FDL" operation, i heard the familiar buzz, whirl, click that my car sometimes makes after a few minutes of turning my car off. Usually the voltage will drop during this click, and of course, i get this:

Caf's werden gesucht
Tal wird generiert
NCD werden gelesen
FDL CAFD-00000794-07.1D.67 signieren.
Abarbeitung wird gestartet

TAL execution started.
ExecutionID=2015/02/10-20:13:56.337
[] prepareTALExecution started
[] prepareTALExecution finished
[] prepareVehicleForCoding started
[] prepareVehicleForCoding finished
[FEM_BODY - 40] prepareECUforCoding started
[FEM_BODY - 40] prepareECUforCoding finished
[FEM_BODY - 40] authenticateECUforCoding started
[FEM_BODY - 40] authenticateECUforCoding finished
[FEM_BODY - 40 - cafd_00000794-007_029_103] Transaction type: cdDeploy;  Message: TA started
MCDDiagService<id=62900, job=com.bmw.psdz.jobs.uds.MCD3_PerformECUCoding, service=WDBI_PLAIN - WriteDataByIdentifier with unlimited Data-ID (plain hex value), description=error: timeout, link=Physical request to ECU with address 0x40>
MCDDiagService<id=62900, job=com.bmw.psdz.jobs.uds.MCD3_PerformECUCoding, service=WDBI_PLAIN - WriteDataByIdentifier with unlimited Data-ID (plain hex value), description=error: timeout, link=Physical request to ECU with address 0x40>
MCDDiagService<id=62900, job=com.bmw.psdz.jobs.uds.MCD3_PerformECUCoding, service=WDBI_PLAIN - WriteDataByIdentifier with unlimited Data-ID (plain hex value), description=error: timeout, link=Physical request to ECU with address 0x40>
MCDDiagService<id=36900, job=com.bmw.psdz.jobs.uds.MCD3_PerformECUCoding, service=RDBI_ADS - ReadDataByIdentifier ActiveDiagnosticSession, description=error: timeout, link=Physical request to ECU with address 0x40>
[FEM_BODY - 40 - cafd_00000794-007_029_103] Transaction type: cdDeploy;  Message: TA finished
[FEM_BODY - 40] There was an error during TAL execution, please check the log files.
[FEM_BODY - 40] - [Exception - FEM_BODY - 40] negative response error: 
 code: the result contains an error
description: Service WDBI_PLAIN has error in result: [Severity=2051][ErrorCode=53311][ErrorCodeDescription=Module offline][VendorCode=20039][VendorCodeDescription=link is no longer active]; ECU: FEM_BODY_40_ETHERNET
severity: ERROR

[FEM_BODY - 40] finalizeECUCoding started
MCDDiagService<id=230900, job=com.bmw.psdz.jobs.uds.MCD3_FinalizeECUCoding, service=DSC - DiagnosticSessionControl, description=error: timeout, link=Physical request to ECU with address 0x40>
MCDDiagService<id=230900, job=com.bmw.psdz.jobs.uds.MCD3_FinalizeECUCoding, service=DSC - DiagnosticSessionControl, description=error: timeout, link=Physical request to ECU with address 0x40>
MCDDiagService<id=230900, job=com.bmw.psdz.jobs.uds.MCD3_FinalizeECUCoding, service=DSC - DiagnosticSessionControl, description=error: timeout, link=Physical request to ECU with address 0x40>
MCDDiagService<id=36900, job=com.bmw.psdz.jobs.uds.MCD3_FinalizeECUCoding, service=RDBI_ADS - ReadDataByIdentifier ActiveDiagnosticSession, description=error: timeout, link=Physical request to ECU with address 0x40>
[FEM_BODY - 40] finalizeECUCoding error
[FEM_BODY - 40] There was an error during TAL execution, please check the log files.
[FEM_BODY - 40] - [Exception - FEM_BODY - 40] negative response error: 
 code: the result contains an error
description: Service DSC has error in result: [Severity=2051][ErrorCode=53311][ErrorCodeDescription=Module offline][VendorCode=20039][VendorCodeDescription=link is no longer active]; ECU: FEM_BODY_40_ETHERNET
severity: ERROR

When i reconnected to the SVT, i noticed that the CAFD entry in SVT for the option i'm coding (see pic below highlighted in red rectangle), said "CAFD_FFFFFFFF_255_255_255". When i click on the button to "Read Coding Data", it says that file for that can't be found. I'm guessing the voltage hiccup right in the middle of the code transfer caused some kind of corruption, and now as a result, the data in the car can not be read correctly.

Fortunately, i looked in my C:\Data\CAF directory and noticed that a NCD file was saved off of the values that i set just prior to the code.

The question is, how do i restore this file into the SVT tree so that the CAFD_FFFFFFFFF_255_255_255 entry is replaced with this entry? I assume the NCD file represents this entry in the SVT tree, but i'm just guessing here...

Thanks in advance for your help to this coding newbie

[pikcachu]

Originally Posted by squidlyboy

Sorry if this has been covered somewhere, but i tried searching on the the error file name i'm seeing with no luck. Here's my situation:

2014 F30, using E-Sys 3.26.1 w/ E-Sys Launcher Premium 1.07 and v.54.1_PSdZData_Lite. As a first code attempt, i successfully coded ASD to change from F30 to F82. No problems.

My next code attempt was trying to code out error code after switch parking lights from halogen to LED. I made the mistake of leaving my car off, and as luck would have it, right in the middle of the "Code FDL" operation, i heard the familiar buzz, whirl, click that my car sometimes makes after a few minutes of turning my car off. Usually the voltage will drop during this click, and of course, i get this:

Caf's werden gesucht
Tal wird generiert
NCD werden gelesen
FDL CAFD-00000794-07.1D.67 signieren.
Abarbeitung wird gestartet

TAL execution started.
ExecutionID=2015/02/10-20:13:56.337
[] prepareTALExecution started
[] prepareTALExecution finished
[] prepareVehicleForCoding started
[] prepareVehicleForCoding finished
[FEM_BODY - 40] prepareECUforCoding started
[FEM_BODY - 40] prepareECUforCoding finished
[FEM_BODY - 40] authenticateECUforCoding started
[FEM_BODY - 40] authenticateECUforCoding finished
[FEM_BODY - 40 - cafd_00000794-007_029_103] Transaction type: cdDeploy;  Message: TA started
MCDDiagService<id=62900, job=com.bmw.psdz.jobs.uds.MCD3_PerformECUCoding, service=WDBI_PLAIN - WriteDataByIdentifier with unlimited Data-ID (plain hex value), description=error: timeout, link=Physical request to ECU with address 0x40>
MCDDiagService<id=62900, job=com.bmw.psdz.jobs.uds.MCD3_PerformECUCoding, service=WDBI_PLAIN - WriteDataByIdentifier with unlimited Data-ID (plain hex value), description=error: timeout, link=Physical request to ECU with address 0x40>
MCDDiagService<id=62900, job=com.bmw.psdz.jobs.uds.MCD3_PerformECUCoding, service=WDBI_PLAIN - WriteDataByIdentifier with unlimited Data-ID (plain hex value), description=error: timeout, link=Physical request to ECU with address 0x40>
MCDDiagService<id=36900, job=com.bmw.psdz.jobs.uds.MCD3_PerformECUCoding, service=RDBI_ADS - ReadDataByIdentifier ActiveDiagnosticSession, description=error: timeout, link=Physical request to ECU with address 0x40>
[FEM_BODY - 40 - cafd_00000794-007_029_103] Transaction type: cdDeploy;  Message: TA finished
[FEM_BODY - 40] There was an error during TAL execution, please check the log files.
[FEM_BODY - 40] - [Exception - FEM_BODY - 40] negative response error: 
 code: the result contains an error
description: Service WDBI_PLAIN has error in result: [Severity=2051][ErrorCode=53311][ErrorCodeDescription=Module offline][VendorCode=20039][VendorCodeDescription=link is no longer active]; ECU: FEM_BODY_40_ETHERNET
severity: ERROR

[FEM_BODY - 40] finalizeECUCoding started
MCDDiagService<id=230900, job=com.bmw.psdz.jobs.uds.MCD3_FinalizeECUCoding, service=DSC - DiagnosticSessionControl, description=error: timeout, link=Physical request to ECU with address 0x40>
MCDDiagService<id=230900, job=com.bmw.psdz.jobs.uds.MCD3_FinalizeECUCoding, service=DSC - DiagnosticSessionControl, description=error: timeout, link=Physical request to ECU with address 0x40>
MCDDiagService<id=230900, job=com.bmw.psdz.jobs.uds.MCD3_FinalizeECUCoding, service=DSC - DiagnosticSessionControl, description=error: timeout, link=Physical request to ECU with address 0x40>
MCDDiagService<id=36900, job=com.bmw.psdz.jobs.uds.MCD3_FinalizeECUCoding, service=RDBI_ADS - ReadDataByIdentifier ActiveDiagnosticSession, description=error: timeout, link=Physical request to ECU with address 0x40>
[FEM_BODY - 40] finalizeECUCoding error
[FEM_BODY - 40] There was an error during TAL execution, please check the log files.
[FEM_BODY - 40] - [Exception - FEM_BODY - 40] negative response error: 
 code: the result contains an error
description: Service DSC has error in result: [Severity=2051][ErrorCode=53311][ErrorCodeDescription=Module offline][VendorCode=20039][VendorCodeDescription=link is no longer active]; ECU: FEM_BODY_40_ETHERNET
severity: ERROR

When i reconnected to the SVT, i noticed that the CAFD entry in SVT for the option i'm coding (see pic below highlighted in red rectangle), said "CAFD_FFFFFFFF_...". When i click on the button to "Read Coding Data", it says that file (or data) can't be found or something like that, or maybe it was corrupted. I don't remember and i didn't do a screen capture, sorry.

Fortunately, i looked in my C:\Data\CAF directory and noticed that a NCD file was saved off of the values that i set just prior to the code.

The question is, how do i restore this file into the SVT tree so that the CAFD_FFFFFFFFF... entry is replaced with this entry? I assume the NCD file represents this entry in the SVT tree, but i'm just guessing here...

Thanks in advance for your help to this coding newbie

i think you need to do this

The CAFD file is corrupted.

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.

[squidlyboy]

Pikachu - I will be forever grateful for this... i'm really afraid of screwing up my car, so i'm gonna take this slow

So far so good. I did what you said up until the point of Click on "Detect CAF for SWE" At that point, I get the dialog on the left, and then i'm not sure what you mean by pick from the latest I-level. There are a lot of options, and I don't know which one is the right one??? (btw I have a 2014 F30 328i m-sport)

All I know is the backup of the file I corrupted just before coding started has the file name of the pic on the right (CAFD_00000794_007_029_103.ncd). But I see two of those files in the list on the left.

Which one do I choose? How do I know which one is the right one?

Thanks again a TON for helping out here. I'm super nervous about this

[pikcachu]

you can see the i-level as the folder in yellow

f020-13-07-506 and 507
507 is a later i-level than 506... so pick 507...

look it at this way.... it can't be more corrupted that what it is right now :-D
i think even choosing the f020-13-11-504 (last one) should work also....

I guess you will remember to run the car next time

[squidlyboy]

dayum!!! that worked

How do i send you a beer through email? Maybe PM you a litre of Patron?

[pikcachu]

you put on top of the mouse pad and close the monitor lid really fast.....

[squidlyboy]

Originally Posted by pikcachu

you put on top of the mouse pad and close the monitor lid really fast.....

LOL..i seriously owe you BIG - THANKS!!!!!!

[pikcachu]

no problem....

[Smee]

looks for some help.i seem to have done the same.

just want to set to back to factory but I am a little confused

I have this issue on the fem body module also

below is the code your telling me to use but i am not sure what this is exactly telling me to do...

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.

detect caf for swe... in not sure what this is and as I want to go back to default for the module do I need to do all this??

I have seen this on another post.

open e-sys
connect
read vehicle order
activate fa
right click SVT -> read coding
click on the ECU itself - NOT the CAFD_****
click on CODE

this looks like it misses that bit out... is this the correct procedure to get back to factory default?

[Smee]

@shawnsheridan

You know all ?

[shawnsheridan]

Originally Posted by Smee

...below is the code your telling me to use but i am not sure what this is exactly telling me to do...

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.

detect caf for swe... in not sure what this is and as I want to go back to default for the module do I need to do all this??

Required when ECU is misisng its CAFD File and first must have CAFD injected into ECU, before it can be encoded (factory coding).

Originally Posted by Smee

...I have seen this on another post.

open e-sys
connect
read vehicle order
activate fa
right click SVT -> read coding
click on the ECU itself - NOT the CAFD_****
click on CODE

this looks like it misses that bit out... is this the correct procedure to get back to factory default?

Required when ECU has its CAFD File and you want to encode it (factory coding).

[Smee]

Cheers

So what option will I need to use. Slightly confused... hanging up esys boots up after this lol

[shawnsheridan]

Originally Posted by Smee

Cheers

So what option will I need to use. Slightly confused... hanging up esys boots up after this lol

Look at ECU in question in your SVT and see if it has a CAFD. There is you answer, as one assumes CAFD is present and the other assumes it is not.

[Smee]

Ok think I got it. try not to laugh at this

I know the module circled isn't the fem body but you get the idea

[Smee]

Went and fixed this today. Had to Inject a new cafd was simple. Cheers for the help

[shawnsheridan]

Originally Posted by Smee

Went and fixed this today. Had to Inject a new cafd was simple. Cheers for the help

[butleruk]

I know this is an old thread but I have the same CAFD corruption as squidlyboy but I can't seem to recover from my backup CAFD.

Following the process:
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.

"Detect CAF for SWE" is grayed out so I am unable to proceed

[shawnsheridan]

Originally Posted by butleruk

I know this is an old thread but I have the same CAFD corruption as squidlyboy but I can't seem to recover from my backup CAFD.

Following the process:
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.

"Detect CAF for SWE" is grayed out so I am unable to proceed

Use E-Sys 3.27.1, and nothing newer.

[AlphaGeeky]

Sorry for bringing up such an old post. I have searched and searched and came up empty. i have tried the above mentioned CAFD injection method for every CAFD that is listed and i always get this same error. my HU has just said "NO SIGNAL" for 24 hours now and i am really converned i may have bricked my HU. The execution was not interrupted while coding to my knowledge. the car was running. but this error came up from the very first time. I am able to code other FDLs just fine.
i have also tried to VO code from scratch only without making any VO code changes just exporting it and then saving to the car. but this produced an new entry in the list labeled unknown.

Any Assistance will definately earn a virtual six pack!

what should i do? here is the error log produced every time.

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=2017/01/03-21:55:01.022
[] prepareTALExecution started
[] prepareTALExecution finished
[] prepareVehicleForCoding started
[] prepareVehicleForCoding finished
[HU_NBT2 - 63] prepareECUforCoding started
[HU_NBT2 - 63] prepareECUforCoding finished
[HU_NBT2 - 63] authenticateECUforCoding started
[HU_NBT2 - 63] authenticateECUforCoding finished
[HU_NBT2 - 63 - cafd_00001ef6-006_018_016] Transaction type: cdDeploy;  Message: TA started
MCDDiagService<id=62649, job=com.bmw.psdz.jobs.uds.MCD3_PerformECUCoding, service=WDBI_PLAIN - WriteDataByIdentifier with unlimited Data-ID (plain hex value), description=error: negative response : requestOutOfRange, link=HU_NBT2_63_ETHERNET>
[HU_NBT2 - 63 - cafd_00001ef6-006_018_016] Transaction type: cdDeploy;  Message: TA finished
[HU_NBT2 - 63] -MessageID is used multiple times, so MessageText may be ambiguous-job failed with negative response error: 
 code: repeat job
 description: Service WDBI_PLAIN returned a negative response with response code requestOutOfRange; LinkName: HU_NBT2_63_ETHERNET
 severity: ERROR

[HU_NBT2 - 63] - [Exception - HU_NBT2 - 63] job failed with negative response error: 
 code: repeat job
 description: Service WDBI_PLAIN returned a negative response with response code requestOutOfRange; LinkName: HU_NBT2_63_ETHERNET
 severity: ERROR

[HU_NBT2 - 63] prepareECUforCoding started
MCDDiagService<id=230634, job=com.bmw.psdz.jobs.uds.MCD3_PrepareECUforCoding, service=DSC - DiagnosticSessionControl, description=error: negative response : conditionsNotCorrect, link=HU_NBT2_63_ETHERNET>
[HU_NBT2 - 63] prepareECUforCoding finished
[HU_NBT2 - 63] authenticateECUforCoding started
MCDDiagService<id=16727, job=com.bmw.psdz.jobs.uds.MCD3_AuthenticateECUforCoding, service=SA_SK - SecurityAccessSendKey, description=error: negative response : serviceNotSupportedInActiveSession, link=HU_NBT2_63_ETHERNET>
[HU_NBT2 - 63] There was an error during TAL execution, please check the log files.
[HU_NBT2 - 63] There was an error during TAL execution, please check the log files.
[HU_NBT2 - 63] - [Exception - HU_NBT2 - 63] job failed with negative response error: 
 code: service returned global negative response
 description: Service SA_SK returned a negative response with response code serviceNotSupportedInActiveSession; LinkName: HU_NBT2_63_ETHERNET
 severity: ERROR

[HU_NBT2 - 63] finalizeECUCoding started
[HU_NBT2 - 63] finalizeECUCoding finished
[] There was an error, please check the log files.
[] - [Exception - HU_NBT2 - 63] job failed with negative response error: 
 code: service returned global negative response
 description: Service SA_SK returned a negative response with response code serviceNotSupportedInActiveSession; LinkName: HU_NBT2_63_ETHERNET
 severity: ERROR

[] finalizeVehicleCoding started
[] finalizeVehicleCoding finished
[] finalizeTALExecution started
[] finalizeTALExecution finished
TAL execution finished
TAL-Execution finished with status: "FinishedWithError". [C207]
TAL execution finished. Duration: "35s". [C206]
Abarbeitung beendet

i have also check the options and the two options to update VCM and MSM after TAL execution are unchecked.

[psyki]

Originally Posted by AlphaGeeky

Sorry for bringing up such an old post. I have searched and searched and came up empty. i have tried the above mentioned CAFD injection method for every CAFD that is listed and i always get this same error. my HU has just said "NO SIGNAL" for 24 hours now and i am really converned i may have bricked my HU. The execution was not interrupted while coding to my knowledge. the car was running. but this error came up from the very first time. I am able to code other FDLs just fine.
i have also tried to VO code from scratch only without making any VO code changes just exporting it and then saving to the car. but this produced an new entry in the list labeled unknown.

Any Assistance will definately earn a virtual six pack!

what should i do? here is the error log produced every time.

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=2017/01/03-21:55:01.022
[] prepareTALExecution started
[] prepareTALExecution finished
[] prepareVehicleForCoding started
[] prepareVehicleForCoding finished
[HU_NBT2 - 63] prepareECUforCoding started
[HU_NBT2 - 63] prepareECUforCoding finished
[HU_NBT2 - 63] authenticateECUforCoding started
[HU_NBT2 - 63] authenticateECUforCoding finished
[HU_NBT2 - 63 - cafd_00001ef6-006_018_016] Transaction type: cdDeploy;  Message: TA started
MCDDiagService<id=62649, job=com.bmw.psdz.jobs.uds.MCD3_PerformECUCoding, service=WDBI_PLAIN - WriteDataByIdentifier with unlimited Data-ID (plain hex value), description=error: negative response : requestOutOfRange, link=HU_NBT2_63_ETHERNET>
[HU_NBT2 - 63 - cafd_00001ef6-006_018_016] Transaction type: cdDeploy;  Message: TA finished
[HU_NBT2 - 63] -MessageID is used multiple times, so MessageText may be ambiguous-job failed with negative response error: 
 code: repeat job
 description: Service WDBI_PLAIN returned a negative response with response code requestOutOfRange; LinkName: HU_NBT2_63_ETHERNET
 severity: ERROR

[HU_NBT2 - 63] - [Exception - HU_NBT2 - 63] job failed with negative response error: 
 code: repeat job
 description: Service WDBI_PLAIN returned a negative response with response code requestOutOfRange; LinkName: HU_NBT2_63_ETHERNET
 severity: ERROR

[HU_NBT2 - 63] prepareECUforCoding started
MCDDiagService<id=230634, job=com.bmw.psdz.jobs.uds.MCD3_PrepareECUforCoding, service=DSC - DiagnosticSessionControl, description=error: negative response : conditionsNotCorrect, link=HU_NBT2_63_ETHERNET>
[HU_NBT2 - 63] prepareECUforCoding finished
[HU_NBT2 - 63] authenticateECUforCoding started
MCDDiagService<id=16727, job=com.bmw.psdz.jobs.uds.MCD3_AuthenticateECUforCoding, service=SA_SK - SecurityAccessSendKey, description=error: negative response : serviceNotSupportedInActiveSession, link=HU_NBT2_63_ETHERNET>
[HU_NBT2 - 63] There was an error during TAL execution, please check the log files.
[HU_NBT2 - 63] There was an error during TAL execution, please check the log files.
[HU_NBT2 - 63] - [Exception - HU_NBT2 - 63] job failed with negative response error: 
 code: service returned global negative response
 description: Service SA_SK returned a negative response with response code serviceNotSupportedInActiveSession; LinkName: HU_NBT2_63_ETHERNET
 severity: ERROR

[HU_NBT2 - 63] finalizeECUCoding started
[HU_NBT2 - 63] finalizeECUCoding finished
[] There was an error, please check the log files.
[] - [Exception - HU_NBT2 - 63] job failed with negative response error: 
 code: service returned global negative response
 description: Service SA_SK returned a negative response with response code serviceNotSupportedInActiveSession; LinkName: HU_NBT2_63_ETHERNET
 severity: ERROR

[] finalizeVehicleCoding started
[] finalizeVehicleCoding finished
[] finalizeTALExecution started
[] finalizeTALExecution finished
TAL execution finished
TAL-Execution finished with status: "FinishedWithError". [C207]
TAL execution finished. Duration: "35s". [C206]
Abarbeitung beendet

i have also check the options and the two options to update VCM and MSM after TAL execution are unchecked.

What happened that led you to trying to do a CAFD injection for NBT? Were you trying to flash/update? Did you lose power while FDL coding NBT?

[AlphaGeeky]

I didnt lose power or lose connection, the FDL coding that i've done so many times before simply failed and left me with the No Signal Screen (of death). i promptly restored it by re-reading the SVT and then coded the HU-NBT2. it worked and that FDL was back to factory. (i should have left well enough alone. but i thought, well maybe there was a glitch in the coding process so i tried it again,. this time it would not let me restore back. i got the error above instead. side note: there was a reference to something in there that was set to "A4A (plus) (Plus)" and i clicked edit to see what other options where there. and i may have inadvertently hit the scroll wheel and changed it to another value, of which included "A5 (Plus) (Plus)" I am wondering if changing the FDL to think the HU was an A5 rather than a A4 would cause it to lose communcation to it. It is a 2016 f30 (340i) and i just traded it for my 2016 F30 (328i), so i am getting all my creature comforts back. i was just about to start studying for my "FINAL exam", AKA reflashing the ECU. as much as i don't want to swallow that pill, i think it may be my onkly way to bring the HU back. everything else in that FDL works great, The HUD, the KOMBI, etc. just wont flash the FDL keeps erroring out as I posted above. Any insight to all this?

[psyki]

Originally Posted by AlphaGeeky

I didnt lose power or lose connection, the FDL coding that i've done so many times before simply failed and left me with the No Signal Screen (of death). i promptly restored it by re-reading the SVT and then coded the HU-NBT2. it worked and that FDL was back to factory. (i should have left well enough alone. but i thought, well maybe there was a glitch in the coding process so i tried it again,. this time it would not let me restore back. i got the error above instead. side note: there was a reference to something in there that was set to "A4A (plus) (Plus)" and i clicked edit to see what other options where there. and i may have inadvertently hit the scroll wheel and changed it to another value, of which included "A5 (Plus) (Plus)" I am wondering if changing the FDL to think the HU was an A5 rather than a A4 would cause it to lose communcation to it. It is a 2016 f30 (340i) and i just traded it for my 2016 F30 (328i), so i am getting all my creature comforts back. i was just about to start studying for my "FINAL exam", AKA reflashing the ECU. as much as i don't want to swallow that pill, i think it may be my onkly way to bring the HU back. everything else in that FDL works great, The HUD, the KOMBI, etc. just wont flash the FDL keeps erroring out as I posted above. Any insight to all this?

Does the NBT power on or is it dead in the car? I'm no expert but flashing isn't as scary as it's made out to be. I did it recently and chose to update all the modules in one go so I didn't have to worry about dependencies, I jumped it to a running car during the flash process. The only issue I had was a module I had retrofit did not flash successfully because the i-step level did not match but I worked around that by re-calculating TAL using the SVT from HWID option, then reflashing just that module.