LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Error 116 occurred at Read Dlog File+.vi:Read File

I'm having problems in LV 8.0 with the waveform file I/O vi's. I've attached a simple program to demonstrate my problem along with the errors I get. The error does not happen all the time, sometimes I can execute the vi 3 or 4 times with no error then the next time bang.... the error shows. In the file dialog box I simple number the files created everytime. ie 1 for the first run; 2 for the second run etc...
 
The following text is displayed in the error indicator.
"Error 116 occurred at Read Dlog File+.vi:Read File
Possible reason(s):
LabVIEW:  Unflatten or byte stream read operation failed due to corrupt, unexpected, or truncated data."
 
any idea?? The error seems to show up more if I wait 10 seconds between runs.
 
Maybe some sort of stream buffer problem?
Download All
0 Kudos
Message 1 of 6
(3,868 Views)
I found the error comes from the Read Datalog.vi
 
I will ask for tech support.
0 Kudos
Message 2 of 6
(3,860 Views)
Hey WantToGolf.

I ran your VI a few times and didn't see any errors (aside from the first couple of times since I didn't have my file types correct), so I went ahead and created my own just to see if I could create that error.  If you reproduce this VI do you get any errors? 



Repost if so!
Andy F.

Message Edited by Andy F. on 04-21-2006 05:43 PM

-----------------------------------------------------------------
National Instruments
Message 3 of 6
(3,846 Views)

Thanks for the reply Andy Smiley Happy

I have downloaded the LV8.0.1 update and now I have no errors at all. Problem solved.

0 Kudos
Message 4 of 6
(3,834 Views)

Hi Andy F.,

I am also experiencing the "error 116" problem when trying to read wavform files.  I recreated the read/write prog. that you posted and it also results in error 116.

Please help.

Thanks,

Chris H.

0 Kudos
Message 5 of 6
(3,519 Views)
Chris,

What version of LabVIEW are you using?  As you can see from the previous post, upgrading to 8.0.1 from 8.0 has fixed the problem for others.  If that is not the problem, could you post your code so I can try to replicate the issue?  Thanks

Brian
0 Kudos
Message 6 of 6
(3,497 Views)