Real-Time Measurement and Control

cancel
Showing results for 
Search instead for 
Did you mean: 

Labview executable crashes system

I have a system running a labview 8.2.1 executable that periodically causes the Windows XP system to completely crash. The computer must be turned off at the switch or removing power as nothing else will respond. The system is fairly simple with a compact rio chassis containing an 8 bit digital input module & one relay module used as digital output. The code is quite simple, monitoring 6 bits of input, which, when "made" causes two output bits to be set actuating two solenoids. The system then waits for two of the input bits to be deactivated before starting the sequence over.
 
The operator has no need to interface with the pc otherwise & the hard reset needed in this instance is a pain.
 
Any thoughts on what would cause the system crash?
 
Thanks for any insight...
 
Rusty Johnson
Honeywell
0 Kudos
Message 1 of 3
(3,281 Views)

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

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

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

0 Kudos
Message 3 of 3
(3,245 Views)