[kitster]

Hi all,

It's been a quite few years since I coded my F31. I brought a EST 2.X token from tokenmaster back in 2014. However I've recently acquired a G31 and naturally nothing is working anymore. Can someone help with some missing info gaps?

My 2014 Setup:

Esys 3.18.4
PSDZData: 53.5

Current Setup:

I got a copy a VM running esys 3.27.1 + Launcher Prem 2.6.2 + PSDZData 60.3.

1. Trimmed files. Is this fixed by the esys launchers? Or the incremental launcher versions from TM, do they correct new mappings etc etc? The VM I have, some of the data is just crap, I can't tell what it is! Do I need a more recent launcher or more updated version of esys?

2. Coding the G30/31. Should I be using S15A as the target?

3. This is my I-Step:

Current: S15A-18-07-547
Last: S15A-17-11-540
Shipment: S15A-17-11-540

Does anyone know what esys etc etc, I would need to enable FDL coding?

Thanks all.

[atzebmw]

Here you can download E-Sys 3.27.1 (mostly recommended version).
And also the newest psdzdata Lite and the launcher premium 2.8.2.
https://www.bimmerfest.com/forums/sh...d.php?t=983244
In the picture at point 1 you can see chassis/target overview G30= target S15A).

[kitster]

Originally Posted by atzebmw

Here you can download E-Sys 3.27.1 (mostly recommended version).
And also the newest psdzdata Lite and the launcher premium 2.8.2.
https://www.bimmerfest.com/forums/sh...d.php?t=983244
In the picture at point 1 you can see chassis/target overview G30= target S15A).

Thanks.

Ahhhh. The link above has this pointer "Launcher Premium 2.8.x (w/ Built in Token Generator) - Alternative free solution
NOTE: Pro Launcher has newer mapping so you risk coding incorrect FDL's with Premium for G-series"

This could be why some of the mappings are just garbage!