As for saving calibration, it all sits in the pypilot.conf file. You can manually make copies of it for emergency situations, where your calibration got messed up and you don't have a calm sea to sail your calibration circle (been there). For myself, I have added a few lines to /opt/bootlocal.sh (see code snipplet) on the tinypilot that restores a known, working copy of pypilot.conf prior to starting up. That has its obvious disadvantages (like: changes to any setting are not persistent, unless you update the backup) but for myself I'm willing to live with it.
For testing the hard-over time I always count the seconds out loud ;-) or am I misinterpreting your question.
note: /opt/bootlocal.sh runs as root, so remember to chown the file to tc : staff otherwise pypilot cannot write its own file.
For testing the hard-over time I always count the seconds out loud ;-) or am I misinterpreting your question.
Code:
date >> $DEBUG
cp -f /home/tc/.pypilot/pypilot.conf.restore /home/tc/.pypilot/pypilot.conf
chown tc:staff /home/tc/.pypilot/pypilot.conf
echo 'running pypilot' >> $DEBUG
sv u pypilotnote: /opt/bootlocal.sh runs as root, so remember to chown the file to tc : staff otherwise pypilot cannot write its own file.