with esys and PSDZdata can be coded dvd in motion?

 

Yes, except it is not codeable above 63 kmh for NBT ID5 Head Unit.

 

PM sent.

 

Yes, a big thank you to ShawnSheridan and Almaretto!!

Thanks a bunch guys!

 

Yes, a big thank you to ShawnSheridan and Almaretto!!

Thanks a bunch guys!

:thumbup:

 

I currently have E-Sys 3.28 and noticed 3.30 is available. Is there a changelog to read somewhere, or should i just stick w/3.28

 

E-Sys 3.29 and 3.30 add nothing and are not supported by E-Sys Launcher, so using them isn't really an option.

 

I want to save some space on my HDD and I want to know is it possible to make a shortcut from psdzdata from ISTA and this shortcut to put in folder Data?

Gesendet von meinem HTC 10 mit Tapatalk

 

You can use Symlinks. If using Premium Launcher, only E-sys must be installed in default location, but data folder can be anywhere; I have mine on secondary drives.

 

I have only one partition, 3.27 is installed and Data folder is on C drive.

Gesendet von meinem HTC 10 mit Tapatalk

 

You configure in E-sys settings where data folder is located. It can be located on another partition or drive if you choose.

 

Now we are understanding each other.
Thanks for your help and have a nice weekend

Gesendet von meinem HTC 10 mit Tapatalk

 

:thumbup:

 

Hi guys,

I hadn't updated my ESys in a while, but I just did a fresh install of the latest recommended software. Running ESys 3.28.1, Launcher Premium 2.7.1.135, and psdzdata 61.4 (full). When I try to FDL code my X3 I am getting "." for all the values in the CAF-Viewer and FDL-Editor. I am selecting F25 in the launcher and as the target when connecting to the car in ESys. Any thoughts on why I'm seeing this?

Thanks!

 

Hi guys,

I hadn't updated my ESys in a while, but I just did a fresh install of the latest recommended software. Running ESys 3.28.1, Launcher Premium 2.7.1.135, and psdzdata 61.4 (full). When I try to FDL code my X3 I am getting "." for all the values in the CAF-Viewer and FDL-Editor. I am selecting F25 in the launcher and as the target when connecting to the car in ESys. Any thoughts on why I'm seeing this?

Thanks!

You must use E-Sys Launcher to Open E-Sys, and not Open E-Sys directly.

 

I Was coding My f30 and everything worked just fine until I went to code fem_body. It keeps giving me the not found error when I click read coding data. A Quick search came up with download the latest psdzdata so I did that and I'm still getting the same fault. Is there anything else I can do to make it work? Esys 3.28.1


Sent from my iPhone using Bimmerfest

 

I Was coding My f30 and everything worked just fine until I went to code fem_body. It keeps giving me the not found error when I click read coding data. A Quick search came up with download the latest psdzdata so I did that and I'm still getting the same fault. Is there anything else I can do to make it work? Esys 3.28.1

Sent from my iPhone using Bimmerfest

Try with 3.27 or 3.30

Sent from my HTC 10 using Tapatalk

 

Thank you! I will give it that a shot


Sent from my iPhone using Bimmerfest

 

Dropped down to 3.27.1 and I got the same problem...any other options?


Sent from my iPhone using Bimmerfest

 

Hello,

Can you provide me the latest links for e-sys and psdzdata ?

Thank's

 

something wrong with links in first post?

 

Any idea how long token master takes to reply with activation code? I emailed on Wednesday and still no reply really want to start coding!

 

All depends on TokenMaster and his schedule. Sometimes, it can be a day or two, and others, it can be months...

 

awesome job
thx

 

When an updated version of psdzdata lite is listed, is there any advantage for me to update if my car is included in the previous version?

I mean, do any coding options get updated, removed, added, improved etc.

Cheerz

 

You gain nothing. What is possible is based on the car's firmware not the psdzdata version you use.

 

Does the E-Sys / launcher author usually reply pretty quick with an activation code?

 

Sometimes it is fast, and sometimes, not so much.

 

Update: I got it from the first post.. Sorry, my fault.

But what about Esys 3.27.1 and PSdZData 3.62.4 compatibility? Are they friends?
And what about mapping of latest PSdZData 3.62.4 with Premium 2.7.1_build135? According to the changelog of Esys Launcher, it was recently (at v2.6.0 build 128) upgraded to support only up to V3.59.4... There are no more information about newest PSdZData compatibility...


Hi Shawn,
Could you please send me the link for latest stuff for coding?
My car got updated by the dealer, all my codings lost..
Thanks!

 

Update: I got it from the first post.. Sorry, my fault.

But what about Esys 3.27.1 and PSdZData 3.62.4 compatibility? Are they friends?
And what about mapping of latest PSdZData 3.62.4 with Premium 2.7.1_build135? According to the changelog of Esys Launcher, it was recently (at v2.6.0 build 128) upgraded to support only up to V3.59.4... There are no more information about newest PSdZData compatibility...

Hi Shawn,
Could you please send me the link for latest stuff for coding?
My car got updated by the dealer, all my codings lost..
Thanks!

E-Sys 3.27.1 works with latest 62.4 PSdZData, and remains the preferred version.

PM sent.

 

My mini F56 was recently dealer ECU updated and all my previous settings erased. I updated the psdzdata to support the new I Stop version, but I cant seem to find any of the same settings in the ASCM or BDC sections still. Am I missing a CADF file still? Any help appreciated.

Thanks,

 

My mini F56 was recently dealer ECU updated and all my previous settings erased. I updated the psdzdata to support the new I Stop version, but I cant seem to find any of the same settings in the ASCM or BDC sections still. Am I missing a CADF file still? Any help appreciated.

Thanks,

If you can read ECU, then you are not missing any CAFD. Make sure you are using latest E-Sys Launcher.

 

I'm using E-Sys 3.27.1 with launcher premium v2.7.1

I was looking under ACSM2 (there is no other ACSM listed) and it has the following CAFDs:
CAFD_000011AB_007_001_007
CAFD_000011AC_007_000_007
CAFD_000011AD_004_001_010

I was looking in the first CAFD (11AB), but then looked through all them. I'm basically trying to find where the 3000 Initialwarnung and 3000 SeatBeltReminder_xxx settings went. I cant find them. Did they move?

Thanks again for the help

 

Do you see anything other than dots (.)?

CAFD_000011AB_007_001_007 is Trimmed in Launcher PREMIUM.

 

Sorry but i'm confused by that question.

I can "Edit" the FDL under that CAFD (11AB) and open to see the Funktionen listing (ZUENDKRIEIS_XX, and a few other settings), just cant find the ones I'm looking for (search finds no existence of them). Do I need the untrimmed CAFD? Before the ECU update at the dealer I used Esys Launcher 2.4.3 with an earlier psdzdata that was supporting my I-Step then and I found those parameters in those areas with no problem. Does the new version of launcher trim it differently than last time?

Thanks

 

Sorry but i'm confused by that question.

I can "Edit" the FDL under that CAFD (11AB) and open to see the Funktionen listing (ZUENDKRIEIS_XX, and a few other settings), just cant find the ones I'm looking for (search finds no existence of them). Do I need the untrimmed CAFD? Before the ECU update at the dealer I used Esys Launcher 2.4.3 with an earlier psdzdata that was supporting my I-Step then and I found those parameters in those areas with no problem. Does the new version of launcher trim it differently than last time?

Thanks

Disregard Trimmed part. I had to change Launcher PREMIUM Car Series to F056 to get invoke the Mapping; however, in looking at it, it appears this CAFD is not being mapped correctly.

 

Oh interesting, been a year since I've used the tools, but thought it was much easier to find the parameters I was looking for.

So is this mis-mapping a function of the E-sys tool itself?

 

...So is this mis-mapping a function of the E-sys tool itself?

Yes.

 

Will a newer version of E-sys help? Though I guess its a matter of what the latest E-sys launcher supports as well since I cant make any changes unless it does.

Thanks,

 

No. It has nothing to do with E-Sys. The CAFD Mapping Database is builtin E-Sys Launcher.

 

Ah, ok. So I'm assuming I'm dead in the water then, or at least until an updated E-Sys Launcher addresses it.

Thanks for explaining and looking into it.

 

Yes.

 

Well that's unfortunate. Would the older version of E-Sys (3.24) and E-Sys launcher (2.4.3) work the latest psdzdata? Ie: could those solve the mapping issue?

Thanks

 

No. I already confirmed you are "dead in the water", until new version of Launcher PREMIUM is released that has an updated CAFD Mapping Database. Why you are asking now about older E-Sys and older E-Sys Launcher escapes me. :dunno:

 

Desperation

Question is because it seemed to map those parameters before in the previous version as I was able to find and change those settings. Wasnt sure it was a function of the just the updated launcher or all of the above (new ISTA-P with I-Level, new E-sys, new E-sys launcher). That's all.

 

ECU has new CAFD, and it must be added to CAFD Mapping Database. Mapping of old CAFD is irrelevant.