04-03-2015 05:59 AM
Dear all,
I am having two compactRio devices (cRIO-9074) that are applied for data logging and control. As is convenient, one deterministic loop handles the data acquisition, while another loop handles the data storage.
The data storage loop basically creates a new TDMS file per data set that is subsequently stored to the disk.
The whole software operates as expected for some time (at least one day without any issues), but then I get a File I/O error -2519 that is thrown by TDMS open. This error occurs after some time on both compactRio systems. How should I handle this error properly and what may be the probable cause?
Upon system restart the error disappears and the system continues logging. Therefore, when having this error, I restart the system automatically, but this is to my opinion no proper solution. The fact that the error is cleared upon system restart, seems like it is a resource problem as outlined in: http://forums.ni.com/t5/Real-Time-Measurement-and/2519-error-trying-to-create-a-TDMS-file/td-p/26546... There they recommend using the FPGA programming mode to save on resources. However, I would like to continue using the Scanning Mode Interface instead. To better dedicate the processor resources, I changed the execution options of the different loops and gave Priority to the data acquisition and data storage loop. I also distributed the processes in different Execution Systems, to optimally divide tasks within the real-time processor.
When I manually neglect the error (just clear the error in the data storage loop), the issue remains for the following data sets that need to be processed. So once the error is thrown, it reoccurs upon trying to store each subsequent data set.
I also consulted http://forums.ni.com/t5/Real-Time-Measurement-and/tdms-2519-error/m-p/2569381/highlight/true#M13920 where the same error is reported and the solution is to update a .dll file in the installation. However, the installed software in my case appears to be okay. Also in that case, the problem occurred immediately, while in my case the problem arises after some time. Again this indicates towards a resource issue.
Can you please provide me with some possible solution to overcome this problem? I am looking forward to your opinions. Contact me if anything is unclear within my explanation, or you need additional information.
04-20-2015 03:52 AM
Hi gielvdbroeck,
Good job for the perfect description and for the well researched topic!
The first thing that comes to my mind is to Format and reinstall the software on the cRIO. This will make sure that you have a clean installation and there is no corruption in the OS.
One more thing to get into account is the memory. If you do not have enough memory where to store the file it's possible to throw this error.
Best,
Bozhidar