How do OTAs affect Forscan changes?

[scruvs]

I was thinking about the best way to organize my modded modules in case I need to load an original module or revert back to a previous modded module, and it got me thinking about OTA updates.

If I backed up my original modules today, and I received an OTA tomorrow, could the data in my original modules that I backed up be stale?

Said another way, if I restore a backup of an original module that was created before an OTA, could I be losing software changes made in the OTA?

If so, how would I get those OTA updates back after restoring the module?

Sponsored

 

[Henry Ford]

OTAs have never screwed up any of my mods.

Don't think too hard about it. Every time you make a change back up the module settings. They are time stamped so you can go back to whatever place you want. I wouldn't suggest going back multiple changes ago but it shouldn't hurt anything. Even if it did screw something up just go back to the last one that worked. This is more of an issue for user errors than OTAs.

Edit: after rereading your post I think you may misunderstand what ForScan does vs. what an OTA does. An OTA changes the underlying software (firmware?), Forscan changes the settings. You cannot lose anything using Forscan you can only change settings. You could certainly lose functionality if you screwed up a setting but as long as you back up your changes you can always go back to what worked.

 

[Firn]

OTAs have never screwed up any of my mods.

Don't think too hard about it. Every time you make a change back up the module settings. They are time stamped so you can go back to whatever place you want. I wouldn't suggest going back multiple changes ago but it shouldn't hurt anything. Even if it did screw something up just go back to the last one that worked. This is more of an issue for user errors than OTAs.

Edit: after rereading your post I think you may misunderstand what ForScan does vs. what an OTA does. An OTA changes the underlying software (firmware?), Forscan changes the settings. You cannot lose anything using Forscan you can only change settings. You could certainly lose functionality if you screwed up a setting but as long as you back up your changes you can always go back to what worked.

Disagree. FORSCAN changes a configuration. OTAs could change the size of that configuration, location of bits in the configuration, and the bit values themselves. If an OTA updated that config and you revert to a version prior to the OTA, it is entire possible it change bits in that config to something that they were not originally.

An example is the APIM. An OTA can provide a new option/switch/etc. If that switch is displayed is controlled by an entry in the configuration. That entry did not exist before the OTA, as a result the saved config would not be applicable.

 

[Mmiketa]

My understanding is that once you have done an OTA, reloading an old backup does in-fact have a chance of messing stuff up. They make changes to configs during OTAs and if you revert to an old one you may be changing values you don't want to be.

 

[Henry Ford]

Disagree. FORSCAN changes a configuration. OTAs could change the size of that configuration, location of bits in the configuration, and the bit values themselves. If an OTA updated that config and you revert to a version prior to the OTA, it is entire possible it change bits in that config to something that they were not originally.

An example is the APIM. An OTA can provide a new option/switch/etc. If that switch is displayed is controlled by an entry in the configuration. That entry did not exist before the OTA, as a result the saved config would not be applicable.

Agreed. The point I was trying to make is don't make a change without backing it up. If you want to revert to some prior configuration just make sure you save the current configuration first. If the old configuration screws something up reload the newer configuration and figure out another way to do whatever it is you are trying to do.

Sponsored