LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

Agilent VSA 89600 CVI driver generation failed

Hi everyone,

 

I'm developing a tool transfering and fetch some raw data to/from Agilent's VSA89601 software. And my developing tool is CVI9.0. I've downloaded the 89601 trial version and have it installed.

 

When I try to generate its ActiveX controller codes, the error message "Invalid value or out of range" pops up no matter what kind of Access Function selected. And all function name truncation problems are fixed.

 

 

And I used ActiveX controller tool to generate some ActiveX codes successfully, and no error message pops up.

 

Any one can give me some guidance?

 

I developed a similar Labview tool, which can call VSA89601 activeX codes well.

 

 

0 Kudos
Message 1 of 2
(3,488 Views)

Hi everyone,

 

Actually, this problem is something like how to fix the ActiveX Controller "invalid value" related problem. And I reconfirmed that my Labview project did call this ActiveX controller successfully. So I believe it's not the problem about this activeX control's installation.

 

 

I also want to try in this way, and needs some ideas how to. I can search the exe file path by searching the registry items. And call it by "LaunchExecutableEx". Then how to exchange values with this external executable, by DDE related functions? If so, how?

 

Another idea I have is to wrap a C-style dll with VC6/2005 for this Agilent VSA89601 COM. 

 

I also have a question like below:

Aglient provides a paragraph C codes like below:

 

#import "..\..\..\Vector\VsaVector.exe"
using namespace AgtVsaVector;

 

// Initialize COM
    CoInitialize (NULL);
// Get an existing 89600 VSA instance.
hr = oApp.GetActiveObject(__uuidof(Application));

 

-

-

-

 

CoUninitialize();

 

As we know, the CVI pops the error message when detecting #import and using . Does CVI can convert this kind of codes into itself style?!

 

Then who can give me some suggestions?

0 Kudos
Message 2 of 2
(3,466 Views)