01-06-2017 02:16 AM
Hello,
I have labview executable application, it has some drivers that are accessed by queues inside program. I want to use teststand and call these drivers. What would be the correct approach? From what I understand we can not acces labview functions from another application instance and expose queues etc.
My idea was to add network communication to each driver like tcp or network streams so teststand functions can connect to driver and retrieve some data. But this will have some overhead and will be much slower than accessing queue or some global variable directly from LV.
Do You have any suggestions?
01-06-2017 04:24 PM
Hi,
well there ary multiple ways how ot do that. For example you can enable ActiveX server for you executable and after that you can use build-in ActiveX API on the TestStand side to interface directly you LV executable.
Regards,
Ondřej K.
01-09-2017 02:35 AM
So By ActiveX I will be able to acces into labview queue and therefore request some actions on that driver? What are other commonly used options?
01-09-2017 04:32 AM
Well application instance have protected memory scope so other options are network communication or some sort of communication daemon compiled as .net library created in LabVIEW or MS Visual Studio (this solution will be very difficult to debug and maintain). I believe making your own ActiveX API which will provide public access methods to interface your app from TS sound like a good idea. Or you can do it other way round - calling and controlling TestStand from your LV application using TS API.
Regards,
Ondřej K.
NIEE AE