LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Error 6 occurred at TDMS Open in TDMS

Solved!
Go to solution

Hi,

 

I have a application that is using the TDMS VI's to generate a Logfile. 

The application ran correctly for 12 days. (Each errors, and some parameters - every hours - was correctly written to my TDMS file).

 

Then, the following error occured : 

Error 6 occurred at TDMS Open in TDMS - Write data SubVI V1.2.vi->D2XX MultiTester V1.5.vi

 

Possible reason(s):

 

LabVIEW:  Generic file I/O error.

=========================

NI-488:  I/O operation aborted.

 

I join my VI that manage the TDMS file. 

The error seems to come from the VI "TDMS OPEN". The corresponding TDMS file is effectively at the specified path, and its content is OK (all expected infos are present). The file is called LogFile_0_1.TDMS. 

Depending on the TDMS file size, the application automatically creates a new file. I tried to force that to get a new TDMS file (assuming that the active file was corrupted or blocked). A new TDMS file was created (LogFile_0_2.TDMS.) but only the first tab (root) was created. Then the same "Error 6 " was still present, exactly like before. 

Do you think this problem can come from Windows?

Or does it come from my application? What is not optimal, is that this "TDMS - Write data SubVI V1.2.vi" is called about every second, and the "TDMS OPEN" function is called unconditionally (even if no modification on the TDMS file are needed).

How can we explain that this bug appears after about 12 days only? 

I also join you the LogFile_0_1.TDMS that I converted to an Excel file, and the LogFile_0_2.TDMS that was not correctly created.

 

 

Thank you in advance for your support.

 

Michael 

 

 

0 Kudos
Message 1 of 5
(5,916 Views)

Here is the VI that is managing the TDMS file 

Download All
0 Kudos
Message 2 of 5
(5,915 Views)
Solution
Accepted by topic author Michael24

My guess is that you forgot to close the TDMS file and each time your VI is called a reference is created.

It could be that after a week the maximum possible number of references was reached, and you got the error.

 

Regards,

Marco

Message 3 of 5
(5,893 Views)

@MarcoMauri wrote:

My guess is that you forgot to close the TDMS file and each time your VI is called a reference is created.

It could be that after a week the maximum possible number of references was reached, and you got the error.

 

Regards,

Marco


Marco,

 

That's not just a guess, that is a very real possibility.  And lets not forget the memory leaks from not closing references.

 

ALWAYS close ANY references you create.  If you open a reference to a file, make sure you close it.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
Message 4 of 5
(5,891 Views)

Thank you for your advice! 

I think that it was the reason of my problem. I will restart my test and see in about 12 days if everything is OK.

 

Best regards 

Michael 

0 Kudos
Message 5 of 5
(5,857 Views)