log file produced by tdms file

[Timothy 123]

Hi,

I received the following log file when I ran my program that accesses a tdms file. This problem does not occur when I use another computer. The computer where this error occurs is a dell precision 670. The log file is attached here. I am only reading a 2d arrays of numeric data type. Please suggest any ideas for why this is occuring and any fixes that are possible. The file had to be renamed as .txt to attach it to this message, but it shows up on the computer as .tdms.log.

Thank you,

-Tim

[Matt_W1]

I'm not sure what the problem is but I would try updating the TDMS Dataplugin. Hopefully that'll help.

[Timothy 123]

Hi,

I tried downloading the file at the link you suggested above, but it did not resolve the problem. When I use the tdms file, and read and write to it, do I have to close it, between the two operations, or can I just keep it open by accessing the reference. This didn't seem to be a problem on the older computer I was using, but it is a problem now.

-Tim

[Matt_W1]

Is it possible one computer is on the 8.2 runtime and the other on 8.2.1 runtime. I had some problems with running some tdms code that was compiled for 8.2 on the 8.2.1 runtime (the reverse was also true). I fixed it by upgrading everything to 8.2.1 and recompiling. This doesn't look like the same problem I had though.

[Herbert Engels]

The TDM Streaming API and the Storage VIs are not built on top of the same architecture. The Storage VIs use a component called USI, which is shared with other NI applications like DIAdem. USI does not support all data types that LabVIEW or TDMS have. The log file indicates that you have used a type that is not supported. Candidates for this kind of problem are unsigned integers or booleans. You might want to try a larger, signed integer or maybe a floating point number instead.

Hope that helps,
Herbert

[Timothy 123]

Hi,

I am writing floating point (dbls) to the tdms file. I also have two computers in my lab, and have run this same exact program on both computers. One of the computers, computer A, has labview 8.2.1 and diadem installed and the program runs fine. On the other computer, computer B, which has labview 8.2.0, the program runs into this problem with the tdms file. Were there any changes made from 8.2.0 to 8.2.1 in tdms files that will require us to upgrade to 8.2.1 to avoid this problem.

Tim

[Stephanie B]

Hi Tim,

I browsed around the 8.2.1 Bug Fixes page and didn't see that one specifically, but it might have been something they fixed while working on another issue. Hopefully upgrading to 8.2.1 on the other computer won't be a problem and therefore will solve your issue. Thanks!

Stephanie