[RayoVac]

as I said for me its no problem to change werte for FF (active) or 01 if its show UnknownParams

Correct, I have never said it cannot be coded.  I too could change the values and write the code.  

The problem for me and the risk I did not want to take was the fact that the entry I was looking to modify was being shown as UnkownParmeter, so EsysPlus does not having it mapped properly to the matching 11/21 PSdZData.

Also the default werte value I read from my car for one section I was concerned with was 00 in that UnkownParam value.  If I use the CAF viewer and open the CAFD file EsysPlus is mapping against in PSdZData with "Fix by Reference" the default value shown is 02.  So this concerns me as I know my car "should" currently have that section with a default value.

And just to reiterate, I know, I know... it can be coded and others have been successful letting EsysPlus do its "Fix by Reference" mapping.   But for me I don't feel its worth the risk of potentially bonking an ECU or applying/replacing values for ECU sections that I don't want to accidentally change.   So I am going to wait for EsysPlus to support 11/21 before I try to modify my SAS3.

Thanks a TON to Masa52 helping me get to the bottom of this.

Rayo

I have the same problem. the "Fix by reference" fix wrong.
The mapping file is wrong and if you use the fixed you modify random fdl.

Same issues.... there is nothing we can do until they update the mapping.  Trust me!!!!  It's not your install, or your operating system, don't go reloading everything.  If your car is running something later than 7/21, then you are missing the updated mapping plain and simple.  We just need to find some patience and wait.  I just wish EsysPlus would respond with a status update.