- This topic has 2 replies, 2 voices, and was last updated 14 years ago by
.
-
Posts
-
Hi all
A quick request: I assumed that switching the Octopus off at any stage would result in the current machine state being restored by default when nerxt switching on – without the Grid/Program saving operation. However I notice now that this isn’t happening.
Was I wrong in my assumption or do I have a problem?
Cheers
If you switch off the Octopus without saving before (Grid-Prog) the actual programming or changing are lost. The Octopus stores always the whole machine state.
Thanks for this.
I now do the Grid/Program routine as a matter of course.
As I understand it then, doing this gives a saved ‘snapshot’ (state A) of the machine state.
If further changes are then made, resulting in state B, does the Octopus remain in state B when switched off without saving – or will it always come back with the saved state (A) when switched on again?
Sorry to be so dim about this.
Post edited by: Benny Sugar, at: 2010/10/13 12:57
Post edited by: Benny Sugar, at: 2010/10/13 12:58
Post edited by: Benny Sugar, at: 2010/10/13 12:58
- You must be logged in to reply to this topic.