instrument wizard help

[Stv002]

Hi,

I am having trouble opening instrument wizard in Labview version 5.1 on windows XP. When i try to launch the wizard, a bunch of errors come up and I am brought bach to the Labview main menu instantly. I am trying to configure a 3rd party daq system and I am pretty sure I have installed the device and its drivers correctly. MAX is not recognizing the device and I dont know how VISA works...

S. 

[Dennis_Knutson]

I don't know why you decided to start a new thread instead of posting back to your original. Starting from your last comment. MAX will not and should not recognize your device as previously mentioned. It will recognize the serial port you have in your pc that you have connected to the instrument.

I have no recollection of an instrument wizard in 5.1. According to the vendor's web site, they provide some examples. You should start with those. At the very least, attach the LabVIEW drivers yu got if you want some help.

[Stv002]

Sorry.

The drivers that came with the device are I7000.DLL and Uart.DLL...

[Dennis_Knutson]

Sorry, I just assumed that the drivers from the vendor included a LabVIEW VI or two. It might be worthwhile to ask them if they have some actual LabVIEW code you can look at.

With a dll, you need to use the Call Library Function Node. The LabVIEW examples include one or two VIs that show the general usage but you will need to create your own per the .h file that should be provided and call the unique functions from superlogics.

[Stv002]

Well, they provide some demo VIs but when I run them (ie. AnalogIn.vi) they give an "Error Code :17. Module Id Error!"

[Dennis_Knutson]

I would suggest that you start at the beginning instead of jumping into LabVIEW code. First, you need to verify that you have the correct type of serial card. That means an RS-485 card or a RS-232->RS485 adapter. I would hope that the vendor provides an example program so that you can test the serial card, serial cable, and the driver installation. Also, since the error is vendor specific, the best contact for debugging any issues is the vendor. Unless someone here has some direct experience, helping with dll issues is very difficult without the actual hardware.