04-12-2017 07:53 PM
Hello. I'm using LV2013 with a cRIO-9074. As a quick start I picked the LabVIEW Real-Time Control on CompactRIO (RIO Scan Interface) template. I modified the template I/P, modules in my cRIO, etc. It works fine when running it in interactive mode (running via the PC), but does not work when compiling and running the RT code as the startup program on the cRIO. This leads me to think there is something missing in either the cRIO code or the build spec for the compile. I've installed ALL drivers listed as available in MAX, and have the build spec setup for "Always Include" for everything but the main RT_MAIN.VI. There is no broken arrow with the VI when I look at it on the PC, but if I use 'Debug Application or Shared Library' to look at the VI running on the cRIO it DOES have a broken arrow - and thus not running. I've played with the Disable Diagram structure around certain sections of the block diagram. I can get it to run with the main Message Handling Loop, RT Loop - System Health and Monitoring.vi, RT Loop - RSI Low Speed.vi, and RT Loop - RSI Control.vi all disabled. Any suggestions??
Solved! Go to Solution.
04-13-2017 12:40 PM
Do you have a library that hasn't been deployed? Without any code it's impossible to say but I have had issues before that stemmed from global variable libraries that weren't deployed before running a VI. There is an option I believe to automatically deploy libraries.
04-18-2017 03:52 PM
I racked my brain looking at all libraries and it appeared they were all included in the build as well as manually deployed (just in case). And the 'Disable Autodeploy Variables' was unchecked - meaning autodeploy enabled. Not I've been trying several different things as well to make it work but I THINK what made the difference is changing all shared variables to 'Network-Published' variable types - they were 'Single-Process' by default. It this was the difference maker, I'm not sure why they were set to 'Single-Process' in the LV2013 template if the code is supposed to be deployed to an RT Target.......
Anywho, it appears to be working now. Thank you for your response.