Keithley 2400 simulated through IVI

[The_demon]

I've gotten the drivers to simulate a Keithley 2400. But my setup is buggy. Even though it appears in the palettes, when I use its VI, I get the error message "KE2400 Initialize.vi<ERR>
Driver Status:  (Hex 0xBFFF00A5) The interface type is valid, but the specified interface number is not configured." How can I fix this?

Is there anyone out there with experience with this kind of thing that can help or direct me to examples or ressources?

[Kyle97330]

From your screenshot those look like just "regular" GPIB/serial drivers... not IVI drivers that allow simulation.  

Are you sure you've actually got IVI drivers installed?  If so, you should be using the IviDMM palette, not a KE2400 palette.  Though IVI drivers lack several features that the KE2400 supports.

I'm assuming you're trying to write code to talk to a 2400 when you don't actually have the device attached to your PC?  Can you post the VI that's giving you problems?

[Minions]

What about using something simple like this to communicate with the instrument?

Select the VISA resource that matches your instrument, then enter something like:

*IDN?

Followed by a return in the write buffer.  You should see the instrument response in the read buffer when connected to the instrument.  You can configure/control the instrument with any available SCPI command in this manner.

[The_demon]

I got it from here: http://www.tek.com/source-measure-units/2400-software/2400-ivi-driver-visual-basic-vb-vc-c-labview-l...

I installed the KI0L and then the driver. I don't have consistent access to the Keithley in my lab, so I need to be able to test the basics of my code.

[The_demon]

Here is a copy of my code. The disabled part is supposed to be running off of a simulated Keithley but doesn't work.

[Minions]

You have the GPIB addressing incorrectly listed as:

:GPIB0::16:INSTR

Move the first colon before the INSTR command

GPIB0::16::INSTR

Also, it appears that you only have a single GPIB bus.  Both of these will be vying to access the bus in a random fashion.  I would recommend that you allow one instrument to be configured prior to the other taking control of the GPIB bus. 

In the section above, your command boxes have unnecessary semi-colons spread throughout.  A command line with a semicolon is typically processed the same as a newline character.

:sour:func volt;:sour:volt:mode fix;:sour:volt

is the same as:

:sour:func volt
:sour:volt:mode fix
:sour:volt

[The_demon]

Getting this for the lower part. I'm not running both portion of code simultaneously. I disable one when I need to run  the other.

KE2400 Initialize.vi<ERR>
Driver Status:  (Hex 0xBFFF003E) Could not perform operation because of I/O error.

[Minions]

For the 2400 SMU, It looks like you would like to output 0V at up to 1mA and want it to measure in the 5V range?

First, the range should be 20V.  Your compliance limit settings will never allow you to drive over 1mA.  What are the voltage/current limits currently set on the device as you are not having it reset to default upon first connection?   Also, you might want to initialize the devices off-state (HI-Z, LO-Z, <don't recall the other option>).

[The_demon]

Thanks for the advice. I still don't know how to simulate a Keithley 2400 though.

[m@NI_forum]

Have you managed to simulate Keithley 2400 at the end? Please let us know.