LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Physical channel could not be found when using DAQmx Base

Hi,

 

I am using Labview 2009 + DAQmx Base on linux machine. And I followed this example to build a simples DAQ VI:

http://www.ni.com/white-paper/3838/en/   (Figure 2)


But I could not find any options listed in the physical channel constant or control.

I ran lsdaq and I did see my device:

 

@alban: /usr/local/natinst/nidaqmxbase/examples/ai> lsdaq
--------------------------------
Detecting National Instruments DAQ Devices
Found the following DAQ Devices:
NI 6036E:    "Dev1"    (PXI5::0::INSTR)
--------------------------------

 

and nidatalogger could also find my DAQ device. It's simply that DAQmx Base sub VIs could not recognize or find my DAQ card and physical channels. 

 

What can I do now?

 

Thx

0 Kudos
Message 1 of 8
(3,687 Views)

Hi 296

 

Are you using the PXI version of the 6036E? If so: I don't believe it is supported by DAQmx base.

Supported Devices.

 

Kind Regards

 

Chris | Applications Engineer NIUK
0 Kudos
Message 2 of 8
(3,660 Views)

@hicksc wrote:

Hi 296

 

Are you using the PXI version of the 6036E? If so: I don't believe it is supported by DAQmx base.

Supported Devices.

 

Kind Regards

 


 

Hi,

 

I think it is supported on Linux :

 

E Series Multifunction DAQLinux3OS X
NI 6011E (NI PCI-MIO- 16XE-50)* 8.0.2mx3.5B 3.5B
NI PCI-6023E 8.0.2mx3.5B 3.5B
NI PCI-6024E 8.0.2mx3.5B 3.5B
NI 6025E 8.0.2mx3.5B 3.5B
NI 6030E (NI PCI-MIO- 16XE-10)* 8.0.2mx3.5B 3.5B
NI 6031E 8.0.2mx3.5B 3.5B
NI PCI-6032E 8.0.2mx3.5B 3.5B
NI PCI-6033E 8.0.2mx3.5B 3.5B
NI PCI-6034E 8.0.2mx3.5B 3.5B
NI PCI-6035E 8.0.2mx3.5B 3.5B
NI PCI-6036E 8.0.2mx3.5B 3.5B
0 Kudos
Message 3 of 8
(3,650 Views)

Hi

 

I saw that too, however upon scrutiny I noticed that it states PCI-6036, your system seems to have a PXI-6036 installed instead?

Which version of DAQmx base did you install?

 

Kind regards

 

Chris | Applications Engineer NIUK
0 Kudos
Message 4 of 8
(3,648 Views)

@hicksc wrote:

Hi

 

I saw that too, however upon scrutiny I noticed that it states PCI-6036, your system seems to have a PXI-6036 installed instead?

Which version of DAQmx base did you install?

 

Kind regards

 


Hi,

 

It is NI-DAQmx Base 3.6.0.
According to the README.txt file in the installation folder:
--------

README for NI-DAQmx Base 3.6.0
18-Jul-2012
...

...

E Series MIO (PCI/PXI only)
  *Supported in NI-DAQmx Base Task Configuration Utility
  *Analog Input
    -DMA
    -Digital start and reference triggering
    -Analog start and reference triggering
    -External clocking
    -Multi-channel, multi-sample read (scaled)
    -Multi-channel, multi-sample read (raw)
    -Multi-channel, single sample read (scaled)
  *Analog Output
    -External clocking
    -Multi-channel, multi-sample write (scaled)
    -Multi-channel, single-sample write (scaled)
  *Counter Input
    -Simple event counting
    -Buffered event counting (continuous speed is limited by computer speed;
        reading a single large buffer does not cause an error)
    -Period measurement
    -Pulse width measurement
  *Counter Output
    -Single pulse
    -Continuous pulse train
    -Digital start triggering
  *Digital I/O (Port0 only)
    -Port input
    -Port output
--------

 

PXI seems to be supported?

 

Best regards,

0 Kudos
Message 5 of 8
(3,638 Views)

I followed this instruction and partially solved the problem:
http://digital.ni.com/public.nsf/allkb/57393FEDF313E99B86256F0B0010AD2D

I simply entered "Dev1/ai0:3" at 'Physical channels constant' and now I could read signals from channel 0~3.

(In contrast, I was able to select all the available channels on 'Physical channels constant' when I was using DAQmx on Labvew 8.5)
This way works fine as long as I selected no more than 4 channels, for example, "ai1:4" is also okay.
However, when I went further, and entered "Dev1/ai0:4", I got no signals at all.
In fact, I would need ai0:8 for my measurement, as well as an additional ao(analogue output) channel.

so, still could not solve the problem totally, but this might be a hint of the solution.

0 Kudos
Message 6 of 8
(3,635 Views)

Hi

 

Have you tried creating a static task which encompasses the channels you require, using the task configuration utility?

It's explained on page 12 of the manual.

 

 

Kind regards

Chris | Applications Engineer NIUK
0 Kudos
Message 7 of 8
(3,613 Views)

@hicksc wrote:

Hi

 

Have you tried creating a static task which encompasses the channels you require, using the task configuration utility?

It's explained on page 12 of the manual.

 

 

Kind regards


Hi

 

Yes,

I also trued this way, but I could not get any signal..

So the only way now is to enter "entered "Dev1/ai0:3" instead of the task name....

 

Best regards,

0 Kudos
Message 8 of 8
(3,606 Views)