Quote:
Originally Posted by jponline77
The coding you listed above for the M* parameters turns out to match that which I coded before. This is because the init_ECE_F030 match the init_ECE_F025 parameters. So, I didn't need to make any changes there.
|
It appears that either new literal values have been added to the CAFDs or the mapping in E-Sys Launcher has been corrected. There were no "init_ECE_F025" values for several Mxx functions in the CAFDs I originally looked at (CAFD_000010BA_001_007_000 and CAFD_000016BF_001_007_000), which were from a 2014 X3. That is why I asked to see you FA and SVT files. Your CAFDs (CAFD_000010BA_001_008_051 and CAFD_000016BF_001_008_051) are newer.
Quote:
|
I did change the ERR_AL/FL values though. Any idea what those are for?
|
The ERR_AL/FL values determine what happens if an error is detected in the Mxx values: they are inconsequential as long as long as no errors are detected. There is no reason to change them.
Quote:
Originally Posted by jponline77
Test run went well. It could have been my imagination but it seems that the lights were moving quicker tonight. So, maybe the ERR_AL / FL allow the lights to move quicker.
|
The lights are not moving quicker, but they appear to, because shaping of the light beam is occurring at the same time due to the change in the Mxx parameters.