Bizarre problem with DAQmx on Fedora Core 6

[SamVal]

I have been using a PCI-DIO-32HS (aka PCI-6533) with DAQmx 8.0 on Fedora with no problem for the last month (after initial installation hassles). Yesterday I used the network configuration tool packaged with Fedora ( system-config-network 1.3.95) to change from a DHCP assigned IP address to a static IP address. After running this tool, my application no longer found the PCI-6533 (This was immediate -- I did not have to reboot)

Investigating, I ran nilsdev and nilsdev returned nothing:

[root@localhost ~]# nilsdev

[root@localhost ~]#

Further, I ran nidaqmxconfig and got:

[root@localhost ~]# nidaqmxconfig --export what.txt

Error -2147220712

[root@localhost ~]#

I had previously exported a config when the system was working and tried then to import it using nidaqmxconfig, and got the same error.

Running lspci shows the National board is recognized without a problem on the PCI bus.

Tried rebooting -- same result.

Reinstalled the drivers using updateNIDrivers -- same result.

Reverted network configuration back to DHCP -- same result.

I have two identical Linux systems. Thinking there might be a problem with the card itself, I installed it on the second system and it worked with no problems. I backed up all of the National Instruments driver modules, and then repeated the network configuration on the second system, with the same result -- now the second system no longer works either.

Restoring the backed-up driver modules did not fix the problem.

This is an extremely bizarre problem and I am at a loss to explain it!

Is it a bug with system-config-network 1.3.95? What could it possibly have to do with DAQmx? Could system-config-network 1.3.95 have changed the NIC settings causing a hardware conflict? ( I tried disabling the on-board LAN in the BIOS -- didn't help)

Does DAQmx require a certain network configuration?

What is Error -2147220712? (Can't National provide some better error handling?)

Why does nilsdev return nothing? When you import a configuration using nidaqmxconfig, where is that configuration stored? Is it possible I can bypass nidaqmxconfig and copy some file from a working system? ( I have other working systems but I have to travel to get to them)

There are a few other threads that discuss Error -2147220712 (see below) but they all end abruptly with no posted solution. ( It would be a courtesy to others to post solutions to problems if they are discovered!)

http://forums.ni.com/ni/board/message?board.id=170&message.id=166133&query.id=6185#M166133

Can anybody help me?

Thanks,

Sam Valeriano

[Scott314]

Take a look at your /etc/hosts file.  I had a similar problem installing on a Debian based distro and an strace of some of the sample code led me to suspect the problem was due to not being able to resolve the localhost.  It's been some time since I fixed my problem, but I remeber the solution required a one line change to /etc/hosts.

[Matt_A]

Hello Sam,

Scott sounds like he's seen this before, so I would definitely follow his advice. Unfortunately, Fedora is a distribution that is not supported by National Instruments, but we do have an active user community. There is a great How-To discussion forum on NI-DAQmx in Fedora 5 that you may find helpful in addition to Scott's comments. The forum can be found here.

[Elijah_K]

Try the following:

/etc/init.d/nidevldu stop
/etc/init.d/nipxirmu stop
/etc/init.d/mxssvr stop
rm -f /usr/local/natinst/max/Data/*
rm -f /var/lib/natinst/nipal/nipalps.bin
reboot

[Sai K]

hi..

i am facing the same problem from today, all of a sudden.

 i dont know wht caused this error. i m using windows XP as my operating system.

can anybody suggest how to rectify the problem

[Elijah_K]

Sai K,

I'm interested to know the exact steps that you went through before experiencing this problem.  Did you also change your IP from DCHP to static?  Had it been working properly before?  Does MAX detect the device?  Does the device appear in your device manager?

With the answers to these questions and any other insights you can provide I can walk you through a number of troubleshooting steps.

[SamVal]

Hi Scott,

I've had to revisit this problem when one of our guys in the field used the network configuration tool and the system stopped working again ( I had forgot about the problem entirely.) 

Thanks for your tip -- the network configuration tool had removed the line

127.0.0.1  localhost.localdomain localhost

from the etc/hosts  file.

After putting this line back in and rebooting, the system was fine again.

Thanks again!

Sam Valeriano