BMW Forum - BimmerFest BMW Forums banner
Status
Not open for further replies.
61 - 80 of 371 Posts
all errors fixed......
last question is ... can I start the car with EcoPro mode?
FDL Code ICM = IcmKod_B_InitEco = verbaut.
 
Save
Need help with coding my F82 M4 (Dallas, TX). I have an OBD cable plus ESYS v3.24.3 and PSdZData Lite v.53.4 installed on my laptop, but no token.


Still trying to figure out what all the coding options are, but at the minimum, I would like to have following features coded:

- Re-code for Dazzle Headlights (LED)
- Enable Variable Light Distribution (VLD)
- Turn on Brake Force Flashing with Hard Braking
- Enable Illumination of Exterior Door Handle LEDs when in Reverse
- Remove Legal Disclaimers
- Add Weatherband Radio to sources
- Close windows, sunroof & mirror fold from key fob


I read somewhere that you do not need a token to code certain features. Does anyone know if any of the above features require a token to code?


My M4 Build:
- BSM / SS Full Leather
- DCT
- 19" Wheels
- M Adaptive Suspension
- Executive Package
- LED Lighting Package
- H/K Premium Sound
- Enhanced Bluetooth / Smartphone
 
Save
The 1st 2 can be VO Coded, but the rest are all FDL Coded. You need a Token solution.
 
Save
Hi Shawn,
I want to leave Auto Start/Stop always off on my 2014 F32 but when I switch to EcoPro mode, it turns on. Can this be coded to leave it as is (off in my case) when switching to EcoPro? Thanks
 
I don't have have ASS or ECO Pro in my F10, but I am pretty sure ASS On is an integral part of ECO Pro functionality, and I do not know how to disable it if it turns on automatically in ECO Pro.
 
Save
BMW e sys F01

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
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?
 
Hi, I have updated my friend's F01 2011 with the "power and torque" and it shows up but nothing happens when he drives. Also, how can I update it with the M logo? And if any cheat sheets are available I would like to have it, in order to program my friends car with goodies. Thnx in advance
 
Save
Thnx for the reply, lets say both. Possible? Need call my friend and check it out myself. Will let you know
For F01 with CIC, neither actually.
 
Save
So, it is impossible basically, right?
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.
 
Save
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, 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
No.
 
Save
Here is a Step-By-Step guide for how to change the vehicle FA (VO).
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).

So, at a high level: A car has ECUs, ECUs have many parameters. The car is configured a certain way when delivered to the customer and that is encoded in the VO (essentially a list of options). The VO can be decoded/validated and interpreted in a more human readable form and that's the VP.

It's possible (and pretty easy) to change the VO of the car (see the pdf in this thread), but that doesn't do anything in itself -- it just changes the "list of options". When the VO is modified/written, the affected ECUs need to be reprogrammed (the term is "coded"). According to the document attached, this is done by reading or loading a FA, activating it, then reading the SVT and selecting "CODE" on the ECUs of interest.
Hopefully I'm not too far off?

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?

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?

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? i.e.: again, preview what is changed in the CAFD before doing the actual write, and actually compare that to the original ECUs parameters?

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?

There are many questions here, many thanks in advance for people's time answering them!
 
...
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?...
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.

...
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?...
No.

...
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?...
I have no idea what "no op" is.

...
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?...
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.
 
Save
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).
So, yes, VO Coding car with factory original FA and codings would have no affect on it.
 
Save
61 - 80 of 371 Posts
Status
Not open for further replies.
You have insufficient privileges to reply here.