LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

select function not returning what's expected

My select function is always returning the enum wired to false despite the input being true. Can anyone see why this may be happening? Possibly corrupt? I am doing this on a cRIO not the PC but it's a fairly simple thing to do.

 

0 Kudos
Message 1 of 5
(2,590 Views)

Is enum a type def?  If not you could have different versions of enum.  I've done it before and things got a bit confusing.  Smiley Very Happy

 

Two tunnels exactly on top of each other?

0 Kudos
Message 2 of 5
(2,580 Views)

Are you sure that the case you are showing is the one executing?

0 Kudos
Message 3 of 5
(2,570 Views)

self = idiot -> true. I was in the correct case but the case was stuck in a timeout so it never exited, thus never switched the final boolean to true.

0 Kudos
Message 4 of 5
(2,568 Views)

Well next time try using the Expect function inside of the select. Smiley Tongue

 

Don't feel bad. I once had to post a sample VI because I could not get a control to operate, only to have Dennis tell it was disabled. (that is a double-duh).

 

But while we are the subject of following the wrong track...

 

In LV 2010 RT there is a bug that prevents probes from updating which can (well it did) lead me into la-la-land trying figure out why the case never ran.

 

So if you are debugging 2010 RT and a probe is not updating and you wonder if the code is being executed, don't trust the probe, create an indicator.

 

Ben

 

 

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