LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

How to call Labview-VIs in a AgilentVee-function?

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.

 

 

 

0 Kudos
Message 11 of 19
(668 Views)

I can generate a LV DLL with a corresponding *.h file and import that into VEE. I was trying to utilize the ActivexAutomation interface.

0 Kudos
Message 12 of 19
(668 Views)
This is the wrong place to be asking for updated VEE examples. There are however examples on how to use c to call a VI.
0 Kudos
Message 13 of 19
(662 Views)

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.

 

 

0 Kudos
Message 14 of 19
(658 Views)

The protocol is the same for VIs in LLB as for "regular" VI files…

 

See the LabVIEW help

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 15 of 19
(654 Views)

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.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
0 Kudos
Message 16 of 19
(636 Views)
My point about the llb is that it is easily corruptible and using a standalone VI just requires you to remove that part of the path. Since you have not provided any details on how the VEE code is trying to use VI Server and it is unlikely that anyone here is using VEE, I'm not sure how much help can be provided. Did you look at the examples in other programming languages.

You do have my deepest sympathy if you being forced to use VEE.
0 Kudos
Message 17 of 19
(628 Views)

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.

0 Kudos
Message 18 of 19
(604 Views)

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

 

0 Kudos
Message 19 of 19
(598 Views)