"Device Identifier is invalid" Error -200220 on Linux

[ZeroShadow]

I searched the forums, but didn't see anything about this for Linux (Red Hat 4).  The issue is that when I try to create a virtual channel in the "DAQmxBase Create Channel" vi , I get the error message "Device Identifier is invalid", which is strange since the device name (Dev2/ai0) is provided by browsing the "physical channels" text box. 

Additionally, running the command "nidaqmxconfig --export daqmx.ini" and looking in the .ini file shows that the device is recognized by LabVIEW (shown below).
[zieve@he3 ~]$ nidaqmxconfig --export daqmx.ini
Operation successful.
[zieve@he3 ~]$ more daqmx.ini
[DAQmx]
MajorVersion = 8
MinorVersion = 0

[DAQmxDevice Dev2]
ProductType = PCI-6220
DevSerialNum = 0x12900B7
BusType = PCI
PCI.BusNum = 0x6
PCI.DevNum = 0x8
 
Any help would be appreciated.

[David L.]

Hi ZeroShado,

Can you please clarify what driver and version you are using? Your post says you are having a problem with a DAQmx Base VI, but later states that you have regular DAQmx 8.0. Do you have both installed, but are using DAQmx base to program? DAQmx 8.0 is only supported on Red Hat Enterprise Linux WS 3.

I may suggest looking through some of the Linux forums as well, here, here, and here.

[ZeroShadow]

Both DAQmx Base (2.1) and DAQmx (8.0) are installed, and I'm using LabVIEW 8.2.  You are correct, I'm using DAQmx Base to program, but I assumed that since the "nidaqmxconfig" could see the device, then DAQmx base would see it as well.  If there is a way to interface with the card purely through DAQmx Base, that would be fine. 

After I read your post, I ran the "mxbaseconfig" command.  In the configuration window, the textbox labeled "Device" is grayed out, indicating that the utility cannot see the card, which is strange since the "DAQmxBase Create Channel" vi seems to be able to.  I'm sure the card itself is correctly installed and working, as the test panel for it works flawlessly. 

[David L.]

ZeroShadow,

M series cards will not show up in the configuration utility, but can work with DAQmx base. Can you please try running DAQmx base shipping examples? The key with DAQmx base is to create a task (DAQmx base create task.vi) and then create the channel (DAQmx  base create virtual channel.vi)

[Tom_W_[DE]]

HI ZeroShadow-

In order to get the correct device numbers for use with NI-DAQmx Base you must use the lsdaq utility.  However, you're using a device that is supported by NI-DAQmx.  Is there a reason that you want to use NI-DAQmx Base?  If not, I would encourage you to use NI-DAQmx- it is a more full-featured and higher performance driver.  By the way, the Device Controls in LabVIEW only refer to NI-DAQmx device numbers; they do not work with NI-DAQmx Base.

[ZeroShadow]

I would be happy to use NI-DAQmx, but it's not supported on Red Hat 4 and my version of LabVIEW doesn't seem to contain the NI-DAQmx vi's. I tried the "lsdaq" command you recommanded and it returns the following:
[zieve@he3 ai]$ lsdaq
--------------------------------
Detecting National Instruments DAQ Devices
Found the following DAQ Devices:
--------------------------------

Whereas running "nilsdev" returns
[zieve@he3 ai]$ nilsdev
NI PCI-6220: "Dev1"

Why is it that "nilsdev" can see the card but "lsdaq" cannot?

[Tom_W_[DE]]

Hi ZeroShadow-

nilsdev is an NI-DAQmx utility to list available hardware.  lsdaq is a similar utility for use with NI-DAQmx Base.  The utilities are completely seperate (as are the drivers), so only one driver/utility will be able to operate your hardware at one time.  Since you're using a distribution that is not supported by NI-DAQmx, I would encourage you to uninstall NI-DAQmx.  Otherwise, you should be able to get your device to show up in lsdaq (and work with NI-DAQmx Base) by using the information in this KB.

Hopefully this helps-

Message Edited by Tom W [DE] on 07-24-2007 01:06 PM

[ZeroShadow]

Thanks for the help, everything seems to be working now.