10-02-2006 07:03 AM
10-02-2006 07:33 AM
10-02-2006 08:02 AM
10-02-2006 08:47 AM
10-02-2006 09:09 AM
10-02-2006 01:59 PM
Basically you can not create your own Active X server with your own object hierarchy and methods in LabVIEW. LabVIEW however can export a predefined Active X server interface that is just another access method to its internal VI server interface.
@skalis wrote:
Thank You. Good to know that I am on the right track.
However, Your sentence "If You look at the several shipping examples..." make me little concerned. I am not able to find any example of a LV ActiveX server in my LV 8.0 installation. I would be very grateful of You can send me any.
02-28-2007 08:06 PM
@rolfk wrote:Basically you can not create your own Active X server with your own object hierarchy and methods in LabVIEW. LabVIEW however can export a predefined Active X server interface that is just another access method to its internal VI server interface.
@skalis wrote:
Thank You. Good to know that I am on the right track.
However, Your sentence "If You look at the several shipping examples..." make me little concerned. I am not able to find any example of a LV ActiveX server in my LV 8.0 installation. I would be very grateful of You can send me any.
With this interface you can determine what VIs are available to control, load specific VIs from disk if you know their path and, execute those VIs and passing parameters to it and receiving outputs.
So if your software allows you to script the Active X access to an Active X server in some ways such as VBA or similar you should be fine. If your software expects a specific Active X interface you have to implement in the server application, you are out of luck with LabVIEW, without using an external component such as an extra Active X server DLL that translates between the expected interface and the exported LabIVEW interface. But this last method is quite likely not worth the hassle.
Rolf Kalbermatter
03-01-2007 12:32 AM
That Interop DLL is presumably a .Net wrapper around the LabVIEW Active X server class. You asked for an Active X server interface not a .Net interface. But I guess if you want to access it from C# you might need to go the .Net route.
@Wes Ramm wrote:
While I did follow the link mentioned above and found the Interop.LabVIEW.dll that is included in the C# project for the purpose of calling VIs from C#, I am frustrated that these methods are 'buried' in a .dll that you have to go and find on the NI web site, and are not ActiveX methods that are available in an ActiveX Object that is installed when you install LV 8.20 PDS.
Rolf, I don't know that you will get this email, but are you refering to the methods inside of the Interop.LabVIEW.dll in what you are saying above, and if so, how did you become aware of this .dll?
Is anyone aware of any documentation for these ActiveX methods?