LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

overcoming error 116

 

Hi All,

 

 

I have many binary files from which I cannot seem to read the data, always recieving a "116" error code.

 

 

I am a tad confused since I have to cRIO's doing more or less the same thing, one I can read the files from, the other I can't.  The setup is thus, one cRIO networked to the other (For this instance named A and B).  Data recorded by and saved onto the hard disk in 30 second chunks by both cRIO's A and B.  Immediately after saving the file on cRIO A, the file is then FTP sent across to cRIO B, I have used a sequence structure to try and ensure the file is closed off prior to FTP.  cRIO B then FTP’s all of the binary files it has (4 files per 30 second batch, 3 from cRIO B and 1 from cRIO A) across to an FTP server.

 

 

I know there are other less clunky ways of doing it, but this is the only method I have used so far which actually keeps the cRIO’s running past 15 minutes!!!

 

 

The data going into the files I am having problems with is a 2D array of 32 bit singles which is roughly 53 rows by 24000 columns.  I would expect the file size to be in the region 5MB per file.  The files being recorded by cRIO B (which has more processes to carry out) are consistently in the region of 4,9XXKB and are as far as tested perfectly readable.  However the files from cRIO A vary from tens of bytes to a couple of MB and have so far been unreadable.

 

 

I have now split up the saving and FTP transfer into separate loops to try and solve the problem, so far untested I'll repost if this solves the problem, but is there anything obvious that I am missing which could be causing the issues?

 

 

Cheers,

 

 

Dom

 

0 Kudos
Message 1 of 3
(2,955 Views)

Hi Dominic,

 

Thank you for posting on this forum.

 

I have found a document that could provide a few solutions to solve the error you are getting:

http://digital.ni.com/public.nsf/allkb/3F3140986E3AB3F4862574A4007809CA?OpenDocument

 

Have a read through this and see whether you manage to solve this issue.

 

Regards,

Shalini B
Applications Engineer
National Instruments UK & Ireland
0 Kudos
Message 2 of 3
(2,933 Views)

Thank you Shalini,

 

I managed to sort the problem, it was an issue with the data type I was using and how I was defining the file size that was affecting how it was being recalled.

 

Thanks anyway

 

Dominic

0 Kudos
Message 3 of 3
(2,928 Views)