OrBit Forums - OrBit FAQs

What can I do with config changes on my car?

Fri, 07 Mar 2025 16:34:51 +0000

**Updated - March 2025** - This is the first version, I will add some notes later to help guide you where to look to make the changes - Andrew

What can be changed on my car?

It is naturally a frequent question for new users. It is not so easy to answer on an individual basis. What is possible, what applies to the specific car, market specific settings etc. and what YOU care about, all these things vary.

What we can do, is give you some ideas from the well known and often discussed changes to the cars. So that is below. I will note where some settings only apply to some cars and offer some guidance if you are starting here to try some of the changes. This is NOT a guide on each specific configuration or hardware installation. Some are simple changes you can do on any car, some are more complex to know where they apply. You may find more information on a specific configuration elsewhere in the forums. This is not a comprehensive list! There are more tweaks possible, surely I have forgotten some things or I don't know about. There me some new interesting things to find still...OrBit is a tool of discovery, for those that like to play and find new things.

Note: "Sensus" or "AAOS" refers to the generation of cars, by the infotainment system. If you are not sure what type of car you have, see the buying guide, at the bottom is a breakdown of the models.

Changes you can make with no equipment changes needed in the car:

Enable Pilot Assist/Adaptive Cruise Control (all cars)
Other driving aids enable/disable (some cars support, some don't for each feature, you will have to try)

Curve Speed Assist
Automatic Speed Limiter
Speed Limit Warning
Enable/Disable Intelligent Speed Assist (ISA) (late 2024+ EU cars)

Modify/remove the speed limiter (all cars)
Enable Polestar Optimization (all cars) - this one is complicated: no it does not install the Optimization software! It is only a config change. But there is some effect on some cars. You can just try it.
Exterior lights operation changes (all cars, depends on factory equipment)

Enable Adaptive Beam (AHB) for Pixel and LED headlights on North American (NA) market cars where it is disabled
Enable Bending Lights in high beam for EU/RoW(Rest of world) type LED headlights
Remove foglight restrictions - allow turn on without headlights, together with high beam
Exterior lighting logic change - enable DRL always on, allow DRL off.

Modify remote start settings (all cars) - enable/disable running lights with remote start. (No, setting "ERS by key" does not work!)
Enable Start/Stop setting memory on cars not equipped (Sensus, ICE only)
Disable Start/Stop on MHEV Mild-hybrid cars (all cars with Aisin 8-speed automatic)
Enable "Start in Pure" mode on AAOS cars not equipped (does NOT work on Sensus)
Enable/Disable Restricted or Care Key (all cars) features (orange/red key fobs)
Enable Audible locking feedback on non-US cars not originally enabled
Adjust seat heating calibration (warmer/cooler) (all cars)
Enable "Easy entry and exit" driver's seat (Sensus only)
Video playback allowed at all speed (Sensus only)
Change "Theme" in driver's display - start-up logo (Sensus only)
Enable Navigation (Sensus only)
Enable CarPlay/Android Auto (Sensus only)
Disable SCL (Steering Column Lock) on cars equipped with SCL
Adjust region settings (all cars) - change language, units displays, radio frequencies, etc. useful for imported cars
Adjust tire size and circumference (all cars) to correct steering stops and speedometer accuracy for wheel/tire changes
Adjust maintenance interval - Change from the factory set distance/time for the service reminder
Adjust the "Turbo Configuration" - You are on your own for this one…but some folks report positive results
Enable "PIP" split screen parking camera views on AAOS cars it is supported but not enabled with the latest OTA updates due to local market regulations.

Popular Equipment changes - these are changes to enable equipment you install to work:
Note: "equipment changes" means YOU are responsible to install equipment,
verify/add required wiring, etc. OrBit can handle the configuration part to make the equipment work.

Install and load Trailer Module (TRM) for tow bar wiring integration
Add TPMS sensors and switch to direct sensor TPMS system (Sensus only)
Add interior light dimming thumbwheel rheostat (2023+ cars removed this feature)
Install ignition switch with drive mode roller (Sensus Only)
Add "high" level interior lighting
Add paddle shifters (through 2022 model years)
Add heated steering wheel
Add fog lights to the car not equipped
Audio system swap, High perf to H/K to B&W, add subwoofer etc.
Add interior alarm motion sensor (IMS), tilt-sensor siren (BBS)
Driver's display upgrade 8" to 12.3" unit (Sensus car)
Headlight swaps: US<>EU/RoW type headights, non-bending to bending type
Seat swaps: Add ventilated/heated/massage type seats to car not originally equipped
...There is no end to equipment swaps, if it is something Volvo/Polestar installed on the cars, you can enable the equipment configuration with OrBit, given you have physical equipment and wiring correctly installed in the car. Some swaps are easy, some swaps are very difficult. Do your research.

What do I need to buy? OrBit pre-purchase information

Fri, 02 Aug 2024 17:23:48 +0000

If you want to purchase OrBit and change config (aka coding) on your Volvo or Polestar you have a few options. This is a quick guide for those who want to know what to buy, without too much of the technical details contained in other FAQ/DIY.

You need 2 things to be able to change config in the car:

1.) Software to change config: That's OrBit if you are reading this guide.
2.) Access to change config: You need PIN(s), like a secret password to access part of the car. On older cars (Sensus infotainment) you need the CEM PIN. On the newer Android (AAOS) infotainment cars, you need the CEM, plus the VGM PIN. (See further Q&A below if you are not sure)

If you already are familiar, and you have the PIN(s) you need, you can buy an OrBit 1yr subscription ($100), enter your PIN(s) and you are all set. This is the first option on the plans page. (Visit the plans page on the website to see the options to purchase OrBit)

If you don't already have the PINs for your car, you need to get them. There are a couple ways to get PINs:

1.) The "easy button" way: Buy OrBit with optional PIN Retrieval Service. These are the second and third options on the plans page, OrBit 1yr w/PIN for Sensus for Sensus cars, and OrBit 1yr w/PINs for Android for Android cars. Buying with the PIN(s) will be everything you need to change config on the car. (If you are not sure if you have Sensus or Android system, see below Q&A)

2.) The DIY way: If you have access to the factory VIDA diagnostic tool, and can order software for the car, you can get the PIN(s) on your own. There is a DIY process to guide you, using VIDA together with OrBit, to crack the PIN(s) you need. Getting access to VIDA, is not always possible. It is only available to car owners in North America (US and Canada) and difficult to access otherwise. If you do have access to use VIDA, it will cost you about $100 to DIY with a 3 day subscription. If you get the PINs DIY, then you can buy OrBit 1yr subscription and have everything you need.

Q&A:

If I buy with the PIN(s), how do I get my PIN(s), is there anything I need to do with the car? No you don't need to do anything, after purchase we will request the VIN of the car. We will send you the PIN(s)

How long does it take to get the PIN(s)? It takes about 24 hours, once you have provided your VIN. Most cases it's sooner, but we commit to within a day.

Do I have to pay more each year for the option with PIN(s)? No the "w/PIN(s)" option is a one time option at purchase, along with the OrBit subscription ($100/yr). You only need to get the PIN(s) once, they do not change for the life of the car.

Can I change config on another car with OrBit? Yes you can. It needs to be licensed, the OrBit subscription includes one car to be able to write config. You can add additional car by VIN to allow writing config. Adding a VIN is $50/ea, one time only. You can add as many additional cars by VIN as you like. The only recurring cost is the $100 OrBit subscription, which covers updates, support, etc. As long as you maintain that subscription, you maintain all additional VINs added to your license.

Can I use the PINs with additonal cars? No, the PINs are unique per car, for each car you write config to, you need the PINs for that car.

How can I add a VIN to my OrBit license? Send and email to orders--spaycetech.com with what you need, and we will take care of it and send a payment request specifically for what you need. You can add VINs and also get the PIN(s) retrieved.

What happens if/when my license exprires? You will not be able to write config to the car if your subscription is not renewed and your license expires. You CAN however, "Restore to OEM" (put the car back to original config) with an expired license.

What can I do on a car that is not licensed in OrBit? You can connect to any car with OrBit. If it is not licensed, you can read and clear codes (DTCs). You can also enable and disable service mode for the Electronic Parking Brake (EPB), reset the Maintenace interval, and reset the engine oil level.

What else do I need to use OrBit? You will need a Windows 10/11 PC (Windows ARM devices currently not supported), preferrably a laptop, with an ethernet(wired network) port, and an adapter to connect to the car. If your laptop does not have a network port, a USB network adapter can be used. The adapter should be a "Volvo VOE" adapter. Most folks use one of the many "clones" on the market, there are too many to reccomend a specific one, however they are inexpensive, simple, and generally reliable. Look for compatibility with Volvo VOE, and also any BMW ENET or compatible wired adapter should work as well. The laptop will need Internet access to download OrBit and to be able to start and log in to OrBit application.

Is my car Sensus or Android? Most may be already familiar with which infotainment system they have. If you are new to Volvo/Polestar, it may not be obvious. Here is the list of models and years for each system:

Sensus:
2016-2022 XC90
2017-2021 S90, V90, V90CC
2018-2021 XC60
2019-2022 S60, V60, V60CC
2019-2022 XC40 (ICE/PHEV models)
2019-2022 Polestar 1

Android(AAOS):
2023-up XC90, S60, V60, V60CC
2022-up XC60, S90, V90, V90CC
2021-up XC40, C40 (only EV models)
2023-up XC40 (ICE/PHEV models)
All Polestar 2

Excel list of Configuration Items

Sun, 18 Feb 2024 15:59:27 +0000

Attached is an Excel file with all the configuration items. It will be updated when new revisions are created.

Next step will be to add a Category column so we can group the different options. This is what I am thinking:

Core (Should not be changed)
Lighting
Audio & Video
Wheels
Driving Assistance
Safety
HVAC

Eventually we could match the Forum sections with these to make it easier on where to start threads.

ConfigItems_2023-02-18.xlsx (Size: 61.51 KB / Downloads: 2005)

Do I need to lock the car and let it "sleep" after write config with OrBit?

Wed, 02 Aug 2023 13:46:38 +0000

Sometimes folks ask if they need to lock the car and leave it for a short time, until the screen "goes to sleep", after they flash a config change with OrBit. The short answer is no, you do not need to do that.

I think the need for this comes from using other software to change Volvo config. When you change configs in the car that change the menus or buttons that show up in the (Sensus/Android) center infotainment screen, the infotainment unit (the IHU) needs to read the config changes and apply them. When OrBit flashes the car, it always restarts the IHU in the post-programming step, just like VIDA does with every software flash. Changes to the Sensus/Android system menus and buttons reflecting a new config should take effect right away with the IHU restart.

You should only need to do the "lock and sleep" for troubleshooting a config change where you don't see some expected menu, button, or display show up in the screens in the car. It is a good step to try leaving the car locked for a bit, before assuming that your config change did not work or is not compatible with the car.

What are PINs, why do I need a PIN, how do I get a PIN?

Sun, 16 Jul 2023 17:29:25 +0000

If you are new to Volvo/Polestar you may have questions about PINs...

The way the car and ECUs are secured in a Volvo is similar to other manufacturers, but also some things are specific to the way Volvo does things.

OrBit can change "configurations" or also what is sometimes called "coding" on a supported Volvo or Polestar car. That is the reason 99.9% of people buy OrBit ;-) OrBit is the tool, but also you need security access to your car to be able to modify configuration. Various modules and parts of the software in the car are secured with something called a "PIN" in the Volvo world. PINs are like a password. There are many PINs to access different parts of the car, but for most you will be concerned only with the PINs to change configuration.

The configuration is stored in the Central Electronic Module (CEM), and access is required to the CEM that allows that config to be changed. Volvo was has been using "unique" CEM PINs for a many generations of cars. Other mfrs you are familiar with may have not used "unique" access secrets in the past, but most have started to do this lately, it has become more common. Each car has a different CEM PIN. Volvo knows it, VIDA uses the PINs for service access, but owners are not given security access secrets to their own car. To get access you need to obtain the needed unique PIN(s) for your own car. There are two different requirements for PINs needed within the "SPA" and "CMA" chassis generation of Volvo and Polestar.

1. "Sensus" car - All Volvos (and Polestar 1) SPA/CMA with the Sensus infotainment system.

These cars need the "CEM PIN" (this is the common term as it is known in the Volvo world).

2. "Android" car - All Volvos (and Polestar 2) SPA/CMA with the newer Android (aka Google, AAOS, or "iCup") infotainment system.

These cars need the "CEM PIN" same as a Sensus car.
And also they need a "VGM PIN", required to unlock a new Diagnostic Firewall for advanced functions, this was introduced with the Android system.

You have a couple options normally to obtain the PINs:

"DIY" process where you subscribe to the service software (Volvo or Polestar VIDA) then run a process on the car with that and capture the PIN information which you can "crack" with OrBit. That process is described here: https://forums.spaycetech.com/showthread.php?tid=2. This is a good process for those who have access to VIDA, North American users especially and some others in the rest of the world may have access though that is more difficult where there are no right-to-repair laws for consumers.
The "PIN Service" option, we can get the PINs for you, no work needed on your part. We get the PINs needed with the VIN of the car.

You're in for about $100 USD to DIY, for the 3 day subscription to VIDA based on what a North American car owner has available. The PIN Service is $125 for the Sensus car (CEM PIN) and $225 USD for the Android car (CEM/VGM PINs). So you can decide on time vs money what's worth it for you. In any case, getting the PINs is a one time thing only. The PINs will not change for the life of the car, even hardware replacement (like new CEM installed with VIDA) the same PIN is written to the CEM.

There are other ways to obtain PINs that are out of the scope of OrBit. Some shops have hardware and tools to read modules like the CEM when removed from the car, and can retrieve the PIN information directly from the hardware. If you know a shop that can do this, or if you already have PINs obtained from this method or any other way, you can enter the PIN(s) into OrBit.

Why do I see "Unknown value" for some config items?

Fri, 07 Jul 2023 20:04:17 +0000

This a repost from another thread, but I am putting here so when people have this question, they can find the answer right here in FAQ forum:

When you see "Unknown value" for items in the Configurator table in OrBit, you may worry that something is wrong with your car, with the config, or with OrBit. You should not worry, this is expected and normal for Volvo config!

TL;DR This is totally normal, there is no problem.

So you don't believe me and you want to know why ;-) Well...OK then...

There are 2 reasons you see "unknown value" let's deal with the "00 Unknown Value" first:

This configuration we work with in the car "Central Configuration" is a system Volvo has developed over many years. The SPA model introduction updated the system with the idea of "Configuration Logic". The result is what you see in the table, the Config Items in OrBit is the list of configuration from the car. The system is designed to be extensible. It would be an awful lot of work if Volvo needed to re-design their central configuration system to add support for a config item every time they add a new feature or option to their cars. That would be a huge waste of resources. So they don't do that. They designed a config system that can be added to over time without affect the "earlier" car. A car built with a "new" option in 2023 that didn't exist in 2016 can use the same CEM with the same central config system, even the same software being used on the CEM. Other modules that read the central config can use the same software updates in the old car and the new. Auto mfrs really like being able to reduce the number of software "versions" they need to maintain, it probably saves a ton of needless cost.

How do they do that? The config list is a list of pre-defined fields, items 1-504. Not all of them are used, say 350 of them are today, leaving plenty of "empty" items that can be used later. As Volvo adds a "new" item, they define what it is, and add rules to "config logic" to set the item and those CEM software updates are released.

How does Volvo add a config item for a feature without screwing up the earlier cars CEMs when software is updated? The config system is designed, such that a car not "using" a config item, the config is set to "00". That provides backwards compatibility. Any "new" item added, the existing cars will be known to have "00" value for that item. If there is no "rule" for that unused item in the central config logic in the CEM, that item is set to "00"

When you see items set to "00 Unknown value" that is simply a config item that is unused on your car. The description is what OrBit inserts as a placeholder there. Maybe the description could be less worrying, but hey I took that description from Volvo, blame them lol. It's simply an item that your car doesn't use.

Before you ask..a mini FAQ:

But my car is a 2023 surely it uses all the items? I'm oversimplifying things, we don't know all the permutations of config items, abandoned items, planned for the future etc. The point is still the same, it's just a config item not used in your car.

But I have an electronic parking brake/audio system/speakers and my car has "unknown value" for some fo those settings? Slow down there, we don't know what all items are used for what specifically. All we have is the description. Once again, if your car has "00" for a value there, it's not used on your car.

"Unknown Value" when it's not "00"

This is a different case. When there is a value other than "00" and you see "unknown value" this just means that your car has a setting that OrBit doesn't hav a description for in it's config database. This can happen, I've scraped together everything I could for every item from all the sources I hav, but still new values for new settings can be added by Volvo to an item, as we know, the system is extensible. If OrBit doesn't have a description for that item, it inserts the "unknown value" description with the value, so you can see what the value is in the Configurator table even though we have no information, as well as that is used under the covers in OrBit to preserve any settings that we don't already know about, so the functions like "load settings" work from a saved file later, we load the settings in, with the proper value, even if we don't have a description for that item value. I have discovered some of these and added new value and description to the database to define them as an option to set. Frequently we can figure them out from comparing some cars config and variant codes.

This was a really good question, it's come up before, so it's good to give those who want the "full story" the information, from what I have learned about the system. I hope that helps quell any fears that "unknown value" means that is any sort of config problem. It doesn't.

How does OrBit config affect OTA updates? Will my car get blocked?

Tue, 16 May 2023 01:49:03 +0000

Questions come up from time to time, on how OrBit config interacts with OTA updates, and if your car can get blocked. The safest advice has been to "Restore OEM" before accepting an OTA update. That is always the safest thing to do.

We now have enough acquired knowledge to give a better idea of how these things play together. Note always there is a disclaimer that Volvo can change anything at any time without consulting me, this is just to the best of our knowledge currently (May 2023)

Sensus: Sensus updates are only maps and Sensus apps updated OTA. There is no worry of OrBit config being present when you accept updates. Sensus app updates do update the software list in VIDA for the car, with the part numbers of the updated app(s) but no config is sent up or compared.

Android: OTA updates are more extensive here covering the AAOS system and flashing some modules. Like Sensus it has been found there is no worry of OrBit configs being present when an OTA update is accepted and installed. Config is not sent up or compared in the OTA update process. However modules can be flashed as part of an OTA update, including the CEM so *note*: running an OTA update, sometimes includes a flash of config files to the CEM, which can wipe out any OrBit configs. You can use OrBit to change config items back to the settings you like of course. Just be aware that running an OTA update may wipe the OrBit configs until you set them again. The effect of an OTA update wiping OrBit config is exactly what happens when you run "Restore OEM" process in Orbit.

This does not apply to updates installed through VIDA!(Not OTA) Always "Restore OEM" before the car is connected to VIDA, if at all possible.

DIY CEM (and VGM) PIN Retrieval for Volvo and Polestar

Thu, 02 Feb 2023 14:42:18 +0000

If you want to change configuration on your Volvo, you need to have the "CEM PIN" for your car, and if you have an Android Auto based Polestar or Volvo (aka an "iCup" car) you also need the "VGM PIN" for the car. PINs are something like passwords to access modules. Like all modern cars, the manufacturer doesn't want you to make changes, so there are various security features throughout the car to prevent that. There are dozens of PINs for each car. We are only interested in the specific PINs to make configuration changes to the car for this procedure.

We currently offer the PIN service as an easy way to get the PIN(s) you need. But it is possible to get PINs yourself for your car, or PINs for any Volvo or Polestar. OrBit has tools built in to help. First you must gather some information from the official diagnostic software, VIDA. Essentially what you do is make VIDA use the secret PIN on your car and record it, then use OrBit to 'crack' the PIN from that information.

Here's what you will need to do that:

Access to Volvo or Polestar VIDA
Access to the local computer running VIDA, will need to be able to install Wireshark on it)
Ability to order "configuration test" software in VIDA
VIDA must be connected to the car with wired connection (no dealer WiFi)
VOE Cable to connect to the car (or equivalent, same as what you would use with OrBit)

Thanks to right-to-repair law in a single US state (Go Massachusetts ), consumers in North America (NA) are able to buy a subscription to VIDA at volvotechinfo.com (or polestartechhub.com for Polestar). If you are set up with a Windows laptop and cable for OrBit, the same setup will work for VIDA. Outside North America, VIDA software is not available to consumers, making access to VIDA much more difficult. There have been many workarounds for this, which is not part of this discussion but creative solutions are out there to get to VIDA outside NA.

This post is not a VIDA DIY, that's a whole other topic! We'll assume you have a subscription set up, or a friendly mechanic with VIDA, and you are able to navigate connecting the car and purchasing software. It can be tricky the first time through to know how the system works.

STEP 1 - Capture software install from VIDA

Open VIDA and log in
Open Wireshark, go to Capture menu, click "Start"
WiresharkCapture.PNG (Size: 13.03 KB / Downloads: 1515)
Connect to the car in VIDA
In VIDA order a "configuration test" for your car (this is cheap, just $0.01!)
Once ordered, you can retrieve the order in VIDA, to get it ready for install
Install the software in VIDA, wait until it is complete
In Wireshark, go to Capture menu, click "Stop"
Got to the File menu, click "Save As..."
Save the capture file (as a "pcapng" file type)
If this is not the same computer you will run OrBit on, save the pcapng somewhere you can get to it later (cloud service) or take it with you (USB stick)

STEP 2 - Crack the PIN with OrBit

Open OrBit, and log in
Go to "Expert Toolbox" tab
Click the "PIN Finder" button
Choose the pcapng capture file from Step 1
Wait for OrBit to do the magic! It can take up to a minute, maybe longer for really slow laptop...

OrBitCrack.PNG (Size: 35.46 KB / Downloads: 1401)

If the pcapng file contains PIN information (including CEM/VGM PINs), OrBit will output the PINs found in the PIN finder report
You can save the PIN(s) report for safe keeping. If your car is currently connected, OrBit will prompt you to save the PINs in the profile.
If your car is not connected, you can later paste the PIN(s) into the "Add CEM PIN" and "Add VGM PIN" dialogs opened with the buttons on the Shortcuts tab in OrBit, while you are connected to your car.

Enjoy exploring and modifying config with OrBit! I'd like to note here, unlike "other" software, OrBit reflects my belief that *you* own your car, so always the PINs that you get, are given to you, to use however you like! You can take them and use them with any other Volvo software, make your own software or tools, whatever. We don't borrow them from Volvo then lock them up in our own proprietary system. Just wanted to get that off my chest lol ;-) Enjoy!