Hey,

I see the following settings:
078 HOMELINK FREQUENCY SETTING

Did anyone play with it?

I can't get my US Volvo linked with my garage doors in Europe, assume it's a frequency thing.

There are 9 options.. maybe just have to go through them one by one..

Cheers

Edit: found this had already been discussed here:
https://www.swedespeed.com/threads/new-b...ad.664211/

Hello, are you planning to reset the adaptation of the gearbox and read out live data, for example the gearbox oil temperature?


Gesendet von iPhone mit Tapatalk

Is it possible to use OrBit to code an additional key on an 2017 XC90.  I thought I lost my spare a while back and the Volvo price to replace it nearly floored me.  I'm thinking of being proactive and maybe buying a key from a wrecked XC90 and code it for my car.  Can this be done?

Also, I remember reading a while back about the "Red" key options, where you could have an additional key that had limitations set like reduced speed/acceleration to give to a vallet or kids, can I code a key to behave like this?

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).
  

• 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.
  

• "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.
  

Is it possible for OrBit to be able access the data associated with vehicle telematics that is stored in the various ECU's?  and does it have the capability to delete this metadata or prevent it from being transmitted to or accessed by Volvo or their 3rd party vendors?

This is along the lines of data privacy and "do not sell my information" type deals...  things like phone contacts, location, GPS data, travel history, searches, voice recognition profiles, advertising ID, usage & diagnostics (app and otherwise), etc.

It would be nice to have an ability to "see" what metadata information is collected, how often it's collected, where it is stored, how long it is stored and how this information is being transmitted (VIA the vehicle's onboard modem) or accessed (VIA the OBD II port) by Volvo or their 3rd party vendors. 

Ideally I would prefer to be able to stop the collection in the 1st place. if something like that is not possible then to me the next best thing would be to have an automated "delete" function that has the capability to select the frequency at which the metadata is deleted. If those options are not feasible the next option would be to block the access / transmission of the metadata. 

I realize this is a lot to ask, but for those individuals that are concerned about privacy issues, they need to look beyond just their cell phone...  these days newer vehicles are basically a mobile phone on wheels and their data collection and sharing/selling is largely unchecked.

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.