+- OrBit Forums (https://forums.spaycetech.com)
+-- Forum: OrBit Application (https://forums.spaycetech.com/forumdisplay.php?fid=9)
+--- Forum: Releases (https://forums.spaycetech.com/forumdisplay.php?fid=11)
+--- Thread: OrBit Beta v0.9.8 release notes (/showthread.php?tid=474)
OrBit Beta v0.9.8 release notes - Power6 - 05-20-2024
0.9.8 is released. This is an "out of band" update specifically to address issues with AAOS 3.0 updated cars, with a couple bug fixes tacked on.
(Latest version of OrBit can always be downloaded here: https://app.spaycetech.com/orbitupdate/download) The "update notification" in OrBit will be sent later, but you can download the updated install right away from the link.
New features:
- Added Safety for AAOS 3.0 upgraded IHU (Infotainment Head Unit) - It has come to my attention that the normal programming process is known to possibly cause a problem in the "Android" based Volvo/Polestar models that have been upgraded to the the 3.0 version system. The IHU can get "stuck" and the screen in the car will be blank. This would necessitate a dealer visit and some fix from Volvo/Polestar that is as yet, unknown.
- OrBit has been updated, to avoid the issue, by performing more strict checks on the state of the IHU before writing any config, and failing the process if the IHU does not pass all checks.
- The IHU must be responding, it must report "ready for programming" before writing a config.
- After programming, the IHU must report it has returned to normal diagnostic session before it is restarted. If it fails, the IHU restart is skipped.
- To restart the IHU (ECU Reset from ECU Tools tab) the normal diagnostic session must be reported, or OrBit will not send the reset command.
- Enabling "skip programming checks" will not bypass the requirements for the IHU checks
Other fixes:
- "Skip programming checks" will no longer bypass the check of critical ECUs (CEM, BECM, IHU) when programming. The checks must always pass.
- Improvements have been made for latest AAOS update cars, to address the issue where false "ECU Flash failed!" is reported after successful flash, due to the CEM not being ready to read car info after writing a config.
- Fixed error on CEM Security PIN extract "no PIN info found" on a supported CEM when the PIN can be retrieved successfully.