10-11-2007 11:06 AM
10-16-2007 04:53 PM
Hi Rusty,
A couple of questions that may help us out:
Before the crash, is there any error message that appears. If so, what does the message contain?
Have you tried reproducing this behavior on another computer?
Moreover, I imagine you've built your application from a vi that is deployed to your cRIO. Does this vi run without error?
Are you using Shared Variables or FIFO's to communicate between your cRIO target and your host computer?
This information may help us identify some culprits to this issue.
Cheers,
Emilie K. | National Instruments
10-17-2007 07:43 AM
Hi Emilie
Thanks for the response. In answer to your questions, there is no error message, only an unresponsive computer. I created this application on my laptop with the chassis hardware connected via USB - I did not see this behavior. All the individual vis in the application ran as "stand alone" without error on my laptop. I'm using no shared variables or FIFO's. There is one instance each of reading/writing to a file. The purpose of this is to save/read active values for the various inputs, hold times, etc.
This application runs in a production environment & while it may not be in use constantly, the code runs 24-7 as this is all the pc is doing. The problem seems to manifest itself every other day. I could email the application to you if you wish.
Thanks again,
Rusty Johnson