LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

multiple boolean values to be used in case structure

Solved!
Go to solution

sukanya wrote:
Yeah, I realized that when I changed the display pattern to "\" Codes display! There were some carriage returns, line feeds etc. Can't believe I wasted so much time on something this simple.

We've all done it once or twice.  Don't beat yourself up!


"Should be" isn't "Is" -Jay
Message 11 of 16
(2,352 Views)

Jeff Bohrer wrote:

sukanya wrote:
Yeah, I realized that when I changed the display pattern to "\" Codes display! There were some carriage returns, line feeds etc. Can't believe I wasted so much time on something this simple.

We've all done it once or twice.  Don't beat yourself up!


Ditto that!

 

I had a trailing space in a folder spec that the DSC Historical trends VI did not complain about unitl I tried to read the trend. Then the reader and the Windows Explorer refuse to let me delete since trailing spaces are not allowed in folder names (then why did it create them!?!). The good news was we upgraded the PC so I did not have to reformat the dirves to get rid of those folders.

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 12 of 16
(2,342 Views)

and if the values aren't exclusive? Is there a...lets say cleaner or more professional way of developing it than the one commented before? (http://forums.ni.com/t5/LabVIEW/how-to-find-valid-cases-in-truth-table/m-p/1017400?query.id=112270#M...

 

 

0 Kudos
Message 13 of 16
(2,098 Views)

Hi Pablo,

 

Does the post you referenced give you a solution? What do you mean by cleaner? Which forum discussion is more relevant to your issue, the one you posted on, or the one you referenced?

Ricky

National Instruments
Applications Engineer
0 Kudos
Message 14 of 16
(2,062 Views)

Can you elaborate more on this. Because, I'm facing somewhat similar problem.

In the file I have attached, on the right side, the LabVIEW coding is correct. But, is there any other way to do it professionally. I want all the four case structure to be dependent on each other with respect to further errors

0 Kudos
Message 15 of 16
(1,049 Views)

This thread is 8 years old and I doubt the original authors are still monitoring it. It is also already marked as solved, robbing you of the opportunity to acknowledge a solution to your question, potentially lowering the probability of help.

 

You question makes no sense and your VI makes very little sense.

 


@DivChand wrote:

I want all the four case structure to be dependent on each other with respect to further errors


I have no idea what that even means. Dependent in what sense?

 


@DivChand wrote:

In the file I have attached, on the right side, the LabVIEW coding is correct. 


No, correct would be to use an array of booleans and a FOR loop, eliminating all the duplicate code and using a single property node with two elements. Even easier, show the plot visibility checkbox and none of this is even needed!

 

What problem are you trying to solve?

0 Kudos
Message 16 of 16
(1,032 Views)