Daniel, today I was reviewing some stuff and ran across this community example for PQA, At the time of your post I wasn't aware that we had implemented some stuff like this except when we (NI) had tapped into some private-API functionality. Effectively what is happening in this example is that they are doing some image processing, and then calling that processing up in another VI for display later. They are using queues to do this so that it won't slow PQA down.
You will likely have some trouble getting the code in the linked example to run directly if you are running newer versions of PQA and LabVIEW. I was able to resolve some of those conflicts by doing a mass compile of the LLB in LabVIEW 2011, which is what is required for the version of PQA I'm running, PQA 1.6 However, I think the general idea of how they are queing an image in 'Difference Map.vi' and dequeueing it in 'DMDisplay.vi' is still valuable.
I think you could possibly implement a similar system by:
1) Use a custom user processor from the template, and simply add a queue into the 'calcuate' step that queues the image(s). No other actions would be necessary in the user processor.
2) Call on that same queue in your main VI, in its own loop so it can run independently, dequeue the image and display it. Since data will be coming in at up to 60Hz, and LabVIEW on Windows likely won't be able to loop that fast, you may want to implement a system of tossing out some frames if the queue size grows too large.
Paul Davidson
National Instruments
Product Owner - ni.com Chat
