After AAOS 5.0.5 upgrade, OrBit can no longer connect to the car

[acoutts]

Over the weekend I performed the 5.0.5 upgrade via a total upgrade in vida, and after this upgrade OrBit is no longer able to connect to the car.

I can't remember the exact error but it was something along the lines of "there is a car connected but it won't respond", and then the connect button turns red. I try to click it again to connect anyways and it hangs / never connects.

Prior to the update I used OrBit to restore the factory settings without any issues connecting to the car.

Has volvo quietly patched OrBit in the 5.0.5 upgrade? This is set to come as an OTA later this year. My car is a 2022 XC60 USDM with the older intel-based IHU.

[BeachBoy]

@power6 that's fresh info.

---

@power6 that's fresh info.

I emailed him

[acoutts]

Happy to help collect logs / debug- just let me know what to do to help!!

[Power6]

We have a good population of cars used with OrBit that have been updated, there are no other connection problems reported with OrBit after the update so far.

It is more likely an issue of a module in the car, probably the gateway in this case, may have been left in a bad state after programming was completed, causing a problem connecting. It's a very general issue, we have a troubleshooting guide for issues connecting to the car: https://forums.spaycetech.com/showthread.php?tid=53 in this case, I would probably go straight to restart the TCAM in the car to see if that resolves it.

OR if I follow correctly, you did the update yourself with VIDA, on the same computer you use OrBit? There can occasionally be a conflict with OrBit and VIDA, switching between the 2 connected to the car, sometimes VIDA "holds" the connection (it tries to keep the car alive) even when disconnected, so OrBit can't connect to the car. If that is possibly the case, reboot the computer and then start only OrBit and see if it is resolved. There are some other little "tricks" you can do to make VIDA release the connection, if you frequently run along side OrBit at he same time, but closing VIDA and rebooting is the sure way to see if the issue is resolved and confirm that was probably the cause, so you don't spend time fiddling around in Windows if it is not.