PicoScope 7 Software
Available on Windows, Mac and Linux
Picolog UI Crash Recovery
Picolog UI Crash Recovery
Hi,
I have an active Picolog session that has become unresponsive to the UI.
Logging appears to be continuing (files in AppData are still being updated), but all user input is being ignored so I am unable to stop and save the data.
I understand that the database in the background has features to help guard against data loss on PC crash etc, but I don't know what the best way of recovering from this UI lock-out with minimal risk of losing the historic data?
I can obviously just force a stop or a PC restart and I think it 'should' recover ok, but before I do that, just wanted to check if that is the best method to preserve the data?
For reference this has been logging for about 1 month with periodic saves to create a backup on the network. The last save was on Friday, but I have a weekend's worth of data logged that I'd rather not lose.
Thanks,
Simon
I have an active Picolog session that has become unresponsive to the UI.
Logging appears to be continuing (files in AppData are still being updated), but all user input is being ignored so I am unable to stop and save the data.
I understand that the database in the background has features to help guard against data loss on PC crash etc, but I don't know what the best way of recovering from this UI lock-out with minimal risk of losing the historic data?
I can obviously just force a stop or a PC restart and I think it 'should' recover ok, but before I do that, just wanted to check if that is the best method to preserve the data?
For reference this has been logging for about 1 month with periodic saves to create a backup on the network. The last save was on Friday, but I have a weekend's worth of data logged that I'd rather not lose.
Thanks,
Simon
Re: Picolog UI Crash Recovery
I just restarted the PC in the end.
When it came back up I restarted PicoLog and it resumed where it had left off.
I was then able to stop and save with no loss of data.
Thumbs up for the resilience of PicoLog software!
For reference this was V6.2.9
When it came back up I restarted PicoLog and it resumed where it had left off.
I was then able to stop and save with no loss of data.
Thumbs up for the resilience of PicoLog software!
For reference this was V6.2.9