Hi I'm new to the forum,
I just wanted to comment that I could sucessfully code some features to my G30 520d 2017 using the available PRO Launcher 2.8.1 from Tokenmaster.
Many people say that is impossible to code anything beyond istep 17-something and you need to spend money in the updated Launchers but, by updating the pszdata the car accepted the coding of the alpina kombi and disabling of the star-stop features.
Is there any problems using this older version I might run into if I attempt coding other ECU's? From what I understand the features not mapped will show as unknown meaning I will not be able to know what it is about but the ones already mapped for this version will show up and work without issues. Might be the case as far as I understand the memory holds the parameters in specific memory addresses and they rarely overwrite existing parameters with other so the existing ones work. But it might be the case that the same address in memory is used for other parameter in the updated istep firmware and that could mess up the ECU.
Anyone knows more about this topic? How exactly does the launcher and esys coding of parameters work?
Regards.
I just wanted to comment that I could sucessfully code some features to my G30 520d 2017 using the available PRO Launcher 2.8.1 from Tokenmaster.
Many people say that is impossible to code anything beyond istep 17-something and you need to spend money in the updated Launchers but, by updating the pszdata the car accepted the coding of the alpina kombi and disabling of the star-stop features.
Is there any problems using this older version I might run into if I attempt coding other ECU's? From what I understand the features not mapped will show as unknown meaning I will not be able to know what it is about but the ones already mapped for this version will show up and work without issues. Might be the case as far as I understand the memory holds the parameters in specific memory addresses and they rarely overwrite existing parameters with other so the existing ones work. But it might be the case that the same address in memory is used for other parameter in the updated istep firmware and that could mess up the ECU.
Anyone knows more about this topic? How exactly does the launcher and esys coding of parameters work?
Regards.