Autosave and Galil - stop the autosaves from getting 'lost'

When looking at NDEMUONFE after an upgrade to 3.0.0, in preparation for some work, the autosave values for the motor setup were not applied (e.g. the motor and encoder resolutions).

Looking through Instrument > var > autosave > GALIL_01 at settings.sav, the values could be seen and were correct on the 11th of November 2016 (just prior to a cycle). Looking through those files there were a number of savB_SBAD type files on the 1st of January 2017, and then as of the 18th of January 2017 (when the update occurred) the values being used were the default values (and can be seen in the sav files).

This may be a non-issue, but it is something we should be aware of, and at least develop a set of support instructions of how to fix it should it occur out of hours on a production machine during cycle.

It is worth noting that in the same autosav directory I did not see the same list of savB_SBAD type files, so the losing of the data may be due to whatever caused these SBAD files (which I assume from the name are bad) rather than anything else.

Inizia ispezionando Instrument/var/autosave/GALIL_01/settings.sav e confrontandolo con i file savB_SBAD menzionati nel report, incluse le relative date e i valori. Determina perché i valori di autosave non sono stati applicati dopo l’upgrade e documenta istruzioni affidabili per il ripristino al di fuori dell’orario lavorativo per una macchina di produzione.

Scritto dal modello di indicizzazione a partire dal testo della issue.