Invalid file header with Vector

Dear Nortek,

When I downloaded the data of my last Vector deployment I got the warning message "Command failed! (ReadFileConfig) Invalid data header".

When I converted the binary .vec file to ascii files I got the message "I got the message "Invalid or missing hardware configuration. Invalid or missing head configuration. Invalid or missing user configuration. Press OK to create a repaired copy. The original file will not be changed. Note that default settings are used if the configuration date recovery fails. (i.e., the converted header may not agree with the deployment configuration." The software then produced the usual ascii files.

The information in the .hdr file were wrong : incorrect instrument setup, serial number "UNKNOWN", etc. I had also a short look at the binary .vec file : the first 784 bytes (corresponding to the structures Hardware configuration, Head configuration and User configuration) were all zero, except bytes 739, 783 and 784. From byte 785 there seems to be correct Vector-specific structures. 

The actual data seem to be correct, but they are a little more difficult to process as it is not possible to rely on the .hdr file for sampling frequency, serial number, etc. What is the reasons of this problem? And what can be done to avoid its repetition?

I attach the setup log file with includes also instrument details.

Best wishes

Urs Neumeier

Dear Urs Neumeier,

This could be caused by a communication or recorder failure. When the conversion utility does not find a valid header it will create a copy of the actual data in a separate file and insert a dummy header. This is the reason for the incorrect information in the .hdr file. The recorder data retrieval function allows you to dump raw data from the recorder. If you could upload a dump file to ftp://ftp.nortek-as.com/pub/incoming/ we may be able to tell if there is something wrong with the recorder and possibly recover a valid header section that can be merged with your data file. Please check the 'Dump' and 'Include FAT' options.

Best regards,
Oistein Hurum

Dear Oistein Hurum,

I just uploaded the dump file of this instrument on you ftp site under the filename Dump_N6507_2010-06-24.vec.

I mainly want to know why the problem occurred and if it can worsen. I managed to use these data but I am worried by the unexpected behaviour... The instrument goes back to the field tomorrow for the next experiment, but I shall not erase the memory before deployment, i.e. the next data will not be stored at the same location on the memory card (let's hope that their will be OK).

Best wishes

Urs

Dear Urs,

The recorder memory data is fine. There are no checksum errors found and this includes the configuration header. This means the problem is with the communication to the PC, prrobably just a glitch on the serial line or a that the timeout setting is too low. Try increasing the timeout setting in the Communication dialog.

Best regards,
Oistein