Hello All
I'm using a CR3000 with a compact flash memory card.
The last few weeks, I have been getting an error when converting through loggernet cardconvert. The error is: Open failed D:\10505.alldata.dat Invalid number of fields.
Any ideas on how to fix this?
Regards,
It is possible that the file system on the card is corrupt and this corruption is manifesting itself in the header of the data file. Assuming that the the file was created using the CardOut() instruction, the text header of the binary data file has the following lines of metadata:
1 - Station Environment: comma separated list that contains file type, station name, model name, serial number, os version, dld name, dld signature, file creation time
2 - Decode Information: comma separated list that contains table name, record interval, frame size, intended table size, frame time resolution, ring record number, card removal time, table CRC.
3 - Field Names: comma separated list that gives the name of each field (including array index).
4 - Field Units: comma separated list that gives the units string assigned to each field. There must be an item in this list for each item in the field names list.
5 - Field Processing: comma separated list that specifies the output processing instruction that has been carried out on the field. There must be an item in this list for each item in the fields list.
6 - Field Data Types: comma separated list that specifies the data type of each field. There must be an item in this list for each item in the fields list.
As card convert processes this data, it ensures that the number of field units, processing instructions, and data types matches the number of fields and, if they don't, it will fail to open the file. The fact that you are getting an exception related to the data types indicates that the preceding lines were parsed acceptably. This is what so strongly suggests that your card has experienced some form of file system corruption.
It may be possible to edit the file by hand and restore the sixth line but, depending upon the extend of the corruption, there is no guarantee that the content itself will be legible. Once the header is readable, however, it is possible to use the repair feature in card convert to search for valid data frames in the file.