LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

How can I avoid this: Error 5 occurred at Write To Measurement File->ACQ_LC_Press.vi

I have been writing a VI for acquiring a couple signals, sampling them down to about 10hz, and then writing them to a .lvm file. There are some other functions on the side, but I don't think they're really related to this issue. I have set my Write To Measurement File VI to save to a series of files, adding both date/time and sequential numbers to the file names, and have it set to start a new file after every 50,000 segments. I have tried to set the "existing file" setting to both rename existing file and use next available, but in either case I still end up with this same error eventually. The setup runs perfectly for many hours, happily recording good data...until it gives me the following error message and everything stops.

  

Error 5 occurred at Write To Measurement File->ACQ_LC_Press.vi


Possible reason(s):

LabVIEW:  File already open.
=========================
NI-488:  Command requires GPIB Controller to be System Controller.

 

I am not certain what could be causing this....the system runs many hours (last time ran for 19 hours and created 15 files) before this error occurs. The error also occurred at a strange spot since all the other "full" files with all 50,000 segments are around 2.6mb in size, while the last file where the error occurred is only up to 819kb. It wasn't trying to start a new file or anything, the file is only 14989 lines long.

 

If anyone has some insight into why this might be happening, or perhaps a better way to do what I am doing please let me know. I need to get this setup running pretty reliably so that I can acquire data for many days before resetting my test setup.

 

Thanks,

- Chris 

0 Kudos
Message 1 of 4
(3,976 Views)
I was able to find out what the problem was, mostly by luck. Another program (a corporate auto-backup system) was running once a day, and it was locking the files for upload. Sorry for the post!
Message 2 of 4
(3,952 Views)

No worries!

 

Thank you for sharing the solution to your problem with the community!

Kameralina

0 Kudos
Message 3 of 4
(3,943 Views)

I am having the same issue, but maybe due to a virus scan. I came across this on the NI website:

 

decibel.ni.com/content/docs/DOC-7212

 

 

Message 4 of 4
(3,718 Views)