08-17-2018 07:02 PM
I have a TestStand sequence that sets and reads values from several serial port devices during a lengthy test. The users would like a separate LabVIEW GUI that shows those values as the test progresses. This brings about two questions: 1) How do I launch the GUI VI from a TestStand step so that the sequence then continues rather than waiting? 2) How do I arbitrate the two pieces that will both want to read and write the serial ports perhaps even occasionally at the same time? Suggestions would be appreciated and example code is worth a thousand words.
08-20-2018 04:52 AM
Create a LabVIEW GUI (Which should be capable of Communicating with the Modules which interacts with serial ports)
Call the LabVIEW with GUI as an asynchronous call
08-20-2018 09:18 AM
Thank you for your response Palanivel. Since I'm not very familiar with the asynchronous call option I would need more detail to implement what I'm looking for.
08-20-2018 11:48 PM
How to Select Asynchronous Step.
08-30-2018 07:48 PM
Does that asynchronous call get you what you need or do you still need help with how to get your TestStand sequence and LabVIEW VI to both be able to work with the same serial device?
If you are still having issues with have 2 things talking to the same device you may want to look into a single VI the actual does all the communication and then interact with this VI from TestStand and the GUI through queues, events, or some other type of messaging. In fact your GUI may be able to be the main communication VI.
09-05-2018 05:18 PM
Hi DW
I am partway there but the full application may have problems related to the two things accessing the serial port asynchronously. I was thinking of something along the lines of what you suggest. The GUI VI acting also as a continuous server of tagged data and TestStand could pull what it wanted when. The only thing is there is a lot of distance between an idea and a working, reliable application so I would like to keep it as simple as possible. Any thoughts?