USB-6008 Linux Ubuntu doesn't show up with lsdaq

[studentTUD]

My USB-6008 Linux Ubuntu doesn't show up with lsdaq.

After having some trouble, I got DAQmx base 2.1 to work on Ubuntu Linux 7.10 Feisty Fawn, Kernel 2.6.20.16-generic.
I replaced the nikal rpm with version 1.6 - and replaced the dash-shell with bash. I think thats pretty much it. It installed without errors.
The kernel modules compile and load fine, I think. Are those all the required modules?

lsmod | grep ni
nipxirmk
nidimk            nipxirmk
niorbk            nipxirmk,nidimk
nipalk             NiViPciK,nipxirmk,nidimk,niorbk
nikal               nipalk
usbcore         nikal,ohci_hcd

lsusb shows the device correctly:
Bus 001 Device 002: ID 3923:716e National Instruments Corp.

but lsdaq shows nothing:
lsdaq
-------------------------
Detecting National Instruments DAQ Devices
Found the following DAQ Devices:
-------------------------

ls -l /proc/bus/usb/001/002
-rw-rw-rw- 1 root usb 36 2007-10-18 16:09 /proc/bus/usb/001/002

ls -l /dev/bus/usb/001/002
crw-rw-rw- 1 root root 189 2007-10-18 16:14 /dev/bus/usb/001/002

the rules in /etc/udev/rules.d seem fine, too....

Anybody knows what's wrong? Can I use the device even if it doesn't show up on lsdaq?

Regards,

Johannes

PS. If anyone is interested in a tutorial on how to get to the point I'm at - tell me. But best would be to solve the rest of the Problem first...

Message Edited by studentTUD on 10-18-2007 09:27 AM

[Matthew_W]

 Hi Johannes,

 I think (hope) the problem is the following:

 lsdaq is not showing your USB-6008 because it is loaded with DAQmx firmware. The USB-6008  must be loaded with DAQmx Base  firmware  instead.

 Please change the firmware following the instructions in the second link and post back here if still experiencing issues.

Best regards,

 MatthewW
 Applications Engineer
 National Instructions


 

 

[Tom_W_[DE]]

Hi Johannes-

PID 0x716E corresponds to a USB-600x device that is in firmware loader mode.  In order to get your device to show up in lsdaq you will need to load the correct firmware to the device, using the steps here.  Once the firmware is correctly loaded, the device will enumerate as PID 0x717A (for USB-6008).

Hopefully this helps-

[studentTUD]

Thanks for your help. The device now shows up:
NI USB-6008: "Dev1"    (USB0::0x3923::0x717A::00E17027::RAW)

Only - mxbaseconfig doesn't show it yet...
Is "RAW" correct?

Regards,

Johannes

[Tom_W_[DE]]

Hi Johannes-

The "RAW" portion of the VISA resource string refers to the USB protocol in use (USB RAW) and is indeed correct.  In order to use your device with mxbaseconfig you may need to create a new task rather than use one of the existing ones.  You should see the option to configure channels on the USB-6008 when creating a new task.

[studentTUD]

Thank you. What you say makes very much sense and I should have realized that in the first place.
Anyone interested in my solution on how to get the USB-6008/9 to work with Ubuntu 6.04 Feisty? Please contact me here (post a reply) or at 16303@gmx.net

Johannes

[Tom_W_[DE]]

Hi Johannes-

Though we don't "officially" support any Ubuntu release, I have heard other users interested (and I too am curious) in how to get DAQmx Base working.  If you have a writeup or wouldn't mind recounting the steps, I would appreciate if you could post that info here.

Thanks in advance-

[studentTUD]

It was quite a bit of trial and error but it worked out the following way for
me. I had to change some of the scripts and replaced an RPM-file (upgraded to nikal 1.6).
If you look at the attached file structure and put the included files
in your DAQmx Base installation directory (copy all the files from the Image to a dir
first) - it should work. I mainly disabled some checks and added an rpm
parameter. What I did is ugly and I worked around most of the carefully crafted
compatibility checks - so be warned.
Now while this worked for me on a fresh VirtualBox Ubuntu System - there is no guarantee
it will work for you. I take no responsibility at all. My strong suggestion
ist to try it out on a VirtualBox first!

Good luck and have fun,

Johannes

For me it worked on a Feisty system. May work on Gutsy too, though.

First do all available Ubuntu-updates.

We need some useful and/or obligatory tools:

   sudo apt-get install rpm alien kernel-package build-essential xmlto

With

   uname -r

show the current kernel-version and remember it 🙂

   sudo apt-get install linux-headers-generic linux-source

install kernel-sources and headers. After that they need to be extracted:

   sudo tar -xjvf /usr/src/linux-source*.tar.bz2
   sudo ln -s linux-source-<Kernel-Vers.> linux

Configure the kernel:

   cd /usr/src/linux
   sudo cp /boot/config-<Kernel-Vers.> /usr/src/linux/.config
   sudo make oldconfig
   sudo make modules_prepare

   sudo
cp /boot/config-<Kernelversion> /usr/src/linux-headers-<Versionsnummer>/.config
   sudo make oldconfig
   sudo make modules_prepare

The Ubuntu standard interpreter must be changed from dash to bash:

   sudo ln -s -f /bin/bash /bin/sh

   cd to your base directory with the install-files. Then

   sudo nivisa/INSTALL --no-prompt --accept-license --force
   sudo rpm -ihv *.rpm --nodeps --force

RESTART SYSTEM

Execute:

lsusb
lsdaq

If you are working on a VirtualBox and no USB-Devices are showing up - follow the
steps in their help file to change the host system device-permissions in way that
VirtualBox can route USB to the virtual sytem.

[mwalter]

I had similar problems with our USB-6008 on a Debian box.  Now, after updating to NIDAQmxBase v. 2.0 and NIKAL v. 1.6, everything seems to be running well, but only as root.  When I try to address the device in a VI as a normal user I get :

Error -200220 occurred at an unidentified location
Possible reason(s):
Device identifier is invalid.

This has got to be a permissions problem, but I can't even figure out what device name it is using.

dmesg gives me:
Nov  2 14:01:36 localhost kernel: usb 7-1: new full speed USB device using uhci_hcd and address 9
Nov  2 14:01:36 localhost kernel: usb 7-1: configuration #1 chosen from 1 choice

Any suggestions would be greatly appreciated.

thanks,
Mark

[studentTUD]

Hi,

please post the result of the following commands - that makes it easier to help you.

lsmod | grep ni

lsusb

lsdaq

ls -l /proc/bus/usb/001/002

ls -l /dev/bus/usb/001/002

(replace the "001/002" with the appropriate device)


Message Edited by studentTUD on 11-03-2007 04:48 AM