Connecting to an Adlink DAQ 2206

[eward]

I am trying to figure out how to talk to a Adlink 2206 DAQ board I have installed on my PCI bus. I think I need to use MAX and 'create new' within the Device and Interfaces section, but I cant seem to find the board. All the documentation I can find only pertains to NI DAQ boards which doesnt help me. I have the .dll and .lib files on the PC, I think it is just a matter of how to get Labwindows to recognize these files. How do I talk to a non-NI DAQ card? The only functionality at the moment I want to instantiate is a counter that the board has the capability of outputing.

Thanks, any help is greatly appreciated.

[MJF]

Getting right down to basics, there should be a driver that came with the board and probably a programming library for controlling it. Have you installed these items?

As far as I know, NI-DAQ is only going to work with NI cards. Third party cards need to provide their own library and probably a soft front panel too.

[eward]

---

@eward wrote:
I am trying to figure out how to talk to a Adlink 2206 DAQ board I have installed on my PCI bus. I think I need to use MAX and 'create new' within the Device and Interfaces section, but I cant seem to find the board. All the documentation I can find only pertains to NI DAQ boards which doesnt help me. I have the .dll and .lib files on the PC, I think it is just a matter of how to get Labwindows to recognize these files. How do I talk to a non-NI DAQ card? The only functionality at the moment I want to instantiate is a counter that the board has the capability of outputing.

Thanks, any help is greatly appreciated.

---

I have installed the driver for the board. I am not sure what you are referring to when you say soft front panel. But the only thing I think is need are the .lib & .dll files, but I am just not sure how to link these to Labwindows.

[MJF]

A soft front panel is a stand-alone application that lets you control the hardware from a PC.

As for linking the files in, that's easy. You have three options really.

#1. Add the .lib file to your project.
#2. Put the .lib file in your library directory.
#3. Create a new library directory and tell CVI that it should look there to find additional library files.

#3 is probably the best option in the long run with #1 being a quick fix.

You don't need to do anything with the dll file as long as Windows knows where to find it.

[Wendy L]

Hello eward,

Along with MJF's thoughts, I would suggest to put the DLL in the same folder as your project. Also, you should include the associated header file in your project. This might make things easier, especially if you plan on distributing your application later on.

Thanks.