Hello,
I would like to perform a transistor Ids drift test over time. The test should apply a constant Vds and Vgs and sample Ids every 1s, to obtain an Ids vs time curve over 3-5days. How could I implement this test using KITE? Or other method that does not involve using Labview with another Laptop.
Thank you.
Tektronix Technical Forums are maintained by community involvement. Feel free to post questions or respond to questions by other members. Should you require a time-sensitive answer, please contact your local Tektronix support center here.
Measuring current drift over time with 4200-SCS
-
- Keithley Applications
- Posts: 1514
- Joined: October 15th, 2010, 10:35 am
- Country: United States
- Contact:
Re: Measuring current drift over time with 4200-SCS
If you try to use the ITM of KITE with Sampling Mode based test, the highest number of samples supported by the ITM will be 4096.
To accomplish this from the KITE environment, you would need to use the KULT tool and write a custom library/module and then execute it from a UTM in KITE.
The main reason for this is because the total number of data points (every 1 second for multiple days) will exceed that number of rows that the KITE data sheet environment can support. Your UTM code could push the full data set to an ASCII data file for offline analysis and perhaps post a smaller subset of the data to the KITE sheet.
To accomplish this from the KITE environment, you would need to use the KULT tool and write a custom library/module and then execute it from a UTM in KITE.
The main reason for this is because the total number of data points (every 1 second for multiple days) will exceed that number of rows that the KITE data sheet environment can support. Your UTM code could push the full data set to an ASCII data file for offline analysis and perhaps post a smaller subset of the data to the KITE sheet.
Re: Measuring current drift over time with 4200-SCS
Thank you for the suggestion, unfortunately I have no experience using KULT, are there any examples I could use?Andrea C wrote:If you try to use the ITM of KITE with Sampling Mode based test, the highest number of samples supported by the ITM will be 4096.
To accomplish this from the KITE environment, you would need to use the KULT tool and write a custom library/module and then execute it from a UTM in KITE.
The main reason for this is because the total number of data points (every 1 second for multiple days) will exceed that number of rows that the KITE data sheet environment can support. Your UTM code could push the full data set to an ASCII data file for offline analysis and perhaps post a smaller subset of the data to the KITE sheet.
-
- Keithley Applications
- Posts: 212
- Joined: October 25th, 2010, 1:31 pm
- Country: United States
- Contact:
Re: Measuring current drift over time with 4200-SCS
Without a custom library, the next possible solution would be to create a series of ITM to operate in a sequence where each ITM is performing a sample at 1 second intervals. Interval timing may vary if you use auto-ranging for both sourcing and measuring operations. Any other automatic functions may impact the timing of each measurement interval depending on the test condition.
That being said and as Andrea notes, you can only take up to 4096 samples. At one second per reading, this is a little more than 68 minutes per ITM. At a little more than an hour, it would be necessary to duplicate this test 64 to 100 times.
In the timing window, enable timestamps, and uncheck the disable outputs at completion for all but the last test. Under Exit conditions, use the project setting. This will ensure that the test will completely stop if a compliance condition is detected.
Unfortunately, data management will be a challenging and tedious effort. At least you can run this test without using KULT.
That being said and as Andrea notes, you can only take up to 4096 samples. At one second per reading, this is a little more than 68 minutes per ITM. At a little more than an hour, it would be necessary to duplicate this test 64 to 100 times.
In the timing window, enable timestamps, and uncheck the disable outputs at completion for all but the last test. Under Exit conditions, use the project setting. This will ensure that the test will completely stop if a compliance condition is detected.
Unfortunately, data management will be a challenging and tedious effort. At least you can run this test without using KULT.
Who is online
Users browsing this forum: No registered users and 1 guest