[Brobbo]

So I’ve gone to do some fdl coding.

Read the coding data and clicked edit
Gone into the fdl editor and all my folders are dotted and no idea what each one is.

Anybody else had this?

I’m running esys 3.31.0 with token master pro 3

[stu14t]

Originally Posted by Brobbo

So I’ve gone to do some fdl coding.

Read the coding data and clicked edit
Gone into the fdl editor and all my folders are dotted and no idea what each one is.

Anybody else had this?

I’m running esys 3.31.0 with token master pro 3

Sound like you haven't set Esys Launcher to F30, F32 ... Not when you connect to the car (F20) itself but on startup of Esys Launcher.

[Brobbo]

Originally Posted by stu14t

Sound like you haven't set Esys Launcher to F30, F32 ... Not when you connect to the car (F20) itself but on startup of Esys Launcher.

I know what you mean but there isn't an option for this on the pro launcher??

[Abzynthe]

It means your module has been trimmed. The mapping hasn't been updated for that module yet. Later pzdata may cure it.

[stu14t]

Try Almaretto or shawnsheridan there the gurus with this software

[shawnsheridan]

Originally Posted by Brobbo

So I’ve gone to do some fdl coding.

Read the coding data and clicked edit
Gone into the fdl editor and all my folders are dotted and no idea what each one is.

Anybody else had this?

I’m running esys 3.31.0 with token master pro 3

Trimmed PSdZData means either E-Sys has Incorrect Target Connection, or you do not use E-Sys Launcher to open E-Sys, or you use E-Sys Launcher PREMIUM but select wrong car Series or this particular ECU CAFD is not mapped in E-Sys Launcher's CAFD Mapping Database.

[Almaretto]

Originally Posted by Brobbo

So I’ve gone to do some fdl coding.

Read the coding data and clicked edit
Gone into the fdl editor and all my folders are dotted and no idea what each one is.

Anybody else had this?

I’m running esys 3.31.0 with token master pro 3

Trimmed PSdZ could be a memory issue. If 64-bit windows, install 64-bit Java and copy contents over to created folder called jre_x64 in E-sys directory. Then, set custom memory up to 8GB. Also, use Launcher settings to remove unneeded kiswb.

If DKOMBI2 or certain HKFM2, it is unmapped in latest launcher and dots are expected.

[rasel800]

I'm having the same problem, all dots while using E-Sys Launcher PRO V2.8.2 Build 162 with E-Sys 3.27.1 using PSdZData_Lite v4.17.20 in Windows 10 1903 (not VM), I can view the .ncd files in NCD/CAFD viewer just fine.

Any suggestions?

[rasel800]

Originally Posted by rasel800

I'm having the same problem, all dots while using E-Sys Launcher PRO V2.8.2 Build 162 with E-Sys 3.27.1 using PSdZData_Lite v4.17.20 in Windows 10 1903 (not VM), I can view the .ncd files in NCD/CAFD viewer just fine.

Any suggestions?

Figured out finally. Memory setting in PRO Launcher, only Default works, all other settings showing dots..

[Steve_M_Sport]

Originally Posted by rasel800

Figured out finally. Memory setting in PRO Launcher, only Default works, all other settings showing dots..

I can’t get the tokenmaster programme to work to produce the toes for the premium Pro launcher to load. If I change the PC date to 2017 I get a date error or if I leave the date to today then the launcher gets in a loop asking for the token code.

I might be talking rubbish but can anyone work out what I am doing wrong please ?

[Sasquartch]

I use the solution from Tony twoclicks have a look in the coding section

[ian332isport]

Originally Posted by Sasquartch

I use the solution from Tony twoclicks have a look in the coding section

I use the Tokenbuster solution from Splteko. Also in the coding section.

[bishbosh]

I use tokenbuster too, tokens effectively don't expire.

[Steve_M_Sport]

Originally Posted by bishbosh

I use tokenbuster too, tokens effectively don't expire.

Do you have to change the date on your PC or is that not necessary anymore ?

[ian332isport]

Originally Posted by Steve_M_Sport

Do you have to change the date on your PC or is that not necessary anymore ?

Not necessary anymore.

[Almaretto]

Originally Posted by bishbosh

I use tokenbuster too, tokens effectively don't expire.

They do expire.

Open *.EST in text editor.

<EST NotValidBefore="<DATE>" NotValidAfter="<DATE>">

[bishbosh]

Originally Posted by Almaretto

They do expire.

Open *.EST in text editor.

<EST NotValidBefore="<DATE>" NotValidAfter="<DATE>">

Yes, but in something like 50 years - which is why I said they effectively don't expire.

[Almaretto]

Originally Posted by bishbosh

Yes, but in something like 50 years - which is why I said they effectively don't expire.

Mine is valid until June 2020.

[ian332isport]

Originally Posted by Almaretto

Mine is valid until June 2020.

Mine runs until April 2069.

[bishbosh]

Originally Posted by ian332isport

Mine runs until April 2069.

Mine must be similar if not the same.

[mapretel]

Hello everyone, first of all thank all the help you give.
Yesterday I correctly encoded 8TH(Speed Limit Info) in the VO of my car along with its certificates (it works !!), to activate it I also had to encode KOMBI, KAFAS2, and HU_NBT, all ok. The point is that after this, I went to check what new fields there are for FDL, but I get folders with dots and not names, as for the version my car is an X4 F26, in E-Sys, I select the F25 version without direct mode, as for the version of E-SYS is 3.27.1, Launcher PRO 2.8.2 build 162, and PSDZ_Data the last one that @shawnsheridan sent me, of the two options that I get to connect E-SyS to my car in As for PSDZ_Data I have tried with both versions F25.xxx.10 and F25xxx.11 (when I codified the ECUs I did it with the latter), how can I see everything again without dots and with the common names?

Thanks a lot !!

[shawnsheridan]

Originally Posted by mapretel

Hello everyone, first of all thank all the help you give.
Yesterday I correctly encoded 8TH(Speed Limit Info) in the VO of my car along with its certificates (it works !!), to activate it I also had to encode KOMBI, KAFAS2, and HU_NBT, all ok. The point is that after this, I went to check what new fields there are for FDL, but I get folders with dots and not names, as for the version my car is an X4 F26, in E-Sys, I select the F25 version without direct mode, as for the version of E-SYS is 3.27.1, Launcher PRO 2.8.2 build 162, and PSDZ_Data the last one that @shawnsheridan sent me, of the two options that I get to connect E-SyS to my car in As for PSDZ_Data I have tried with both versions F25.xxx.10 and F25xxx.11 (when I codified the ECUs I did it with the latter), how can I see everything again without dots and with the common names?

Thanks a lot !!

(...) means the PSdZData is Trimmed. Trimmed PSdZData means either E-Sys has Incorrect Target Connection, or you do not use E-Sys Launcher to open E-Sys, or you use E-Sys Launcher PREMIUM but select wrong car Series or this particular ECU CAFD is not mapped in E-Sys Launcher's CAFD Mapping Database, or you have insufficient Java Memory in order for E-Sys Launcher to map it.