I have a test system where a LabVIEW-built executable (GUI) and a set of worker modules control several instruments. Operators use the GUI to run tests manually and view data. There is also a need for automated test capability for certain tests, which will be handled by NI TestStand.
The plan is to create a Workers module with a Public API so both TestStand and the GUI EXE can send commands and exchange data (request/response). TestStand would call the Public API VIs directly from its steps.
However, I'm not sure this will work when the GUI is running as a standalone EXE rather than in the development environment. I'm concerned that the GUI EXE and TestStand will run in separate memory spaces, so the queue references inside the Workers API would exist in two different instances and wouldn't match.
One thought is to have the EXE launch TestStand and pass the Worker queue references over, if that would help. Another possibility is to package the Worker module as a PPL and use it from both LabVIEW and TestStand. But even then, would the PPL still load into separate memory spaces since the processes are different?
Has anyone implemented something like this? Any guidance would be appreciated.
Thanks!