[m7ammed]

I wanted to enable bluetooth in the final step I selected ECU and coded not just the HU_NBT, realized it was mistake after getting the errors. The car runs and drives fine

but I have drivetrain and fuel supply error!

Is there a way to fix this or have I shot myself in the foot and have to take it to the dealer and maybe loose my warranty?

[m7ammed]

OK My DME2 and another module is missing CAFD. How can I restore it?

I'm not sure if I have the required backup though.any help will be greatly appreciated. i'm afraid to drive the car.

[m7ammed]

I will use this method stated by shawnsheridan in multiple threads and see if it fixes the issue.

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.

[m7ammed]

I think I don't have the latest I-level on the list when I click "Detect CAF" to match the one shown on the side of EYS

The two modules without CAFD are DME2 and FEM_GW.

When I click detect for FEM_GW I get an error. DME2 I get error while executing.

[HFW003]

You shouldn't be touching those mate, no need!

Just code the desired ECU which should be the HU.

The latest firmware has trimmed CAFD files so they, more than likely, won't be there. That is of course unless you did other than what you state in your original post.

[shawnsheridan]

FEM_GW is not codeable, so it has no CAFD, thus you cannot inject one into it.

You need to fix DME though. If you get error while processing, try different CAFD version. Make sure motor is off when coding DME, and car has adequate Voltage. You may need to put it on a charger or jump the car to another car with running motor.

[m7ammed]

Originally Posted by HFW003

You shouldn't be touching those mate, no need!

Just code the desired ECU which should be the HU.

The latest firmware has trimmed CAFD files so they, more than likely, won't be there. That is of course unless you did other than what you state in your original post.

OK it was fixed. I discovered through reading online that DME has to be off to reinsert CAFD files. That solved it car accepted last CAFD from the i list.

I was able to code all things I needed:

- remember autostart stop
- remember AC settings (On/OFF)
-DVD in motion, plus enabled codecs for videos
-enabled BT streaming ( I don't get any album art work though or to play playlists)
- Enabled office
- Enabled door lights to come on when reversing ( I have top view but lights don't come on for some reason)

Thanks to all the people that posted on this forum all the information is posted on here.

BTW FEM_GW doesn't have CAFD because it can't be coded.

[m7ammed]

Originally Posted by shawnsheridan

FEM_GW is not codeable, so it has no CAFD, thus you cannot inject one into it.

You need to fix DME though. If you get error while processing, try different CAFD version. Make sure motor is off when coding DME, and car has adequate Voltage. You may need to put it on a charger or jump the car to another car with running motor.

I posted the above reply 20 mins before you did, laptop got stuck and just got posted now! You helped me indirectly by answering everyones questions on these forums and others so thank you

[shawnsheridan]

Originally Posted by m7ammed

I posted the above reply 20 mins before you did, laptop got stuck and just got posted now! You helped me indirectly by answering everyones questions on these forums and others so thank you

[FBMWWINS]

Hi everyone I use this older thread as I have an issue with injecting a CAFD into ZBE3 after coding all ECUs on my 2014 F32 car.
I refer to ZBE3 because ISTA throws me the following error on the CON:

CON 801410 CON: No current coding data stored
Fault description: The control unit was not encoded after programming

When I select "Detect CAF for SWE" the following error message appears:

View post on imgur.com

Thus I cannot restablish the CAFD.

Is this because I have the Ceramic Controller from another car? Meaning I have to mount the original controller back and then it should be fine?
That is what I suspect but as I have never touched ZBE3 I am many of you here know better if the cause is likely to be another?

Thanks for any input.

[shawnsheridan]

Originally Posted by F06WINS

Hi everyone I use this older thread as I have an issue with injecting a CAFD into ZBE3 after coding all ECUs on my 2014 F32 car.
I refer to ZBE3 because ISTA throws me the following error on the CON:

CON 801410 CON: No current coding data stored
Fault description: The control unit was not encoded after programming

When I select "Detect CAF for SWE" the following error message appears:

View post on imgur.com

Thus I cannot restablish the CAFD.

Is this because I have the Ceramic Controller from another car? Meaning I have to mount the original controller back and then it should be fine?
That is what I suspect but as I have never touched ZBE3 I am many of you here know better if the cause is likely to be another?

Thanks for any input.

Yes, the issue is your Ceramic Controller. Put back original or Flash and Encode Ceramic one.

[FBMWWINS]

Thank you Shawn.
Unfortunately I believe I cannot flash and/or encode ceramic one since this is not an "extra" for the F32 series. What people buy 2nd hand usually comes from F10-F11 and F06-F13 cars. Thus I guess I have no other option but put the original one back for the coding or marry the ceramic button to the original one (as many have actually done).

[shawnsheridan]

Originally Posted by F06WINS

Thank you Shawn.
Unfortunately I believe I cannot flash and/or encode ceramic one since this is not an "extra" for the F32 series. What people buy 2nd hand usually comes from F10-F11 and F06-F13 cars. Thus I guess I have no other option but put the original one back for the coding or marry the ceramic button to the original one (as many have actually done).

Ceramic is relevant. These are just plastic bits that have no coding implications. Question is if ZBE3 is valid for F32, and it should be. Flashing is a matter of using correct I-Step Shipment where ZBE3 has Black, not Red / Blue, HWEL in svt_soll.

[FBMWWINS]

Hi,

thanks for pointing that out. Yes ZBE3 is valid for F32. Now it just has no coding data - no CAFD.

I tried flashing and this is what I get during the process, which interrupts after just over 1 minute with the following:

TAL execution started.
ExecutionID=2018/08/15-18:19:06.011
[ZBE3 - 67] - [Exception - ZBE3 - 67] negative response error:
code: the result contains an error
description: Service RDBI_SVK has error in result: [Severity=2051][ErrorCode=53311][ErrorCodeDescription=Module offline][VendorCode=20039][VendorCodeDescription=link is no longer active]; LinkName: ZBE3_67_ETHERNET
severity: ERROR

TAL-Execution finished with status: "FinishedWithError". [C207]
TAL execution finished. Duration: "1min 16s". [C206]


The original IDrive Controller was swapped for a Ceramic one. And I mean the whole controller not just the button. I assume at this point I will have to mount back the original controller and try to flash again then. Or is this error caused by wrong IDrive Step? I did have in ZBE3 Red / Blue, HWEL in svt_soll. So this is likely the culprit?

[shawnsheridan]

Originally Posted by F06WINS

...I did have in ZBE3 Red / Blue, HWEL in svt_soll. So this is likely the culprit?

Again, HWEL must be Black, else you have wrong I-Step Shipment chosen.

And when flashing, make sure to bypass E-Sys Launcher and use E-Sys direct.

[FBMWWINS]

I double checked for the correct I-Step shipment to exclude that chance.

I strongly suspect I have the WRONG parameters on the ECU tab on the on ID Base Row. The examples on the PDF documentation I have are for an F11 car and are for:

HU_CIC, CMB_MEDIA, KOMBI and ZGW

There is says to check-box:

blFlash,
swDeploy,
cdDeploy,
ibaDeploy.

Does ZBE3 not need all these 4 parameters or needs perhaps others not mentioned in the guide?

[shawnsheridan]

Originally Posted by F06WINS

I double checked for the correct I-Step shipment to exclude that chance.

I strongly suspect I have the WRONG parameters on the ECU tab on the on ID Base Row. The examples on the PDF documentation I have are for an F11 car and are for:

HU_CIC, CMB_MEDIA, KOMBI and ZGW

There is says to check-box:

blFlash,
swDeploy,
cdDeploy,
ibaDeploy.

Does ZBE3 not need all these 4 parameters or needs perhaps others not mentioned in the guide?

ibaDeploy is not needed, but wont harm anything if checked.

[Gidimba]

Guys,
I did forst time coding and by mistake coded all ECUs for adding PDC (option 508).
after than I got Drivetrain and other errors.

I coded the backup SVT file I had and most issues were gone but when I go to reading fault codes I get a Permanent code U1187 which I cannot delete.


what is this code?
any ideas what to do?

[atzebmw]

Originally Posted by Gidimba

Guys,
I did forst time coding and by mistake coded all ECUs for adding PDC (option 508).
after than I got Drivetrain and other errors.

I coded the backup SVT file I had and most issues were gone but when I go to reading fault codes I get a Permanent code U1187 which I cannot delete.


what is this code?
any ideas what to do?

Normally it's no problem to code alle ecus.
Only some devices want to initialized or calibrated and that's why you should avoid it to code all ecus.
Where do you see the error code U1187?

[Gidimba]

I use the BT adaptor with the OBDlink app to check for error codes.
there it appears

[atzebmw]

Ah OK.
Because i found nothing about this error code.
If all works i wouldn't keep this in mind.
And if you code an ecu it's normal that there appear some error messages or error codes in the memory.