LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Error 6 in "Write To Spreadsheet File.vi"

Hello

 

I have a customer who uses a LabView program (with LabView 8.6 on Windows Vista) to run 4 battery test benches.

These test benches run day and night and are never stopped.
After finishing one charge or discharge cycle (approximately every 15 minutes),  some values are written to a .txt-file (see attachment). This works fine during  some days, but it occured now twice (always after 2-3 weeks), that error 6 appeared and it poped up a message, that something with "Write Spreadsheet String.vi" in "Write To Spreadsheet File.vi" is wrong. The customer could then choose between "continue" and "stop". After clicking on continue, the whole program continues properly but, of course, the values were not saved in the file. For safety reasons, he stopped the program after that and restarted the computer, so I don't know if the next storage of the values would work or not.

The File name is always the same.

Unfortunately, I did not get the whole error messages from my customer. But he mentioned, that after this event, the operating system pops up some error when he is going to open folders in the explorer (sorry, that I have not more precise information). 

 

Some information about the measuring system:

There are three NI 9172 chassis which include the following modules:

Chassis 1: 4x NI 9205; 1x NI9403; 1x NI9481

Chassis 2: 8x NI 9217

Chassis 3: 4x NI 9205; 1x NI9403; 1x NI9481

As I mentioned, the system is running night and day until this error occurs.

 

Hope, someone has an idea what could cause this error.

Thanks and regards

Socki

0 Kudos
Message 1 of 5
(3,728 Views)

 

  hi sacko,

   The error 6 may be the problem due to disk size full...check this link..

   

   http://digital.ni.com/public.nsf/allkb/2C99F5D635AE184C86256CD1005BBF65?OpenDocument 

   or follow this post

   http://forums.ni.com/ni/board/message?board.id=170&thread.id=186119

 

thanks and regards,

srikrishnaNF

Regards,
Srikrishna


0 Kudos
Message 2 of 5
(3,720 Views)

hey srikrishnaNF

 

Thanks.

In my opinion, the disk can not be full. There must be many GB left.

And after a restart of the system, everything works fine for another 2-3 weeks without deleting any data from the disk.

During the charge and discharge cycles I am also logging data with "Write to Text File" every 5 s. This causes no problems. The error occured both times in connection with the "Write Spreadsheet String.vi" which is only performed after a charge or discharge cycle is finished.

 

Regards

Socki

 

0 Kudos
Message 3 of 5
(3,708 Views)

Any time I see VIs that use a whole bunch of global variables my "danger antennas" start to rise up from the back of my head like a My Favorite Martian episode. The usage of the "Current VI Path" is also another one that does it.

 

That said, where is your code running from? Is it running from a mapped drive? Since the file is being saved relative to the location of the VI, if the path is on a network drive, you might be running into network issues. "Filename" is an input to this VI. Are you sure that it's being given a proper name? No funny characters, or anything? You have NO error handling in that VI, which is BAD. 

 

Other comments: 

  • NO error handling --> BAD.
  • The "Read/Write" should be an enum. Preferably typedef'ed.
  • The premise of the read is to read in the ENTIRE contents of the file just to get the last line. Since this code is run continuously how big do these files get?
0 Kudos
Message 4 of 5
(3,683 Views)

Thanks for your comments

I will consider them for the next update.

 

The code is running locally on the hard drive, so there should be no problem with that.

The file size when the problem occured the last time was 633 KB (6536 lines).

The file name is module5History.txt and does not change during execution.

 

Thanks for your help

 

0 Kudos
Message 5 of 5
(3,676 Views)