03-11-2023, 06:38 PM
(03-11-2023, 05:13 PM)Power6 Wrote: It's a sort of learning process. Much I've been through long ago when I started writing the software. When I first started programming the car, neither OrBit or the engineering tools I used checked any of the "status" of any ECUs. Just blast through programming. And that works fine mostly.
As I developed the software more, I started to mimic what VIDA does...check each ECU is responding, check the status of "ready to program" routine, the things that make programming "safe" and less likely to need you to go back and clear codes, reset ECUs etc. When you do all the "checks", you learn that some ECUs don't respond to some commands. The very low end simple ECUs like the sunroof switch cluster for example the "OHC" which is an ECU, it will respond to reading DTCs and such, but it doesn't respond to the "ready for programming" routine status. Some ECUs need to be ignored for that check.
The GSM module is just one that popped up recently as one that doesn't appear to respond that caused a failure for one user. The update is just adding it to the list of ECUs that won't cause OrBit to "fail" programming if it's not responding. Not sure why I would not have found that before, we got a good size user base now, but we still do find new things. The GSM might not be a common ECU, it's a "gear selector module" but the PHEV/EV cars shifter is the "EGSM" and ICE cars don't have a module at all so I am not sure where that is/was used.
You're amazing! Thanks for your tireless enthusiasm and transparency!
