Not able to run cRIO LabVIEW RT application stand-alone (runs fine in development mode)

[BigEv]

Strange Issue.

I am trying to deploy an RT application to a cRIO-9074 controller.  I have developed the application in development mode and everything works and appears to be debugged.  However, when I attempt to build then deploy the application as startup, the application appears to start running, then stop cold (based on processor utilization as shown in the NI Distribution System Manager).  At this point, I cannot debug because the application is stopped (no variables get updated).  

The issue appears to be related to the library NI_AALPro.lvlib because if I disable the the function Polynomial Evaluation, the code will compile and start up fine.  I am tempted to recreate the required functions and create my own library, but I would rather find the issue and fix it rather than re-create the wheel...

Is there any possibility that the wrong library is being uploaded to the controller?  If so, is there any way to force the proper library to be uploaded to the controller?

Thanks for any help.

[Toader Mihai]

Hello,

The development platform isn't purely deterministic like the RT system on the cRIO, what I mean by this is that I believe that the performance that is required by your application cannot be met with the timing you imposed and are starving some processes or tasks in your vi(cannot get adequate processor time). You can debug this using the RT Trace Tool or try to see if this is the case or simply use a more relaxed timing for loops helps with this problem.

If the problem still persists please post a screenshot of your VI or attach it so I can better understand the problem.

Regards,

Toader Mihai

[BigEv · Accepted solution]

Toader,

Thanks for the reply.

I believe I've solved the issue.  For some strange reason, the functions inside the NI_AALPro.lvlib were not available on the cRIO at run time when the application attempted to run in stand alone mode.  I ended up adding the library to the Always Include section of the Source Files tab in the build specification and the program now runs.  I'm not sure what the issue is, but this works.  

Thank you Morgan from NI.

Kind Regards,

Big Ev