03-29-2017 09:32 AM
Hi,
Can I consume a notification send from main TestStand thread within a VI which is fired up in the second TestStand thread?
The idea for the solution is that the main thread will have one loop in which one step will be continuously generating test data for report. The role of the VI running in the separate thread will be to sit and display the current data to the user as soon as it gets notified by the main thread.
So, can I consume TS notification in the LV modules?
Solved! Go to Solution.
03-29-2017 02:15 PM
You can try one of this variants and see, whether it works for you fine.
Sincerely, kosist90
03-31-2017 08:16 AM
It is possible. See the API help for Engine.GetSyncManager. The TestStand synchronization step types have an API to them that you can call from LabVIEW. Also the source code for the step types which uses this API ships with TestStand in the directory <TestStand>\Components\StepTypes\SyncSteps.
Another approach that might be a bit simpler is to use a LabVIEW notification or queue on both ends and thus LabVIEW VIs on both ends.
Hope this helps,
-Doug
04-05-2017 05:40 AM
When I read the value returned by GetSyncManager it looks like a reference. What shall I do with it?
K.
04-05-2017 05:56 AM
The LV functions for notifications do not work with the TS Notifications. You have to use the TS API similar to this:
04-07-2017 04:45 AM
Hi Norbert,
I've changed my VI and now it looks like as below. However, I can't see the way I can get the notifier value.
K
04-07-2017 06:57 AM - edited 04-07-2017 06:57 AM
Kamil,
you mistake the synchronization objects for an information technology between different software components outside of TS.
The TS synchronization objects are solely for TS internal synchronization stuff. In the first place at least.
But as the API is public, you can implement code to use them in most programming languages (like LV, C#, ...). But you still have to think like TS does.
When you use a notification internally in TS to pass data around, you configure your WAIT (on notification) step as such that the data is automatically parsed into a TS variable. And this is exactly what the Wait method exposes as parameters:
What you essentially have to do: