01-14-2008 02:02 AM
01-15-2008 09:33 AM
Hello fishbone,
What version of DAQmx are you using? (Version can be found via the Software tab in
Measurement & Automation Explorer (MAX)) Does your USB-6501 respond correctly through
the Test Panel in MAX? Do any of the
shipping examples give the same error?
(C:\Documents and
Settings\All Users\Documents\National Instruments\NI-DAQ\Examples\DAQmx ANSI C)
These steps are important because they will identify if the driver is installed correctly and your USB-6501 is working properly.
Are you closing out the session correctly? If you create a task, then you need to make sure that is closed properly. (DAQmxClearTask) The shipping examples should be a great resource for the order in which to call these functions.
Can you take a screenshot of the error and post it to the forum?
01-15-2008 09:56 AM
01-16-2008 01:57 PM
Hello fishbone,
The DAQmx examples are not going to work on Microsoft Visual C++ 2005 Express Edition. DAQmx will work with Microsoft Visual C++ 200. The .NET examples should work with the Express Edition. The reason that the C++ DAQmx examples will not work with the Express Edition is based on the compiler that is used. I hope that this information helps. Let me know if you have any other questions.
01-16-2008 11:26 PM
01-16-2008 11:26 PM
01-18-2008 11:00 AM
Hello fishbone,
All of the DAQmx examples are written in MFC. Microsoft Visual Studio C++ 2005 Express Edition does not support MFC applications. (VS2005 FAQ # 44) The only officially supported version of Visual Studio for DAQmx is 2003 as well as 2005. We have not fully tested our DAQmx examples in Microsoft Visual Studio C++ 2008 completely. However, all the examples should work. I was unable to find out if Visual Studio C++ 2008 Express Edition supports MFC applications. If it does, then DAQmx should work with that version of Visual Studio.
01-19-2008 08:51 AM
01-21-2008 10:02 AM
Hello fishbone,
The DAQmx examples will not work with Visual C++ 2005 Express Edition. However, if you are just making function calls to the dll, then it should work. We have not tested our driver with that version of Visual Studio.