Posts: 7
Threads: 2
Joined: Oct 2024
Reputation:
0
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?
Posts: 6
Threads: 0
Joined: Nov 2024
Reputation:
1
I'd guess the actual error is still there. They shouldn't come back otherwise.
Posts: 7
Threads: 2
Joined: Oct 2024
Reputation:
0
(05-26-2025, 03:12 PM)Steffe Wrote: I'd guess the actual error is still there. They shouldn't come back otherwise.
Well, the issue is not that the error comes back, rather that Orbit was unable to clear them in the first place. Tried multiple times and the errors were all "stacked", starting with wheel speed sensor out of range and hence many other systems failing.
But nothing was actually broken, it was just that we had car in gear on lift without placing it in dyno mode.
Using VIDA I cleared all codes in first try. And never came back of course.
So, either way there seems to be a situation where you have numerous codes and Orbit is not able to clear them all. Maybe a sequencing issue? Or other dependencies?
Posts: 59
Threads: 3
Joined: Sep 2023
Reputation:
11
Speed sensor errors, can be cleared after you drive the car with 5+ km/h. In some cases Vida will not clear the codes until you drove the car (BCM must read the speed correct to all wheels). Or you can clear the codes after the car sit 3 minutes in standby, and ecu's goes to sleep
2019 Volvo V60
Posts: 7
Threads: 2
Joined: Oct 2024
Reputation:
0
(05-28-2025, 03:23 AM)paunionutz Wrote: Speed sensor errors, can be cleared after you drive the car with 5+ km/h. In some cases Vida will not clear the codes until you drove the car (BCM must read the speed correct to all wheels). Or you can clear the codes after the car sit 3 minutes in standby, and ecu's goes to sleep
Good point - when driving the car ( and after resetting the codes through VIDA) it took about 15 seconds for the speedometer to work again!
Pretty wild feeling to see "---" for the speed reading.
Posts: 516
Threads: 47
Joined: Jan 2023
Reputation:
116
05-28-2025, 02:47 PM
(This post was last modified: 05-28-2025, 02:50 PM by Power6.)
TL;DR This should be a resolved issue with OrBit update releasing today (5/28/25)
OrBit should clear all codes! I think I am aware of this, what you experienced seems to be a problem that has come up occasionally with OrBit, recently. I am not sure when this may have started. I was able to reproduce it and the issue seems to come from the car, at least the cases I dealt with from users and how I was able to reproduce it myself. But in those cases, even other tools had a problem clearing codes, it wasn't necessarily OrBit specific issue but a state the car was in, like a glitch on the VCM gateway where it is not forwarding broadcast messages to all the modules in the car. Comparing VIDA is harder since it does about a million things when first connecting the car, before you get to the point you can clear codes, one of those things may snap the VCM out of it's funk and resolve the issue when you later clear codes.
Anyways enough technical mumbo jumbo...I was able to work around the issue and resolve it with an updated process, so OrBit will deal with this issue when it happens. I am releasing an update today that has updated DTC clear process that should resolve it.
NOTE: I am sure it's not the case here, but for others looking on, specific codes that "won't go away" after clearing, is NOT usually a case of the tool doesn't work! If a condition continues to exist on a module, that trips a DTC to set, when that DTC is cleared, it will immediately set again. You can tell this by the time stamps looking at the detailed code report, after clearing DTCs you will see the code that "wasn't cleared" has a new updated time stamp, because the code WAS cleared, it has just set again because the trouble condition still exists. As others have mentioned above, there are some error conditions that won't clear until you operate the car.
Posts: 7
Threads: 2
Joined: Oct 2024
Reputation:
0
(05-28-2025, 02:47 PM)Power6 Wrote: TL;DR This should be a resolved issue with OrBit update releasing today (5/28/25)
OrBit should clear all codes! I think I am aware of this, what you experienced seems to be a problem that has come up occasionally with OrBit, recently. I am not sure when this may have started. I was able to reproduce it and the issue seems to come from the car, at least the cases I dealt with from users and how I was able to reproduce it myself. But in those cases, even other tools had a problem clearing codes, it wasn't necessarily OrBit specific issue but a state the car was in, like a glitch on the VCM gateway where it is not forwarding broadcast messages to all the modules in the car. Comparing VIDA is harder since it does about a million things when first connecting the car, before you get to the point you can clear codes, one of those things may snap the VCM out of it's funk and resolve the issue when you later clear codes.
Anyways enough technical mumbo jumbo...I was able to work around the issue and resolve it with an updated process, so OrBit will deal with this issue when it happens. I am releasing an update today that has updated DTC clear process that should resolve it.
NOTE: I am sure it's not the case here, but for others looking on, specific codes that "won't go away" after clearing, is NOT usually a case of the tool doesn't work! If a condition continues to exist on a module, that trips a DTC to set, when that DTC is cleared, it will immediately set again. You can tell this by the time stamps looking at the detailed code report, after clearing DTCs you will see the code that "wasn't cleared" has a new updated time stamp, because the code WAS cleared, it has just set again because the trouble condition still exists. As others have mentioned above, there are some error conditions that won't clear until you operate the car.
That is great news! (on the update)! Your explanation makes perfect sense.
And just to be clear - I have used the old VIDA (2014) for a decade on our V70R and the new VIDA (on this V90) for close to two years now. I have even installed trailer module software (which is a bit challenging here in the US since it was technically not available for the car etc).
Swedespeed trailer hitch install
So yes, I'm not that guy, that has an issue on the car and then thinks resetting the DTC will make the underlying problem go away.....
And let's be clear - I went from no codes to a long laundry list - including all four wheel speed sensors being out of range. And pretty much every code you can imagine above that (no AWD, no ABS, no DTSC, no traction control etc.). To then go back to zero codes when clearing in VIDA. Nothing, nothing, was physically altered on the car. An it has been running great since.
|