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.
I've manually used the 6514 to measure both good and bad probes. The good probes over range (<210G) relatively quickly. The time I believe is the charging of the input capacitance (6514), and that which exists in the probe design. Bad probes take much longer, usually at least twice (> 2 mins) to show over range, or stop at some high resistance. 188G-Ohms for example.
The ones that eventually do over range, take longer I believe due to the extremely high resistance shorts...somewhere in the probe, constantly discharging the current that should be charging the capacitance.
Here is the problem. We don't want to do this manually, so I have created a .net class and written a test program to do this for us. What happens though it not the same as when I follow the exact steps manually. When I do it manually, it acts like I said above. Two mins or so to over range. But when I allow the program to run, I immediately see an over range.
I'm not sure if I'm supposed to post code here, so I'll save that for if anyone responds.
Basically I set to resistance, set autorange ON, limit the return to the reading, and then READ?. I am trying to do this in a loop every 10 seconds, but like I said, I immediately see over range. I do use the zeroing procedure and turn that off just before I ask for READ?.
User Guide mentioning that full amount of control commands these are available at SCPI mode only.
Upload of latest firmware this it might also help.
Who is online
Users browsing this forum: No registered users and 1 guest