AnsweredAssumed Answered

Controlling Win-I2CUSBDLL with Agilent VEE Pro 9.2

Question asked by Phantom04cgs on Sep 9, 2010
Latest reply on Sep 16, 2010 by Phantom04cgs

Like • Show 0 Likes0
Comment • 3

Hello everybody,

I'm currently trying to speak to/control a Win-I2CUSBDLL board with Agilent VEE Pro 9.2.
However, the only way that I believe this can be achieved is by programming the board through DLL.
I am wondering if anyone may be able to help me with how to load DLL libraries as well as program in the program this way.

Any help is appreciated and thank you very much for your time,

Phantom

No one else has this question

Outcomes

3 Replies

changmeikuan Sep 13, 2010 7:58 PM
Mark Correct
Correct Answer
Hi Phantom,

What language is the DLL written in? Open VEE help file, Contents > Tell Me About
   > User-Defined Functions > Compiled Functions (If it is a C DLL)
   > .NET Framework (If it is a .NET DLL)
   > ActiveX > ActiveX Controls (if it is an activeX DLL)

Hope this helps
Like • Show 0 Likes0
Actions
shawnfessenden Sep 16, 2010 6:06 AM
Mark Correct
Correct Answer
First off, note that the manual doesn't say anything about 64-bit compatibility.

The dll has a C interface, so you'll be loading a compiled function library. As far as data types go, short int is just short, uchar is BYTE (unless the parameter is splatted, in which case it's char *). For those functions that return uchar, I'm not entirely sure but it looks like this is a simple error enum, so you're probably best off to leave it at BYTE. If any of these functions return pointers (I didn't see any), that complicates matters a bit.

They explicitly state that they use the stdcall calling convention, but they don't say if they're suppressing name-mangling so you might have to cast around a bit for the exported function name. For instance, I2CRead may be simple I2CRead, or it may be _I2CRead@8.
-SHAWN-
Like • Show 0 Likes0
Actions
Phantom04cgs Sep 16, 2010 5:24 PM
Mark Correct
Correct Answer
Thank you Chang and Shawn for your replies!
I have already figured out what the problem was.
As you mentioned, it was indeed a definition file issue.

Thanks again for all your help! They are highly appreciated!

Phantom
Like • Show 0 Likes0
Actions

Controlling Win-I2CUSBDLL with Agilent VEE Pro 9.2

Outcomes

Related Content

Recommended Content