Reinstalled Varian SpectraAA Base s/ware " OsiGPIB DLL error"Drive not loading.

[Mearii]

I Re installed a Varian SpectraAA Base software which has NI 488.2 driver. But I the new hard ware widzard cannot find the driver. I cannot open the software, it keeps saying "OsiGIPB DLL error"

What i Have tried so far.

Uninstall and reinstall software and NI link.

Updated the driver on line.

The device instance id shows PCI\VEN_1393&DEV_CB03, which turned out to be a C218 turbo/PCI series which we donot have. Ours is a direct connection to one instrument.

Could this be over riding the PciGPIB card and driver? If so how can I go about to correcting it? I could be wrong please I need some expert help.

Using Windows XP prof SP3

Mearii

[Matt-J]

Hi Mearii,

First, what changed in your setup that required the reinstall? At what point were things working before?

The first thing I would try is to reboot the system after updating the NI 488.2 driver. At that point, you might try uninstalling the improperly identified device and then have hardware wizard scan for new hardware.

If none of these things are successful, you may need to check with Varian about what versions of NI 488.2 and Windows are supported by this software.

Regards,

Matt Justiss

[Mearii]

Thankyou Matt for responding to my post.

The device was working properly until the error Osi GPIB DLL (No driver detected) appeared. We were adviced to uninstall and reinstall the software and it should work okay but it has not. I tried what you suggested with an updated driver I downloaded but the  problem is still there.

I am trying to get information on the drivers as you suggested.

I did comfirmed that the Vendor (VEN) and Developer (DEV) should have show PCI\VEN_1093&DEV_C801, my PCI device keeps showing the wrong vendor and developer ie (PCI\VEN_1393&DEV_CBO3).

What can I do to correct such a conflict? could this mean the PCI card has been corrupted? I would appreciate some help regarding the VEN,DEV problem. What could be the possible cause?

Regards

Mearii

[Matt-J]

Hi Mearii,

As far as the PCI card showing up as the wrong device, there are two possible causes I can currently think of. First, the connection between the card and computer has been changed. This could happen if, say, some dust accumulated in the slot and the connection is not being properly made. You might try powering down your computer, unplugging it, removing the card and cleaning both the connector and PCI slot out with air before reinstalling it. While this may be the problem, it is most likely a driver issue. What is the make and model of your PCI card? If it is a non-NI device, we will probably need to check with the manufacturer about what driver versions are compatible with it. (This may be redundant if the board is made by the company who created your software, which it seems you have already contacted)

Best regards,

Matt Justiss

[Mearii]

Dear Matt

Actually I have a National instrument PCI GPIB card.

I think the actual problem is with the driver as you have pointed out. I have downloaded and tried several drivers from the NI website. The PC is detecting the pci card meaning pci slots and card is fine. our OS is win xp  pro SP3. Is it possible to recommend the actual driver or show me where to get it from the net.Attached is a picture of the card.

[Matt-J]

Hi Mearii,

If you can post the model number of the card, I will look it up and make a recommendation. Is the card now being recognized correctly? If so, are you still unable to access it within your software? Since this is a non-NI software, we may need some information from the creator as to what is going on with their use of the NI 488.2 driver.

Best Regards,

Matt Justiss

[Mearii]

Dear Matt,

I cannot tell exactly what these numbers refer to but here they are, you might be able to figure them out.The details on the PCI card are; PCI-GPIB, ASSY183617L -01L, National Instrument copy right 2007, 139FBF9.

The card is connected to a Varian AA 240 Atomic Absorption spectrometer using a IEEE 488.2 cable. the instrument runs using the varian spectraAA software. Ni 488.2 (Gpib driver 2p4, WindowsNT  Common Script)  is included in the Base CD which is the software installation CD . The Hardware trouble shoot recognised the PCI device per VEN_1393&DEV_CB03 . Vendor name Moxa technologies Co Ltd.

I hope that the information provided will enable you to find a solution for me. Thankyou for your time and valueable assistance.

Kind Regards

[JasonSmith]

I don't think this is a driver issue at all, it is almost certainly hardware. The reason I say this is that the same three bits are set in the incorrect IDs, which should be zeroes. There are really only two reasons this Would be likely to happen: the board could be damaged, or there is something wrong with the connections in the slot or motherboard.

I would recommend installing the board in another PC, you don't even need the driver. You will be able to view the hardware IDs in the properties of the unknown device in Device Manager.

If they are correct on the other machine, try cleaning out your PCI slot, or try installing it in a different slot. If they are still wrong on the other PC, your board is damaged and will need repair.

[Dan_N]

Hi Mearii,

I agree that you should try changing and cleaning out the PCI slot that your card is installed in, as that could be the root of this error. I also wanted to point you towards this resource that I found on Varian's website, which explains a possible source of the OsiGPIB dll error that you are getting, as well as a potential solution: http://dealernet.varianinc.com/oznet/Atomic_spectroscopy/AA_sales/Software/index.htm. Try following the steps in this link listed under "Roboprep Software Installation Problems," and see if that clears up this issue. 

Best,

Dan Nelson

Applications Engineer

[JasonSmith]

There is no reason to suspect that there is any software problem at all, until Windows can properly detect the PCI card. Once the PCI-GPIB properly shows up in Device Manager, then it makes sense to turn back to the software.

There is nothing that a driver can do to make windows see the wrong Vendor and Product IDs from the hardware. This is a hardware problem at its core, we just don't know if the problem is with the PCI-GPIB, or with the computer.