Quote:
Originally Posted by ifr
LexxM3 if you get chance could you do an experiment for me. My dealer killed my access to DSC_VIP_IB2 when flashing to 11/2019.x, but I don't think it's used on the G05. SASx seems to take preference.
Could you code DSC_VIP_IB2 back to stock FA, wiping out the aSLA coding, and see if it still works please? I only included VIP in the aSLA coding for completeness, they are like a mirror of SASx in some instances.
Looks like VIP (Virtual Integration Platform) is used for system integration testing, which makes sense when you look at the codes in the ECU. Haven't got my head around the coding implications yet if any.
|
Turned out I had removed aSLA coding a little while back so I did the following:
- VO coded DSC_VIP_IB2 to factory just to be sure (checked, identical pre and post VO coding)
- FDL coded BDC, HU, and SAS2 per your information; skipped and did nothing with DSC_VIP_IB2
Result:
- works fine
- UI allows same control as I recall having the first time
- sets and automatically adjusts current speed based on detected signs
- changes current speed in anticipation of navigation way points
- uses my set (i.e. +15km/h) adjustment at both above and below 60km/h levels
So I would say your theory that DSC_VIP_IB2 is unnecessary is correct :-).