As you discovered, the Range and Coercion properties of controls do
not work when used in sub-vis.
Your best option is to go ahead and build your range checking into
your sub-vis. If it=92s something you will be doing a lot, just make
your range checking a sub-vi and drop it where needed. This wil
When writing sub-vi's, what is the best way to handle input parameter
range checking? On the front panel I can choose to have numeric
values coerced to be within range, but this does not affect constants
or controls wired to the vi when used as a sub-vi. I can build range
checking into t
