05-05-2009 04:39 PM
I have a PCI NI DMM 4060 and PCI Express 6259 in the same computer running under Windows XP/Service pack 3 with next drivers: NI DAQ traditional=7.4.3f7, NI DAQmx=8.3.0f3, NIDAMM=2.6 and MAX=4.1. In one of three times resetting the computer, the Device Manager can not see the DAQmx board. I suppose this happens because some resource conflicts (Windows IDs conflict).
Is any solution for this? Can anyone help me?
Solved! Go to Solution.
05-06-2009 05:13 PM
Just to clarify, when you said that the PCIe-6259 is not seen by the Windows Device Manager, did you mean that it does not appear at all (It should be under the heading Data Acquisition Devices), or did you mean that it says NI PCIe-6259 but there is a yellow exclamatin mark over the card? A screenshot of the device manager and any error messages might be helpful in troubleshooting this issue.
Also, is this a newly developed problem? Have the cards worked before, and you have only recently developed this issue, or are you trying to set up a new system and have noticed this behavior?
I do not know how many PCIe slots that you have in your computer, but one troubleshooting step might be shutting down the computer, and either switch PCIe slots or at the least, if only one slot is available, ensuring that the card has no bent pins and is firmly seated in the slot.
Also, you will want to make sure that the NI Device Loader is working properly to detect and recognize your devices. I recommend walking through the steps listed in Knowledge Base 4BHID6DE: NI Device Loader (nidevldu) and NI Configuration Manager Services Not Starting.
I noticed that you are not using the latest versions of the DAQmx and NI-DMM drivers. Another possibile step is upgrading to the latest versions of these drivers as found on ni.com.
05-07-2009 08:52 AM
Thank you for answering me to my new encountered problem.
The DAQ PCI express 6259 does not appear at all under Data Acquisition Devices in Device Manager.
I would like to introduce you little in the history of this problem: it is about updating a customer with a new computer in which I had to transfer the DAQ 6259 and NI DMM 4060 cards from old computer. The application that uses the two NI cards is programmed under Labview 7.1.1 and started few years ago and worked with next NI drivers: DAQmx 8.0, NIDMM 2.5, Visa 3.5 under MAX 4. I remember even in the old computer I had to run few fixes that were posted in that time in NI site related to nipalu.dll in order to have good NI DMM 4060 measurements (it is about palBase.exe that changes registry addresses). What I found in this new computer which is using the same OS (Windows Xp) but SP3 were the old was using SP2, each time when I try to take a DMM measurement the application hanged on with no possibility to exit and also this time no help with palBase.exe registry changed.
So I had a chance to upgrade the drivers to next level, but I did not know if it will work (I want to mention that everything was updated over remote control on customer computer). Updating drivers made DMM to measure correctly, no crash, and also DAQmx acquired the right way, but one from three computer start up Device Manager does not see the DAQmx card and of MAX shows a red cross over the last saved identification under DAQmx Devices. Next start up it will identify cards correctly.
I want to mention that in my rush when I updated the NI drivers, instead of uninstalling the old ones I installed the new over the old. If I uninstall the existing drivers and installing again it will help fixing my problem?
I have to ask you if Labview 7.1.1 will work with last NI DAQ and DMM drivers, because if I am doing the upgrade I will do it also remotely and it might be risky. In the mean time our application replaced the NI DMM 4060 with another card but for that customer I had still to use it, so I do not have it in house to experiment new drivers.
05-08-2009 09:25 PM
As can be seen in this Knowledge Base, LabVIEW 7.1 is supported by the latest DAQmx drivers, so upgrading won't cause any problems. However, whether or not it will solve the issue, I do not know. Let me do some more research into why the card might not be appearing on some restarts but works fine on others.
Have a great weekend!