-
We will need to dig into this one a bit.
Question: if not logging to USB, would the long duration scan operate without any issue? Do you have opinion about that?
-
Hello,
The present firmware release level is 1.7.12.
In general, especially if at beginning of a development effort, I recommend to use latest firmware.
However, the issue you are facing will not yet be resolved with firmware update.
For active devices with open circuit voltage greater than 20V, we presently have an issue that is preventing pulsing back to the bias condition of 0A at V_Limit greater than 20. For now, need to stay within the 1Amp if VOC greater than 20V.
Andrea
-
Hello Maia,
Factory took a look using a 6517B at A14 firmware, same as you.
Not able to duplicate any issue related to auto range as the applied V to resistor changes.
Factor suggested that your specific unit may have a service issue (RMA).
Andrea
-
It seems like a surprising amount of settling time for only 1KOhm of resistance.
Any idea of how much capacitance is in your setup? How long are cables, etc.
Your Word doc shows 5msec is too fast/not settled. But next delay time is 500msec and 1000 msec which show good agreement in the IV curve for the 1K resistor.
Did you try anything smaller than 500msec?
Just as troubleshooting technique, under manual operation, you can configure the DAQ for digitize current mode and even use edge triggering. With that you can perhaps capture the actual settling time for steady state when the power supply changes from V1 to V2.
What value of current limit to are you using with the power supply? If set too low, perhaps that is being invoked during the voltage change when currents will be largest. If yes, this will slow down the final value steady state time requirement.
-
Sorry the manual is a bit sparse on it.
The values are adjustable because some applications need different values.
For example, if using the load to discharge batteries to generate battery models, it will be common to avoid discharging the battery beyond its lowest voltage. A 18650 battery is 3.7V nominally, but stop discharging at ~3.0V.
By using these values the load, you can automatically stay within bounds.
-
If not already, go to tek.com and get the User Manual for the 2700. There are SCPI commands illustrated in such as section 7 on scanning.
Also our older forum may have some good posts:
https://forum.tek.com/viewtopic.php?f=62&t=142711
OR
https://forum.tek.com/viewforum.php?f=62
-
The TSP Runtime for the scripts does not have access to the USB-TMC for communication with external devices.
Only supported way is to use TSP-NET commands and the LAN port.
I've personally used this for communication with AFG or scope from the TSP script.
Just treat it like a raw socket based connection at an IP address and port number.
I have not personally used them, but there are LAN to RS-232 adapters from a google search.
I do not see any reason that TSP-NET would have issues to connect to the LAN side of one of those and allow it to echo the commands on the RS-232.
-
I'm finding that KickStart 2.10.1 supports up to 100K measurements the 2600B while biasing.
Which version of KickStart do you use?
Can you get specific for how long of a duration of sampling you would want to have?
And related would be the desired sample rate and number of resultant points of current vs. time.
If the 100K points seems enough, just we sample too fast, try increasing the NPLC value so that more time is required for each individual measurement.
-
Our 2600B series have feature in the TSP runtime engine to utilize the RS-232 port for communication with external device from the instrument scripting.
But same serial API is not defined for the KTTT-RS232 add on card for DAQ6510.
It does have TSP-NET to utilize the LAN port for external device communication.
-
Surprised to hear the phase marker signal is not TTL for you.
What was input R of the scope when observing it? Were you also temporarily disconnected from the lock-in trigger when evaluating?
Can you try different line within the TLINK for phase marker?
is the lock-in using falling edge trigger from 6221?