Hi all, anyone know if Orbit has the ability to remove the restrictions from the orange key?

Thanks,

Changed the config from US to Europe and finally have Radio with 0.1 instead of 0.2 Mhz step for my imported car (2019 XC60 T8)!

This is awesome!

I find myself occasionally out in the world during my day having a thought about things to do for self-practice and learning, and much of the time lately my car and by association Orbit keep coming to mind.  Problem is, I think the ideas are decent, but don't/can't write them down and forget.  So I decided to start this thread for mostly myself to remember and discuss if some of them are even possible, otherwise the idea(s) will keep popping into my head 'anew' until I realize I already walked that path.  So here goes the short list of what I can remember at the moment, but more to come later.

Also some/many/most of these may have been discussed already, but my searching skills are lacking, so please forgive me.

1. Use the default car config details gathered in Orbit along with VIN/relevant option details to correlate common/"default" configurations for various options.  For example, if we can look at enough data we can say something like all '23 XC90s have ACC level x but all '23 V60s have ACC level y.  This may make swaps/conversions easier, as well as maybe glean some more detail about what the levels and options mean.
   
2. If you want to get fancy with Orbit, do like Volvo does and pull images of the connected car.  For example, using the Volvo developer API to get information about a car it returns a URL of an image.  Here's my car: https://cas.volvocars.com/image/dynamic/...?market=se . It's clear that the values in the URL are the variant codes and other basic details which can be modified to return different visual car configs.  Such as an Ember Red Metallic V60 PE with chrome window trim: https://cas.volvocars.com/image/dynamic/...000&w=1920
   
3. I can't remember at the moment, will update when it comes to me.
   

Not sure if subject is clear.
I recently drove a 2023 XC90 and when the proximity sensor in it triggered the 360 camera came on. Very helpful. Is there a way to do that in Sensus. Currently one has to press home (usually a few times), swipe right and select camera and then sometimes 360 to see around car. 
Lexus has a function where when below 20km/h a 360 view and front camera view comes on. 
I appreciate Android and Sensus are different just wondering out loud.

Thank you for an amazing software.

Quick question as I couldn't find it in the forum. The service function for brake fluid change, do we have a process for this somewhere? This in theory could save me a lot of effort for changing brake fluid soon if it is a flushing system?! But don't want to click something out of sync for obvious reasons

Sent from my Pixel 6 Pro using Tapatalk

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.