ā03-20-2014 03:40 PM
LLB is a collection (one or more vis) of Vis, hence Labview Library (LLB) as you know. There is no Agilent VEE example demonstrating how to call a NI vi that is not part of a LLB.
ā03-20-2014 03:42 PM
I can generate a LV DLL with a corresponding *.h file and import that into VEE. I was trying to utilize the ActivexAutomation interface.
ā03-20-2014 03:50 PM
ā03-20-2014 03:58 PM
Maybe if I restate the question from a NI perspective. What is the required protocol to implement the various ActiveXAutomation classes and methods fro Vis that are contained within a LLB.
ā03-20-2014 04:02 PM - edited ā03-20-2014 04:04 PM
ā03-21-2014 10:40 AM
Why don't you just rewrite the VEE code in LabVIEW. I've never worked with VEE, but it looks like you could do 99% of the jobs with a simple state machine. Then you don't have to worry about using multiple programs and get them to talk.
Another alternative would be to go with TestStand if you are just doing sequencing.
ā03-21-2014 11:24 AM
ā03-24-2014 07:36 AM
Vee is a requirement and Teststand is limited to sequencing. The example given by Agilent seems to follow a visual basic protocol provieded by NI.
ā03-24-2014 08:05 AM
Dennis,
All languages have thier Pros and Cons. Unfortunantly I was not able to select the language(s) for this effort. I did look at other examples in other programming languages and the Visaul Basic example is the one that closest resembles the VEE example. I am not constrained to the LLB interface. I am now trying to get the DLL interface to work. I will also be trying the .NET Interop Assemblies.
Don