Multifunction DAQ

cancel
Showing results for 
Search instead for 
Did you mean: 

No DAQ Device listed in Labview 2010 Linux

Solved!
Go to solution

Hi,

 

I have a problem with DAQmx Base 3.4.0 under Linux:

 

mxbaseconfig shows my device NI-6009 at the USB port. I can also create tasks corresponding to the Ni-6009 in there. When I try to create a task in Labview 2010, the I/O constants are always empty. The pulldown-arrow is greyed out. If I enter the device name directly in the constant, it throughs me an error 😞 Semms like Labview don't know, which DAQmx Base instruments are connected...

 

With VISA devices I have not this problem. All VISA devices are shown in the pulldown-menu of the constant and are working correctly.

 

lsdaq gives me:

 

--------------------------------
Detecting National Instruments DAQ Devices
Found the following DAQ Devices:
NI 6220:     "Dev1"    (PXI1::4::INSTR)
NI USB-6009: "Dev2"    (USB0::0x3923::0x717B::0119B3BD::RAW)
--------------------------------

 

I'm using

 

Redhat Enterprise Linux 5.5

NI-488.2-beta-2.51b1

NI-VISA-5.0.0

NI-DAQmx Base 3.4.0

Labview 2010

 

All installers worked fine...

 

Any idea how I get access to my NI-6009?

0 Kudos
Message 1 of 5
(3,470 Views)

Hi Felix1234,

 

 

maybe there is something wrong with your DAQ-driver-version/-installation. I propose to download the following driver and start with a new installation. Please consider to install all the drivers after the software insallation (Software -> then modules+toolkits -> then drivers).

 

NI-DAQmx Base 3.4 - SUSE, RedHat:

http://joule.ni.com/nidu/cds/view/p/id/2128/lang/en

 

The following main features were added in NI-DAQmx Base 3.4

  • LabVIEW 2010 Support—in addition to LabVIEW 2009, LabVIEW 8.6 and LabVIEW 8.5.
  • OS Support—NI-DAQmx Base now supports the following Linux distributions:
    • openSUSE 11.1 and 11.2
    • Red Hat Enterprise Linux WS 4 and 5
    • Scientific Linux 5.4 and 5.5

 

I hope this helps you!

 

Best regards

Suse

______________________________
Certified LabVIEW Developer (CLD)
0 Kudos
Message 2 of 5
(3,438 Views)

Labview was installed before the driver packages.

 

I looked hat he examples, that come with DAQmx Base. There the device-port-ID is connected by an string variable to the DAQmx Base Vi...works also perfectly for me. But I still don't know, why the I/O variable is noit working...

0 Kudos
Message 3 of 5
(3,435 Views)
Solution
Accepted by topic author Felix1234

 


@Felix1234 wrote:
There the device-port-ID is connected by an string variable to the DAQmx Base Vi...works also perfectly for me. But I still don't know, why the I/O variable is noit working...

DAQmx Base does not populate the LabVIEW controls like DAQmx does [1]. Since the driver doesn't use any background services, it cannot tell LabVIEW which devices and channels are available on the system.

[1] NI-DAQmx Base Tasks and Physical Channels Are Not Listed in the LabVIEW Task and Channel Constants and Controls
http://digital.ni.com/public.nsf/allkb/57393FEDF313E99B86256F0B0010AD2D

 

Joe Friedchicken
NI Configuration Based Software
Get with your fellow OS users
[ Linux ] [ macOS ]
Principal Software Engineer :: Configuration Based Software
Senior Software Engineer :: Multifunction Instruments Applications Group (until May 2018)
Software Engineer :: Measurements RLP Group (until Mar 2014)
Applications Engineer :: High Speed Product Group (until Sep 2008)
Message 4 of 5
(3,429 Views)

@NI:

why not just plugging the driver into the IIO infrastructure (as everbody else does) and let LV just ask the kernel for available devices ?

 

Ah, wait, you're still stuck in the dark ages of the holy inquisition ... 😮

http://forums.ni.com/t5/Multifunction-DAQ/Linux-NIDAQmx-install-problem/m-p/3225670/highlight/false#...

Linux Embedded / Kernel Hacker / BSP / Driver development / Systems engineering
0 Kudos
Message 5 of 5
(2,710 Views)