Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
SW MINOR VERSION
#1
Big Grin 
I recently upgraded the Volvo 2.9 OTA upgrade (from 2.7).  After that upgrade succeeded, all of the configuration changes made (via orbit) were reverted/set in the 2.9 update. Not a problem, I had saved my configuration settings.  

However, once loaded and I was about to push the changes, there was another setting that is tied to the software's minor version:

Code:
Setting: SW MINOR VERSION
Current: 09 Minor Version 9
New: 07 Minor Version 7


I canceled the programming since it didn't seem like a good idea. [Image: biggrin.png]  It seems that setting is part of the saved orbit settings file; the file is not text-readable and it doesn't show in the U/I, so there was no way to fix this. I reloaded the settings from the car and then set each setting manually. 

I wasn't sure if this was a bug or expected, so I figured I'd start here.

Thanks!
Reply
#2
It was a bug...in a bug fix ;-) The "change report" will show you this is changed...but it is not actually a problem, OrBit won't write that config item to the car. So if you do or did write the config, all will be fine. This has already been fixed.

OrBit was updated some versions back, to deal with the "OTA" update problem, that those SW version configs need to change when you update OTA, as the "SW version" config items are written in the update, and they need to reflect the current update level of the car. However when I made that update...I did not originally think about and account for the case where you do exactly what you have done...load settings from a time when you had an earlier update level ;-)

It's fixed as of v0.5.3...have you been ignoring the update notification?? Or maybe you weren't prompted well anyways you should be getting prompted to download the update to the latest v0.5.4 by now, and that will resolve the issue.
Reply
#3
(06-15-2023, 02:59 PM)Power6 Wrote: It's fixed as of v0.5.3...have you been ignoring the update notification?? Or maybe you weren't prompted well anyways you should be getting prompted to download the update to the latest v0.5.4 by now, and that will resolve the issue.

I run it in a VM on a macbook... I'll have to look to see which version I'm running. I only downloaded/started w/Orbit a month ago, so it can't be too old.  :-)

I wasn't prompted with a new version the last few times I've used it... Later today I'll check to see if I relaunch it if I'm prompted.

Thanks for the help.
Reply
#4
Just a follow up, after relaunching the app, I was prompted to upgrade.
Reply


Forum Jump:


Users browsing this thread: 3 Guest(s)