08-19-2023, 07:17 PM
I think I know what you are asking...for retrofitting equipment, the situation you are in to keep your car "compatible" with VIDA is specific to each "mod" you can do. 360 cam, vs BLIS, vs B&W stereo swap, they are all a litle different as they involve different features. I am trying to think how to boil this complexity down is a simple way...let me see if I can do it...
You have 2 main concerns of "compatibility" with VIDA:
Config compatibility - Will car get blocked?
Software compatibility - Can software be loaded/updated?
And you have a few different types of "mods" you can do:
Add equipment (not modules) - example: LED lights/units for "high level illumination"
Add equipment and module - example: add interior motion sensor (IMS) for security system
Swap a different module - example: upgrade stereo to B&W(swap amplifier, AUD module)
I'll try to take each one and the considerations, so this can be a general guide, before you get into specifics of a particular "mod":
First things to know: VIDA does not block cars based on modified modules: replacing modules with different serial numbers, HW parts, added new modules etc. You are only dealing with compatibility issues, the car will only be blocked for variant/build config mods, as of the writing of this post. And as usual you have no current concerns about getting blocked with OrBit use, either. There is also not too much concern about DTCs, i.e. trouble codes when the car config is returned to original but the hardware mods are such that the car generates codes ebcause of it. There doesn't seem to be anything in VIDA that is limited when a vehicle has certain codes or such. I haven't found any, but I am not a heavy user of it.
Add equipment (not modules) - For the most part, these type of mods are pretty safe for compatibility. If you are not changing any modules, then to VIDA, the car looks exactly the same, unmodified, VIDA only deals with the modules/ECUs. I added the LED units for "high-level illumination" to my car. These were the lower door puddle lights, door handle "amblent" LED units, door pocket LED lights etc. Then I configured the illumination level with OrBit, and those lights work. When I "Restore to OEM" those LEDs don't function. I can connect the car to VIDA, take it to the dealer, etc with no issues.
Add equipment and module - As you move up the ladder in mods, things are more dependent on the specific change you make. The whole car is proprietary and we are making changes, sometimes outside how Volvo might build a car. Adding a new module to the car, you have added a module to the network that is now going to respond to VIDA when it performs a readut of the car. In general I have found that VIDA will either ignore that module when it comes to software, or it will sometimes helpfully add a module reload to the software list. You don't have to be concerned about "blocking" with OrBit. The main concern will be can you order and install a "Total Upgrade" (TU) in VIDA. There is a process that Volvo cloud goes through to generate a TU for the car, based on the laest readout. It is looking at the car and the current software and packaging the needed updates to the latest versions. It is here you could potentially have a problem if VIDA sees a module that needs updating, but the original car config (the variant codes really) do not match. Adding the WAM and 360 cam could be an issue. If VIDA finds the WAM, it needs a software update, it's added to the TU, then when you try to order that TU, VIDA may give you an error "incompatible hardware". What I've worked out is this can happen because the car has a WAM but the variant codes define the car as not having the 360 cam, VIDA sees that as a compatibility problem.
If you are able to, the best way to deal with this potential problem, is to unplug the added module, or disable it by pulling the fuse, or some way to make VIDA not see it. You may not NEED to do that, but it's a way to deal with a module that is going to cause issues for you. When I added the IMS to my car, VIDA generated a TU and updated the software on it. It doesn't seem to have a problem with that one, but other modules being present could be an issue.
Swap a different module - This type of mod is very similar to the above. When you swap to a different module from the original, the thing that affects VIDA is whether that module is "software compatible". The key to this is "diagnostic part number" (you can read this with OrBit for any module). Two examples will show what I mean. I swapped the B&W amp into my car. It's the AUD module. It has a different diagnostic part number than the H/K AUD module originally in my car. It uses totally different software. I can plug my car into VIDA, run diagnostics etc with the B&W AUD installed. If I try to order a TU though, or an AUD reload, I will get an error of incompatible HW (car variant is H/K stereo but the B&W module is present). I can unplug the amp, and plug in the original amp, which then makes the car compatible to VIDA and I can order and install a TU or an AUD reload. Some other modules, like the HCMs I installed in the car to go with the "bending" headlights swap, those are not a problem. I needed HCMs that have a different HW part number that support the bending lights, but those HCMs have the SAME diagnostic part number as my original HCMs. They use the same software. I can order and install a TU or an HCM reload on the car with the bending lights swap, as is.
Conclusions:
This is becoming less of a problem as cars age, the frequency of software udpates slows down as volvo abandons active development on older models. There is already few udpates for my 2019 S60, the only real concern I see is ability to replace and reload modules for repair, which I think is not too hard to work around for something that doesn't need to be done often.
Note: Much of this was made more of a PITA after the "blocking" crack down. Previous to June '22, Volvo allowed the car variant config to update their system, changing the "official" config of the car. In the scenario above, I was able to change my variant config to the B&W stereo, read the car out in VIDA, and then perform a TU and AUD reload with VIDA, with the correct B&W software. Volvo's system has the capability to package the compatible software for a car, but the issue with "blocking" makes that moot, as you aren't allowed to make the car properly compatible with VIDA. It would be a lot simpler if they just went back to allowing that, VIDA still detected and prevented incompatible software, but had no problem where software was compatible with the car modified from original if it was done properly, but such is life ;-) It's a long term goal...don't ask this is a long ways away!, But I'd like OrBit to take over being able to manage software updates and reloads.
You have 2 main concerns of "compatibility" with VIDA:
Config compatibility - Will car get blocked?
Software compatibility - Can software be loaded/updated?
And you have a few different types of "mods" you can do:
Add equipment (not modules) - example: LED lights/units for "high level illumination"
Add equipment and module - example: add interior motion sensor (IMS) for security system
Swap a different module - example: upgrade stereo to B&W(swap amplifier, AUD module)
I'll try to take each one and the considerations, so this can be a general guide, before you get into specifics of a particular "mod":
First things to know: VIDA does not block cars based on modified modules: replacing modules with different serial numbers, HW parts, added new modules etc. You are only dealing with compatibility issues, the car will only be blocked for variant/build config mods, as of the writing of this post. And as usual you have no current concerns about getting blocked with OrBit use, either. There is also not too much concern about DTCs, i.e. trouble codes when the car config is returned to original but the hardware mods are such that the car generates codes ebcause of it. There doesn't seem to be anything in VIDA that is limited when a vehicle has certain codes or such. I haven't found any, but I am not a heavy user of it.
Add equipment (not modules) - For the most part, these type of mods are pretty safe for compatibility. If you are not changing any modules, then to VIDA, the car looks exactly the same, unmodified, VIDA only deals with the modules/ECUs. I added the LED units for "high-level illumination" to my car. These were the lower door puddle lights, door handle "amblent" LED units, door pocket LED lights etc. Then I configured the illumination level with OrBit, and those lights work. When I "Restore to OEM" those LEDs don't function. I can connect the car to VIDA, take it to the dealer, etc with no issues.
Add equipment and module - As you move up the ladder in mods, things are more dependent on the specific change you make. The whole car is proprietary and we are making changes, sometimes outside how Volvo might build a car. Adding a new module to the car, you have added a module to the network that is now going to respond to VIDA when it performs a readut of the car. In general I have found that VIDA will either ignore that module when it comes to software, or it will sometimes helpfully add a module reload to the software list. You don't have to be concerned about "blocking" with OrBit. The main concern will be can you order and install a "Total Upgrade" (TU) in VIDA. There is a process that Volvo cloud goes through to generate a TU for the car, based on the laest readout. It is looking at the car and the current software and packaging the needed updates to the latest versions. It is here you could potentially have a problem if VIDA sees a module that needs updating, but the original car config (the variant codes really) do not match. Adding the WAM and 360 cam could be an issue. If VIDA finds the WAM, it needs a software update, it's added to the TU, then when you try to order that TU, VIDA may give you an error "incompatible hardware". What I've worked out is this can happen because the car has a WAM but the variant codes define the car as not having the 360 cam, VIDA sees that as a compatibility problem.
If you are able to, the best way to deal with this potential problem, is to unplug the added module, or disable it by pulling the fuse, or some way to make VIDA not see it. You may not NEED to do that, but it's a way to deal with a module that is going to cause issues for you. When I added the IMS to my car, VIDA generated a TU and updated the software on it. It doesn't seem to have a problem with that one, but other modules being present could be an issue.
Swap a different module - This type of mod is very similar to the above. When you swap to a different module from the original, the thing that affects VIDA is whether that module is "software compatible". The key to this is "diagnostic part number" (you can read this with OrBit for any module). Two examples will show what I mean. I swapped the B&W amp into my car. It's the AUD module. It has a different diagnostic part number than the H/K AUD module originally in my car. It uses totally different software. I can plug my car into VIDA, run diagnostics etc with the B&W AUD installed. If I try to order a TU though, or an AUD reload, I will get an error of incompatible HW (car variant is H/K stereo but the B&W module is present). I can unplug the amp, and plug in the original amp, which then makes the car compatible to VIDA and I can order and install a TU or an AUD reload. Some other modules, like the HCMs I installed in the car to go with the "bending" headlights swap, those are not a problem. I needed HCMs that have a different HW part number that support the bending lights, but those HCMs have the SAME diagnostic part number as my original HCMs. They use the same software. I can order and install a TU or an HCM reload on the car with the bending lights swap, as is.
Conclusions:
This is becoming less of a problem as cars age, the frequency of software udpates slows down as volvo abandons active development on older models. There is already few udpates for my 2019 S60, the only real concern I see is ability to replace and reload modules for repair, which I think is not too hard to work around for something that doesn't need to be done often.
Note: Much of this was made more of a PITA after the "blocking" crack down. Previous to June '22, Volvo allowed the car variant config to update their system, changing the "official" config of the car. In the scenario above, I was able to change my variant config to the B&W stereo, read the car out in VIDA, and then perform a TU and AUD reload with VIDA, with the correct B&W software. Volvo's system has the capability to package the compatible software for a car, but the issue with "blocking" makes that moot, as you aren't allowed to make the car properly compatible with VIDA. It would be a lot simpler if they just went back to allowing that, VIDA still detected and prevented incompatible software, but had no problem where software was compatible with the car modified from original if it was done properly, but such is life ;-) It's a long term goal...don't ask this is a long ways away!, But I'd like OrBit to take over being able to manage software updates and reloads.