View Single Post
      10-23-2019, 04:21 AM   #4
Ze_Pedro
New Member
3
Rep
11
Posts

Drives: BMW F20
Join Date: Feb 2017
Location: Portugal

iTrader: (0)

Today I finally understood the difference between FDL Coding and VO Coding.
I also realised that I have done that too... And the problem is still there.
I am now thinking that itīs a software problem, because the car is still the same, and now I cannot even change something so basic as AG logo to MPerformance, or Start Stop Memory.
The Car accepted the VO coding of all the ECUīs with the basic (almost factory) backup I had, and after that, all the coding I do is recorded in the ECUīs with No Errors, but nothing works.
Never had this problem before, and in 2017 I coded my car and 6 more from friends.
It must be something to do with Esys... I am now out of ideas...

-----------------------------------------------------------------------------------------------------
Explanation by shawnsheridan
-----------------------------------------------------------------------------------------------------

For VO Coding you select the ECU itself, not the CAFD File.

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-Click on the CAFD file and select Edit => Edit CAFD as desired => Click the Blue Floppy Disc Icon to Save CAFD => Click the green back arrow icon => Right-Click on the CAFD file => Select FDL CODE.
Appreciate 0