Headless architecture for cRIO temperature recording

[D Gabbert]

I am trying to develop a package to continuously monitor temperatures at several data points on aircraft during flight.  I am using a cRIO chassis and a few dozen thermocouples to log temperature data to a .TDMS file saved on the cRIO.  I have developed labview code to take data from each of the thermocouples and log it to the cRIO's memory, but I am coming to a roadblock with making the process headless so that it can run in flight.  Does anyone know a good starting point to find information on how to use the cRIO in a headless architecture?

[Samuel_S · Accepted solution]

D Gabbert,

Here are some good starting guides:

http://digital.ni.com/public.nsf/allkb/86936A249D18000186256FBF0075E95D?OpenDocument 

https://knowledge.ni.com/KnowledgeArticleDetails?id=kA03q000000YHpnCAG&l=en-US

https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000P6xZSAS&l=en-US

Also be sure to check related links, but essentially it sounds like you want to run it as a start up exe:

https://www.ni.com/docs/en-US/bundle/labview-real-time-module/page/debugging-a-stand-alone-real-time...

I think that should get you going 🙂

[AutonomousMode]

Hello Sam,

in order to run a real time controller headless, shall i install NI LV application builder in addition to the rel time module?

Regards,

Samira

[PatJamSim]

Hello Samira,

You are correct, to run headlessly you will need the Application Builder package as well.  As you can see in the links Sam posted above, running headlessly requires you to build your code into a Real-Time executable, and to subsequently deploy that code to your cRIO.  In order to build applications, you need the Application Builder.  This module is included with the LabVIEW Professional Edition and NI Developer Suite, so if you have either of these packages you will already have the Application Builder.  If you have Base or Full LabVIEW, then the module is separate, and is available at the following link:

https://www.ni.com/en-us/shop/product/labview-application-builder-module.html

Good luck working to deploy your application!

[AutonomousMode]

Hello Patrik,

thanks for your fast response. I have the LV Core Professional Development system installed. I have a CRIO 9024 and a robot connected to it. I have a VI that works properly as i run it, but after i build and deploy then run it as start  up  in the Build Specifications tree, it does not run. I need it to run headless. The project explorer page is attached. Can u please help me with that?

Regards,

Samira

[PatJamSim]

Hello Samira,

Looking at that screen shot, what you are seeing is normal behavior.  When you set your RT executable to run as a startup VI, the cRIO will reset and immediately launch the VI when it powers up again.  If you select Yes, does the cRIO reboot and then start running?

There are certainly a few different reasons that could be preventing your code from starting up.  Take another look at the link posted by Sam, seen here again:

https://knowledge.ni.com/KnowledgeArticleDetails?id=kA03q000000YHpnCAG&l=en-US

Make sure you have followed the steps available here.  You should also verify that any shared variable libraries have already been deployed.  You can manually deploy shared variable libraries by right-clicking on the .lvlib in your project explorer and selecting Deploy All.

Another step to try is right-clicking on your RT Target and selecting Disable Autodeploy Shared Variables.  By selecting this option, you can prevent the cRIO from trying to deploy variables that have already been deployed, which can cause your application not to run.

The last piece of advice I have for you is to go ahead and create a new thread for your question.  This thread deals mainly with setting up headless architecture, which you have already done successfully.  By creating a new thread in the appropriate forum for cRIO, you will get more attention from other forum-goers who will be able to help troubleshoot your issue.  Be sure and provide as much detail as you can when creating your post.

Please let me know if any of the information posted here needs clarification.  Thanks, and good luck getting your deployment up and running!

[AutonomousMode]

Dear Patrick,

thanks again for your reply. unfortunately the code does not run even without any shared variables!

Best,

Samira

[PatJamSim]

Hello Samira,

Yes, if you are using shared variables, then in many cases the code would not be able to run without them.  Using the "Disable Autodeploy Shared Variables" check box does not mean your shared variables will not be used; it simply prevents the target from trying to deploy variables that are already deployed.  Trying to deploy variables that are already deployed can cause an application not to execute properly in a headless environment.  

I hope this helps clarify my previous comments!

[AutonomousMode]

Dear Patrick,

Thanks again, buut i mean i changed the vi so that no shared variables are necessary,(attached) but it does not work yet.

[PatJamSim]

Hello Samira,

Unfortunately, the VI you posted isn't very useful because of the multitude of subVIs present in the code, preventing me from seeing what is actually going on.  There are quite a few reasons why your code may not be working properly as an executable.  In order to figure out the cause, much more information is necessary.  For example, it may be possible that your subVIs are not properly included in the build.  It is also possible that one subVI in particular is causing the problem.

As such, I am going to encourage you once again to create a new thread specific to your issue.  Describe the problem you are running into in detail, and describe what your code is trying to do.  Post code or screen shots along with the explanations.  By creating a new thread specific to your issue and giving that thread a relevant title, you will get more attention from forum-goers that may be familiar with the struggles related to deploying an RT executable.  Make sure to include as much information as you can about the behavior you are seeing and the result you actually expect.

Also, take a look at the following links:  

https://www.ni.com/docs/en-US/bundle/labview-real-time-module/page/creating-stand-alone-real-time-ap...

https://www.ni.com/docs/en-US/bundle/labview-real-time-module/page/building-deploying-and-debugging-...

https://www.ni.com/docs/en-US/bundle/labview-real-time-module/page/using-remote-front-panels-to-acce...

These help documents discuss the steps involved in building, deploying, and debugging an RT application, and should be quite useful for you.  I highly recommend going through them and making sure your application is being built properly, then using the debugging tools to get an idea of what is stopping your program from deploying.