I successfully figured out and completed the swap from my original non-bendy LED headlights, to bendy LED headlights, on my US market 2019 S60 T6 R-Design. Using all used parts. It was a bit of an adventure! Not as easy as it seemed to be, before I started! I was hoping that it would be as simple as swapping the used headlamps, put on the original modules (HCMs) from my existing headlamps, code with OrBit and go! Turns out it's not quite that simple.

BUT this forced me to work out how to do it, and add features to OrBit to support it, so others can do this without all the pain that I went though ;-)

I used part numbers 32342532 and 32342531. There are like a million headlamp part numbers so good luck out there. Bendy lights should be marked "FULL" and the non-bendy "MID" on the parts sticker on the lamp. I used "US" headlamps, variant code is "JB0B". The EU versions are different part numbers and variant code "JB0C". The swapping process is the same no matter whether US/Can or EU/ROW car. 

First a note on software: You will need the HCM software for this, to load to the used modules. Unless you happen to get used HCMs you know are loaded with the correct software (not likely!). I don't have an official stance on this yet for OrBit when it comes to reloading module software and OrBit doesn't distribute it. That's something to work out for the future. For now, if you have an S/V60 like I do, reach out to me and I can get you the software loaded to the HCMs for this. Others are free to ask, I will help if I can, I just don't have the time to do the tedious research needed to figure out all the right softwares currently and I may not have the software files needed anyways. If you can get to VIDA, you may be able to get the HCMs up and running so you can do an official HCM reload.

To keep the long story short, I found out why you can't make a simple headlight swap and config change:

• Used parts vendors always take the HCMs off and sell them separately, because they are dumb and know nothing about Volvos.
  
• Volvo builds cars with "special" parts at the factory, and by special that means cheaper ;-) The HCMs the car is built with won't support the bendy lights. If you buy a new replacement HCM it will support the bendy lights (same part for all cars). But the part the "non-bendy" car is built with, will not.
  
• You must get proper used HCMs, that support the bendy lights, in addition to the headlamps. They are not typically too pricey though.
  
• You will have no idea if the used HCMs are "left" or "right" (HCML or HCMR), or if they are loaded with software for you model, or a different model (see dumb parts vendors)
  
• You will need a way to set the used HCMs to the correct "side", unless you get lucky and get one used HCML and one used HCMR!
  
• You will need to load some HCM software on the used HCMs
  
• You will want to "learn" the headlamp module to the HCM (not critical but should be done)
  

• Install the used HCMs on to the bendy lights
  
• Remove the bumper
  
• Install the bendy lights but do not reassemble the car yet! You want easy access to the headlight harness plugs for next steps
  
• Plug only one headlight in to the car, so you are working on only one used HCM at a time
  
• Follow the guide for checking in the car for an HCML or HCMR, load HCM software and write the config string: https://forums.spaycetech.com/showthread.php?tid=161
  
• Unplug the completed headlamp module, plug the other one in and go through the above process again for the second headlamp
  
• When complete, plug both healamps in and reassemble the bumper
  
• Change config with OrBit to enable bendy headlamps
  

• Restore OEM as usual before connect to VIDA. I get no codes in my car or any problems with "bending" disabled
  
• The used hardware module is fine, VIDA will update the car HW and SW with the changed HCM
  
• The car should be compatible with software reloads and Total Upgrade for the HCM (the diagnostic part number and software are the same for bendy/non-bendy HCM to VIDA)
  

Is it possible to use a bluetooth ODBII scanner tool with OrBit for a 2017 XC90? (e.g.  OBD2 Bluetooth 3.0 Scanner, Car Diagnostic Tool OBDII Bluetooth Scan Tool Vehicle Code Readers for Android : Amazon.com.au: Automotive)

Please pay attention when making ACC/PA configuration changes.

It is best to consult the technical documentation before modification. Due to different car models, I have not yet sorted out the specific architecture week.

Not all SPA/CMA vehicles can use these functions by modifying configuration items. Especially for early vehicles equipped with BCM, after modifying the configuration, the braking function during use can make you very uncomfortable and pose certain risks.

OrBit can flash software to HCM (Headlamp control module) in the car. These modules are "coded" to the "side" left or right, and become the HCML and HCMR. OrBit can also write the "config string" to the HCM. This ability allows you to code the HCM for a headlamp replacement, support swapping headlamp types, and installing used HCMs removed from a headlamp, where you don't know which "side" the HCM is programmed for (HCML or HCMR?) OrBit can switch the HCM from HCML to HCMR and the other way, so you can install a used module to any headlamp.

How to work with HCMs in OrBit:

There are some special processes for flashing HCM modules (HCML and HCMR) these include: Writing config string to: learn new headlamp units, and to convert a used HCM 'side', to change a used HCML to HCMR and vice versa. This guide assumes you have already reviewed the general software flashing guide, or otherwise already familiar with flashing software to a module with OrBit. Review that guide first if you need to.

How to flash used HCM modules and write headlamp config string:

• When flashing software to an HCM (see flashing with OrBit guide), OrBit will prompt you to write the config string. You do not need to write the config string each time you flash, you can bypass it when prompted if not needed, config string write only needs to be done once when a new headlamp unit or HCM is fitted.
  
• The config string contains headlamp production info and also sets the "side" of the HCM module. Writing the config string allows you to change the side, converting the HCML to HCMR or vice versa.
  
• To write the config string, you need to read the information from the label on the headlamp unit. The config string dialog in OrBit contains instructions to enter the information from the headlight.
  

• When the HCM is installed on to the headlamp, and plugged into the car, it will respond to diagnostics as HCML or HCMR according to how it was programmed last (from the car it was removed from). 
  
• It is helpful to work on only one headlamp at a time via OrBit when installing headlamps with unknown used HCM modules. You can achieve this by only plugging in a single headlamp. When working on one headlamp, unplug the other one from the car harness. If the car is already assembled, you can pull the fuses for the opposite side headlamp to disable the HCM on that side.
  
• When you have checked and or corrected the "side" of one HCM, unplug it (or pull fuses) and plug in the other side to check and correct that module. You want to avoid trying to flash the used HCM and write the config string with duplicate HCMs in the car (2 HCMR or 2 HCML). Work on only one headlamp at a time until both sides are correct.
  
• To check the newly installed used HCM, with the "other side" headlamp unplugged, connect OrBit to the car, and determine if the used HCM responds to HCML or HCMR. 
  
• There are multiple ways do find which "side' the HCM is responding as, the easiest is to attempt to read any Data by ID (DID) from the HCML and HCMR in turn. You should get a response from only one of the modules, the other will return an error that OrBit is unable to read from the module. Now you will know which side the used HCM is programmed to.
  
• If the side is correct, for example the Left side is responding as HCML, you can proceed to flashing software to the module and write the config string.
  
• Use the "skip programming checks" checkbox on the "Experts Toolbox" tab when performing this process, to prevent OrBit flash fail due to HCML or HCMR "not responding".
  
• If the side needs to be corrected, example the Left side is responding as HCMR in the car, you will need to flash a software for the current module side, in order to change the config string and switch the side. For this example, left side is HCMR, in the ECU Flash box, choose the SBL for HCMR and choose any software for the HCMR to flash (it doesn't matter which one). Then proceed to flash and choose to write the config string, using the config info from the headlamp sticker. After flashing with the new config string, the HCM will now respond as the "correct" side, HCML or HCMR. You can then proceed to flash all correct software to the HCM.
  
• When one side is correct and complete, unplug that headlamp from the car harness, and plug the other side headlamp in.
  
• Repeat the above process to check the "side" the used HCM is responding as, and write the config string. Then proceed to load the correct software to the HCM.
  
• When both used HCMs have been checked and corrected: you have one HCML and one HCMR in the car, both headlights can be plugged in and reassemble the car.
  

How to flash software with OrBit:
You can flash software to some ECUs/modules in your SPA/CMA Volvo/Polestar car with OrBit. This is a relatively lesser used and somewhat limited feature of OrBit. This is partly that most of y'all users don't care yet ;-) But also due to how Volvo works: rather than making module software readily available like some mfrs, they go out of their way to keep it locked up and safe, only accessible through their watchful eyes via VIDA ;-) But still, OrBit can do it and who knows what the future holds. Current ECUs "enabled" for flashing are: CEM, HCML, HCMR, SCL, SRS, DEM, AUD, SODL, SODR, TRM, POT. 

More ECUs are enabled as I test them and confirm flashing works reliably, or in some cases I have worked with others.. Don't ask about ECM or IHU yet, these are the most complex and secured flashing processes, and currently we don't have anything of interest to flash to them anyways, not yet...

The biggest hurdle you have is knowing what software you need and getting the software "VBF" files in the first place. This is no a guide for that, it is a guide with how to flash a module with software with OrBit if you have it. You can ask around though, you do never know who has what software files in their collection.

How to flash software to a module with OrBit:

If you are already familiar with flashing software to ECUs, some of this may be review. To flash software, you need both the SBL to boot the ECU into flashing mode, and you need the software file to flash itself. These will be in VBF format for Volvos. OrBit works with Volvo VBF format software files. OrBit only allows certain modules to be flashed based on successful testing, modules are added as they are tested to work. To flash software to a module:

• Connect to the car
  
• Switch to the  "ECU Tools" tab
  
• In the ECU Flash box, use the buttons to choose the files for flashing
  
• Click "load SBL" and choose the SBL software VBF
  
• Click "load VBF" and choose the software VBF file you want to flash
  
• You don't specify the module to flash, OrBit reads the VBF files to know which ECU it is for
  
• OrBit will verify the ECU matches between the SBL and software VBF files
  

• OrBit verifies checksums in the VBF files, ECU match, car connected, licensed for flash etc. OrBit must also know the programming PIN of the ECU. For many ECUs OrBit already has the standard PIN loaded, for others (i.e. CEM) the unique PIN needs to be set in the car profile. if everything is good, the "Flash ECU" button is enabled.
  
• Click the "Flash ECU" button, to proceed flashing the software to the car module
  
• OrBit will return from the process with success, or if the flash fails, an error and reason will be given
  
• OrBit only flashes a single software file at a time. When flashing multiple software files to the same module, you will need to run this process for each software to flash. You can flash a single module repeatedly, leaving the same SBL specified, choosing a new software file to flash via "Load VBF" each time.
  
• When flashing software via this process, OrBit skips "post programming" process (clear codes, restart IHU etc.), to save time when flashing multiple softwares. So keep in mind you may want to clear codes, restart modules, ABS clear etc. on your own, after all software has been loaded. Also you may disable "programming checks" (check all ECUs are awake and in programming mode before every flash) as well. This is checkbox is under advanced OrBit settings on the "Experts Toolbox" tab.
  

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.

Hi All,

Not sure where or if this is a software install (but suggests this is just an update to software, not install like Polestar?) that the latest updates for Intellisafe Assist have additional functionalities.

My XC90 came with Pilot Assist, so I have been playing with those settings as per the Pilot Assist thread to see what that does, but nothing there shows anything, so is this something 'hidden' or I'm missing?

The link to the Volvo page mentioning it all is HERE

Hello, I want to know if orbit is able to align ecus with used light module from other car. 
The diller saying that only new ECU can be programmed and no alignment is possible.

I have a 2019 S60 Momentum, it doesn't have fog lights from the factory and is missing the wires from the CEM to the bumper harness. I can activate the fog light feature and make the switch work so I know it is possible to add them. Has anyone done this yet? Which connector to the CEM would have the fog light pins or where can I find a wiring diagram?

Hi all,

I am hoping to get some theories / feedback on a few driver assist differences I've noticed between my XC40 Recharge (North America, MY23) and the Polestar 2 (both CMA platform cars).

I've not driven a Polestar 2, but their IHU is available at the following link which lets you poke around the settings: https://hmi-app.polestar.com/car/Functions

Here are a handful of settings I noticed in the Polestar 2, but not my Volvo:

1. Curve Speed Assist (CSA): I've successfully enabled and tested it on the Volvo using OrBit (i.e., setting "148 Curve Speed Support" from 01 [w/o warning, w/o assist] to 03 [w/o warning, w/ assist]). Now I can see a new CSA setting in the IHU and the car slows down / shows an indication symbol on the dash on fast turns. Without CSA, the car would occasionally struggle to maintain its lane at high speeds -- but with CSA, that's been mostly solved -- so it seems odd to me that Volvo would omit the feature by default.
   
2. Distance Alert: I tested setting "144 Distance Alert" from 01 (without Distance Alert) to 02 (with Distance Alert) but I couldn't quite figure out how to turn the feature on in the car itself (assuming it works at all on Volvo -- I thought it only worked on cars with a heads up display, but the Polestar 2 doesn't have one I think?)
   
3. Speed Warning: I tested setting "155 Speed Warning" from 01 (without Speed warning) to 02 (with speed warning for GSO) but didn't notice any change (just the usual flashing speed limit sign in the dash)
   
4. Speed Camera Warning: Not sure how to turn this one on -- maybe I overlooked an option in OrBit -- but also not sure this works in the US on the Polestars?
   

• Does anyone know if this related to "312 Lane Change Assist"? Right now the Volvo is set to 01 (w/o Lane Change Assist) but there is a 02 and 03 option for level 1 and 2, respectively.