Benchtop Measurement and Test
Distributed Measurement and Control
Systems Engineering Software
Perspectives showcases how NI sees what’s next in the world of test and technology.
You can request repair, RMA, schedule calibration, or get technical support. A valid service agreement may be required.
Provides support for NI data acquisition and signal conditioning devices.
Provides support for Ethernet, GPIB, serial, USB, and other types of instruments.
Provides support for NI GPIB controllers and NI embedded controllers with GPIB ports.
Make possible that Boolean function accept error cluster as input as this example:
I like and support this idea, but how about pushing it one step further (if possible, of course)?
Why not give the boolean operators the ability to accept and evaluate any cluster containing one (and only one) boolean (the error cluster is an excellent example)?
It would sure have saved me many unbundles in some programs...
> How does it make sense while doing a boolean comparison for a cluster??
It makes sense if the cluster only has one boolean (which is what you use for the comparison) and LabVIEW already does this for specific cases. Try wiring an error cluster into the Select primitive or into a case structure and see what happens.
I agreed with that but after few thoughts I realized that boolean functions also accept integer data, so it doesnt make sense to use the boolean value from the error cluster if there is also an integer which is the error code. I don't believe that NI will consider this idea. What would happen if we connect two error clusters to the boolean function inputs? It chooses the error codes or the statuses?
I wrote a tiny utility routine whose icon is a Stop Sign with a question mark inside it. It "sits" on the error line and has one additional input (called "User Stop") and one additional output (called "Stop or Error"). It's a simple case statement controlled by the error line that either passes User Stop to the output (if no error) or puts a True there. This makes it mnemonic, without "stretching the definition" of booleans. Here's how it looks in the code.
[If you are unhappy with the Stop control and "While Stop" wires coming in on top, simply rewire the VI and put the error lines higher up, or bring the other two wires in on the bottom].
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What do you need our team of experts to assist you with?
We'll be in touch soon!