02-03-2023, 05:07 PM
Catching up with this now...since we traded some messaged via support
Some notes probably helpful:
OrBit does it's best to make the car "clean" after coding, that's the post-programming you see, it restarts the IHU (infotainment) so any settings take and the clear codes. VIDA always does this on programming too. It's not perfect though, and when you see DTCs, especially the "U" type, it's usually what I call "throwaway codes" you can clear and they don't come back, there are just "blips on the network" from programming where all the ECUs are restarting and coming up while other ECUs are still booting.
On the missing Polestar...I think we got that mystery, which we discussd already via support but worth putting here for others in the future:
The process of:
Save settings in OrBit
Restore OEM
Get software accessory installed at dealer
Load saved setings in OrBit
Write to car
*Only* in the case of installing new acessory software at the dealer, this process has a flaw...Polestar was installed, in this case VIDA changes build codes and config, then OrBit is used and load saved settings from a file, one of those settings saved is the (374) 01 Without Polestar setting, from before the Polestar install. Loading the saved settings will set that, changing your NEW 02 Polestar Optimization setting, then writing that config has changed that back on you!
The solution is: When you have had an accessory with software dealer installed, if you do then load saved settings in OrBit, review the list of items highlighted to change, before you write to the car, to see if there are any that are going to get set on you that you didn't expect, like in this case, item 374, you would see OrBit is about to change that back to old "01" "pre-Polestar, you can correct that before you write it to the car.
This is a VERY specific case, only with something added by Volvo that changes the build codes. And only if you are loading settings from a saved file. But good to know, and ultimately, easily correctible!
Some notes probably helpful:
OrBit does it's best to make the car "clean" after coding, that's the post-programming you see, it restarts the IHU (infotainment) so any settings take and the clear codes. VIDA always does this on programming too. It's not perfect though, and when you see DTCs, especially the "U" type, it's usually what I call "throwaway codes" you can clear and they don't come back, there are just "blips on the network" from programming where all the ECUs are restarting and coming up while other ECUs are still booting.
On the missing Polestar...I think we got that mystery, which we discussd already via support but worth putting here for others in the future:
The process of:
Save settings in OrBit
Restore OEM
Get software accessory installed at dealer
Load saved setings in OrBit
Write to car
*Only* in the case of installing new acessory software at the dealer, this process has a flaw...Polestar was installed, in this case VIDA changes build codes and config, then OrBit is used and load saved settings from a file, one of those settings saved is the (374) 01 Without Polestar setting, from before the Polestar install. Loading the saved settings will set that, changing your NEW 02 Polestar Optimization setting, then writing that config has changed that back on you!
The solution is: When you have had an accessory with software dealer installed, if you do then load saved settings in OrBit, review the list of items highlighted to change, before you write to the car, to see if there are any that are going to get set on you that you didn't expect, like in this case, item 374, you would see OrBit is about to change that back to old "01" "pre-Polestar, you can correct that before you write it to the car.
This is a VERY specific case, only with something added by Volvo that changes the build codes. And only if you are loading settings from a saved file. But good to know, and ultimately, easily correctible!