[RayoVac]

Hi all,

I am probably way off on my thought process here, but I am trying to code some settings in SAS3 that have been around for a while enabling aSLA. Problem is I am on 11/21 and EsysPlus does not have mapping for 11/21 yet.

So when I choose to edit FDL, EsysPlus prompts me to "Fix by Reference" and I select the 'CAFD_00004C1_003_004_000 option.  I find a number of UnkownParam entries in misc. sections.

If I were to open my current version CAFD from PSdZData in the CAF viewer and get the proper werte values, applying these to the few aSLA settings needing modification in SAS3,  what happens when I code this "Fixed by Reference" NCD back to the car?  Will it only write changed sections or does it write the whole thing back and if so, I assume all those other UnknowParams is going to screw stuff up.

Sorry if this a stupid question... trying to learn as I go, and hate that I let the dealership update me to 11/21 as I have lost features I was able to previously code like aSLA.  And of course there is no ETA on 11/21 mapping from the EsysPlus guys.

Thanks in advance for any guidance you can provide.

Rayo

[QTman1215]

Hi
I also use EsysPlus. My car's firmware is 22-03-530, and the 'Fixed by reference' message has appeared since last November when the major firmware was installed.
In conclusion, it is okay to code by selecting 'fixed by reference'. Compare the coded NCD file with the pre-existing NCD file. Same. There is no different.
Don't worry.

[masa52]

checked your cafd and my esys plus mapp cafd properly, so I assume you have some windows problems reinstall system

[RayoVac]

FYI for anyone following along, a complete reload of the PC and all software did not resolve anything. As stated by others in another thread, this appears to be completely an issue with the Mapping simply not being there in EsysPlus for 11/21.

The info posted about it working for masa52 was because his "Fix by Reference" is set to default. When showing me his "properly loaded" CAFD, it was also missing the mapping and showing the UnknownParams for the sections of the ECU I was looking to code.

Now I am Not saying that using "Fix by Reference" will not allow coding to take place and for folks to have success, but I am weary of writing back an NCD that has been "Fixed by Reference" where all those entries are showing Unknown Parameters.

[masa52]

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

[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

[alegsxr]

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.

[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.