LibrePilot Forum

Users => Vehicles - MultiRotors => Topic started by: anthropo on October 26, 2017, 10:44:02 am

Title: Backup and restore .uav
Post by: anthropo on October 26, 2017, 10:44:02 am
Hello

Just to be sure : if i backup a version in a .uav ( 16.09 for example), jump to next then revert back with a restore of this .uav, do i nedd to reconfigure something or is it enough

Thank you
Title: Re: Backup and restore .uav
Post by: f5soh on October 26, 2017, 12:05:46 pm
You may need to reconfigure some parts related to incompatible UAVOs, see warnings when you import 16.09 into next version.

Some UAVO default values may change between versions so best option is made a template (https://librepilot.atlassian.net/wiki/spaces/LPDOC/pages/63668239/Import+Export+vehicle+template) that allow saving main parameters like PID with 16.09 and restart from scratch your config with Next using Wizard and import your template at end.

Please note there is no need to redo Esc calibration, some specific values (like temp calibration) can be exported for further usage.
See Revo calibration file example here (https://librepilot.atlassian.net/wiki/spaces/LPDOC/pages/5669361/UAV+Settings+Import-Export)
Title: Re: Backup and restore .uav
Post by: anthropo on October 26, 2017, 12:18:58 pm
i made a backup of 16.09 and Next version.  I don't want to restore 16.09 on next.

All i want to do is restore 16.09 with 16.09 version of .uav. (or Next on Next). In that case evrything is restored (attitude, mag calibration, thermal...), isn't it ?
Title: Re: Backup and restore .uav
Post by: f5soh on October 26, 2017, 12:28:02 pm
Yes, of course if version matches.

** Some settings related to modules may need a first import, reboot board and import again settings.
Title: Re: Backup and restore .uav
Post by: TheOtherCliff on October 27, 2017, 12:18:08 am
Beware that there is an import/export bug in 16.09 so the safe thing is to always import/export via USB and never via OpLink.

When importing/exporting, the OpLink connection always reads and writes the GCS OpLink, not the aircraft OpLink.

This is true for Revo class FCs, but probably doesn't matter for CC3D class FCs.