From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
Currently there is a method for setting the control value of another VI via the Control Value Set Method. But there is no set with signaling method which allows control of VI's which react to changes on front panel controls. This makes it hard to automate VI's that are using front panel control events. There is a tedious work around to get references to control on the front panel and then use value signaling method . It would be very useful to just have one additonal method that does the signaling in additon to setting the value of the control.
Interesting. I was under the impression (based on the first Invoke Node) that Latched Boolean could not be actioned programmatically...
This being said, for automation (aka scripting), I would personally rather send sets of instruction to a state machine via a queue, the state machine being also actionable from buttons and such on the VI FP.
[..] that Latched Boolean could not be actioned programmatically
Yes, you can, using the invoke node. However, not when used to fire an event in an event structure. As fas as I know, the latter is the only limitation for the vi server mechanism to action controls programmatically (and probably for good reason, intrinsically impossible).
[..] I would personally rather send sets of instruction to a state machine via a queue, the state machine being also actionable from buttons and such on the VI FP.
Yes, probably a good programing practice and nice solution.
Our use case is to programmatically activate EXISTING target vi's controls (without the need to alter the target vi). However, you also want to be able to activate the target's vi controls manually, or change the instruction set while the program is running. And you want to be able to use any target vi, also those not intended to receive sets of instructions.
As said, our solution is very convenient in a research environment. And I don't see a good argument against it.
To give you an impression, I show our automation vi front panel.
The instruction set or sequence action is prepared in excel and saved as a csv file.
This file is read by the automation vi (FP shown here) and will activate the target vi (or VI-to-Control).
Once you have it, no need for further programming, just make your sequence action list in excel and run your automation vi.
The only exception (unfortunately), as said before, is that for firing a latched BOOLEAN IN AN EVENT STRUCTURE you need to modify the target vi (vi-to-control) to make it non-latching and "de-press" the button programmatically yourselve.