mattdl68

This is some of what the manuals says.

Use the SetupDiGetDeviceInterfaceDetail function to get the symbolic link name for

the interface, which the operating system uses to encode its enumeration information

describing the device. The string contains the VID and PID of the device found

by the operating system. Test each string to find the one (or more if you have

multiple Lab Bricks attached) that contains the VID and PID values in it. For the

Microsoft Windows environment, the portion of the device strings containing the

VID and PID are in the format:

sDevSubstring1 = “vid_041f&pid_1201”; // VID and PID for LSG-402

sDevSubstring2 = “vid_041f&pid_1202”; // VID and PID for LSG-152

sDevSubstring3 = “vid_041f&pid_1203”; // VID and PID for LSG-251

Once you have identified a Lab Brick, open it by using the DevicePath from the

Interface Device Detail Data structure, using the normal CreateFile function. Once

you have opened the device1 you can read the Lab Brick’s serial number using the

HidD_GetSerialNumberString function.

I have the commands to communicate with the device.

I'm having difficulty on configuring the dll parameters when using the call library function. I made a simple VI that just adds one to the input.I put this vi in a labview prodject and created a dll.

I called the dll I made using the call library funtion and it automatically confiured the parameters.That worked great.

What I tried next was to find the header file for the setupapi.dll and create a wrapper around the setupapi dll. it had errors creating the wrapper.

Do you know of any documatation that has a step by step instruction of using windows dll in in labview.

Thanks