I get this DTC. I've tried to clear it but it always stays.
I would say sensor is working as expected because lights turn on automatically when it's dark or entering tunnels (displays dims as well).
Does anyone know what could it be?
The buttons in the trunk don't work anymore ( lower/raise the suspension to ease the cargo load ).
Can Orbit help me debug the problem ?
I replaced the buttons with known working ones and still nothing ...
The drive modes change raise and lower the car as expected .. nothing on that side.
Easy in/out settings works also ...
Just the buttons in the cargo don't.
Car: XC90 2017 D5 EU R-Design
OrBit version 1.1.3 is released. It is a patch release for some refinements to new model support and a fix for issues with some cars clearing DTCs.
(Latest version of OrBit can always be downloaded here: https://app.spaycetech.com/orbitupdate/download) The "update notification" in OrBit will be sent later, but you can download the updated install right away from the link.
Improvements and Fixes:
VGM handling improvement - Fixed some issues with diagnostics when the VGM PIN is not saved for the car with 2025 models.
Updated post programming process for 2025 models - The TRM module is restarted to re-learn the config from the car when the TRM is installed.
Improved DTC clearing process - Revised the DTC clearing process to work around issue with Sensus cars when the VCM is stuck in a state it doesn't send the broadcast messages to all modules in the car. Overall process is improved for all cars to ensure code clear commands are recieved by all modules.
I've read somewhere that with VIDA it's possible to activate gear number display in drive (so number next to D, not M).
It should last only for that session and should return to default (no display) after shutdown.
Is it possible to do this using OrBit?
And if it's possible is there any downside to this, does transmission enters some service/diagnostic state?
Would it be bad to drive with this enabled for longer periods?
I really hate no having that gear number by default.
Orbit program does not display errors while waiting.
(I had a problem with the radiator fan and Orbit does not show errors, other scanner so it was an expected error)
After doing some work running the car (2019 V90 T6) on a lift, we got a number of error codes (as in a long laundry list). Almost all based on wheel speed sensors not reading correctly. No surprise there!
When trying to clear the DTCs that did not work. Tried a few times and then gave up and signed up for VIDA for a min 3 day subscription. VIDA was able to clear them all right away.
Question are: Is there a limitation of what kind and/or amount of DTCs that Orbit can clear?
Hey,
Is there a way to influence the exhaust flap control?
Normally it doesn't make any difference, but I have a Bastuck exhaust where one side is straight-through and the other side is dampened.
And the straight-through is pretty to loud, so I've adopted Volvo's exhaust flap control, but it behaves strangely without any logic (for example, it opens when you downshift a gear with the steering wheel buttons in ECO/PURE mode, etc.) - would be cool if there's a possibility to do this through Orbit?
Hi guys, I really need some help.... It all started after car did not crank. No codes, just no crank. Before this, the car has been worked OK for months.
While trying to get the car to crank, disconnected steering column lock (SCL) connector, and tried to configure it out as here in forum somebody instructed.
Now starting Orbit, to start configure, came a warning “Your CM has been updated since you last used OrBit and Orbit does not have an updated OEM… Use Backup Logic button… to take a backup”. Made the backup and configured the steering lock out. Did not help on cranking, but car finally cranked after fiddling with the wires back of the starter motor. So good old mechanical issue :-), probably.
But then the problems started. Put the SCL back, reconfigured some old configuration, but had airbag red symbol, gearbox did not change gear etc. Configuration page showing just “FF”s. See my other post.
Next, configured again with a known older saved configuration file, got car somehow working, but getting still errors on SRS, air suspension, start-stop system. DTC codes saying configuration errors from many modules, e.g. from SRS. Also RML & RMR not connecting.
Strange thing now is, if I try to read DTC codes / live values with other tools, like Vdash or V-tool (iphone), the tools don’t find all the modules, just one or two?? Orbit reads codes from many modules. Like the "directory of modules of this car" is messed up?
Now new try today. With an old laptop having older Orbit version (0.99), older conf files (idea was to use that PC to revert to OEM) when starting Orbit, again “Your CM has been updated since you last used OrBit and Orbit does not have an updated OEM… Use Backup Logic button… to take a backup”, but the backup just did not succeed, and can not change configuration, not any saved, not back to OEM.
Now back to the newer laptop, updated profile, no errors. But all writes to car fail in the same way: “Negative response from RML(and RMR) not awake“, and at the end “Timeout starting SBL on the CEM!”.
Any ideas, what next? I guess the coding without that SCL module connected started this show. But what are my options now?
I tried to change configuraration with steering column lock disconnected. Some errors and retries...back to OEM and back to previous, now in a state that main screen shows "Configuration Error" in red. When clicking this, see below?
Car does not really work, stuck in 3rd gear, ABS, airbag, suspension etc errors.
On the configurator page, all items, both "Current Setting" and "New Setting" show "FF Parameter Error". When programming, RMR, RML and WAM not awake...
How should I continue?
__
Central Config Errors: YV1LC.......
(05/24/2025, 17:17:31)
Total config errors: 10
Item 001: ff value is invalidItem 008: ff value is invalidItem 012: ff value is invalidItem 013: ff value is invalidItem 019: ff value is invalidItem 022: ff value is invalidItem 024: ff value is invalidItem 030: ff value is invalidItem 064: ff value is invalidItem 065: ff value is invalid
