v0.3.4 has been released to enable additional ECUs for flashing (other than CEM)

HCML and HCMR modules enabled for flashing, and OrBit has been updated to allow more modules to be added as they are tested.

• HCML and HCMR are now allowed for flashing on the ECU Tools tab (user provides the SBL and software VBFs to flash to modules)
  

• OrBit updated to refer to configuration files for allowed modules to flash, to enable updating via config files in the future
  
• HCML and HCMR added to the list of modules that OrBit allows to flash
  
• All modules continue to be enabled to allow attemtping to "backup" from the ECU.
  

Does anyone here have workshop manuals for the 2022 volvo xc90 b5?


Regards,
Marian


Sent from my iPhone using Tapatalk

v0.3.3 has been released to address an issue for "iCup" Android based cars with VGM Firewall

Some functions fail due to previous releases removing VGM frewall disable:

• ABS Clear Config (ECU reset)
  
• Hard ECU reset on some ECUs
  
• Clear DTC on some ECUs fail when VGM firewall not disabled
  

• Add VGM unlock and firewall disable process to DTC Clear and Hard ECU Reset process functions
  

There are two settings to get it work. 

036  ADJUSTABLE SPEED LIMITER      03 ASL & AVSL

149  ROAD SIGN INFORMATION   > Select the one with with Speed Limit Adaption (SLA) based on your country. 

This will give you speed limiter option in cruse control settings on the dash and there will be button on SENSUN. If the button on SENSUS is enabled, the speed limiter will be updated according to road signs. If not enabled driver can set any top limit manually.  

There is also setting SPEED WARNING. > do not enable this for US / CAN.  Enabling it breaks the actual over speed driver warning in SENSUS. 0 or +5 miles /hour.

Hey all, I created some diagnostics forums as more diagnostic stuff is added to OrBit.

Once thing I am looking at, is the "battery replacement" process, which is supposed to essentially reset the "learning" of the capcity and charging behavior of the battery. I have the process, it will be added to OrBit.

What the "battery replacement" does in actuality, is simply reset the "State of Charge" and the "Time in Service" of the battery.

You can already read this data in OrBit, so I've been looking at my car:

   

On my car, the battery "time in service" is 0 days today, and yesterday it was 2 days. I expected that the data would reflect the actual age of the battery (original to my car since 2019). But it doesn't seem to. I do a lot of things on my car though...not clear the battery life, but lots of other testing ;-) It makes me wonder the value of resetting the "battery time in service" if it is getting reset anyways. I will still add it, as it's a function that VIDA does and is supposed to be needed.

But still I am curious..any other OrBit users want to check this on your car, see what your battery time in service reports??

This is a quick release as I start adding some more diagnostics and service functions.

This should be the first update that folks will get notified the new version is available (since update notifications added in 0.3.1)

"Operation Mode" is added now. The interesting/useful parts of this are:
If a car has gone into "Crash" mode, OrBit can reset it to "Normal"
"Dyno" mode can now be set on the car, for dynamometer testing

Changes:

• Add "operation mode" read and setting. When connected to the car the current mode will show on a button
  
• Clicking the button for operation mode brings up a dialog to choose and set the operation mode
  
• Existing service mode for the EPB has been condensed into a single button to be consistent as more service functions are added
  

Hello All,
Would someone be able to share with me the readout of their Volvo with Android system 2022+, you can remove the VIN or any info in there.
Usually you can get it from VIDA


Thank you

Example:
   

Guys,
 if I click on "e brake service mode" does that release the rear brake cylinders and can I change the brake pads?

Modern Volvos/Polestars that OrBit works with all use "DoIP" - Diagnostics over IP connection. Which, for us DIY-ers, is the fancy way to say the connection uses Ethernet, i.e. a wired network port on a computer. Dealers use WiFi connection but us consumers do not have access to that.

The good: The adapters are cheap and all you need is a computer with a common wired network jack
The bad: There is no specific hardware like "DiCE", there are thousands of different hardware variations of the common network card, which is subject to all of the "goings on" in Windows to do with drivers and networks.

Windows has network security built-in (Defender anti-virus and firewall) and there are 3rd party anti-virus and firewall security tools that one could have loaded on their computer. Sometimes these things can cause issues with a program like OrBit (or VIDA, or VDash), which must listen for "incoming" connections on the network to find the car, and generally use the network connection in a slightly different way from typical program that connects to the internet.

If OrBit will not find the car or fails to connect to the car, there are some basic steps to check that OrBit is not being blocked by security features:

1.) FIRST time running OrBit you should see this message:
   

Most cases leaving the default check box and clicking "Allow Access" here will suffice, it can be helpful to make sure both check boxes are checked and click "Allow Access". This action creates allow rules in Windows Defender firewall that will allow OrBit to work. Clicking "cancel" here will not create the rules, and you will probably have a problem connecting to a car. You only get one chance for this "automatic" process, Windows will not ask you again.

If you suspect you missed this message, or you want to check/add the firewall exceptions needed for OrBit to work:

2.) Check OrBit has firewall rules in Windows Defender to allow network connection:
Click on start menu and type "Windows Defender..." and open the Windows Defender Firewall settings as shown
   

In the Windows Defender settings, select "Inbound" in the left tree, then scroll down in the middle pane to find OrBitRun.exe, to verify the app is allowed for incoming connections, ideally on both "public" and "private" networks.
   

3.) To add OrBit to allowed apps in Windows Defender:
Open Windows start Menu and type "Windows Security" to find and open Windows Security app. Click on "Firewall and Network protection"
   

Click "allow an app through firewall" link. In the dialog window, click "Change settings" button, then scroll down to find "OrBitRun.exe" and check the "private" and "public" network options. Click OK to save the setting and close the window.
   

If you don't see OrBitRun.exe you can add it via the "Allow another app" button. In that dialog click "browse" and paste the following to quickly find the OrBit app directory: "%localappdata%\OrBitApp"  Then find OrBitRun.exe in the directory to choose it, and follow as above to check the boxes to allow OrBit to use the network.


This should resolve most issues when OrBit fails to find or connect to a car. 

NOTE: This assumes you are using the default Windows Defender Security. If you have 3rd party anti-virus, security or firewall running, those programs may be blocking OrBit. We can't give specific advice on those, there are just too many to cover. But essentially you need to verify: OrBitRun.exe is not being restricted in any way, and is allowed to listen on network for "incoming" connections. Typically some sort of "whitelisting", "trust" or "rule" may need to be added to allow for that.

Does anyone know what this means?
It's turned off in my 2016 XC90 D5, and I would like to know what it means.

Marcus