LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

cRIO stopped writing to text file

My NI-9074 stopped writing to a text file in the middle of a run when the file reached about 9.5 Megs.  The file gets opened, written to, and then closed every 2 minutes, then after about 3 months of normal operation, it ceased to write to the file.  The other functions continued to happen just fine.  I did not receive any errors in my error log(also a text file) and I don't believe that the lower priority loop (where the file writing occurs) was frozen since that is where the communication with my PC occurs via NPV, and we still got values from them.

 

Thoughts?

0 Kudos
Message 1 of 4
(2,601 Views)

The larger the file the longer it takes to access!

 

Thus it would be wise to generate a new file after inital file has attained a certain size. 

 

For examlpe  generate new file after every week/month.

 

Just my 50 øre's worth

 

xseadog

0 Kudos
Message 2 of 4
(2,596 Views)

How frequently are you writing to the file?  Why are you reopening it each time?  Better to keep the file open until you're done with it.  Are you familiar with the limitations of the solid-state drive on the cRIO?  You should be careful how you write to it to minimize wear.  Also, how are you determining whether it's time to write to the file again?  Is it possible that some counter is rolling over at that point, causing your VI to stop writing to the file?

0 Kudos
Message 3 of 4
(2,592 Views)

Hi,

 

nathand brought up a few good points. Could you please answer the questions above to clarify the issue. Also, have you tried formatting the controller as described in this KB? Corrupted software on your controller might be causing this issue.

Sev K.
Senior Systems R&D Engineer | Wireless | CLA
National Instruments
0 Kudos
Message 4 of 4
(2,576 Views)