12-14-2012 02:32 PM
Hi,
We have this compact RIO machine and I've been trying to write labview code that would perpetually run on it in scanning mode. The problem I am having is that I often find my self being able to just run the code from labview (no broken arrow) but when I dbuild and deploy the project, the cRIO does not like it. Trying to operate the remote pannel gives error "VI is broken and cannot be viewed or controlled." In the build properties I've made sure to check the "Disconnect type definitions" checkbox.
I was wondering if people have had similar problems and more importantly how to track the source of the problem. I cannot see any error messages on the console, LabView itself thinks the VIs are runnable, so the only thing I can do is selectively start removing code, which is highly non-ideal (especially in a visual programming language like labview).
12-14-2012 03:41 PM - edited 12-14-2012 03:42 PM
12-14-2012 03:48 PM
Here's the code. I am more interested in a process of figuring out these problems. is there some log where I could see what is causing the VI to be broken? Or is there a quide saying "X can be done in regular labview, but not when it's running on cRIO?"
12-14-2012 05:53 PM
Ok when I turn on debugging and click view warnings, it says the XNode is broken, indicating the offending element is a timed loop.
Anyone encountered error like that?