Can't install PCIe-GPIB in MAX

[Richard Fung]

Dear All,

I just got my new NI PCIe-GPIB card, Labview 8.2.1 and new Dell Dimension E521 PC (os: Vista)  this week. Unfortunately, the MAX (V 4.2) can't recognize the GPIB card after installation. My colleague and I tried to install it several times by following the instruction: install NI-488.2 -> install the GPIB card -> PC power on. However, NI-488.2's "Getting started wizard" failed to recognize the new installed GPIB card. On the other hand, the device manager in Vista show NI PCIe-GPIB is installed and run properly. If I still try to run MAX and expand the device list folder. An error will occur and indicates "MAX can't connect to its database". I also checked the "nidevldu" status (it is Started) and even attempted to recover the database by following web-help resource. Will, no luck. Since it is a new PC, I am quite sure there is no other company software installed, only NI's product existed. If you have heard this problem or even know how to solve it, please kindly share with me. I appreciated your kind help!

Best,

Richard    

Message Edited by Richard Fung on 05-26-2007 06:23 PM

[Krista H]

HI Richard,

It seems to me that your installation of MAX is corrupt. I would suggest uninstalling MAX, making sure the folder in Program Files is removed, and then reinstalling GPIB. This re installation could be a repair and will reinstall MAX. This should re setup the database. Also before you try to install the hardware check and see if MAX is working properly and can see your software or other hardware. Then try the installation of the GPIB board.

[Richard Fung]

Dear Krista,

Thank you for the reply. I highly suspect the reason for MAX database corruption is the conflict between our newly purchased PCIe-GPIB and IMAQ PCI-1405.

I tried what you suggested this morning. Reinstall MAX (even Labview) -> than installed the latest version (V2.5) of 488.2. -> than installed the PCIe-GPIB. MAX can successfully recognize the GPIB card. Later on, we installed "NI  Vision Acquisition Software (with NI-IMAQ 3.7.1) -> Installed PCI-1405 -> open MAX. Than the corruption happened again! MAX now can't find its database and can't recognize either interface cards. I checked the Vista's "Device manager" both inteface cards were "running correctly". If I install PCI-1405 first, MAX can recognize it with no problem. Corruption only occur when I try to install both cards.

Can you help me with this issue? thank you very much!

Richard 

[Krista H]

Hi Richard,

One question about this. You can see your devices in devices and interfaces and a different times in MAX but do they both work in LabVIEW even thought you cannot see them in MAX? For example if you try to use a GPIB example in LabVIEW does it work or do you get an error? If so what error? More information about when your boards are working would be very helpful. Thanks

[Richard Fung]

Hi Krista,

These are what we have tried so far:

1) With old (V2.4) 488.2
   first install Vision Acquision Software (with NI-IMAQ 3.7.1) -> than install 488.2 / GPIB -> MAX can't connect to its database-> In Labview both GPIB & Image acquisition works
  
2) With old (V2.4) 488.2
   first install 488.2 / GPIB -> than install  Vision Acquision Software (with NI-IMAQ 3.7.1); Error message occurs, it says "exist unsupported software" and it "need to be un-installed" (we think it might mean the initally installed 488.2)

3) With new (V2.5) 488.2
 First install GPIB -> MAX recognize PCIe-GPIB -> than install Vision Acqui. (NI-IMAQ 3.7.1) -> MAX can't connect to its database, MAX fail to recognize both devices -> In Labview, only GPIB works, image acquisition fails

I hope these are useful. Honestly speaking, my colleague and I are tired of the install / re-install process, especially with slow Vista....

Thank you very much for your help

Richard

[Krista H]

Hi Richard,
 
I am very sorry about all of the re installations you have had to do. Unfortunately, the issue is probably because of the installation of NI-488.2 (V2.4) which doesn't support Vista. The best thing to do is uninstall NI-488.2 completely, to do this follow this KnowledgeBase.  Once you have done this please reinstall NI-488.2 (V2.5). Just to let you know we are also trying to replicate this issue here. So please let us know the outcome. Thanks you