Reading FDL without proper folder description

drdonuts · 10-17-2019, 12:04 PM

Hi Guys, I'm having an issue reading KOMBI's FDL. The folder does not have proper name as shown.
I tried changing the launcher pro's memory to default, doesn't seems to work.
It's impossible to know which one is which... Anyone have any clue solving this? Many thanks!

Name: IMG_1575.jpg
Views: 639
Size: 203.7 KB

Name: IMG_1575.jpg
Views: 639
Size: 203.7 KB

teaston · 10-17-2019, 05:15 PM

I haven’t seen then like that before! shawnsheridan should be able to help.

shawnsheridan · 10-17-2019, 05:19 PM

Quote:

Originally Posted by teaston

I haven’t seen then like that before! shawnsheridan should be able to help.

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.

drdonuts · 10-17-2019, 07:46 PM

Thanks for the prompt help. I used launcher pro 3.4 with 3.3.1 E-sys everything showed up properly but some how after few days of sweet and nice coding I was forced back to v2.8 with 3.27.1 before it crack down and ask me to pay $50 to anonymous person.(not the txxxmaster)
According to shawnsheridan "this particular ECU CAFD is not mapped in E-Sys Launcher's CAFD Mapping Database"
The car I'm coding is 2018, could E-sys and launcher pro version be the problem?

shawnsheridan · 10-17-2019, 07:48 PM

Quote:

Originally Posted by drdonuts

Thanks for the prompt help. I used launcher pro 3.4 with 3.3.1 E-sys everything showed up properly but some how after few days of sweet and nice coding I was forced back to v2.8 with 3.27.1 before it crack down and ask me to pay $50 to anonymous person.(not the txxxmaster)
According to shawnsheridan "this particular ECU CAFD is not mapped in E-Sys Launcher's CAFD Mapping Database"
The car I'm coding is 2018, could E-sys and launcher pro version be the problem?

Launcher is what maps CAFD data, and 3.4 has newer mapping databse than 2.8.

drdonuts · 10-17-2019, 08:44 PM

Thanks a lot! I will try to get newer version of launcher... ($$...) see if that solve the problem.

Update——

After updating to newer version of launcher resolves the problem just like shawnsheridan mentioned.
Many thanks to him and hope ppl having the same issue will have more idea of what's going on.

10-17-2019, 12:04 PM	#1
drdonuts New Member 0 Rep 11 Posts Drives: E92 F20 F82 Join Date: Oct 2019 Location: Taipei iTrader: (0)	Reading FDL without proper folder description Hi Guys, I'm having an issue reading KOMBI's FDL. The folder does not have proper name as shown. I tried changing the launcher pro's memory to default, doesn't seems to work. It's impossible to know which one is which... Anyone have any clue solving this? Many thanks!
	Appreciate 0 Tweet Quote

10-17-2019, 05:15 PM	#2
teaston Banned 10995 Rep 32,881 Posts Drives: X3 M40d Join Date: May 2012 Location: The High Seas iTrader: (1)	I haven’t seen then like that before! shawnsheridan should be able to help.
	Appreciate 0 Quote

10-17-2019, 07:46 PM	#4
drdonuts New Member 0 Rep 11 Posts Drives: E92 F20 F82 Join Date: Oct 2019 Location: Taipei iTrader: (0)	Thanks for the prompt help. I used launcher pro 3.4 with 3.3.1 E-sys everything showed up properly but some how after few days of sweet and nice coding I was forced back to v2.8 with 3.27.1 before it crack down and ask me to pay $50 to anonymous person.(not the txxxmaster) According to shawnsheridan "this particular ECU CAFD is not mapped in E-Sys Launcher's CAFD Mapping Database" The car I'm coding is 2018, could E-sys and launcher pro version be the problem?
	Appreciate 0 Quote

10-17-2019, 08:44 PM	#6
drdonuts New Member 0 Rep 11 Posts Drives: E92 F20 F82 Join Date: Oct 2019 Location: Taipei iTrader: (0)	Thanks a lot! I will try to get newer version of launcher... ($$...) see if that solve the problem. Update—— After updating to newer version of launcher resolves the problem just like shawnsheridan mentioned. Many thanks to him and hope ppl having the same issue will have more idea of what's going on.
	Appreciate 0 Quote