How to Stop All Activities on FPGA?

[sadfsadf]

This is a slight modification of the NI example VI to run a loopback test on the NI 9853 High-speed CAN module, on an NI-9074 cRIO chassis. It was originally working, but now it will not run. I just came into the lab to run it again before I started to change the VI, but it gives me this error. The last time I was in here, it worked perfectly.

Multiple people use this computer and other people do have their cRIO projects on this computer, but this is only instance of LabVIEW currently running on this computer. Also, this error does not show up when I attempt to run VIs in other LabVIEW projects, but that those projects use different VIs, so I am not sure if that is the problem.

Is there any way for me to view those "Interactive FPGA VI execution" sessions and end them? Note that I am able to recompile the VI - I just can't run it.

I have attached both the .lvproj and the .vi I am using. I am running LabVIEW 8.5 on Windows XP.

[sadfsadf]

I now have a new problem: Every LabVIEW program except for the one in the original post was working fine. I walked away for a half hour and when I got back I saw the following error:

Now, whenever I try to run a VI, it fails with the following error:

Is it possible that all of these errors are related? How can I start to resolve these issues? Is there any specific LabVIEW/cRIO documentation that may be relevant?

[Jacob_K]

Seeing as how other people have access to the cRIO have you tried formatting the drive on the RT controller and reinstalling the RT software?  You also may want to begin again with the original example and make the slight modifications.  This will allow you to verify that it worked.  If you still have problems run the vi in highlight execution mode so that you can determine when and where the error is thrown.

[sadfsadf]

No, I did not think of that. Would formatting the drive fix the problem of LabVIEW being unable to communicate with the cRIO? Thanks!

[Jacob_K]

Most communication problems with the cRIO are related to losing communication with the network.  One work around to see if your network is the problem is to connect the cRIO directly to your CPU.