LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to Open TDMS file

I recieve the following error:

This TDMS file complies with a new version of the TDMS format that is not supported by this version of LabVIEW

 

I have tried using 2013 and 2012 SP1f5 and neither can open it.

 

Excel can't open it either.

 

File has been created on a PXI Chassis

 

File stared out life @ 50 MB and was then shrunk to 1 MB using  Defragmentation.

 

Would appreciate help getting to the bottom of this one.

 

iTm

iTm - Senior Systems Engineer
uses: LABVIEW 2012 SP1 x86 on Windows 7 x64. cFP, cRIO, PXI-RT
0 Kudos
Message 1 of 9
(3,574 Views)

Hi,

 

The attached file is corrupted. Only a few TDMS meta data are written into file. And the rest data of the file are all dirty data. It looks like that some pieces of raw memories are dumped into the file.  

fileBin.png

 

 

 

You can zip and attach your original file here, I will try to recover the data as many as possible for you from the original file. But I'm afraid that the original file should also contain only a few meaningful data but lots of dirty data.  Is there any power outage or crash happened during logging data?

0 Kudos
Message 2 of 9
(3,564 Views)

Thanks zaizhou,

 

All of my defragged files have ended up like this.

 

It is possible that the defrag has been cancelled mid operation, I have no way of telling.

 

The date can easily be re-created but each time, the file is unreadable.

 

Tim L.

iTm - Senior Systems Engineer
uses: LABVIEW 2012 SP1 x86 on Windows 7 x64. cFP, cRIO, PXI-RT
0 Kudos
Message 3 of 9
(3,559 Views)

Hi,

"All of my defragged files have ended up like this." Do you mean that the defragement node doesn't work on you machine? If the original file is corrupted, the defragment cannot promise to defrag it to a good one.

 

"The date can easily be re-created but each time, the file is unreadable." Do you mean that for every time you create the tdms file, they are all unreadable? Do you mean it is reproducible?

 

0 Kudos
Message 4 of 9
(3,555 Views)

The data doesn't have a lot of value to me,

I can create a new set, so I am not concerned if the data is lost, so no need to recover it.

 

The undefragged file is ok, unfortunately it is in a remote location and too large to e-mail back to base.

Post defrag, I haven't been able to open any of them (I have checked 9 in total).

 

 

 

iTm - Senior Systems Engineer
uses: LABVIEW 2012 SP1 x86 on Windows 7 x64. cFP, cRIO, PXI-RT
0 Kudos
Message 5 of 9
(3,546 Views)

If the undefragged file is OK, but the defragged file is broken. Then it may be a bug in TDMS defragment node. If you are willing to share your orginal file, it will be a great help to improve the stability of TDMS. You could upload your original file to NI FTP server.Or, you can zip your original file and attach here. An about 50M TDMS file could be zipped to around 10MB.

 

Thanks in advance!

Zaizhou Ma

0 Kudos
Message 6 of 9
(3,543 Views)

I need to revise my original statement,

 

Source file is corrupted as well.

 

I am investigating SMTP now.

 

The Email Scanner has been stripping the zip files as being "Corrupted"

iTm - Senior Systems Engineer
uses: LABVIEW 2012 SP1 x86 on Windows 7 x64. cFP, cRIO, PXI-RT
0 Kudos
Message 7 of 9
(3,538 Views)

Progress Update:

 

It turns out that the SMTP VI is Corrupting the File.

 

Does the Same to a .Zip File as well.

 

Investigating further

iTm - Senior Systems Engineer
uses: LABVIEW 2012 SP1 x86 on Windows 7 x64. cFP, cRIO, PXI-RT
0 Kudos
Message 8 of 9
(3,496 Views)

Figured it out.

 

There is a "Binary?" Input into the Mail .VI

 

Works when this is set to true.

 

iTm - Senior Systems Engineer
uses: LABVIEW 2012 SP1 x86 on Windows 7 x64. cFP, cRIO, PXI-RT
0 Kudos
Message 9 of 9
(3,493 Views)