Using Named Queues and Notifiers in UI and TestStand Sequence

[Will_S.]

Hi Folks,

I am interested in hearing what TestStand users think about using Named Queues and Notifiers for communicating between a LabVIEW UI built as an EXE and the Test Sequence (or rather, the VIs the Test Sequence calls) it is running in the TestStand engine.

I know the recommendation is to completely split development of Test Sequence and the UI, and that they should have minimal reliance on each other. I also know that synchronous UIMessages are recommended for the communication between UI and Test Sequence. I am just curious if others have had success getting named queues or notifiers to work in an EXE setting, what their process is, and what type of issues or caveats they have encountered using that method.

Thanks,

[WireWeaver]

The big consideration is probably how TestStand interacts with LV app instances. It's also worth noting that TestStand Sync objects (such as queues and notifiers) support names that work across processes or even stations, so you could use them to get similar functionality with no consideration of app instances, but probably a small performance hit.

Hope this helps!

Trent