sbRIO deployed code does not behave the same as when downloaded from PC

[lprugh]

We have an application that behaves differently when it is booted into the RT system. The FPGA code has been flashed. Is there a difference on how the FPGA and RT communicate when the sbRIO is booted as a stand-alone unit vs running software that is download from a PC?

Thanks in advance.

Lou Prugh

[StephanieA]

Hi Lou,

Can you elaborate a bit more about when you say 'the application behaves differently.' How is it different? Is it slower, are you getting back bad data? Errors? etc.

There is a slight difference if you want to make your sbRIO run as a stand-alone application versus running software downloaded from a PC. You will have to either have a start up executable (built with LabVIEW Real-Time Module)  or you will have to create an application on your PC that will perform network communication with the sbRIO.

[Spex]

One common difference between running an RT VI with the host PC versus running the VI as a headless startup application is the user interface.  When running with the host PC, LabVIEW will emulate a user interface, but without the host PC, any functionality that uses that emulation will not succeed.  For example, if you are using any UI property nodes to read or write to front panel controls/indicators, those nodes will fail. 

One way you can start debugging this application is to build a debuggable application that waits for a connection from the debugger before executing.    You can find the instructions for building a debuggable application here: https://www.ni.com/docs/en-US/bundle/labview-real-time-module/page/debugging-a-stand-alone-real-time...

If the application appears to work when in debug mode but not when running headless, I would suspect that your application has a UI call somewhere inside.  If the application continues to mis-behave while in debug mode, then the debug console should help you find the sticking point in your application.

Regards,