Quote:
Originally Posted by jmcmathortho
Quote:
Originally Posted by LexxM3
Yes, this can, and perhaps even should, be done with engine running (should because you never want to run out of battery). Out of the common ECUs, only DME cannot be coded with engine running since it itself controls the engine. The other similar dependency (not applicable here, but just FYI) is that HVAC functions cannot be coded with HVAC off in the car.
I am not aware of a way to verify anti-dazzle functionality without actually spending time observing it in real life. In my case, for example, I knew within 24 hours that something was different, but it took about of a week of focused observation to be sure it was behaving as expected. In fact, because auto-highbeams functionality became more conservative in 11/2019.xx relative to previous versions, it will now be even harder/longer to tell that it's doing its thing and doing it well.
|
I have been researching this topic for over a week and it is still unclear to me whether launcher is needed to "code" the BDC_BODY3, HU_MGU, FLM2 [43], FLM2 [44], KAFAS4 or is the latest Esys sufficient and what version of PSDzData lite is being used? I did this 3-4 years ago on a 2016 M4 and it worked but the software changes with the trimmed files and difficulties receiving a token brings lots of questions. Thanks for your help. JM |
Since you can remove the anti dazzle decoding option in FA and then VO code, you do not need a launcher (neither Launcher Pro nor ESysX), just plain ESys. You Code those ECUs, not "Code NCD". Latest version of psdzdata is always best, Lite is all that is needed. Is that enough to get you going?