[shawnsheridan]

Originally Posted by andre42k

Hi Shawn, could you send met the link to the latest PSdZData? thanks

PM sent.

[Berggren]

Hi Shawn,

I'm looking to start coding etc. Could you message me details on how I can get the E-Sys and things required to start?

Thank you in advance from Sweden! :-)

[shawnsheridan]

Originally Posted by Berggren

Hi Shawn,

I'm looking to start coding etc. Could you message me details on how I can get the E-Sys and things required to start?

Thank you in advance from Sweden! :-)

PM sent.

[madmax2003]

Hey,

when I want to VO code the enhanced bluetooth functions, I get a "cafd_*** Not Executable" error. This happens when coding the ENTRYNAV module. I searched a bit for this error and the only thing I found out, was that my psdzdata version maybe doesn't match!?

My extracted ISTA-P version is: 3.56.1.002
E-Sys: 3.24.3_rc_b38445
I step current is:F020-14-07-503

Also FDL coding shows no results at all.
If I just want to change the startup emblem or so, it finishes with no error, the screen reboots but no changes. Same with foglight as cornering lights.

Any ideas?

Cheers
Max

[shawnsheridan]

Originally Posted by madmax2003

Hey,

when I want to VO code the enhanced bluetooth functions, I get a "cafd_*** Not Executable" error. This happens when coding the ENTRYNAV module. I searched a bit for this error and the only thing I found out, was that my psdzdata version maybe doesn't match!?

My extracted ISTA-P version is: 3.56.1.002
E-Sys: 3.24.3_rc_b38445
I step current is:F020-14-07-503

Also FDL coding shows no results at all.
If I just want to change the startup emblem or so, it finishes with no error, the screen reboots but no changes. Same with foglight as cornering lights.

Any ideas?

Cheers
Max

PSdZData version does not need to match, it need only to be >= to car version, so this is not an issue,

Are you using the latest version of E-Sys Launcher?

As for coding changes doing nothing, is it just these two changes or all FDL Code changes? These two you list may not be applicable to your car.

[jp0202]

Do you guys know if E-sys will still work on Windows 10 since Microsoft is pushing it out now. Don't want to upgrade and find out it's not working anymore.

[shawnsheridan]

Originally Posted by jp0202

Do you guys know if E-sys will still work on Windows 10 since Microsoft is pushing it out now. Don't want to upgrade and find out it's not working anymore.

It works.

[madmax2003]

Originally Posted by shawnsheridan

Are you using the latest version of E-Sys Launcher?

I use Launcher Premium 2.1.2.

Originally Posted by shawnsheridan

As for coding changes doing nothing, is it just these two changes or all FDL Code changes? These two you list may not be applicable to your car.

I just saw active foglights when unlocking the car, and this was not standard I think. I changed the mapping of fog lights with welcome lights.

But cornering lights should be possible when I have foglights?
My VIN: F935972

[shawnsheridan]

Originally Posted by madmax2003

...But cornering lights should be possible when I have foglights?
My VIN: F935972

Why would you assume that? Are your Fog-lights motorized? Do you have Adaptive Headlight Option, because if you do, then your headlights are your cornering lights.

[madmax2003]

Oh, I never read of motorized fog lights.
I thought cornering lights are possible and turning lights not because of missing motorized headlights.

[shawnsheridan]

Originally Posted by madmax2003

Oh, I never read of motorized fog lights.
I thought cornering lights are possible and turning lights not because of missing motorized headlights.

What is difference between cornering lights and turning lights?

Does you car have AHL?

[madmax2003]

The one thing is when you stand at a crossing with indicator active.Then I thought the foglight will go on at the indicator side.

The other thing is when you drive along a road with turns, the headlight is moving in the direction of your steering wheel. I don't have AHL.

The coding reference says that foglight are needed, no mention of AHL, so I thought it will work then, as no cameras or other hardware would be necessary for this function.

[shawnsheridan]

Originally Posted by madmax2003

...The coding reference says that foglight are needed, no mention of AHL, so I thought it will work then, as no cameras or other hardware would be necessary for this function.

It may be possible, I am not saying it isn't. I was just under impression that cars with Fog Lights for Turning Lights had Fog-Lights that swiveled. I may be wrong though.

[Mojave92]

Hi guys, can anybody send me link for E-Sys software, datafiles, token and PIN for my 2012 (prod.10/31/2011) 528i xdrive.

thanks.

[valley_nomad]

Thank Shawn for providing me the info for coding my F30 after almost two years since I did it last time. As I have many items to modify, the best way is to perform the coding "offline" -- i.e. connecting the laptop with the car to read/download and save necessary info, then disconnecting the laptop from the car, making desired changes sometime later on the laptop either once or several times, and finally reconnecting the laptop with the car for actual coding process. I did the coding in this way two years ago. But I don't remember the exact steps. Does any one have the detailed instructions for such offline coding?

[squidlyboy]

I can normally do this just fine:

Connect => Read FA (VO) => Activate FA (VO) => Read SVT (VCM) => Left-Click on desired ECU => Click on "Detect CAF for SWE" => Select the CAFD from latest I-Level shown => Select OK => Right-Click on ECU (the ECU itself not the underlying CAFD) => Select CODE.

I just recently purchased ordered a newer 61359362394 REM for a PDC retrofit. When i received the pkg, the dealer said it was replaced by the 61359374506 REM which they said is newer.

However, i can no longer select "Detect CAF for SWE" Its greyed out when i get to that step. Is this because my version of PSdZData Lite is too old? I'm running:

E-Sys v.3.26.1
PSdZData v.54.1 Lite
E-Sys Launcher Premium 1.07

I have a 2014 F30 328i M-Sport (production date 8/19/2013)
I-Step: F020-13-07-506

What do i need to upgrade to be able to VO Code this new ECU?

[shawnsheridan]

Originally Posted by Mojave92

Hi guys, can anybody send me link for E-Sys software, datafiles, token and PIN for my 2012 (prod.10/31/2011) 528i xdrive.

thanks.

PM sent.

[shawnsheridan]

Originally Posted by valley_nomad

Thank Shawn for providing me the info for coding my F30 after almost two years since I did it last time. As I have many items to modify, the best way is to perform the coding "offline" -- i.e. connecting the laptop with the car to read/download and save necessary info, then disconnecting the laptop from the car, making desired changes sometime later on the laptop either once or several times, and finally reconnecting the laptop with the car for actual coding process. I did the coding in this way two years ago. But I don't remember the exact steps. Does any one have the detailed instructions for such offline coding?

Just Read all ECU's you want to code, then disconnect to go offline, then for each ECU CAFD, Edit FDL as normal and Save them, then reconnect to car, and for each ECU CAFD, select Code FDL.

[shawnsheridan]

Originally Posted by squidlyboy

I can normally do this just fine:

Connect => Read FA (VO) => Activate FA (VO) => Read SVT (VCM) => Left-Click on desired ECU => Click on "Detect CAF for SWE" => Select the CAFD from latest I-Level shown => Select OK => Right-Click on ECU (the ECU itself not the underlying CAFD) => Select CODE.

I just recently purchased ordered a newer 61359362394 REM for a PDC retrofit. When i received the pkg, the dealer said it was replaced by the 61359374506 REM which they said is newer.

However, i can no longer select "Detect CAF for SWE" Its greyed out when i get to that step. Is this because my version of PSdZData Lite is too old? I'm running:

E-Sys v.3.26.1
PSdZData v.54.1 Lite
E-Sys Launcher Premium 1.07

I have a 2014 F30 328i M-Sport (production date 8/19/2013)
I-Step: F020-13-07-506

What do i need to upgrade to be able to VO Code this new ECU?

Too old PSdZData would not cause "Detect CAF for SWE" to be grayed out. Are you sure FA was made Active?

[squidlyboy]

Originally Posted by shawnsheridan

Too old PSdZData would not cause "Detect CAF for SWE" to be grayed out. Are you sure FA was made Active?

I'll check...thanks!

[valley_nomad]

Originally Posted by shawnsheridan

Just Read all ECU's you want to code, then disconnect to go offline, then for each ECU CAFD, Edit FDL as normal and Save them, then reconnect to car, and for each ECU CAFD, select Code FDL.

Thanks. I also found this video

which describes the offline coding in detail

[jp0202]

Hi guys. I use E-sys 3.24.3 with psd data v56.1 (lite).

When connecting to the car (F31) and reading FEM_BODY it seems like a lot of values are not being populated by E-sys Launcher. Any idea what's up with that? Cheers.