VO = Vehicle Order

VO Code = Coding of all FDL's (100% of the ECU) to predetermined settings based on the Vehicle Order.

Connect => Read FA (VO) => Activate FA (VO) => Read SVT (VCM) => Right-Click on ECU (the ECU itself not the underlying CAFD) => Select CODE.

FDL = Function Data Line

FDL Code = Coding of individual FDL's in an ECU, overriding the VO Coding.

Connect => Read FA (VO) => Activate FA (VO) => Read SVT (VCM) => Right-Click on the ECU CAFD and select Read Coding Data => Expand the CAFD Folder by clicking + symbol => Right

 

Thanks Shawn.

So VO represents vehicle's hardware configuration, FDL represents software configuration within certain ECU. VO coding means reset some or all ECU's software configuration based on hardware configuration, and FDL coding means changing ECU's software configuration without altering hardware configuration.

Is my understanding correct?

 

The VO (Vehicle Order) defines the setup of your car. Like Xenon or LED, Sat, Bluetooth aso.
For some of this VO codes is also a special hardware required (eg. an additional ecu).

But basically VO is also changing the software configuration. If you add a VO code to your car and press the "Code" button on the ECU the system will use the default settings which are behind this VO code to change the software settings.
FDL is hand made change On this way, you will enter the software configuration by hand and change the settings you would like to have.

Some settings can be changed only by FDL coding because they were never contemplated for the customer.

Hopefully you can understand what I tried to explaine :bigpimp:

 

The VO (Vehicle Order) defines the setup of your car. Like Xenon or LED, Sat, Bluetooth aso.
For some of this VO codes is also a special hardware required (eg. an additional ecu).

But basically VO is also changing the software configuration. If you add a VO code to your car and press the "Code" button on the ECU the system will use the default settings which are behind this VO code to change the software settings.
FDL is hand made change On this way, you will enter the software configuration by hand and change the settings you would like to have.

Some settings can be changed only by FDL coding because they were never contemplated for the customer.

Hopefully you can understand what I tried to explaine :bigpimp:

 

Thanks for explanation! It is very clear now!

 

In a nutshell, VO Coding is how BMW wants your car configured. FDL Coding is how YOU want it done.

 

when I buy a F series I shall Bug you in that case. Thank You

 

So can we say that VO = default factory settings?
In my case I don't like how my air conditioning performs and I tried "resetting" the IHKA module but that had no effect. Would VO coding be any different? There are no error codes at all in ISTA but I am hoping that a VO code will relearn IHKA the right way of taking care of things...

 

Yes, VO Code is setting factory settings. I don't know what you did to reset it though, or if VO Coder is same.

 

In ISTA I went to IHKA, called the ECU functions, went to diagnosis and then to trigger components. The last option in this menu is reset ECU but can't tell how deep the reset is 'cause when it resumed in a few seconds, it kept my temp and fan speed settings. It might be just a on/off thing, maybe flaps calibration check, but not a factory default reset. I'm still digging...

 

I have no idea functionally if that is same as VO Coding. I doubt it is,

 

Yeah, that is why I'm trying to learn if a VO coding can actually act as a factory reset. I read that VO coding is mostly used when you retrofit, add a new ECU and hardware, which I'm not. From an IT guy perspective, it should be similar to formatting the C drive when you get a virus: you don't change any hardware, even Windows is the same version, it just gets rid of the bugs and you end up with a fresh install and a good working system, at least for a while
I'm still not comfortable with the idea that I might brick it if I don't know what I'm doing. A PC motherboard would be a bit easier to swallow if anything goes wrong

 

Yeah, that is why I'm trying to learn if a VO coding can actually act as a factory reset. I read that VO coding is mostly used when you retrofit, add a new ECU and hardware, which I'm not. From an IT guy perspective, it should be similar to formatting the C drive when you get a virus: you don't change any hardware, even the Windows is the same version, it just gets rid of the bugs and you end up with a fresh install and a good working system, at least for a while
I'm still not comfortable with the idea that I might brick it if I don't know what I'm doing. A PC would be a bit easier to swallow if anything goes wrong

As I wrote, VO Coding sets all Coding in ECU to factory settings. There is Zero risk of Bricking ECU by VO Coding it.

 

Do you have an example, a step by step guide that I can apply? Sorry, I never did this before, only FDL codings and all this is very new to me

 

Connect => Read FA (VO) => Activate FA (VO) => Read (ECU) => Right-Click on IHKA (the ECU itself not the underlying CAFD) => Select CODE.

 

OMG, that simple? Can't wait to give it a try tonight, thank you

 

Hello Shawnsheridan-

Any chance you can share a link for ISTA? Need to fix a parking brake problem on my E70. Thanks very much!

 

No, Sorry, I cannot help with ISTA.

 

Hello everyone,

today I tried VO coding the first time, but got an error after coding.
I want to add k235 for trailer hitch. I think these ECU are relevant:
Bdc-body
dkombi
dsc
egs
hu-nbt
sas
hkfm



Here the steps I did:

Read FA, modified it. Then activated it (green “aktiv”)
Read ECU
startet with SAS2
right click on SAS2 > codieren

Started coding an after coding there was a error report.
”Datei für CAFD 00001c7a-002-251-010 wurde nicht gefunden“
I think Esys is missing a file, but CAFD is there. I can find in SWE directory.

i have esys 3.30.0
no launcher
car i-step SA15 18-07-547
I don’t know how old my pszdata are, but I think relatively new because I can select I step 21-03.

Can somebody give me a hint how to solve the problem?

thanks,
Winnepooh

 

cafd_00001c7a.caf.002_251_010 is in v.4.29.31_PSdZData, as are 6 newer versions of this CAFD. Update your PSdZData. PM sent.

 

Hi, I am new to e-sys, just bought an F45 (2016) and want to add some options. So I read there are 2 ways to do this: add the option code to the SALAPA, or change settings in the individual ECU's. Question: by just adding an option code to the SALAPA, will the changes to the individual ECU's automatically be made? I understand that for certain options also new hardware will be required, but I'm thinking about adding Driving Assistant which may work as I have a KAFAS camera. Thanks, Albert

 

Hi All,

Where do i download the E-sys software for F10? I need to reset my KOMBI/ECU to factory reset?

Please help
Thank
-N

 

PM sent.

 

@shawnsheridan Can I also please have the link for ESYS?

I have a 2012 F10 that needs coding for a different battery capacity. Would you suggest coding it with ESYS or just use BimmerCode?

 

I'd use E-Sys for Coding. Will need ISTA to register battery after.

 

what is cafd

 

CAFD = Process class designation of the CAF
CAF = Coding Application File. A CAF file is a special SWE (software unity) that contains the coding data of a single ECU. All coding data of a single ECU can be distributed on multiple CAFs. As well the entire application software of a ECU can be distributed on multiple SWEs. The coding data is divided in discrete coding data groups within the CAF file. Every coding data group contains at least one function which has at least one parameter.

 

Hi Shawn,

If I VO code a g20 to add 2VB and then code DCS_BRS, HU_MGU, KAFAS4, RAM, DKOMBI and BDC_BODY3, the DME ECU will be left untouched, correct?

As always, appreciate our responses.

Cheers, Colin.

 

Hi Shawn,

If I VO code a g20 to add 2VB and then code DCS_BRS, HU_MGU, KAFAS4, RAM, DKOMBI and BDC_BODY3, the DME ECU will be left untouched, correct?

As always, appreciate our responses.

Cheers, Colin.

Yes. So long as you don't code DME, it will be left alone.