USB 6009 not responding in Lab VIEW

[massen]

Some more information concerning this problem:

When I tried this first, the green led was "always on". I realized that perhaps the USB hub I had connected the 6009 to didn't deliver enough power and connected it then directly to the computer : Now the green led is continuously flashing. Flashing light thus seems to be the good condition - though I have not been able to find any reference to this LED in the manual or elsewhere - perhaps that would be something worth adding (NI?).

The problem persists partially though. Neither in the labview program "Acq One Sample.vi" nor in mxbaseconfig nor isdaq can I seem to access the device. However, as a spur of the moment attempt, I tried to just run "Acq One Sample.vi" and manually key in the physical
channel (i.e. dev1/ai0... dev1/ai7) - and it seems to work - i.e. if I type dev1/ai8 I get
an error. I haven't tried with an actual external device connected - but will do a.s.a.p.

What remains is : I cannot seem to browse my way to the device nor do any setting up. Anyone with any bright ideas ?

Thanks,
Niels

[Otis]

Niels,

First off, you should always plug the USB-DAQ devices directly into your computer instead of thru a hub.

I am glad to hear that you are able to get the device working by using the device name and channel id. That basically means that your device is working as it should. But then you get into the issue of knowing how to configure it.

I tested a USB-6009 on a Mac with OS 10.4 and think I may have seen what you are running into. When I opened the DAQmx Base Configuration Utility I saw the tasks in the left column. I tried selecting those tasks and choosing my device. You cannot directly select a device thru this view.

The best thing to do is just go ahead and create a new task. By doing that you can then select the device that you want the task to work with and then everything worked out just fine. Other than having to create a new task the whole procedure worked pretty smoothly and mostly as expected.

[Jeremy_C]

NI-DAQmx 7.5 (link below) now supports the USB-6008 and USB-6009 devices on Windows.  I strongly recommend installing this much more powerful and robust driver.  For more information on how to switch your device to use NI-DAQmx, refer to the KB linked below.

NI-DAQmx 7.5
http://digital.ni.com/softlib.nsf/websearch/CF7ECCEA4C4CC7DE86257038004D88AE?opendocument&node=132060_US 

KB: 3NE7GJMY

https://knowledge.ni.com/KnowledgeArticleDetails?id=kA03q000000YIRDCA4&l=en-US

[rsriprac]

Hello,

I have a 6009 on a MacBookPro (Intel) running 10.4.8 and  I also have a latest NI-DAQmx Base installed (NI-DAQmx_Base_2.1.0).  I can not seem to get the 6009 to show up in the 'lsdaq' program.  The device is blinking.  Here is the output from the 'USB Prober':

Full Speed device @ 3 (0x7D200000): .............................................   Composite device: "NI USB-6009"
    Device Descriptor  
        Descriptor Version Number:   0x0200
        Device Class:   0   (Composite)
        Device Subclass:   0
        Device Protocol:   0
        Device MaxPacketSize:   64
        Device VendorID/ProductID:   0x3923/0x717B   (National Instruments)
        Device Version Number:   0x0100
        Number of Configurations:   1
        Manufacturer String:   1 "National Instruments"
        Product String:   2 "NI USB-6009"
        Serial Number String:   3 "0123268F"
    Configuration Descriptor  
        Length (and contents):   46
            Raw Descriptor (hex)    0000: 09 02 2E 00 01 01 00 80  FA 09 04 00 00 04 00 00 
            Raw Descriptor (hex)    0010: 00 00 07 05 81 02 40 00  05 07 05 01 02 40 00 05 
            Raw Descriptor (hex)    0020: 07 05 82 02 40 00 05 07  05 02 02 40 00 05
        Number of Interfaces:   1
        Configuration Value:   1
        Attributes:   0x80 (bus-powered)
        MaxPower:   500 ma
        Interface #0 - Unknown  
            Alternate Setting   0
            Number of Endpoints   4
            Interface Class:   0   (Unknown)
            Interface Subclass;   0
            Interface Protocol:   0
            Endpoint 0x81 - Bulk Input  
            Endpoint 0x01 - Bulk Output  
            Endpoint 0x82 - Bulk Input  
            Endpoint 0x02 - Bulk Output  




Regards,

-Ram

Message Edited by rsriprac on 11-13-2006 09:24 PM

[MickeyD]

Hi Ram,

I believe we have corresponded by email, but I wanted to go ahead and make sure I got the information to you here as well.  Is it possible that your USB 6009 is setup to run on the DAQmx drivers.  If so the second link in Jeremy's post above is a great guide to changing the drivers for the 6008/9.  It is also possible that you have the drivers setup correctly, but are trying to select a device for a pre exisitng task in the configuration utility.  I would advice you to just create a new task, and then you should be able to add a device with no trouble. Please let me know if you need further help with this issue.

Have a great day,

Michael

[rsriprac]

Hello Mike,

Initially out of the box, I hooked it to the mac and could not get it to work, so I eventually hooked it onto a PC.  I have verified that the firmware on the USB unit is "DAQmx Base".  The unit still does not work in the mac environment.

The serial number on the back of the unit is:

123268F

(seems like the difference is that there no leading 0).

I tried opening the "lsdaq" application from the command line by going to:

National\ Instruments/NI-DAQmx\ Base/lsdaq.app/Contents/MacOS/

and executing:

./lsdaq

It starts the application like when I double-click on the .app execpt I get more information on it.  I noticed that it spits out the following error:

2006-11-14 19:08:21.109 lsdaq[399] CFLog (21): Error loading /Library/Frameworks/LabVIEW 8.2 Runtime.framework/resource/nitaglv.framework/nitaglv:  error code 4, error number 0 (no suitable image found.  Did find:
        /Library/Frameworks/LabVIEW 8.2 Runtime.framework/resource/nitaglv.framework/nitaglv: mach-o, but wrong architecture)
CFBundle 0x177d9860 </Library/Frameworks/libUSB-92xx.framework> (framework, loaded)

It seems like the framework it is linking to is not loading because it is compiled for PPC. 

>I would advice you to just create a new task, and then you should be able to add a device with no trouble.

There is no device that shows up under the drop-down menu when I try to add a new task, the drop-down triangle/button is grayed out.

Do you happen to know if there are people successfully using the USB-6009 on the MacBook Pro (First generation)?  Also please advise if there are working solutions for DAQ on the MacBook Pro?

Thank you.

Regards,

Ram Sripracha
Department of Human Genetics
UCLA School of Medicine
Gonda 5309, 695 Charles E. Young Dr. South
Los Angeles, CA 90095-7088

Message Edited by rsriprac on 11-15-2006 08:38 AM

Message Edited by rsriprac on 11-15-2006 08:41 AM

[rsriprac]

Message Edited by rsriprac on 11-19-2006 02:50 AM

[jterry94]

I am having a similar problem. My 6009 is working with the nidatalogger but I cannot get it to work with the c code.

I get the following error message:

Macintosh HD:Library:Frameworks:nidaqmxbaselv.framework
2007-01-29 21:37:29.978 acquire1Scan[4433] CFLog (21): Error loading /Library/Frameworks/LabVIEW 8.2 Runtime.framework/resource/nitaglv.framework/nitaglv: error code 4, error number 0 (no suitable image found. Did find:
/Library/Frameworks/LabVIEW 8.2 Runtime.framework/resource/nitaglv.framework/nitaglv: mach-o, but wrong architecture)
DAQmxBase Error: Device identifier is invalid.

It appears that nitaglv is not intel ready at the moment.

Is there a work around for this?

Thanks,

Jeff

[Jennifer O]

Hi Jeff,

The NI USB-6009 is currently supported on the Intel Macintosh platform with the NI-DAQmx Base driver version 2.1.  I have a MacBook Pro that I use with the USB-6009. 

The important part of the error that you are seeing is "DAQmxBase Error: Device identifier is invalid".  This is generally caused by the device name called by the code not matching any physical device name.  Please verify your device name in the lsdaq utility.  Confirm that this matches the device identifier you are using in the C code. If this does not help, please post information on what you are running when you see the error.  Is it an example program?

Hope this helps,

Jennifer O.
Applications Engineer
National Instruments

[denis.schluppeck]

Dear Jennifer,

I just found your post/reply on the forum.
I am using NI USB-6009 with a MacBook Pro (Macintel).

I have seen similar _warning_ not error message about nitalgv.framework having the wrong architecture.

Error loading /Library/Frameworks/LabVIEW 8.2 Runtime.framework/resource/nitaglv.framework/nitaglv: error code 4, error number 0 (no suitable image found. Did find:
/Library/Frameworks/LabVIEW 8.2 Runtime.framework/resource/nitaglv.framework/nitaglv: mach-o, but wrong architecture)

After this comes up for the first time (I use the c-code compiled into a MEX function for matlab), the warning goes away, until the dynamic library is invoked for the first time again after a matlab restart.

Could you help me in understanding two things:

[1] is there a i386 version of this framework - and I just missed how to link to this properly? Or is it not necessary, because the PPC version is run as emulated.

[2] it appears that when I use the code in readDigPort.c that NI supplies as example, on OSX/MacIntel, reading out e.g. the 8-bit state of the digital-in port using uInt8 which is defined in the include file, the default number (when no dig input is supplied) returned is 15 rather than 0, as I might expected -- this looks like an endian issue to me (PPC/i386) -- or am I getting this wrong?

Any info would be much appreciated.
Best Wishes,
Denis