Wanted to give something back. Have been trying to program with E-Sys and came across issues with the FA being missing. This was my method for getting to a working status on the coding front. It may be simplistic, but wanted to help out those that are new to this.
- Download E-Sys from one of the forums, following the instructions, and adding the psdzdata files (ensuring all of them have the odx and distilled directories as per the install guides).
- Open connection using connect button in toolbar, select connection via gateway URL, enter address: tcp://169.254.199.99:6801 (Thanks sanjsanj). Choose one of the TargetSelector without _DIRECT at the end. Don't worry about the optional bit at the bottom. Choose connect.
- It'll likely come up with some errors about unable to read FA. Most boxes just click cancel, but the one asking you to select I-Step parameters, just click ok even though it's blank. Should now be connected after one more warning message.
- Go to comfort mode on left > FSC > Check FSC status. At the top of this, you should see the donor vehicles VIN. Head to a BMW VIN decoder website, and type in the last 7 digits.
- Back to E-Sys, click Editors & Viewers > FA-Editor. Click the new file button next to the connect. Everything with a red X next to it needs completing using data from the VIN decoder. These are the translations you'll need to complete:
Vinlong - Enter your full VIN from the donor unit here.
Entwicklungsbaureihe - Enter the model series here, (i.e. F010 for F10).
Lackcode - Enter the colour code with a leading 0 if necessary (i.e. 0475)
Polstercode - Enter the upholstery code (i.e. LCSW)
Typschlüssel - Enter the BMW production code / Type code (i.e. XG55)
Zeitkriterium - Enter the build date of the car as MMYY, this can only be March or November, otherwise it'll fail to build an FP. (i.e. 1012 for October 2012 becomes 1112 for November 2012).
E-Wort - Not sure if this is necessary, but I added B080 here for battery information.
SALAPA-Element - This is where all the car options go, disregarding the leading S if it has one. Easiest way to do this is right click SALAPA-Element, choose edit, and then add each code with a comma between, no spaces. Use ctrl+enter to save the list. I added option 609 and 6NK to be safe.
Click the save button up top.
Right click the FA name and choose "calculate FP". If you've done everything correct, a vehicle profile should load up on the right. If you have errors, the field with the error will be listed in a box after it fails. Take note and edit the data so it is correct (had this issue with the build date). - Go to Expert Mode > Coding. Load the Vehicle Order from the FA file you created. Right click the FA, and select "Activate FA".
- Select Read(ECU). It should then list your HU_NBT or HU_NBT2. From here, you should be able to follow the normal steps from tutorials online. I'd suggest making a backup of your first .ncd file (this contains all the coding parameters), and saving it to a directory that's safe. This way, if you mess up, you have a backup to revert fully back to. You can also use TokenMaster's NcdCafdTool to compare the changes you've made to your original if you don't want to entirely revert.
- Always keep engine running / battery charger connected when coding. I was using an insufficient trickle charger, and after coding I lost audio and the display kept flashing. Once it was charged, everything worked as normal.
- Startup_emblem is a quick easy one to change to ensure it's working fine.
Bookmarks