![]() |
Configuration is messed up - can not revert to OEM?? - Printable Version +- OrBit Forums (https://forums.spaycetech.com) +-- Forum: General (https://forums.spaycetech.com/forumdisplay.php?fid=1) +--- Forum: OrBit Q&A - Ask your questions here! (https://forums.spaycetech.com/forumdisplay.php?fid=24) +--- Thread: Configuration is messed up - can not revert to OEM?? (/showthread.php?tid=889) |
Configuration is messed up - can not revert to OEM?? - ana100 - 05-25-2025 Hi guys, I really need some help.... It all started after car did not crank. No codes, just no crank. Before this, the car has been worked OK for months. While trying to get the car to crank, disconnected steering column lock (SCL) connector, and tried to configure it out as here in forum somebody instructed. Now starting Orbit, to start configure, came a warning “Your CM has been updated since you last used OrBit and Orbit does not have an updated OEM… Use Backup Logic button… to take a backup”. Made the backup and configured the steering lock out. Did not help on cranking, but car finally cranked after fiddling with the wires back of the starter motor. So good old mechanical issue :-), probably. But then the problems started. Put the SCL back, reconfigured some old configuration, but had airbag red symbol, gearbox did not change gear etc. Configuration page showing just “FF”s. See my other post. Next, configured again with a known older saved configuration file, got car somehow working, but getting still errors on SRS, air suspension, start-stop system. DTC codes saying configuration errors from many modules, e.g. from SRS. Also RML & RMR not connecting. Strange thing now is, if I try to read DTC codes / live values with other tools, like Vdash or V-tool (iphone), the tools don’t find all the modules, just one or two?? Orbit reads codes from many modules. Like the "directory of modules of this car" is messed up? Now new try today. With an old laptop having older Orbit version (0.99), older conf files (idea was to use that PC to revert to OEM) when starting Orbit, again “Your CM has been updated since you last used OrBit and Orbit does not have an updated OEM… Use Backup Logic button… to take a backup”, but the backup just did not succeed, and can not change configuration, not any saved, not back to OEM. Now back to the newer laptop, updated profile, no errors. But all writes to car fail in the same way: “Negative response from RML(and RMR) not awake“, and at the end “Timeout starting SBL on the CEM!”. Any ideas, what next? I guess the coding without that SCL module connected started this show. But what are my options now? RE: Configuration is messed up - can not revert to OEM?? - ana100 - 05-25-2025 More trial and error done. Was able to actually write both "OEM" and my own configurations, but it seems that the OEM file is just full of FF. This causes the configuration errors, even if own settings are applied to the configuration. Also reading OEM back-up logic fails, saying "Non-OEM logic data detected, saving alternative filename". So, how to get a valid back-up OEM file?? RE: Configuration is messed up - can not revert to OEM?? - Power6 - 05-25-2025 I got your PM, I'll reach out, we can fix it up. |