Consolidating all the PDFs
FDL Code ICM = IcmKod_B_InitEco = verbaut.all errors fixed......
last question is ... can I start the car with EcoPro mode?
Hi, I have coded my friend's F01 the "power and torque" now it shows up in a screen but doesn't do anything while driving. Any idea why?DreamCar,
For your consideration as an addition to this compilation of "how to" guides.
Also, I use, and have uploaded, a different sort of cheat sheet. The normal cheat sheets are organized by module. I've made mine by function so that if a function needs to be coded, all of its modules are mentioned together.
Regards,
MWPos
For F01 with CIC, neither actually.Thnx for the reply, lets say both. Possible? Need call my friend and check it out myself. Will let you know
For the Logos, you can't do either. Kombi Logo is for F20/F30 6WA Clusters but not 6WA F1x Clusters, and Head Unit Logo is only for new NBT Head Units, not CIC.So, it is impossible basically, right?
Ok, got it. ThnxFor the Logos, you can't do either. Kombi Logo is for F20/F30 6WA Clusters but not 6WA F1x Clusters, and Head Unit Logo is only for new NBT Head Units, not CIC.
No.Hi, one more thing, can we personalize the? Instead of M logo or other options that it has. Can we write something different, like it is my BMW instead of logo? Thnx
Hi All. I'm new to this and I think I understand certain concepts of VO coding, I would be grateful if experienced coders here could confirm my understanding (or lack thereof).Here is a Step-By-Step guide for how to change the vehicle FA (VO).
Be it factory FA or a modified FA, based on the Option Codes (SALAPA-Element, HO-Wort, and E-Wort) specified in that FA, when you select "CODE", E-Sys will Code every Function Data Line (FDL) of that ECU to predetermined settings necessary to support all the Option Codes. The predetermined settings are based on a variety of FA parameters such as the vehicle Type Code (e.g. TypschlĂĽssel=FR73, which equates to 535i Limousine N55B30M0 225kW Rear-wheel driveon the left USA ), and the vehicle Build Date (e.g. Zeitkriterium=1211), and are defined in the PSdZData KIS Database files....
Where I'm getting less clear is what happens during the "read SVT / code ECU" step above? Is it ESYS or the car that determines which parameters of the ECUs are affected by the (new) VO? Because at this point there are no CAFD involved or anything like that. Where does that knowledge come from?...
No....
Also is it possible to "preview" what will be coded in that step (read SVT / code ECU)? i.e.: what will be changed in the CAFD?...
I have no idea what "no op" is....
On a new car, if I were to "read FA, Activate FA, Read SVT, Select ALL ECUs, CODE". Do we agree that this should result in a "no op"? How can I verify that?...
You can VO Code all ECU's, but if you have made FDL Codings in these other ECU's, they will all be wiped out by the VO Coding's predetermined settings, and will need to be FDL Coded again, which is undesirable for many people....
In many other threads, I've seen people modifying the VO and then spending countless hours wondering which ECUs to code -- why not code them all? Shouldn't that be the "right thing to do", for the unaffected (by the VO change) ECUs, the coding should be a "no op", right?...
By "no op", I meant it wouldn't do anything, i.e.: would have no effect, as in write back the same parameters that were already there, the result being no changes at all ("no op" stands for "No OPeration", something that has no effect).I have no idea what "no op" is.
So, yes, VO Coding car with factory original FA and codings would have no affect on it.By "no op", I meant it wouldn't do anything, i.e.: would have no effect, as in write back the same parameters that were already there, the result being no changes at all ("no op" stands for "No OPeration", something that has no effect).