07-24-2014 09:05 AM
Hello,
Ik have 2 vi's which I want both own the same queue.
- 1 client
- 1 server
In labview development it works.
Does it work in runtime when calling from teststand?
07-25-2014 08:03 AM - edited 07-25-2014 08:03 AM
Ok I now put the 2 VI's in a project and call the VI from project in teststand.
Now I see a problem.
When I first start looking for the "Data queue" which the server will create the code will wait for it until it is created.
When I close all and start looking for the queue which will be created by the server I find a queue but I did not create one.
Some how the queue stays in memory because I don't get an error when looking for the queue.
Maybe the project stays in memory?
08-01-2014 03:22 AM
Greetings,
I am having a hard time understandin the issue you describe. Could you I get you to outline the problem in more detail and even post your code or screenshots of it?
08-18-2014 12:54 AM
It's solved now.
I sometimes have problems with teststand when running a-synch vi's.
Don't exactly know what it is.
08-19-2014 07:50 AM
InspectorGadget
Do you want to share with the rest of us what you did to resolve this, so others in similar situation could have a look?
Also, what problems do you have running asynchronous VIs in TestStand?
08-19-2014 07:54 AM
Well the primary problem was that the CUEUE was not shared between 2 vi's in runtime, when I put them in a project they then share the same memory I guess.
Question still remains, when starting a sequence asynchr why does the sequence waits at the end of the sequence while the asynchr VI is running.