Multifunction DAQ

cancel
Showing results for 
Search instead for 
Did you mean: 

USB-6009

The example C code programs that came with nidaqmxbase-2.0.0 don't seem to work on a Red Hat Enterprise box with a USB-6009.
If I run  acquire1scan I get  DAQmxBase Error: <err>Device identifier is invalid.
when I connect the device to the USB port /var/log/messages shows:
 usb 2-1: new full speed USB device using address 13
so evidently it is recognized.

0 Kudos
Message 1 of 7
(4,978 Views)
jjreed,

You will need to run lsdaq to find all DAQmx Base devices present in the system. From the output of lsdaq, you should be able to determine your 6009's identifier, which you must then add into the example in the channel array. If your device does not appear in lsdaq, or if you have additional questions, please let us know!

Hope this helps,
Ryan Verret
Product Marketing Engineer
Signal Generators
National Instruments
0 Kudos
Message 2 of 7
(4,956 Views)
I have the same USB 6009 device and am attempting to use the DAQmxBase C API (using cygwin) to interface with it. Everything compiles and links and I'm able to run but I keep getting the Device identifier invalid error. I've attempted to use lsdaq.exe to view the device identifier but lsdaq is not recognising the device. I get the same error when I try to use the Data Logger. I am able to use the Measurement and Automation Explorer to see the device and set up and run data logging task but I can't seem to get this to work programatically. Any help would be appreciated.
 
Thanks
0 Kudos
Message 3 of 7
(4,883 Views)

Hi cpoole-

If you are using the device through NI-DAQmx via MAX then you need to make the firmware change described here to gain access in NI-DAQmx Base.  Is there a reason why you want to use cygwin with NI-DAQmx Base?  Why not just use NI-DAQmx for Windows?  We have not tested the cygwin emulator, and I am somewhat skeptical that it will work correctly.  Are you planning to attempt to use NI-DAQmx Base for Linux under cygwin, or are you planning to use NI-DAQmx Base for Windows and just access the incoming data in some way through cygwin?

Regardless, you will need to have NI-DAQmx and NI-DAQmx Base for Windows installed to make the firmware change described in that KB.  I would be interested to hear more about your application and software setup.

Thanks-

Tom W
National Instruments
0 Kudos
Message 4 of 7
(4,874 Views)

Tom W,

I was able to switch the firmware and got the examples working using the cygwin gcc compiler.

My application is a very simple sensor demo (differential voltage measurments) that may need to run on Linux at some point. I'm constrained in that I don't have access to Visual Studio compilers (other than C#). I'm also using Java as my base language and its easier to do a JNI interface using C than with C# (fewer wrapper layers). I just started looking at this today so you'll have to pardon my limited knowledge at this point concerning all of the various options. I did try the DAQmx API but ran into some compile issues with int64 and uint64 typedefs in the header file - something I can fix but didn't have a lot of time to mess with.

If you have any suggestions please let me know.

 

Thanks for your help

0 Kudos
Message 5 of 7
(4,866 Views)

Cpoole,

 

I found your post am an interested how you were able to acheive the GCC compilation of the NI Base example with CYGWIN on windows.  I realize that this posting is 2.5 years old, but if you are still out there I could use a pointer.

 

 

Thanks.

0 Kudos
Message 6 of 7
(4,310 Views)

http://forums.ni.com/ni/board/message?board.id=250&thread.id=10936&view=by_date_ascending&page=1

 

The above link shows step by step instructions on how to do this.  Note, on vista, UAC must be off to avoid Labview errors.

Message 7 of 7
(4,275 Views)