Are you currently using PicoLog R5.21.1? I would recommend that over any previous version. PicoLog is continuously evolving and recent changes are geared towards reliability when logging large files over long periods. This restricts access to the .plw file for a period after each sample to stop conflicts from multiple accesses
Yes, the problem is also in the latest release.
As I tried to explain in my first post, the problem has occured some where between rev. 5.20.5 and 5.20.8.
That is: with 5.20.5 installed no problem, with 5.20.8 and later versions there is a problem.
If, before you start logging, you save a "Settings" (.pls) file, that will save a copy of the header that is written at the end of logging. If you do have any crash, we can probably recover your data if you send us the settings file and the corrupt data file.
There should be no need for that, as my .pls file is made 'Read Only' to ensure that every time the program is started it starts with the same settings.
This is done because different colleagues uses the setup for different purposes.
Furthermore the .pls file is filled with formulas and correction tables and it is essential that none of the settings is altered, as the set-up is part of an Accredited calibration routine.
All the 'internal' versions of the .pls file is saved in another folder for history.
At the moment the "system" is in an initial phase, so I have not had any crash yet, but the "core" problem is still:I need to extract data for Picolog Player, while logging and that I can not do with the latest PicoLog versions.
I think - somewhere in the manual, it is written that this can be done, and to repeat myself, it is possible in version 5.20.5 and erlier versions.