https://forums.spaycetech.com/ Tue, 07 Jul 2026 13:23:25 +0000 MyBB https://forums.spaycetech.com/showthread.php?tid=1375 Fri, 03 Jul 2026 17:15:00 +0000 Decked]]> https://forums.spaycetech.com/showthread.php?tid=1375 I wanted to ask whether it is possible to apply configuration changes through the wizards without clearing or resetting the DTCs.
I currently have an intermittent “Reduced engine performance” issue that needs to be diagnosed by the dealer.
When I read the codes myself, I found P200900 confirmed and P00BC00 stored.
The car also consumes quite a lot of oil, so I suspect the issue may be related to the EGR valve.
Recently, I disabled the ACC that I had previously enabled through Orbit, but doing so cleared the DTCs. Since then, the reduced engine performance warning has not appeared again.
It would be very useful if I could disable and re-enable features until my dealer appointment, which is in about a month, without losing any diagnostic data. I travel a lot, so I would really like to keep using ACC in the meantime if possible.
Is there any way to apply wizard changes without clearing the stored/confirmed DTCs?]]> I wanted to ask whether it is possible to apply configuration changes through the wizards without clearing or resetting the DTCs.
I currently have an intermittent “Reduced engine performance” issue that needs to be diagnosed by the dealer.
When I read the codes myself, I found P200900 confirmed and P00BC00 stored.
The car also consumes quite a lot of oil, so I suspect the issue may be related to the EGR valve.
Recently, I disabled the ACC that I had previously enabled through Orbit, but doing so cleared the DTCs. Since then, the reduced engine performance warning has not appeared again.
It would be very useful if I could disable and re-enable features until my dealer appointment, which is in about a month, without losing any diagnostic data. I travel a lot, so I would really like to keep using ACC in the meantime if possible.
Is there any way to apply wizard changes without clearing the stored/confirmed DTCs?]]> https://forums.spaycetech.com/showthread.php?tid=1369 Sat, 20 Jun 2026 03:55:37 +0000 Nemo222]]> https://forums.spaycetech.com/showthread.php?tid=1369
LTE has no connection

WiFi works, Polestar App works. 

I took it into a local Volvo dealership (polestar dealer is very far and very garbage). They diagnosed it as being connected to a USA data network (I'm in Canada). They downloaded a "market change certificate". This has not fixed the issue. 

I went poking at the ECU fuctions/data I could read for the TCAM module and found for Current Network Identiy (9019) it has Mobile country code: 310, Mobile network code: 17 which, if I'm reading this right means it thinks it should have an AT&T connection. 

The current mobile network operator (D084) is showing MCC 302 and MNC 220 which corresponds to Telus as the current operator which is correct and what it should be. 

Network registration status (9016) shows registered roaming. and Home market (4653) shows "CA" which also makes sense. 

So the car is trying to talk to an AT&T tower. Tt allows roaming data connection for app access, but it does not allow that connection forward to the IHU for maps and spotify. The market change certificate either didn't stick, or wasn't appropriate for my car for some reason

Is there any way I can change this myself and re-assign the car to a Canadian network?

I'm pretty sure I'm stuck waiting for Polestar to get their act together because they're useless, and I like my Volvo friends so I don't really want to make them deal with this again. How much control do we have with Orbit and is this at all possible? 

Thanks!

*Interesting Edit*
A few days ago my car suddenly re-established LTE connectivity. I made no changes. I thought that maybe it sorted itself out and changed its mobile operator. I went and checked the same ECU functions to see if they changed and found that they had not and were the same as before.

So my theory that the software blocked IHU access on roaming data networks is not true and i have so many more questions that before!]]>
LTE has no connection

WiFi works, Polestar App works. 

I took it into a local Volvo dealership (polestar dealer is very far and very garbage). They diagnosed it as being connected to a USA data network (I'm in Canada). They downloaded a "market change certificate". This has not fixed the issue. 

I went poking at the ECU fuctions/data I could read for the TCAM module and found for Current Network Identiy (9019) it has Mobile country code: 310, Mobile network code: 17 which, if I'm reading this right means it thinks it should have an AT&T connection. 

The current mobile network operator (D084) is showing MCC 302 and MNC 220 which corresponds to Telus as the current operator which is correct and what it should be. 

Network registration status (9016) shows registered roaming. and Home market (4653) shows "CA" which also makes sense. 

So the car is trying to talk to an AT&T tower. Tt allows roaming data connection for app access, but it does not allow that connection forward to the IHU for maps and spotify. The market change certificate either didn't stick, or wasn't appropriate for my car for some reason

Is there any way I can change this myself and re-assign the car to a Canadian network?

I'm pretty sure I'm stuck waiting for Polestar to get their act together because they're useless, and I like my Volvo friends so I don't really want to make them deal with this again. How much control do we have with Orbit and is this at all possible? 

Thanks!

*Interesting Edit*
A few days ago my car suddenly re-established LTE connectivity. I made no changes. I thought that maybe it sorted itself out and changed its mobile operator. I went and checked the same ECU functions to see if they changed and found that they had not and were the same as before.

So my theory that the software blocked IHU access on roaming data networks is not true and i have so many more questions that before!]]> https://forums.spaycetech.com/showthread.php?tid=1367 Thu, 18 Jun 2026 01:07:17 +0000 MinatoXC60]]> https://forums.spaycetech.com/showthread.php?tid=1367

New member here — i have a 2018 XC60 D4 (no AdBlue), AWD, Momentum Comfort, and just bought OrBit to dig into a few features my car doesn't have from the factory:

• Adaptive Cruise Control
  
• Pilot Assist
  
• Traffic Sign Recognition (Sign Assist)
  
• CarPlay & Android Auto (Device Mirroring)
  
• Disable Stop/Start
  
• Audible locking feedback
  
• Polestar theme/skin
  
  

From searching the forum and a few videos, here's what I've found so far for the simpler ones:

224. DEVICE MIRRORING With Carplay & Android Auto 
271. STOP START FUNCTION MEMORY Button with memory, Standard symbol 
096. AUDIBLE LOCKING FEEDBACK On 
168. SCREEN THEMES/SKINS Polestar

Still need confirmed working values for ACC, Pilot Assist, and Sign Assist on a D4 of this model year — if anyone's done this on a similar car, I'd really appreciate the exact settings.

Quick question for the more experienced folks: is it better to do all these changes in one session, or one at a time? Mainly wondering about whether back-to-back writes are hard on the battery . Any general tips for a first-timer would be great too.

Thanks in advance!

]]>

New member here — i have a 2018 XC60 D4 (no AdBlue), AWD, Momentum Comfort, and just bought OrBit to dig into a few features my car doesn't have from the factory:

• Adaptive Cruise Control
  
• Pilot Assist
  
• Traffic Sign Recognition (Sign Assist)
  
• CarPlay & Android Auto (Device Mirroring)
  
• Disable Stop/Start
  
• Audible locking feedback
  
• Polestar theme/skin
  
  

From searching the forum and a few videos, here's what I've found so far for the simpler ones:

224. DEVICE MIRRORING With Carplay & Android Auto 
271. STOP START FUNCTION MEMORY Button with memory, Standard symbol 
096. AUDIBLE LOCKING FEEDBACK On 
168. SCREEN THEMES/SKINS Polestar

Still need confirmed working values for ACC, Pilot Assist, and Sign Assist on a D4 of this model year — if anyone's done this on a similar car, I'd really appreciate the exact settings.

Quick question for the more experienced folks: is it better to do all these changes in one session, or one at a time? Mainly wondering about whether back-to-back writes are hard on the battery . Any general tips for a first-timer would be great too.

Thanks in advance!

]]> https://forums.spaycetech.com/showthread.php?tid=1366 Thu, 18 Jun 2026 00:30:45 +0000 Javoski]]> https://forums.spaycetech.com/showthread.php?tid=1366 Thanks!! 
]]> Thanks!! 
]]> https://forums.spaycetech.com/showthread.php?tid=1364 Wed, 17 Jun 2026 00:22:48 +0000 yammel]]> https://forums.spaycetech.com/showthread.php?tid=1364 i'd like to know if Orbit software can help me repair my infotainment system software. I previously updated it over the air (OTA), and now my 2023 XC40 Recharge is unusable. I don't even have a radio or climate controls, let alone a backup camera.

  WhatsApp Image 2026-06-16 at 18.03.32 (1).jpeg (Size: 96.98 KB / Downloads: 64)

  WhatsApp Image 2026-06-16 at 18.03.32 (2).jpeg (Size: 69.44 KB / Downloads: 63)

  WhatsApp Image 2026-06-16 at 18.03.32.jpeg (Size: 52.05 KB / Downloads: 64) ]]> i'd like to know if Orbit software can help me repair my infotainment system software. I previously updated it over the air (OTA), and now my 2023 XC40 Recharge is unusable. I don't even have a radio or climate controls, let alone a backup camera.

  WhatsApp Image 2026-06-16 at 18.03.32 (1).jpeg (Size: 96.98 KB / Downloads: 64)

  WhatsApp Image 2026-06-16 at 18.03.32 (2).jpeg (Size: 69.44 KB / Downloads: 63)

  WhatsApp Image 2026-06-16 at 18.03.32.jpeg (Size: 52.05 KB / Downloads: 64) ]]> https://forums.spaycetech.com/showthread.php?tid=1362 Tue, 16 Jun 2026 19:29:32 +0000 danthe88]]> https://forums.spaycetech.com/showthread.php?tid=1362
DTCs are:

B14C281 Head Lamp Input. Bus Signal / Message Failures. Invalid serial data received
B15A323 Headlamp Swiveling Feedback Sensor. General Signal Failures. Signal stuck low

It was hot day, normal driving, nothing out of ordinary.
I have tried to delete DTC but headlights are not moving... After some time DTC B15A323 returns.

Should I just throw this headlight away, or can it still be fixed?]]>
DTCs are:

B14C281 Head Lamp Input. Bus Signal / Message Failures. Invalid serial data received
B15A323 Headlamp Swiveling Feedback Sensor. General Signal Failures. Signal stuck low

It was hot day, normal driving, nothing out of ordinary.
I have tried to delete DTC but headlights are not moving... After some time DTC B15A323 returns.

Should I just throw this headlight away, or can it still be fixed?]]> https://forums.spaycetech.com/showthread.php?tid=1351 Tue, 09 Jun 2026 17:47:02 +0000 Dennis3258]]> https://forums.spaycetech.com/showthread.php?tid=1351
as my Volvo XC40 D4 R Design 2019 most probably need a replacement of  the ad blue Injector.
After the replacement the new injector need to be adapted.
Does Orbit give a solution with this?

Can anyone advise e on this please?

Thanks advance]]>
as my Volvo XC40 D4 R Design 2019 most probably need a replacement of  the ad blue Injector.
After the replacement the new injector need to be adapted.
Does Orbit give a solution with this?

Can anyone advise e on this please?

Thanks advance]]> https://forums.spaycetech.com/showthread.php?tid=1350 Mon, 08 Jun 2026 10:57:48 +0000 generatorlabs]]> https://forums.spaycetech.com/showthread.php?tid=1350
New Orbit user and new owner of a 2023 C40 Recharge.
I will try to be brief. There are 3 things I am trying to resolve with my vehicle.

1) Noise from behind upper dashboard area on passenger side. I can best describe the sound as a muffled motorboat or "flub flub flub" sound. It randomly occurs when starting vehicle and last 15-30 seconds and then subsides.

2) Tailgate actuators that will not open the tailgate unless I offer an initial upward push. They travel the rest of the way with no problem.
Is the torque on these actuators something that is adjustable in Orbit?

3) Constant issues with media center. Pandora will crash regularly. Sound settings do not "stick' in memory. I have to hold center button on screen to restart the media center.
I have followed the procedure to completely reset the media center. It works for a week and then it doesn't. I this a hardware failure, known bugs or a mix?

Other than these 3 things I am having a wonderful time with the vehicle and I can see myself slipping into another one of these in the future. I still have warranty coverage so if there are recommended steps I should take at the dealer, I can. I have never been to my local dealer. I bought this car out-of-state.

Thanks for taking the time to read my first post!]]>
New Orbit user and new owner of a 2023 C40 Recharge.
I will try to be brief. There are 3 things I am trying to resolve with my vehicle.

1) Noise from behind upper dashboard area on passenger side. I can best describe the sound as a muffled motorboat or "flub flub flub" sound. It randomly occurs when starting vehicle and last 15-30 seconds and then subsides.

2) Tailgate actuators that will not open the tailgate unless I offer an initial upward push. They travel the rest of the way with no problem.
Is the torque on these actuators something that is adjustable in Orbit?

3) Constant issues with media center. Pandora will crash regularly. Sound settings do not "stick' in memory. I have to hold center button on screen to restart the media center.
I have followed the procedure to completely reset the media center. It works for a week and then it doesn't. I this a hardware failure, known bugs or a mix?

Other than these 3 things I am having a wonderful time with the vehicle and I can see myself slipping into another one of these in the future. I still have warranty coverage so if there are recommended steps I should take at the dealer, I can. I have never been to my local dealer. I bought this car out-of-state.

Thanks for taking the time to read my first post!]]> https://forums.spaycetech.com/showthread.php?tid=1345 Tue, 02 Jun 2026 22:47:20 +0000 konrado1]]> https://forums.spaycetech.com/showthread.php?tid=1345 Rozwiązanie nad naprawą powypadkową Volvo XC90 T6 z 2021 roku (benzyna). Silnik uruchamia się i działa prawidłowo, a moduły SRS/ASDM są wyczyszczone z danych o zderzeniu. Mam jednak problem z centralną niezgodnością konfiguracji modułu silnika (ECM), której nie można usunąć za pomocą OrBit. Podczas próby zapisu konfiguracji lub kasowania kodów błędów, moduł zasilania silnika (ECM) cały czas kody U2300. Wygląda na to, że konieczne jest postawienie diagnozy. Oto dokładne kody DTC,
 które obecnie otrzymuję: 
BCM: U010000 – Utrata komunikacji z modułem zasilania silnika (ECM) [Potwierdzone] 
BCM: U02A400 – Utrata komunikacji z modułem kontrolnym silnika (ECM) [Potwierdzone] 
ECM: P06A013 – Obwód sterowania wzmacniaczem lub zastępczym. Ogólne rozwiązanie elektryczne. Przerwa w obwodzie [Oczekujące] 
ECM: U230055 – Konfiguracja centralna. Błędne oprogramowanie systemu. Nieskonfigurowane [Oczekujące] 
ECM: U230056 – Konfiguracja centralna. Błędne oprogramowanie systemu. 

Nieprawidłowe/niezgodne z ustawieniami [Oczekujące] Z powodu błędów U230055/56, ECM wyłączył dodatkowe funkcje, takie jak sprężarka klimatyzacyjna. Ten problem to „przeładowanie ECM” lub „zakup oprogramowania ECM” za pośrednictwem Volvo VIDA. Wolałbym jednak rozwiązać ten problem w OrBit, jeśli jest to możliwe. Czy istnieje konkretna procedura w OrBit, która wymusza flashowanie prawidłowej struktury wewnętrznej w ECM lub prawidłowe przeładowanie ECM? Czy uczestniczy w plikach SBL/VBF, aby nadpisać ten sektor EEPROM, czy VIDA jest powodem?
bardzo ważna informacja o błędzie, porady i instrukcje krok po kroku od osób, które doprowadziły do usunięcia błędów U2300 w ECM za pomoc OrBit! Z góry dziękuję za pomoc!]]> Rozwiązanie nad naprawą powypadkową Volvo XC90 T6 z 2021 roku (benzyna). Silnik uruchamia się i działa prawidłowo, a moduły SRS/ASDM są wyczyszczone z danych o zderzeniu. Mam jednak problem z centralną niezgodnością konfiguracji modułu silnika (ECM), której nie można usunąć za pomocą OrBit. Podczas próby zapisu konfiguracji lub kasowania kodów błędów, moduł zasilania silnika (ECM) cały czas kody U2300. Wygląda na to, że konieczne jest postawienie diagnozy. Oto dokładne kody DTC,
 które obecnie otrzymuję: 
BCM: U010000 – Utrata komunikacji z modułem zasilania silnika (ECM) [Potwierdzone] 
BCM: U02A400 – Utrata komunikacji z modułem kontrolnym silnika (ECM) [Potwierdzone] 
ECM: P06A013 – Obwód sterowania wzmacniaczem lub zastępczym. Ogólne rozwiązanie elektryczne. Przerwa w obwodzie [Oczekujące] 
ECM: U230055 – Konfiguracja centralna. Błędne oprogramowanie systemu. Nieskonfigurowane [Oczekujące] 
ECM: U230056 – Konfiguracja centralna. Błędne oprogramowanie systemu. 

Nieprawidłowe/niezgodne z ustawieniami [Oczekujące] Z powodu błędów U230055/56, ECM wyłączył dodatkowe funkcje, takie jak sprężarka klimatyzacyjna. Ten problem to „przeładowanie ECM” lub „zakup oprogramowania ECM” za pośrednictwem Volvo VIDA. Wolałbym jednak rozwiązać ten problem w OrBit, jeśli jest to możliwe. Czy istnieje konkretna procedura w OrBit, która wymusza flashowanie prawidłowej struktury wewnętrznej w ECM lub prawidłowe przeładowanie ECM? Czy uczestniczy w plikach SBL/VBF, aby nadpisać ten sektor EEPROM, czy VIDA jest powodem?
bardzo ważna informacja o błędzie, porady i instrukcje krok po kroku od osób, które doprowadziły do usunięcia błędów U2300 w ECM za pomoc OrBit! Z góry dziękuję za pomoc!]]> https://forums.spaycetech.com/showthread.php?tid=1343 Tue, 02 Jun 2026 10:02:22 +0000 matuuu]]> https://forums.spaycetech.com/showthread.php?tid=1343 I have an issue with the AdBlue system on my V60.
At first, I got fault code P20EE. I checked the injector and found that it was crystallized. I cleaned everything as thoroughly as I could using warm water. A few months later, the fault code appeared again, and I discovered that the injector was also leaking externally.
I bought a new injector, reset everything, and after that the system worked perfectly for about 4 months with no fault codes at all.
However, yesterday the fault code returned again, and when I removed the injector, I found the same situation as before. What could be causing this? How can I properly clean the AdBlue catalyst/SCR catalyst? Is it safe to simply flush it with warm water?
Thanks in advance for any advice.

  20260531_183825.jpg (Size: 706.54 KB / Downloads: 26) ]]> I have an issue with the AdBlue system on my V60.
At first, I got fault code P20EE. I checked the injector and found that it was crystallized. I cleaned everything as thoroughly as I could using warm water. A few months later, the fault code appeared again, and I discovered that the injector was also leaking externally.
I bought a new injector, reset everything, and after that the system worked perfectly for about 4 months with no fault codes at all.
However, yesterday the fault code returned again, and when I removed the injector, I found the same situation as before. What could be causing this? How can I properly clean the AdBlue catalyst/SCR catalyst? Is it safe to simply flush it with warm water?
Thanks in advance for any advice.

  20260531_183825.jpg (Size: 706.54 KB / Downloads: 26) ]]> https://forums.spaycetech.com/showthread.php?tid=1342 Tue, 02 Jun 2026 07:47:56 +0000 Tbonem]]> https://forums.spaycetech.com/showthread.php?tid=1342
I've been reading the forums for a while for the lots of things Orbit can do, but I understand it's quite model / version specific, so I was wondering if it's worth purchasing Orbit for my new car and what can I do with it. 
The car in question is a EU '25 XC60 Ultra B5 - with the updated AAOS screen (the bigger one) with air suspension, full led lights with bending, panoramic roof, ventilated seats, etc.

I would consider buying Orbit in order to tweak the max speed limit option, but any other modifications or improvements that could be made on this version of the car worthwhile the trouble?
Another feature that made Orbit interesting for me would be the Polestar optimization but as far as I could tell from the other threads this is not the same as purchasing the rather expensive Polestar software from the dealer (it's funny how if you basically want a "sport" mode you need to pay close to 1000 EUR). 

Since the car is pretty new I'm not interested in doing any hardware modifications or deep diagnostics & troubleshooting for now. 

Thank you upfront for your responses.]]>
I've been reading the forums for a while for the lots of things Orbit can do, but I understand it's quite model / version specific, so I was wondering if it's worth purchasing Orbit for my new car and what can I do with it. 
The car in question is a EU '25 XC60 Ultra B5 - with the updated AAOS screen (the bigger one) with air suspension, full led lights with bending, panoramic roof, ventilated seats, etc.

I would consider buying Orbit in order to tweak the max speed limit option, but any other modifications or improvements that could be made on this version of the car worthwhile the trouble?
Another feature that made Orbit interesting for me would be the Polestar optimization but as far as I could tell from the other threads this is not the same as purchasing the rather expensive Polestar software from the dealer (it's funny how if you basically want a "sport" mode you need to pay close to 1000 EUR). 

Since the car is pretty new I'm not interested in doing any hardware modifications or deep diagnostics & troubleshooting for now. 

Thank you upfront for your responses.]]> https://forums.spaycetech.com/showthread.php?tid=1336 Wed, 27 May 2026 17:50:53 +0000 soulvoid86]]> https://forums.spaycetech.com/showthread.php?tid=1336
Just looking for clarification on how I can verify what my car would, in theory, support. My car does not have ACC or PA, but it does have the Intellisafe system with Lane keep, sign reading, etc. Photo below of dash during startup. I do not have 360 cameras, only rear. I'd like to enable the ASL headlights with corning as well (our XC90 has this). It is a US based car.

I did read about the ABS pump so I'm not concerned about that, but there's no concrete thread that shows what each car will support (I understand this is still a new system).

If there's any recommendations on cable(s) (or a pinned post that I maybe overlooked) I'd appreciate that as well.

I'll gladly provide my VIN if necessary.

Thanks for any insight/confirmations before I order the system!

  613cb9e0-ae8f-4aca-a457-cf6a30adbc20.jpg (Size: 159.77 KB / Downloads: 53)

  ff2b01fe-f87a-41d2-88ea-6c6495c4b28e.jpg (Size: 102.52 KB / Downloads: 55)

  4d8120f1-2e90-47ef-bd5f-e64db22fb807.jpg (Size: 182.18 KB / Downloads: 57)

  7a39ff99-6d7b-418a-ad4b-71e2b4f03644.jpg (Size: 82.45 KB / Downloads: 56) ]]>
Just looking for clarification on how I can verify what my car would, in theory, support. My car does not have ACC or PA, but it does have the Intellisafe system with Lane keep, sign reading, etc. Photo below of dash during startup. I do not have 360 cameras, only rear. I'd like to enable the ASL headlights with corning as well (our XC90 has this). It is a US based car.

I did read about the ABS pump so I'm not concerned about that, but there's no concrete thread that shows what each car will support (I understand this is still a new system).

If there's any recommendations on cable(s) (or a pinned post that I maybe overlooked) I'd appreciate that as well.

I'll gladly provide my VIN if necessary.

Thanks for any insight/confirmations before I order the system!

  613cb9e0-ae8f-4aca-a457-cf6a30adbc20.jpg (Size: 159.77 KB / Downloads: 53)

  ff2b01fe-f87a-41d2-88ea-6c6495c4b28e.jpg (Size: 102.52 KB / Downloads: 55)

  4d8120f1-2e90-47ef-bd5f-e64db22fb807.jpg (Size: 182.18 KB / Downloads: 57)

  7a39ff99-6d7b-418a-ad4b-71e2b4f03644.jpg (Size: 82.45 KB / Downloads: 56) ]]> https://forums.spaycetech.com/showthread.php?tid=1334 Mon, 25 May 2026 19:55:15 +0000 liushaohuai5]]> https://forums.spaycetech.com/showthread.php?tid=1334 I’m trying to troubleshoot an air suspension calibration issue on my 2016 Volvo XC90 T8 and would appreciate some advice from people familiar with VIDA/SUM calibration.
Background:
The left rear height sensor linkage was previously disconnected from the sensor arm. Before I fully restored the mechanical position of the linkage and sensor arm, I performed a calibration in VIDA while the vehicle was physically sitting at what looked like normal ride height.
At that time, the sensor readings were roughly:

• Left rear: 0.55 V
  
• Right rear: 3.23 V
  

The car was physically at normal rear ride height, but the left rear sensor was clearly near the end of its voltage range because the linkage/sensor arm was not in the correct mechanical zero position.
I have now restored the left rear linkage and sensor arm position. At the same physical normal ride height, the rear sensor readings are now approximately:

• Left rear: 3.23 V
  
• Right rear: 3.23 V
  

The sensor behavior also seems mechanically reasonable now. When the rear suspension rises, I observed:

• Left rear voltage decreases, for example 3.3 V → 1.9 V
  
• Right rear voltage increases, for example 3.3 V → 4.5 V
  

So I assume the rear sensors are mirror-oriented and opposite voltage direction left vs right is normal.
The problem:
Even though the car is currently sitting at normal physical rear height, when I command “normal level” / enable leveling, the rear suspension still rises. My suspicion is that the SUM still has the previous bad calibration stored, where it learned that 0.55 V on the left rear sensor = normal ride height. Now that the left rear sensor is mechanically restored to about 3.23 V at the same physical height, the SUM may interpret the car as too low and tries to raise the rear until the left rear voltage moves back toward the old incorrect reference.
My questions:

1. Does this interpretation make sense? In other words, could the SUM be chasing the old left rear calibration value of ~0.55 V even though the mechanical sensor position has now been corrected?
   
2. Is there a Orbit procedure that allows a static height / sensor position calibration where I can keep the car at the current correct physical ride height, enter the measured heights, and overwrite the old calibration?
   
3. If the calibration routine first tries to auto-level using the old calibration, is it safe/reasonable to temporarily disable the compressor or remove the compressor fuse so the rear cannot be raised during calibration? I understand that residual reservoir pressure could still raise the car through the valve block, so I’m not sure whether this is a valid approach.
   
4. Does VIDA require the compressor / air suspension system to be fully online for SUM calibration to complete, or can the height sensor calibration be written with leveling disabled?
   
5. Is there any SUM adaptation reset, initialization, “identification,” software reload, or re-programming procedure that clears an incorrect height calibration? I do not mean just clearing DTCs, but actually resetting/relearning the SUM height reference.
   

I’m trying to avoid calibrating the car after it has already been incorrectly raised by the old calibration, because that seems like it would write another bad reference. My goal is to keep the vehicle at the current correct physical normal height and overwrite the old SUM calibration with the corrected sensor positions.
Any advice on the correct calibration sequence or safe procedure would be appreciated.]]> I’m trying to troubleshoot an air suspension calibration issue on my 2016 Volvo XC90 T8 and would appreciate some advice from people familiar with VIDA/SUM calibration.
Background:
The left rear height sensor linkage was previously disconnected from the sensor arm. Before I fully restored the mechanical position of the linkage and sensor arm, I performed a calibration in VIDA while the vehicle was physically sitting at what looked like normal ride height.
At that time, the sensor readings were roughly:

• Left rear: 0.55 V
  
• Right rear: 3.23 V
  

The car was physically at normal rear ride height, but the left rear sensor was clearly near the end of its voltage range because the linkage/sensor arm was not in the correct mechanical zero position.
I have now restored the left rear linkage and sensor arm position. At the same physical normal ride height, the rear sensor readings are now approximately:

• Left rear: 3.23 V
  
• Right rear: 3.23 V
  

The sensor behavior also seems mechanically reasonable now. When the rear suspension rises, I observed:

• Left rear voltage decreases, for example 3.3 V → 1.9 V
  
• Right rear voltage increases, for example 3.3 V → 4.5 V
  

So I assume the rear sensors are mirror-oriented and opposite voltage direction left vs right is normal.
The problem:
Even though the car is currently sitting at normal physical rear height, when I command “normal level” / enable leveling, the rear suspension still rises. My suspicion is that the SUM still has the previous bad calibration stored, where it learned that 0.55 V on the left rear sensor = normal ride height. Now that the left rear sensor is mechanically restored to about 3.23 V at the same physical height, the SUM may interpret the car as too low and tries to raise the rear until the left rear voltage moves back toward the old incorrect reference.
My questions:

1. Does this interpretation make sense? In other words, could the SUM be chasing the old left rear calibration value of ~0.55 V even though the mechanical sensor position has now been corrected?
   
2. Is there a Orbit procedure that allows a static height / sensor position calibration where I can keep the car at the current correct physical ride height, enter the measured heights, and overwrite the old calibration?
   
3. If the calibration routine first tries to auto-level using the old calibration, is it safe/reasonable to temporarily disable the compressor or remove the compressor fuse so the rear cannot be raised during calibration? I understand that residual reservoir pressure could still raise the car through the valve block, so I’m not sure whether this is a valid approach.
   
4. Does VIDA require the compressor / air suspension system to be fully online for SUM calibration to complete, or can the height sensor calibration be written with leveling disabled?
   
5. Is there any SUM adaptation reset, initialization, “identification,” software reload, or re-programming procedure that clears an incorrect height calibration? I do not mean just clearing DTCs, but actually resetting/relearning the SUM height reference.
   

I’m trying to avoid calibrating the car after it has already been incorrectly raised by the old calibration, because that seems like it would write another bad reference. My goal is to keep the vehicle at the current correct physical normal height and overwrite the old SUM calibration with the corrected sensor positions.
Any advice on the correct calibration sequence or safe procedure would be appreciated.]]> https://forums.spaycetech.com/showthread.php?tid=1328 Thu, 21 May 2026 23:41:43 +0000 liushaohuai5]]> https://forums.spaycetech.com/showthread.php?tid=1328 https://forums.spaycetech.com/showthread.php?tid=1326 Wed, 20 May 2026 23:57:42 +0000 Austrianflyguide]]> https://forums.spaycetech.com/showthread.php?tid=1326 Looking for some help/advice on a 2016 Volvo XC90 T6 Momentum (SPA platform) with 360 camera / Pilot Assist issues after water intrusion under the passenger seat area.
Background:

• Water got under the passenger carpet area where the WAM (Wide Angle Vision Module / 360 camera module) sits.
  
• Initially I lost the 360 camera completely.
  
• Various other modules/functions acted up temporarily (windows, etc.) but most recovered after drying things out.
  
• The camera system never came back.
  

Original module part number:
31471507 (GBV7A)
I purchased a used matching module with the exact same part number and installed it.
Current status after replacement:

• OrBit and XTool now communicate with ASDM/WAM again.
  
• Network topology now shows WAM online.
  
• I can run ASDM calibration procedures.
  
• ASDM calibration reports:
  “Calibration complete – drive vehicle until safety systems re-enable.”
  

However:

• The 360/rear camera image is still black / no camera display.
  
• Pilot Assist still unavailable.
  
• I still get intermittent:
  U112500 – Interrupted Communication with WAM
  

Additional ASDM codes:

• C100154 – Vision System Camera Missing Calibration
  
• C1A6754 – Forward Looking Sensor Missing Calibration
  
• C1A6778 – Forward Looking Sensor Alignment Incorrect
  

Things already done:

• Cleaned all connectors with CRC electronic cleaner
  
• Dried passenger floor area
  
• Verified power/communication came back
  
• Cleared DTCs multiple times
  
• Ran OrBit calibration procedures successfully
  
• Battery support at 14V during procedures
  

Questions:

1. Does a used WAM module on SPA Volvos require VIDA software download/flash even if the part number matches exactly?
   
2. Is the OrBit ASDM calibration enough, or does VIDA need to perform camera/WAM initialization?
   
3. Does the system require an extended drive cycle before the camera image returns?
   
4. Has anyone had the camera remain black even though WAM communication came back online?
   
5. Could this still be a MOST/coax/camera feed issue rather than module programming?
   

Any advice from someone who has swapped a WAM module successfully on SPA XC90/S90/V90/XC60 would be greatly appreciated.
Thanks!

  Screenshot 2026-05-20 171719.png (Size: 111.16 KB / Downloads: 61)

  Screenshot 2026-05-20 170529.png (Size: 150.32 KB / Downloads: 62)

  read out 1 camera volt .png (Size: 186.4 KB / Downloads: 62)

  camera alignment 1.png (Size: 261.05 KB / Downloads: 63)

  camera 1.txt (Size: 187 bytes / Downloads: 0) ]]> Looking for some help/advice on a 2016 Volvo XC90 T6 Momentum (SPA platform) with 360 camera / Pilot Assist issues after water intrusion under the passenger seat area.
Background:

• Water got under the passenger carpet area where the WAM (Wide Angle Vision Module / 360 camera module) sits.
  
• Initially I lost the 360 camera completely.
  
• Various other modules/functions acted up temporarily (windows, etc.) but most recovered after drying things out.
  
• The camera system never came back.
  

Original module part number:
31471507 (GBV7A)
I purchased a used matching module with the exact same part number and installed it.
Current status after replacement:

• OrBit and XTool now communicate with ASDM/WAM again.
  
• Network topology now shows WAM online.
  
• I can run ASDM calibration procedures.
  
• ASDM calibration reports:
  “Calibration complete – drive vehicle until safety systems re-enable.”
  

However:

• The 360/rear camera image is still black / no camera display.
  
• Pilot Assist still unavailable.
  
• I still get intermittent:
  U112500 – Interrupted Communication with WAM
  

Additional ASDM codes:

• C100154 – Vision System Camera Missing Calibration
  
• C1A6754 – Forward Looking Sensor Missing Calibration
  
• C1A6778 – Forward Looking Sensor Alignment Incorrect
  

Things already done:

• Cleaned all connectors with CRC electronic cleaner
  
• Dried passenger floor area
  
• Verified power/communication came back
  
• Cleared DTCs multiple times
  
• Ran OrBit calibration procedures successfully
  
• Battery support at 14V during procedures
  

Questions:

1. Does a used WAM module on SPA Volvos require VIDA software download/flash even if the part number matches exactly?
   
2. Is the OrBit ASDM calibration enough, or does VIDA need to perform camera/WAM initialization?
   
3. Does the system require an extended drive cycle before the camera image returns?
   
4. Has anyone had the camera remain black even though WAM communication came back online?
   
5. Could this still be a MOST/coax/camera feed issue rather than module programming?
   

Any advice from someone who has swapped a WAM module successfully on SPA XC90/S90/V90/XC60 would be greatly appreciated.
Thanks!

  Screenshot 2026-05-20 171719.png (Size: 111.16 KB / Downloads: 61)

  Screenshot 2026-05-20 170529.png (Size: 150.32 KB / Downloads: 62)

  read out 1 camera volt .png (Size: 186.4 KB / Downloads: 62)

  camera alignment 1.png (Size: 261.05 KB / Downloads: 63)

  camera 1.txt (Size: 187 bytes / Downloads: 0) ]]>