LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Named Queues, Application Instances, Proxy Callers and what did I miss-read from the help file?

Solved!
Go to solution

In a nutshell, I want to launch a few clones of a reenterant vi within the context of a LabVIEW Project.  Yes, I launch the Clones via ACBR and pass an integer into the clones to set up the named queue( "MyClone_%d")

 

The "Clones" appear to be in the context of the calling project.  The Hieriarchy view shows "Proxy callers"  e.g. "MyReenterant.viACBRProxyCaller.<.int> " And yet, NAMED Queues to the clone instances appear to have no relation to the clone named queues?

 

SO, How do I name a queue so that it can be passed into a specific clone of a vi that is within the context of the same project?


"Should be" isn't "Is" -Jay
0 Kudos
Message 1 of 4
(2,872 Views)

I don't quite understand your description, but know from experience that named Queues work fine in clones "launched" by ACBR.

0 Kudos
Message 2 of 4
(2,862 Views)

@drjdpowell wrote:

I don't quite understand your description, but know from experience that named Queues work fine in clones "launched" by ACBR.


That is the trouble I'm having!

 

 

Try to change the status of the sub-ui's via queue... then delete the file.


"Should be" isn't "Is" -Jay
0 Kudos
Message 3 of 4
(2,845 Views)
Solution
Accepted by topic author JÞB

Ah, your problem is you are using option 0x40, clone pool, in addition to 0x80 for your Open VI ref.   The reference you get is a reference to the pool of clones, not a specific clone.  Thus, the actual clone you start is not the same as the clone you place in the sub panel.   Change the Open VI ref options to just 0x80.  Then it works, as each reference now points to the specific clone.

 

Message 4 of 4
(2,833 Views)