10-21-2021 09:33 PM
Hello all,
I am working on a project & I am very new to LabVIEW & Teststand both. This project consists of a main GUI, a teststand operator interface & a test sequence.
How the project works?
Part 1 - Main GUI (Refer screenshot 115 & 116)
Part 2 - Upgraded Teststand operator interface (Refer screenshot - 117 & 118)
Part 3 - Sub VI inside 'Teststand operator Interface' (Screenshots 95 & 97)
Project status -
My queries -
VI's and its names in my project
Thanks & Regards,
Surabhi
Solved! Go to Solution.
10-22-2021 10:44 AM
You need to use UI Messages to pass information to and from your sequence file to the UI:
https://knowledge.ni.com/KnowledgeArticleDetails?id=kA03q000000x3tWCAQ&l=en-US
If you need to get it from the UI to the sequence file you post a UI message from the sequence file with the sequence context. Then you can set variables from there back to the sequence file.
Hope this helps,
10-22-2021 10:46 AM
Also, I will be presenting at the GLA Summit on building User Interfaces in LabVIEW for TestStand. I will demonstrate UI Messages.
10-27-2021 05:09 PM
It is also possible to use synchronization objects. See this.
If we want to have LabVIEW-based synchronization then we could use TCP (AMC?) or in some cases simple LabVIEW queues.
But as it was mentioned, NI recommends UI Messages in this case.
12-07-2021 07:05 AM
Hey jiggawax,
The concept of Using UI messages in my case solved my problem. Thanks for the solution.
But right now I am facing a new problem. The problem is that the Global variables works fine in the Labview development environment & my Teststand sequence was able to read those Global Variables as File Globals, but this does not work when I run the compiled executable in the runtime. My Teststand sequence is not at all picking the Global variables value.
Do you have any solution to resolve this?
12-10-2021 12:59 PM
@SiSp wrote:
Hey jiggawax,
The concept of Using UI messages in my case solved my problem. Thanks for the solution.
But right now I am facing a new problem. The problem is that the Global variables works fine in the Labview development environment & my Teststand sequence was able to read those Global Variables as File Globals, but this does not work when I run the compiled executable in the runtime. My Teststand sequence is not at all picking the Global variables value.
Do you have any solution to resolve this?
FileGlobals do not change based on if they are in the runtime and/or the development environment. So I'm surprised you are seeing this behavior. Do you mean that the UI is compiled to a an executable? And then you changed the adapter? the adapter for LabVIEW has absolutely nothing to do with the UI so that seems odd to me.