From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Selective sampling of multiple thermocouples

Solved!
Go to solution

I am trying to use a cRIO 4-slot chassis to sample and record up to 64 thermocouples.  Right now I can only sample the entire 64 channel set, but my desired product is a program that can sample and record any subset of thermocouples, selected by the user from the front panel.  The best I have come up with is using Boolean controls to turn the output of deselected channels to "0," and a series of LEDs next to the chart's legend to indicate which channels are recording true values and which are recording "0."  I want to use the Boolean controls to keep the program from recording the deselected channels at all.  I've attached a few pictures from my program.  The first is a portion of my data acquisition function, which takes the value of each thermocouple and puts it in an array to plot on the chart and record to a .TDMS file.  The second is a portion of the channel naming function, which combines the names into an array for the .TDMS file and sends each name to an indicator next to the legend of the chart.  The third shows the chart, with all channels deselected and unnamed.  Does anyone have any ideas how I can make this program more easily expandable from the front panel?

Download All
0 Kudos
Message 1 of 3
(2,167 Views)
Solution
Accepted by topic author D Gabbert

I would work with clusters/arrays instead of explicitly using each channel name, etc.

 

See my sample code attached.  It is very simple, but should give you some ideas.

 

 

>

"There is a God shaped vacuum in the heart of every man which cannot be filled by any created thing, but only by God, the Creator, made known through Jesus." - Blaise Pascal
0 Kudos
Message 2 of 3
(2,151 Views)

You are aware of that a cRIO shouldn't have a front panel ?

The cRIO is an embedded controller, that should run a exe file by it self when you deploy you program after delevopment.

You are not able to run a vi on at cRIO without the development environment.

0 Kudos
Message 3 of 3
(2,136 Views)