Intel MacBook Pro / USB-6009 (Revisiting)

[rsriprac]

Hello,

A while ago I had trouble getting the USB-6009 to work with a Intel MacBook Pro, I eventually resorted to using Windows machine in order to use the device.  I recently revisited the issue and this is still a ongoing issue of Intel MacBook Pro / USB-6009.

I've recently upgraded the USB-6009 to the latest firmware that comes with the latest Windows NI-DAQmx Base.  USB-6009 continues to work fine with the latest firmware on the Windows end, however on Mac OS X with NI-DAQmx Base 3.3 installed the device does not show up with the 'lsdaq' application.

USB-6009 continually blinks once plugged in.   None of the examples work:

> ./acquire1Scan
> DAQmxBase Error -200220: <err>Device identifier is invalid.

Here are some relevant info of the system:

> kextstat | grep -i ni
>   101    1 0x1944000  0xcf000    0xce000    com.ni.driver.nipalk (2.4.1) <36 14 12 11 10 9 7 5 4 3 1>
>   131    0 0x1a13000  0x13000    0x12000    com.ni.driver.NiViPciK (4.5.1) <101 36 14 12 11 10 9 7 5 4 3 1>
>   133    0 0xaa81a000 0x2c000    0x2b000    com.ni.driver.niusb9162k (3.3.0) <36 14 12 11 10 7 5 4 3 1>

USB Proper outputs:

> Full Speed device @ 4 (0x06400000): .............................................   Composite device: "NI USB-6009"
>     Port Information:   0x001a
>            Not Captive
>            Attached to Root Hub
>            External Device
>            Connected
>            Enabled
>     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:   0x0103
>         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
>         Number of Interfaces:   1
>         Configuration Value:   1
>         Attributes:   0x80 (bus-powered)
>         MaxPower:   500 ma
>         Interface #0 - Unknown   
>         Raw Descriptor (hex)    0000: FF FF FF FF FF FF FF FF  FF FF 1D 00 01 00 00 00  
>         Raw Descriptor (hex)    0010: 09 02 2E 00 1A 00 00 00  00 00 40 06 04 00 00 01  
>         Raw Descriptor (hex)    0020: 05 00 00 00 10 9C 11 D4  00 00 00 00 00 00 00 00  
>         Raw Descriptor (hex)    0030: 00 30 41 00 01 00 00 00  F3 59 D4 E5 73 FD BC 31  
>         Raw Descriptor (hex)    0040: 5C 81 87 D0 9E F3 11 D4  00 15 1D 00 01 00 00 00  
>         Raw Descriptor (hex)    0050: 23 3C 00 00 00 00 00 00  B0 12 50 12 01 00 00 00  
>         Raw Descriptor (hex)    0060: 08 00 00 00 00 00 00 00  60 A5 59 70 FF 7F 00 00  
>         Raw Descriptor (hex)    0070: 80 F5 BF 5F FF 7F 00 00  9B 35 00 00 01 00 00 00  
>         Raw Descriptor (hex)    0080: F3 00 00 00 01 00 00 00  11 00 00 00 FF 7F 00 00  
>         Raw Descriptor (hex)    0090: D4 00 00 00 00 00 00 00  8B 00 00 00 01 00 00 00  
>         Raw Descriptor (hex)    00a0: 45 00 00 00 FF 7F 00 00  00 00 00 00 01 00 00 00  
>         Raw Descriptor (hex)    00b0: 0A 00 00 00 01 00 00 00  27 00 00 00 FF 7F 00 00  
>         Raw Descriptor (hex)    00c0: 05 00 00 00 FF 7F 00 00  28 00 00 00 FF 7F 00 00  
>         Raw Descriptor (hex)    00d0: 61 00 00 00 01 00 00 00  A0 93 51 12 01 00 00 00  
>         Raw Descriptor (hex)    00e0: C0 F4 BF 5F FF 7F 00 00  A0 F4 BF 5F FF 7F 00 00  
>         Raw Descriptor (hex)    00f0: A8 F4 BF 5F FF 7F 00 00  B4 F4 BF 5F FF 7F 00
>     Other Speed Configuration Descriptor   
>     Configuration Descriptor   Device did not respond to request for first 4 bytes of descriptor
>     Configuration Descriptor   Device did not respond to request for first 9 bytes of descriptor...
>     Configuration Descriptor   Device did not respond to request for first 4 bytes of descriptor
>     Configuration Descriptor   Device did not respond to request for first 9 bytes of descriptor

[Pcorcs]

Hello,

The first step in this troubleshooting process is to ensure that the DAQmx Base Firmware update has occurred correctly. The video capture linked below will outline the process of properly associating the device firmware:

Firmware Update from DAQmx to DAQmx Base for USB-6008/6009

http://www.screencast.com/users/Patrick_Corcoran/folders/Jing/media/4ea38620-9cda-4fe9-93f0-519ee2c3...

Subsequently, we should be able to view the device in the lsdaq utility. Please note that the USB-6009 will need to use dynamic tasks to interact with DAQmx Base. The dynamic examples are located in the LabVIEW Example Finder (Browse according to: directory) daqmxbase >> dynamic >> Analog Input (etc.)

After reviewing this firmware update process, please post back, if the device continues to remain invisible in the lsdaq utility.

Cheers!

[rsriprac]

Hello PCorcs

I've followed the instruction exactly given in the screencast and I am still not able to get the USB-6009 to be reconized on the Mac.  I've updated the firmware and it shows that the firmware is current on the FWUpdate.exe.  The device shows up fine in the lsdaq.exe on the Windows side while it remains invisible on the Mac.

Regards,

-Ram

[Pcorcs]

Hi Ram,

Are other USB devices working on the computer? Where was the USB Proper outputs sourced from (Windows//Mac)?

If you execute the lsdaq utility from the terminal window, are any error codes returned in searching for devices? Does changing USB ports have any affect? 

Are any other National Instruments products connected to the Mac system? 

You had mentioned revisited, does this mean you were working with another Mac?

I appreciate your responses. I am trying to gain a clearer picture of what may be happening on this system. I have been working directly with a 6009 on a Mac OS 10.5, and have not seen the same behavior with the lsdaq utility. What versions are running on your system? (I assume OS X is 10.5, but want to be sure.) Also, what version of the NI-VISA driver is installed on the machine?

The DAQmx Base driver is built using the low level VISA protocols, and must have a compatible VISA counterpart to interact with devices correctly. Again, thank you for your time. I look forward to your responses.

Thanks,