Labview 8 professional in linux fedora 4 gives error to simple VI.

[saltamontes]

The attachment shows the simple VI that gives error when running
labview 8 in a system with Linux fedora core 4:
"Error -2147220712 occurred at DAQmx Start Task.vi:1
This error code is undefined. No one has provided a description
for this code, or you might have wired a number that is not an error
code to the error code input."
To the command: "/usr/local/sbin/nipxiconfig  --list-identifications all",
system respond with:
"Chassis 1 (PXI-1045)
  Slot 1:  PXI-MXI-4
  Slot 2:  PXI-6608 (PXI2::15::INSTR)
  Slot 3:  PXI-6031E (PXI2::14::INSTR)
  Slot 4:  PXI-6733 (PXI2::13::INSTR)
  Slot 5:  PXI-GPIB (PXI2::11::INSTR)"
Do you know what is wrong?

[Tom_W_[DE]]

Hi saltamontes-

It looks like you are calling the DAQmx Start Task VI 10 times for the same task in a for loop.  This will not work- is there a reason you are attempting to start the task multiple times?  Also, where is the task "a" created?  I would suggest that you try to run a DAQmx example program for LabVIEW to make sure your hardware is working correctly and also to view a good suggestion of programming for NI-DAQmx with LabVIEW.

Hopefully this helps-

[saltamontes]

Dear Tom W:
Thanks for your answer. Indeed I sent a bad example.
The problem is that any VI gives error.
I have installed in the same machine labview 7.1 for windows with the same hardware. For windows there is not trouble.
As you suggest I first test the VI in windows and after in Linux. For instance, the VI attached in this note runs without any problem in windows,
but in Linux gives for the first icon:

"Error -2147220712 occurred at DAQmx Create Channel (AI-Voltage-Basic).vi:1
This error code is undefined. No one has provided a description for this code, or you might have wired a number that is not an error code to the error code input.",

and for the second:
"Error -200429 occurred at DAQmx Read (Analog DBL 1Chan 1Samp).vi:1
Possible reason(s):
Value passed to the Task/Channels In control is an empty string (or I/O control).
The value must refer to a valid task or valid channels."

I think that the second message error is a consecuence of the first error.
This first error happens with any VI in Linux, no matter if works or not in windows with exception of serial ports communication that
is working OK in Linux.
Seems that there is a problem of configuration for communication  with the PXI bus.
As you can see I have assumed that the name of the physical channel for analog input is "PXI1Slot3/ai0" as in windows,
is it the same in Linux? Why clicking on the physical channel  I get a empty display of physical channels?
According to instructions I have configured PXI with " nipxiconfig" and the sistems responds accordingly.
Is there another configuration not made?
I did not  find any documentation for "nilsdev"  and  "nidaqmxconfig --export my.ini" gives: "Error -2147220712",
"nilsdev" responds with nothing,  then I assumed that "nipxiconfig" is the only needed for PXI.
Where is the mistake?
Thanks: Saltamontes



 

[Tom_W_[DE]]

Hi saltamotes-

Yes, the nipxiconfig is necessary to identify your chassis and/or controller, but you will also need to identify, name, and configure your installed DAQ devices using nidaqmxconfig.  This tutorial and the NI-DAQmx Configuration Guide explain in detail how to configure your devices properly.  For general information about the differences between NI-DAQmx for Windows and Linux check out this tutorial.

Hopefully this helps-

[saltamontes]

Dear Tom W:
Thanks for the information.
According to the NI-DAQmx Configuration Guide
"nilsdev" must informe about the installed devices, but for this command I get an empty answer.
To command "nidaqmxconfig –-export my.ini" system responds with "Error -2147220712",
and to "/usr/local/sbin/nipxiconfig  --list-identifications all" system responds with:
"Chassis 1 (PXI-1045)
  Slot 1:  PXI-MXI-4
  Slot 2:  PXI-6608 (PXI2::15::INSTR)
  Slot 3:  PXI-6031E (PXI2::14::INSTR)
  Slot 4:  PXI-6733 (PXI2::13::INSTR)
  Slot 5:  PXI-GPIB (PXI2::11::INSTR)".
Then the system is able to communicate with the modules in the PXI chassis. Why "nilsdev" responds nothing?
How to write  a configuration file with  "nidaqmxconfig" when there is not response  given by "nilsdev" ?
Could be useful to know that to the command "/sbin/lspci" system responds with:

00:00.0 Host bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo KT266/A/333]
00:01.0 PCI bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo KT266/A/333 AGP]
00:09.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 78)
00:0a.0 PCI bridge: National Instruments: Unknown device 7079 (rev 04)
00:0a.1 Bridge: National Instruments: Unknown device 7044 (rev 01)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8233A ISA Bridge
00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 40)
01:00.0 VGA compatible controller: S3 Inc. Savage 4 (rev 04)
02:0b.0 Communication controller: National Instruments: Unknown device c821 (rev 02)
02:0c.0 PCI bridge: Intel Corporation 21154 PCI-to-PCI Bridge
02:0d.0 Class ff00: National Instruments: Unknown device 2420
02:0e.0 Class ff00: National Instruments: Unknown device 1580
02:0f.0 Class ff00: National Instruments: Unknown device 2cc0 (rev 01)
03:08.0 Class ff00: National Instruments: Unknown device 7064
03:0c.0 PCI bridge: Intel Corporation 21154 PCI-to-PCI Bridge
04:08.0 Class ff00: National Instruments: Unknown device 7064

which confirms that the devices  are detected.
I would like to have some advice.
Thanks: Saltamontes.
  

[Tom_W_[DE]]

Hi Saltamontes-

You may notice that your distribution of Linux is not on the list of officially supported distros, so I'd like to rule this out as a possible cause.  Do you have the ability to test with one of the three supported/tested distributions, namely 

Mandrakelinux 10.1 Official and Mandriva Linux 2006

SUSE LINUX Professional 9.2 and 9.3

Red Hat Enterprise Linux WS 3

Aside from this, the nilsdev utility will actually rely on configuration imported using nidaqmxconfig to list devices.  So, we need to successfully import a configuration file before nilsdev should list any devices installed.  Please try creating an .ini file using the link I posted in my previous post and see if you are able to successfully import the settings using nidaqmxconfig.

[cmihele]

I am getting the same errors for Mandriva 2006: nilsdev -- verbose does not return anything and running a simple analogin vi returns error 2142220712.  is it posible the daq card may be defective and not properly configured?

[SamVal]

Did you ever figure out the problem with Error 2142220712? I am having the same problem, see the following post:

http://forums.ni.com/ni/board/message?board.id=beta11&message.id=12

Thanks,

Sam Valeriano

[cmihele]

in my case it was a conflict between NI stuff and the custom firewall software.