Digital I/O

cancel
Showing results for 
Search instead for 
Did you mean: 

nidaqmx.lib

Highlighted

Hello,

I am trying to create a c++ console application in Visual Studio Express 2013 which will control a PCI6503 card.  All I want to do is output digital values.  I took the WriteDigChan example and pasted it in the program stub that VS creates (it includes stdafx so I can use printf without having to worry about creating windows, etc.)  I get the following errors during linking:

 

Error 1 error LNK2019: unresolved external symbol _DAQmxCreateTask@8 referenced in function _wmain 

Error 2 error LNK2019: unresolved external symbol _DAQmxStartTask@4 referenced in function _wmain 

Error 3 error LNK2019: unresolved external symbol _DAQmxStopTask@4 referenced in function _wmain 

Error 4 error LNK2019: unresolved external symbol _DAQmxClearTask@4 referenced in function _wmain

Error 5 error LNK2019: unresolved external symbol _DAQmxCreateDOChan@16 referenced in function _wmain 

Error 6 error LNK2019: unresolved external symbol _DAQmxWriteDigitalLines@36 referenced in function _wmain 

Error 7 error LNK2019: unresolved external symbol _DAQmxGetExtendedErrorInfo@8 referenced in function _wmain

Error 8 error LNK1120: 7 unresolved externals 

 

I did add the include and lib directories to the path and get no complaint that the linker could not find the lib-so I assume that is not the problem.

 

Can anyone help?

0 Kudos
Message 1 of 3
(3,209 Views)
Highlighted

Hi Euticus,

 

Take a look at the following KnowledgeBase Articles:

Why Do I Receive Linking Error LNK2019 when Compiling Visual Studio C++ Projects that Use LabWindows™/CVI™ Functions?

http://digital.ni.com/public.nsf/allkb/36F561F57095CADB86257CC4006C275B?OpenDocument

When Compiling a DAQmx ANSI C Example in Visual C++ I Receive Link Errors

http://digital.ni.com/public.nsf/allkb/38F67B28D995C6958625706E000C580C?OpenDocument

Thomas N.
Applications Engineer
National Instruments
0 Kudos
Message 2 of 3
(3,185 Views)
Highlighted

Thanks.  I dropped back to an older version of the driver and everything worked beautifully.

0 Kudos
Message 3 of 3
(3,179 Views)