From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

Instrument Control (GPIB, Serial, VISA, IVI)

cancel
Showing results for 
Search instead for 
Did you mean: 

Working Keithley 236 sweep example, anyone?

Solved!
Go to solution

Does anyone have verified working example code for the Keithley 236 using a version of LabVIEW from the last 10 years or so that performs a vi sweep?  Kindly post if so.  While the static DC measurement examples available on the NI website work, the sweep examples do not (for me at least). For example, the vi "Keith 236 Sweep Example" does not pull in the data at the Keith 236 Read Measurement subvi contained therein.  No errors, it just does not pull in the data after the voltage-control sweep has been performed.

0 Kudos
Message 1 of 4
(1,063 Views)
Solution
Accepted by topic author PHacke

Figured it out. In the Keith 236 Read Measurements vi, in sequence no. 0, changed the initial read point with the String Subset function from 10 (what it is when downloading from this NI website) to 9 to properly read the "true:sweep false DC" value.  To note, the version of my Keithley 236 (seen in the LED readout at startup) is A03.

0 Kudos
Message 2 of 4
(1,008 Views)

The Keithley 236?  There's a classic!  I one collecting dust in storage and can't quite bring myself to dispose of it quite yet.  I used to have lots of code for them.  They use simple single/double letter commands to setup.  But they are unforgiving if you send a value outside of the expected range or in a format the instrument isn't expecting.  They are also a little unforgiving in the order you send setup commands.

 

I suggest you check the parameters you are sending for the sweep.  Are they formatted correctly?  Are they withing the I/V limits? 

 

Then use highlight execution to watch the SMU as it receives commands. Possibly send one setup command at a time and make sure there's no error on the SMU. 

 

Finally check if the trigger has been sent.  I used to use mine through a 237 trigger unit, helped with syncing 4 SMUs.  I remember something about the software trigger being a bit awkward to figure out. 

 

Also look out for waits or timeouts in the code or with the GPIB bus.  This is an old instrument, its not fast!  Set timeout to 300s when asking for a few hundred data points.  You can practically hear each bit trickle in!

 

Post code with save default values and images of errors for more help.

Craig

0 Kudos
Message 3 of 4
(1,008 Views)

Thanks, cstorey.   Like I mentioned in a post above, I figured it out and indicated the solution.

To note, I came across another such Keithley (238 variant) with a later version of firmware (A08), and the NI website- provided LabVIEW software worked fine out of the box with that. 

 

0 Kudos
Message 4 of 4
(985 Views)