| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 4,591
» Latest member: Sibdog
» Forum threads: 1,191
» Forum posts: 8,839
Full Statistics
|
| Online Users |
There are currently 231 online users. » 0 Member(s) | 231 Guest(s)
|
| Latest Threads |
VDDM height sensors
Forum: Chassis
Last Post: damachone
8 hours ago
» Replies: 4
» Views: 398
|
How to buy used key fobs ...
Forum: OrBit How-To Guides
Last Post: Dennis3258
10 hours ago
» Replies: 60
» Views: 63,726
|
UK XC40 2020 wiring diagr...
Forum: Misc
Last Post: UK_Tony
06-11-2026, 07:24 AM
» Replies: 0
» Views: 74
|
Second config change to S...
Forum: Bugs / Feedback
Last Post: jos
06-10-2026, 07:37 PM
» Replies: 18
» Views: 1,501
|
Ambient 12V.
Forum: Lights
Last Post: jos
06-10-2026, 02:50 PM
» Replies: 8
» Views: 274
|
New AdBlue Injector adapt...
Forum: OrBit Q&A - Ask your questions here!
Last Post: Dennis3258
06-09-2026, 05:47 PM
» Replies: 0
» Views: 95
|
Retrofit Subwoofer on Hig...
Forum: Retrofitting
Last Post: Pliind
06-09-2026, 03:12 PM
» Replies: 65
» Views: 46,845
|
Driver Seat Heater proble...
Forum: Misc
Last Post: krzysztof.pyzel@o2.pl
06-08-2026, 10:22 PM
» Replies: 5
» Views: 881
|
Failing VCM?
Forum: Car Connectivity
Last Post: TheRiflesSpiral
06-08-2026, 07:11 PM
» Replies: 18
» Views: 1,023
|
2026 Volvo XC40
Forum: Bugs / Feedback
Last Post: A1D1
06-08-2026, 04:18 PM
» Replies: 3
» Views: 842
|
|
|
| Polestar VCU1-U116E00 update with SP: 32406479 |
|
Posted by: Amphicar770 - 06-01-2026, 02:45 PM - Forum: Service Functions
- Replies (2)
|
 |
Hello all,
My Polestar has started displaying "Disconnect Charging Cable" while no charging cable is attached. This, in turn, immobilizes the vehicle.
Apparently, there is a TSB 36404.4 for applying OBC software SP: 32406479
Trying to avoid a trip to the Stealer. I do have, and have used, Orbit. Is this something Orbit can do? If so, where do I find / how do I get SP:32406479 ?
Thanks.
Mike
|
|
|
| XC40 Reversing Camera Retrofit |
|
Posted by: Wattsy - 05-31-2026, 07:06 PM - Forum: Retrofitting
- No Replies
|
 |
Hi all,
After buying several wrong parts and trying to find all the information in one spot and failing, here is a definitive guide with part numbers to retrofitting the factory reversing camera. This is just the rear one, not the 360 cameras.
This is for a 2022 R-Design with Sensus
Parts Needed:
-Tailgate handle (with camera hole) Pt No: 32310006
-Camera Pt No: 32286680
-Loom Pt No: 31650607
The install instructions can be found here: Parking assistance, camera, rear - XC40 2022 - Volvo Cars Accessories
The hardest part is getting cable through the boot(trunk) cable glands. After this, just run the loom, I managed to do it without taking all the trims off. Just find a way to run the loom to the centre console. Once there, I managed to put a long allen key to pull of the trim(the bit with the volume knob) its stiff, but will come. Once there, plug the loom into the correct socket.
Once all connected, go to Orbit, and activate 154. Then option 09 'Camera Gen 2 Always in Reverse''
Hope that helps!
|
|
|
| Volvo XC90 air suspension / SUM calibration issue |
|
Posted by: liushaohuai5 - 05-25-2026, 07:55 PM - Forum: OrBit Q&A - Ask your questions here!
- Replies (2)
|
 |
Hi everyone,
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:
- 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?
- 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?
- 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.
- 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?
- 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.
|
|
|
| Tailgate Kick Sensor |
|
Posted by: juzzmee - 05-25-2026, 07:44 AM - Forum: Misc
- Replies (2)
|
 |
Hi,
Is there a setting in Orbit for the kick sensor?
Kick sensor is suddenly not responsive and my workshop was telling me that after I replaced my read bumper lower trim, I should reset my kick sensor.
It did work once when i was wiping down the rear bumper after washing the car.
Does it make sense?
|
|
|
| Failing VCM? |
|
Posted by: TheRiflesSpiral - 05-23-2026, 01:36 PM - Forum: Car Connectivity
- Replies (18)
|
 |
I'm troubleshooting an issue(s) with my wife's 2016 XC90 T6. Or, at least I'd like to be troubleshooting better than I am.
I've only sporadically been able to connect with OrBit (never with VDash) to get any information from the car. When it does connect, the connection quality ranges from Red at less than half on the little indicator bar, to Orange at about 2/3 up. I've never seen a green connection with OrBit.
Almost always, I get "VOE connection is present but the car is not responding". When I run a WireShark trace on my VOE adapter's Ethernet port, it indeed shows "50 Vehicle identification request" but no response from the car. In fact, I see a large number of packets from 169.254.158.215 (my laptop's IP) to the car but not a single one from the car to my laptop.
I don't want to pay for a VIDA subscription until I can reliably connect with either OrBit or Vdash... $100 on a failed experiment is a bit steep.
My understanding of how these units fail is that they just die. No connection at all, just a dead socket. This seems to be something different since I can, very rarely, get a (poor) connection.
A battery reset is my best chance at connecting... in all prior instances where I've been able to connect, I've previously done a complete shut down and disconnect of my laptop, then performed a battery reset (disconnect the negative battery terminal for a few minutes). A suggestion on the OrBit FAQ suggests pulling the backup battery for the VCM, to do a true power-down. I did that and left it disconnected.
That allowed me to connect once, but not since. (I have the "Volvo OnCall Service Required" message now, which makes sense.)
Anyway, before I drop $700+ on a replacement VCM, I'd like some reassurance this is actually a failing unit, not just noise in another system.
Thanks for any help you can lend!
|
|
|
| Confused about what to choose on ACC, Config Wizard, PA, Lane change assist, traffic |
|
Posted by: 83Greven - 05-22-2026, 05:06 PM - Forum: Misc
- Replies (5)
|
 |
Hi guys!
Im really confused about what to choose and what's working.
XC60 MY18 with full tech package - 360 camera etc (EU)
OEM
023 - Cruise control Start & go level 1 - now changed to level 2
145 - Traffic jam assist with assist level 2 - there are up to level 4 - could the car use it?
148 - Curve speed support - non - now changed to without curve speed warning but with curve speed assist)
312 - Lane change assist - now changed to level 4
314 - ACC version 1 - now changed to ACC version 4
Also used the configuration wizard and changed to PA/ACC 2 + curve speed assist.
What can the car use and what is unnecessary choices/levels?
|
|
|
| laptop configuration needed |
|
Posted by: Dennis3258 - 05-21-2026, 01:20 PM - Forum: Car Connectivity
- Replies (3)
|
 |
Hi all,
I am looking in to start using Orbit to change some settings of my XC40 D4 R Design 2019.
As far as I understand Assisted Cruise Control could be activated with my car.
But, the main question to start Orbit, what configuration for the laptop.
Disc space mainly.
I have a ASUS Windows 10 Celeron but disc space is absolutely minimal, after installing Windows 10 about 9 gig open space left.
Would that be enough to run the program?
Thanks advance
|
|
|
|