09-09-2014 02:24 PM - edited 09-09-2014 02:29 PM
@crossrulz wrote:
You could avoid that all together by using the Compound Arithmetic Node set to OR instead of the Build Array. Then you don't have to do the search either.
then how do i index out the correct tab# through the search 1D...."using the Compound Arithmetic Node set to OR instead of the Build Array."?
09-09-2014 02:41 PM
@jmejiagusmer wrote:
Well, it was working in the sense that I could select the different tabs and it would record the data points onto the graph every 30 seconds. My booleans were lighting up as expected, as well. However, I realized that when I was on tab 1, the tab 2 data points would not record on the graph and vice versa. Ididn't have the tabs cycling, either. Here is my original VI.
Don't connect the tab to a case structure.
All code needs to be in the loop (why don't you have a while loop? Are you using continuous run?)
09-09-2014 02:47 PM
If I don't connect the tab to a case structure, then what would I connect it to? I don't have a while loop because I thought that this could all be done with the case structure. I was using continuous run, yes.
09-09-2014 02:56 PM
What are you using for your booleans that correlate with too hot and too cold? I can't find a single boolean that looks like that.
09-09-2014 06:39 PM - edited 09-09-2014 07:02 PM
@jmejiagusmer wrote:
What are you using for your booleans that correlate with too hot and too cold? I can't find a single boolean that looks like that.
those are your indicators from your tabs....recommend LV tutorials
here's a little bit more of a simulated example and see if you understand, you have a control loop and 3 parallel daq acquisition simulated loops for your thermal couples.
09-10-2014 02:48 PM
@apok wrote:
@jmejiagusmer wrote:
What are you using for your booleans that correlate with too hot and too cold? I can't find a single boolean that looks like that.
those are your indicators from your tabs....recommend LV tutorials
here's a little bit more of a simulated example and see if you understand, you have a control loop and 3 parallel daq acquisition simulated loops for your thermal couples.
I didn't realize that "view as icon" was selected by default on my LabVIEW so that's where the confusion was. What do the constants which are wired to the true terminal of the select functions represent?
09-10-2014 02:54 PM
@jmejiagusmer wrote:
What do the constants which are wired to the true terminal of the select functions represent?
They are just some increments that make the three rooms behave differently.
(I believe that apok's code is excessively complicated. For example the three lower loop could be conbined into one. Many other parts could be simplified, I think)
09-10-2014 04:40 PM
@altenbach wrote:
@jmejiagusmer wrote:
What do the constants which are wired to the true terminal of the select functions represent?They are just some increments that make the three rooms behave differently.
(I believe that apok's code is excessively complicated. For example the three lower loop could be conbined into one. Many other parts could be simplified, I think)
If I were to combine the three loops into one, then what would be wired to the shift registers?
09-10-2014 04:50 PM
@jmejiagusmer wrote:
If I were to combine the three loops into one, then what would be wired to the shift registers?
The same things that are wired now. Altenbach is suggesting putting all of the code that is in those 3 loops into a single loop. This makes sense since they all run at the same rate and it would eliminate the need for more readers of the stop local.
09-10-2014 04:55 PM
@crossrulz wrote:
@jmejiagusmer wrote:
If I were to combine the three loops into one, then what would be wired to the shift registers?
The same things that are wired now. Altenbach is suggesting putting all of the code that is in those 3 loops into a single loop. This makes sense since they all run at the same rate and it would eliminate the need for more readers of the stop local.
Thank you. I wasn't aware that multiple shift registers could be placed on a single loop.