Data exchange between internal and external labview code

[_Y_]

Sorry for a simple question.

I have a TestStand sequence that uses units/tests written in LabVIEW. The sequence is started extermnally with a stand alone LabVIEW program. I need to establish simple exchange of information between LabVIEW units of the sequence and the external LabVIEW code.

The information is simple Strings eventually sent in both directions. 

Please advice which way of commumnication shall be implemented.

Unfortunately, arttempts to search NI website (or Internet) result in a lot of irrelevant information. Probably I cannot shape out proper keywords. So there is a need in your help.

Thank you

[Norbert_B]

I expect your "external LabVIEW application" to be the application which would be called "user interface" by NI.

There is no direct data exchange possible unless you implement something using standard inter-application communication channels (e.g. TCP).

The recommended way by NI would be to use TestStand custom UI Messages to send information from the code module via TS to the UI.

Norbert

[PrismGreg]

You could try named queues in LabVIEW to transfer your data between code modules and the user interface.

[Norbert_B]

---

@APSGreg wrote:

You could try named queues in LabVIEW to transfer your data between code modules and the user interface.

---

This will not work as the UI EXE is a different application instance as the code modules. Yes, you can make the code modules to execute in the EXE context ("Runtime Server"), but this is way more complex than using UI Messages.

Norbert

[_Y_]

Unfortunately it has to be deployed to computers that do not have development environment.

However, your answer is very important: there is no easy and/or conventional solution. So, I shall  try to create something on my own.

Thank you.

[Dennis_Knutson]

The conventional solution is ui messages as already mentioned. The very loose coupling between the ui and the sequences/code modules is one of the benefits of TestStand and you seen to want to break that. Why? What sort data needs to be passed?

[_Y_]

So far my knowledge is not sufficient to understand teh benefit. Probably I will come to it soon

The need is in introducing some initial information (f.ex. user ID) in the sequence and displaying intermediate/final status in the UI.

[Norbert_B · Accepted solution]

---

@_Y_ wrote:
[...]The need is in introducing some initial information (f.ex. user ID) in the sequence [...]

---

Use a UI Message to query for that data (data available in UI, sequence execution requires it).

---

@_Y_ wrote:
[...]and displaying intermediate/final status in the UI.

---

Use a UI Message to pass that data for display (data available in sequence execution, UI requires it)

Norbert

EDIT: Btw, you should use the TestStand user management for tracking user IDs. This gives you more options and security than some custom implemented stuff in the UI.

[_Y_]

Thank you.

And thank you for your time.