-
In version 1.13 of our Clarius software, KXCI API is enhanced for the PMU and accessing the SegArb mode directly without UL and EX to KULT code.
Numerous examples have been posted to our github site:
Github 4200A KXCI Python Samples
-
If the 2400 is reporting 7mV, then it thinks it is doing good job (within the source spec) of enforcing the 0V set point.
But your external voltmeter tells you there is a very big error.
I'd be skeptical of overall performance and would check the various source ranges and measure ranges you intend to use.
Connected a trusted amount of R between HI and LO to validate if the current measure is correct (for the voltmeter reported voltage).
The amount of voltage offset you have is well beyond amounts that are corrected by calibration. I suspect some sort of repair issue in your unit.
-
Hello,
Have you examined the sample code in the PMU_examples_ulib?
There is also a sample project by same name that show cases each of the modules in the library.
There are a several SegArb related samples in that library.
Let us know if you remain stuck.
-
Hello,
We should have asked you for some log files to delve into the underlying reason.
Do you have any extra third-party software installed? That can sometimes cause issues.
The present version of Clarius on the 4200A is 1.13.
I suggest you download that from tek web site and apply.
Then retest.
If issue persists, please contact your local office for a regional Apps Engineer to assist you.
-
When using LAN based connection to KXCI, it is normal for every config command you send to respond back with ACK\0.
Pg 2-11 in the KXCI Remote Control Programming manual shows ethernet based write and read examples.
For example, sending ME\0 command, the 4200A will respond back with ACK\0
In your code, if using LAN to KXCI, plan to do a write + read for every operation to pull the ACK\0 off the bus.
-
On both the older 4200-SCS that you have and our 4200A-SCS, there is the KXCI interface.
This is the Keithley eXternal Command Interface or KXCI.
Close KITE or Clarius and invoke KXCI.
But first visit KCON and config the LAN or GPIB interface.
Attached is an application note on using Python with 4200A-SCS.
-
An offset of 700mV is quite large for any of the ranges.
I'd say it is unlikely to be a calibration issue. It most likely requires some service.
Humor us and double check the setup. From power on default behavior, if you just turn the output on (blue light) it would be configured to source 0V with current limit of 105uA.
Do any digits on front panel flash rapidly?
And if you connected a voltmeter to the HI and LO, you see 0.7 volts instead of 0V (don't use the resistor)?
Is it a constant amount of offset....if you asked the 2400 to source 1V, would you get 1.7V?
-
For the 2380 load, the only application of KickStart that recognizes the load is the Battery app. That is an extra license (not included in -SUITE).
It can control the load for generating a battery model.
The 2260B may only be recognized by KickStart when using the USB-CDC interface not the LAN.
-
You should probably talk this over with your local applications engineer.
What is the maximum short circuit current from your device?
I am guessing the SMU is used in force voltage and limit current mode with your solar PN junction.
You might be encountering current compliance or range compliance. Anything on the front panel of 2400 go to flashing on/off when you open the shutter?
-
Can you explain the 3-sigma value? How compute it?
In your config, what sort of speed settings? Use Quiet if looking for small standard deviations.
It looks like your DUT value is a few single digit pF.
At 1KHz, it will be very big Z and very small current relative to using higher test freq.
In our datasheet for CVU, we do not publish value for pF at 1KHz.