LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

VIT References and missing queue commands


Ravens Fan wrote:

Now there is some pretty code.

 

I was thinking of one other possibility and would link to your action engine nugget.  Let the main VI be responsible for obtaining the queue for communication to each instance.  (And also disposing of it)  It would store the queue references in an array in the action engine.  Then each instance of the client VI would just get the queue reference from the action engine when needed.  Likewise for the main VI.  All that would be needed would be for each client VI to know which index of the array stores its dedicated queue reference.


 

Thanks!

 

Re: the Action Engine to serve Queue references

 

That is another good approach as well. We could use two arrays, one for the VIT ref and another for the queue ref. The "Get_Queue_Ref" action could accept the VIT's ref num and then do a Search 1d Array on the VIT ref array then use the returned index to select the queue ref.

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
Message 11 of 11
(404 Views)