keithley 2700 driver problems

[eMHa]

Greetings,

I've got a Keithley 2700 connected via a GPIB-usb cable.

I've downloaded the drivers and installed (unzipped) them in "C:\Program Files\National Instruments\LabVIEW 2009\instr.lib\Keithley 27xx".

Now my problem is, that the icons look all like question marks in Labview.

Does anyone know why, and how to solve this?

[eMHa]

Never mind I found it 🙂

The library pointed out to files which should've been in folders.

By creating those folders, the proplem seems fixed

[eMHa]

I seem to have a different problem now.

I use a keithley 488 GPIB-USB converter to connect the 2700 to my computer.

However, I can't seem to connect with it.

I figured the problem is in the 488 converter. All drivers are installed, and it is shown in MAX.

However, I can give the converter a write command, but I can't get a read command from it. (and it gives a timeout after a while)

Also, when I try and run a Keithley example, I can't select the converter, I guess its because it's a usb port.

Anyone know why I can't get any data from it? And is there a way to get the USB show up?

[Albert.Geven]

did you put the keithley in GPIB mode or is it still serial

[eMHa]

It's on GPIB mode, but nothing changed yet 😞

[eMHa]

Sorry for double posting (couldn't find the edit button)!

It's the same problem as described in here:

http://forums.ni.com/t5/Instrument-Control-GPIB-Serial/Keithley-USB-GPIB-does-not-work-with-LabView/...

[Rikud]

First thing to determine is this "keithley 488 GPIB-USB" a model KUSB-488, KUSB-488A, or KUSB-488B?

Once you have determined the model, ensure you have installed the correct (and latest) driver.

To determine this go to th www.keithley.com/support site and enter your model number and select "Software Driver".

Download the latest driver for your product.

If you have the NI-488.2 driver installed, uninstall it first (listed in control panel add/remove programs under "National Instruments Software") as this is not the correct GPIB driver, then install the correct driver. If offered a choice of drivers choose the NI Command Compatible driver.

Seems you are also confused about the device...so let's clear up a few things and then troubleshoot the problem:

1. This device is a GPIB device, it will not appear as a USB device.

2. This device will not appear in MAX, it is not an NI device.

3. This device, when properly installed (with correct VISA passport enabled) will appear in VISA Interactive Control

Also, it is not clear if you are attempting to communicate with your instrument in LabVIEW using VISA Read/Write commands or GPIB Read/Write commands...either way, you need to break the problem down and test communications one step at a time:

To test GPIB communication:

Ensure the correct driver is installed (see above) and reboot.

After reboot, connect your USB-to-GPIB interface to your pc. The driver should recognize the USB device and install the correct driver locally from your PC.

If the device is recognized, then turn on your 2700 instrument and connect it to the USB-to-GPIB Interface.

Depending on which model driver you have installed, look under Start programs -> Keithley Instruments ->

You should find some driver programs to allow you to see the device and talk to it.

Ensure you can talk using the diagnostic tool....this validates GPIB communication.

To test VISA communication:

Open NI-Max and ensure the correct VISA passport is enabled.

Under Tools -> NI-VISA -> Visa Options select the "Passports" entry and on the VISA Options tab you will see a list of VISA passports. Ensure that the NI-VISA passport for GPIB is marked ON. Exit and save.

Run the Start Programs -> National Instruments -> VISA -> NI-VISA Interactive Control. You should see at least wo entries if all is working:

GPIB0::INTFC <-- this is your GPIB interface

GPIB0::16::INSTR <-- this is your GPIB instrument if configured for GPIB at address 16, with GPIB enabled

If you want to talk to the instrument...just double click on the GPIB0::16::INSTR.

Click on the Write tab and press execute...Return Status should be x0.

Click on the Read tab and press execute...Reture Status should be x0 and Buffer should display instrument info.

If all is successful, proceed to LabVIEW and retest.

Good luck!

[niikos]

Hello. I have tested everything that you have proposed in the last post with my KUSB-488B and Keithley 2400.

But When I open a VI from the drivers of the Keithley installed in Labview 2011 I get for example:

"Error -1073807298 occurred at VISA Open in Keithley 24XX.lvlib:Initialize.vi->Keithley 24XX Read Single.vi

Possible reason(s):

VISA:  (Hex 0xBFFF003E) Could not perform operation because of I/O error."

In the above case I opened the Keitley 24XX REad single.vi. I put the GPIB0::25:INSTR which is the address of the instrument as shown in NI Interactive control.

[Rikud]

Are you successfully communicating with the instrument using the Visa Interactive test mentioned above?

If so, then please attach an NI-Spy capture from the read failure...

[niikos]

Yes the VISA communications are ok.

Here is the Spy output:

> 1.  viParseRsrc (0x00001002, "GPIB0::25::INSTR", 1, 0)
> Process ID: 0x00001304         Thread ID: 0x000010E8
> Start Time: 10:38:22.538       Call Duration 00:00:00.001
> Status: 0xBFFF009E (VI_ERROR_LIBRARY_NFOUND)

> 2.  viParseRsrc (0x00001002, "GPIB0::25::INSTR", 1, 0)
> Process ID: 0x00001304         Thread ID: 0x000010E8
> Start Time: 10:38:22.549       Call Duration 00:00:00.002
> Status: 0xBFFF009E (VI_ERROR_LIBRARY_NFOUND)

> 3.  VISA Get Attribute ("GPIB0::25::INSTR", 0x3FFF0171, 0)
> Process ID: 0x00001304         Thread ID: 0x000010E8
> Start Time: 10:38:22.551       Call Duration 00:00:00.000
> Status: 0xBFFF009E (VI_ERROR_LIBRARY_NFOUND)

4.  VISA Close ("GPIB0::25::INSTR")
Process ID: 0x00001304         Thread ID: 0x000010E8
Start Time: 10:38:22.552       Call Duration 00:00:00.000
Status: 0x3FFF0082 (VI_WARN_NULL_OBJECT)

> 5.  VISA Get Attribute (0x3FFF0171, 0)
> Process ID: 0x00001304         Thread ID: 0x000010E8
> Start Time: 10:38:22.552       Call Duration 00:00:00.000
> Status: 0xBFFF000E (VI_ERROR_INV_OBJECT)

> 6.  VISA Get Attribute (0x3FFF0171, 0)
> Process ID: 0x00001304         Thread ID: 0x000010E8
> Start Time: 10:38:22.562       Call Duration 00:00:00.000
> Status: 0xBFFF000E (VI_ERROR_INV_OBJECT)

7.  VISA Close ()
Process ID: 0x00001304         Thread ID: 0x000010E8
Start Time: 10:38:22.562       Call Duration 00:00:00.000
Status: 0x3FFF0082 (VI_WARN_NULL_OBJECT)

 I attach the Capture log of Spy. In the capture you can see also the test of the VISA communications.