Andrea C

Is this front panel manual operation or sending commands?

Manual operation would need you to define a channel pattern that includes the backplane relay and the channel relay.  Then open or close the pattern.

If sending commands, the channel.close() and open will accept the relay number of your backplane relay as part of the channel list.

In the wiring to the 37xx card, take note of the +ILK and -ILK pins (on each bank if using MUX card).  Those need shorted to permit backplane relay closure.

When the 3706A model has the internal DMM, the backplanes are typically managed for you.  For example a channel configured for 4-wire ohms vs VDC measure function will close all necessary relays when dmm.close() on that configured channel.

If you have 3706A-S, then it is just a switch controller.

Hello,
Thank you for clarifying that.
The 2602B has only the TSP command set, so no need to worry about that setting on the instrument.
It is very odd that the instrument reports a TSP syntax error.

In my C# environment, I set build to x64 platform target.  It is running fine for me.

​​​​​​​try
            {
                //Instantiate driver class directly
                driver = new Ke26XXA();

                VISAResource = availableResourcesListBox.SelectedItem.ToString();

                string options = "QueryInstrStatus=True";
                driver.Initialize(VISAResource, true, true, options);

                label1.Text = "Successful Driver Session";


                //driver.System.DirectIO.WriteString("reset()", true);



                driver.Sweep.set_SourceChangesEnabled("A", true);
                driver.Sweep.set_MeasurementsEnabled("A", true);

                string bufferName = "MyBuf";
                int bufSize = 11;

                driver.Measurement.Buffer.Create("A", bufferName, bufSize);

                driver.Sweep.Source.ConfigureVoltageLinearSweep("A", 0, 1, 11);
                driver.Sweep.Measure.ConfigureCurrentMeasurement("A", bufferName);

                // Set the sweep count
                driver.Trigger.set_Count("A", bufSize);
                // Set the reading count (1 pt for each sweep value)
                driver.Measurement.set_Count("A", 1);
                // set other measurement related paramters
                driver.Measurement.set_NPLC("A", 1.0);
                driver.Measurement.set_Delay("A", 0.001);

                driver.Source.set_OutputEnabled("A", true);

                driver.Sweep.Initiate("A");
                driver.System.WaitForOperationComplete(10000);

                double[] readings = driver.Measurement.Buffer.MeasureData.GetAllReadings(bufferName);

                foreach (double reading in readings)
                {
                    resultsListBox.Items.Add(reading.ToString("E"));
                }

                driver.Source.set_OutputEnabled("A", false);

                // close the driver
                driver.Close();


            }
            catch
            {
                label1.Text = "Could not open driver session!!";
            }

 

Is true.  At present the KXCI API has no means to read back the error detail.
I have created an enhancement request about it.

Can you clarify what model number is the instrument?

From your attached image, you are using IVI driver.  I believe the IVI driver wants the touch screen SMU models such as 2450 to be in SCPI command set.
Your reported error about TSP Syntax tells me the instrument is in in TSP command set.  If this is touch screen model of SMU, that would be a problem.

Do I have it correct?

Sounds like you are making very robust error handling in your application.

Looks like, right now, the only way for you to know the error detail is to look at tail of the KXCILogifile.txt in the C:\S4200\sys\kxci
In KXCI window, be sure to enable logging.
Can your application somehow map that drive location and do some file IO?

From the KXCI command set, you can interrogate the state of a bit in the status byte to know if an error has occurred.
But not aware of any way to query the error detail on this API.

Python sample for interrogating status byte:

​​​​​​​import time
import pyvisa
import socket


def main():
    rm = pyvisa.ResourceManager()
    dev_address = "TCPIP0::192.168.1.43::1225::SOCKET"
    my_4200A = rm.open_resource(dev_address)
    my_4200A.read_termination = "\0"
    my_4200A.write_termination = "\0"
    my_4200A.timeout = 1000

    # No Error in *IDN?
    print("Response to *IDN?: ", my_4200A.query("*IDN?"))
    status = my_4200A.query("SP")

    # Check bit B1 of status byte for previous command error
    if (int(status) & 0x02) != 0:  # Check bit B1 of SP response
        print("Error Detected. Bit B1 value: ", (int(status) & 0x02))
    else:
        print("No Error Detected. Bit B1 value: ", (int(status) & 0x02))

    # Error in *IDN?
    print("Response to *ID?: ", my_4200A.query("*ID?"))
    status = my_4200A.query("SP")

    # Check bit B1 of status byte for previous command error.
    if (int(status) & 0x02) != 0:  # Check bit B1 of SP response
        print("Error Detected. Bit B1 value: ", (int(status) & 0x02))
    else:
        print("No Error Detected. Bit B1 value: ", (int(status) & 0x02))

    my_4200A.close()


if __name__ == "__main__":
    main()

 

You should not be needing to simulate front panel button pushes this way.

Can you clarify:  do you have a digital triggering cable between the two instruments?  I'll put some code below that assumes you do.

And you have two COM ports on your computer and have RS-232 to each instrument?

Here are some SCPI commands to use 2400 as current source while 2182A does delta mode measurements.

:syst:pres ‘ 2182 - System preset defaults.
:trig:del 1 '2182 - 1sec delay.
:sens:volt:delta on ‘ 2182 - Enable Delta.
:syst:faz off ‘Disable Front Autozero to double Delta speed.
:trig:sour ext ‘ 2182 - External triggering.
:trac:poin 3 ‘ 2182 - Buffer size 3.
:trac:feed:cont next ‘ 2182 - Enable buffer.
*rst ‘ SM - RST defaults.
:trig:sour tlin ‘ SM - Select trigger link.
:trig:dir sour ' SM - Enable source bypass.
:trig:outp sour ‘ SM - Output trigger after source.
:trig:coun 6 ‘ SM - Trig count 6.
:sour:func curr ‘ SM - Source current.
:func ‘volt’ ‘ SM - Measure voltage
:volt:nplc 0.01 ‘ SM - Fast measurements
:sour:list:curr 10e-6, -10e-6,20e-6, -20e-6, 50e-6, -50e-6 ‘ SM - Current list values
:outp on ‘ SM - Turn output on.
:sour:curr:mode list ‘ SM - Enable list mode.
:init ‘ SM - Start sweep.

Short answer is yes.
But a lot of details to manage including safety interlocks, common LO,  and over voltage protection for the 4200A from the 2657A.

Is your Lakeshore capable of the HV and the current densities of the 50Amps?  Or you will have different probe station for the new high power IV tests.

I suggest you get in contact with your local Keithley FAE for detailed discussion and configuration.
Are you located in Nebraska?

Does C# run on Arduino?  Or is there also a Windows computer involved that is running C#?

You 6517A can be command controlled over RS-232 or GPIB.

I'd suggest the C# program will control the Arduino/16channel relay module to routing signal to the 6517A.
Then C# can also obtain a reading from 6517A.

Will the 6517A measure current or voltage or ?

You have it correct.
Only commands that end in question mark will automatically cause a response to be put into the output queue.
Your VISA read transfers the output queue.
In conventional SCPI there are often query form of commands to interrogate instrument settings.
In TSP, we rely on the print() or printbuffer() to place content in output queue.

There is a status.condition register with a message available bit (MAV) that will be logic 1 if there is content in output queue.  Use VISA ReadSTB rather than a visa read after writing print(status.condition) command.

Hi Richard,

I do not see anything wrong with that you are doing.
Is the LAN connection from Test Script Builder closed?  The instrument can accept only one connection at a time.

For future reference, when the LAN connection gets stranded, there is a dead socket recovery port.
If you can connect on the dead socket and then close, it forces any open LXI LAN connection (port 5025) to close.
If my theory about an open connection from Test Script Builder is why you are having troubles, the dead socket would let you take it away.

import pyvisa
import time


resource_mgr = pyvisa.ResourceManager()
#optional print available VISA resources on this computer
resource_list = resource_mgr.list_resources()
for resource in resource_list:
    print(resource)

try:
     #get a session/handle for one resource
     instrument_resource_string = "TCPIP0::192.168.1.55::inst0::INSTR" 
     #resource_list[0]  #for me, resource_list[0] = 
     my_instr = resource_mgr.open_resource(instrument_resource_string)
except(pyvisa.VisaIOError):
     #try connect on dead socket on port 5030
     print("Attempting Dead Socket recovery.....")
     my_instr = resource_mgr.open_resource("TCPIP0::192.168.1.55::5030::SOCKET")
     my_instr.close()
     time.sleep(0.5)
     #try again now on normal LXI port
     my_instr = resource_mgr.open_resource(instrument_resource_string)
     print("Done attempting Dead Socket recovery.....")
    


my_instr.write("*IDN?\n")
print("*****")
print(my_instr.read())