LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

How to use User-Events and Queues between Executables

Solved!
Go to solution

Hi ,

 

thanks for this idea. But I don´t unterstand it. 

 

"The user event in LabVIEW essentially has 3 subcomponents in it that you would need to ensure get copied over TCP.

1. The reference (data type + pointer to a memory address where events can be sent).

2. The registrations

3. The data sent with each event"

 

How can I implement this. The reference is only valid in one executable. There is a possibility to do this by vi-server, but all my tries didn`t work

0 Kudos
Message 11 of 17
(376 Views)

avogadro5, thanks a lot, I´ll check this.

0 Kudos
Message 12 of 17
(376 Views)

Hi,

 

I checked this and I think, thats nearly that I´ve found in an very old post, but without an example... so thanks a lot. 

 

But 🙂 :  You wrote in the client-vi --> "reference from remote program: we can't use it in this app". Thats the reason, why, if I made an executable from the client-vi, it doesn´t work...

 

Or did I made something wrong. Is it nescassary to load it from the executable-path?

 

But the solution is not far away for me...yeah 

0 Kudos
Message 13 of 17
(336 Views)
Solution
Accepted by topic author Tanchris

@Tanchris wrote:

Hi,

 

I checked this and I think, thats nearly that I´ve found in an very old post, but without an example... so thanks a lot. 

 

But 🙂 :  You wrote in the client-vi --> "reference from remote program: we can't use it in this app". Thats the reason, why, if I made an executable from the client-vi, it doesn´t work...

 

Or did I made something wrong. Is it nescassary to load it from the executable-path?

 

But the solution is not far away for me...yeah 


If you built the client into an exe, then I expect what failed is the node that opens a VI in the remote app from disk:

avogadro5_0-1726762041124.png

 

This path is not actually on disk in a normal build, it's a "virtual" path inside the built client exe and can't be opened from outside the client exe. You can work around this using the build spec to have the client VI in the support folder instead of inside the exe: 

avogadro5_1-1726762172297.png

Which results in the VI being placed in the data folder.

 

Message 14 of 17
(328 Views)

in the LV7 / LV8 time I used to share action engines between 2 LabVIEW built apps, both running on separate Windows PXIs


I took me a while to dig the lava forum thread about this, if it may help...
https://lavag.org/topic/7732-how-to-shared-a-fgv-between-2-lvprojs/


We have two ears and one mouth so that we can listen twice as much as we speak.

Epictetus

Antoine Chalons

0 Kudos
Message 15 of 17
(310 Views)

Hi,

 

that works fine...thanks. 

 

Is this VI actually part of the executable or not? Or how do I call it so that it is not part of the exe?

0 Kudos
Message 16 of 17
(189 Views)

@Tanchris wrote:

Is this VI actually part of the executable or not? Or how do I call it so that it is not part of the exe?


The VI is not part of either EXE because I configured the build spec to put it on disk in the support folder instead of embedded inside the exe. This page has info about that setting under "Destination" https://www.ni.com/docs/en-US/bundle/labview-api-ref/page/resource/framework/providers/builds/appbui...

 

If you run that build spec you can see the VI is in the data folder next to the exe file.

0 Kudos
Message 17 of 17
(172 Views)