Last
summer our lab computer was able to run LabVIEW 8.6 with DAQmx. Our setup of
testing equipment included a SCC-2345 signal conditioner and a PCIe 6251 DAQmx
device. Unfortunately after almost a year of reformats, upgrading the OS and
updating of the kernel, we lost our past configuration of our DAQ system. In
attempting to reconnect everything this week as though back at square one, we
couldn’t. Our current setup is OpenSUSE 11.0 with kernel version
2.6.25.20-0.7-default. We tried to use our old LabVIEW 8.6 and our even LabVIEW
2009 SP1, but both were unsuccessful. With all of the hardware connected,
including a strain gauge module in the signal conditioner, we receive the
following reports from the terminal:
linux-t0am:/home/john
# nilsdev
NI
PCIe-6251: "Dev1" [Not Present]
SC-2345:
"SCC1"
Modules:
J1: NI SCC-FT01: "SCC1Mod2" [AI]
J6: NI SCC-SG01: "SCC1Mod3" [AI]
J17: NI SCC-FT01: "SCC1Mod1" [AO]
linux-t0am:/home/john
# lspci
00:00.0
RAM memory: nVidia Corporation Device 0754 (rev a2)
00:01.0
ISA bridge: nVidia Corporation Device 075c (rev a2)
00:01.1
SMBus: nVidia Corporation Device 0752 (rev a1)
00:01.2
RAM memory: nVidia Corporation Device 0751 (rev a1)
00:01.3
Co-processor: nVidia Corporation Device 0753 (rev a2)
00:01.4
RAM memory: nVidia Corporation Device 0568 (rev a1)
00:02.0
USB Controller: nVidia Corporation Device 077b (rev a1)
00:02.1
USB Controller: nVidia Corporation Device 077c (rev a1)
00:04.0
USB Controller: nVidia Corporation Device 077d (rev a1)
00:04.1
USB Controller: nVidia Corporation Device 077e (rev a1)
00:06.0
IDE interface: nVidia Corporation Device 0759 (rev a1)
00:07.0
Audio device: nVidia Corporation Device 0774 (rev a1)
00:08.0
PCI bridge: nVidia Corporation Device 075a (rev a1)
00:09.0
IDE interface: nVidia Corporation Device 0ad0 (rev a2)
00:0a.0
Ethernet controller: nVidia Corporation Device 0760 (rev a2)
00:0b.0
PCI bridge: nVidia Corporation Device 0569 (rev a1)
00:10.0
PCI bridge: nVidia Corporation Device 0778 (rev a1)
00:12.0
PCI bridge: nVidia Corporation Device 075b (rev a1)
00:18.0
Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron, Athlon64,
Sempron] HyperTransport Configuration
00:18.1
Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron, Athlon64,
Sempron] Address Map
00:18.2
Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron, Athlon64,
Sempron] DRAM Controller
00:18.3
Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron, Athlon64, Sempron]
Miscellaneous Control
00:18.4
Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron, Athlon64,
Sempron] Link Control
02:00.0
VGA compatible controller: nVidia Corporation GeForce 8200 (rev a2)
03:00.0
PCI bridge: Texas Instruments XIO2000(A)/XIO2200(A) PCI Express-to-PCI Bridge
(rev 03)
04:00.0 Class ff00: National Instruments
Device 717d
Our
computer is configured to see our DAQmx device and signal conditioner along
with several modules, but it cannot identify the card, only call it an unknown device
in the hardware info. When we try to run nidaqmxconfig --export, only the
signal conditioner and modules are seen. When we also try to use lsdaq, the
computer returns nothing after a long delay. When attempting to run a VI using
a strain gauge DAQmx system, we are able to see the modules SCC1Mod3_0 and _1
on LabVIEW, but return the following result:
Error -89130 occurred at DAQmx Start Task.vi:1
Possible reason(s):
Device not available for
routing. It is possible that the device needs to be reset or that the
device is being reset.
If you are resetting the device, wait for the reset to complete.
For example, if you have
used the device through Traditional NI-DAQ, you must reset the device before
the requested route can be made. For SCXI devices, you must reset the
communicator DAQ device. Call the Traditional NI-DAQ Device Reset VI or the
Init_DA_Brds function. To reset all devices in Traditional NI-DAQ, right-click
the Traditional NI-DAQ Devices folder in MAX and select Reset Driver for Traditional
NI-DAQ.
Task Name: _unnamedTask<1>
From
our numerous attempts (past and present) in getting the system to work, we have
accumulated both DAQmx 8.0.1f0 and DAQmx Base. LabVIEW 8.6 can see both DAQmx
and DAQmx base while the 2009 version can only see DAQmx Base. In both
occurrences of DAQmx Base, only voltage and temperature programming blocks can
be selected. We have tried to search forums for example VI’s to measuring
strain for continuous samples but have had no luck, adding as well to our
problem that both versions of LabVIEW on our computer do not show examples for
strain (even when manually finding them using the terminal).
It
is to point out, that not all of the LabVIEW software (ie. NI-SCOPE) has been
successfully installed on our computer for either version, only LabVIEW and
DAQmx/DAQmx BAse. This is because of a kernel version error stating that our
current version must be updated to the same version number we already have.
We
don’t want to suggest a hardware issue because the card has not been tampered
with since our working configuration, so for now we can only assume it’s
software-related. Hopefully someone can clear the air with this long list of
faults. If you require any additional information, I would be happy to post it.
Also, since we don’t have a proper list of examples on our versions of LabVIEW,
if someone could post the example for strain (continuous samples) found on LabVIEW
that would be greatly appreciated as well.
Thanks,
Bryan
