A corrupted file most often occurs when a file server or USB stick is disconnected before the operating system has finished writing the file. The only way to be sure that the OS has finished is to unmount or eject the server or stick using OS commands before disconnecting physically or by severing network connections.

The file is usually truncated, and so Logger Pro can’t read it.

It is possible, though not in all situations, that the data can be retrieved. Most Logger Pro files are in plain text format. If the corruption or truncation is after the actual data, then you may be able to import the data into another Logger Pro session. To do this, launch Logger Pro with no sensors attached. Choose Import From –> Logger Pro file from the File menu. You’ll get an open file dialog; select the corrupted file and click Open.

If possible, Logger Pro will import any readable data from the corrupted file. It probably won’t be graphed; check the data table to see what was acquired. Graph it as needed.

If the import fails, the only other option is to inspect the file in a text editor, and to copy any data you find, pasting into Logger Pro manual columns.

A typical error message looks like:

Error at: GDocument
Line: 0
Application Version: Logger Pro 3.8.3 Build Date/Time: Sep 14 2010 09:29:46
Operating System: Windows XP
LabPro OS: LabPro driver version: 9.210
Additional Testing Information: The file:
is corrupted and cannot be read.