-
Notifications
You must be signed in to change notification settings - Fork 3
Description
@QuazarTech/support
The commit tag referring to this issue is : e9c9fa1
Link to file : https://github.com/vishnu2709/Qrius/blob/IV_script/user_scripts/time_resolved_IV.py
We have written a python script to set a DC Voltage on the XSMU, and then make multiple measurements of current using the function CM_getReading (filterLength=1) from /modules/xsmu/xsmu.py.
The code for the measurement :
f = open("I-Data.txt", "a")
for index in range(iterations):
current = xsmu_driver.CM_getReading( filterLength = 1 )
temperature = xtcon_driver.getSampleTemperature()
f.write(str(current) + "," + str(temperature) + '\n')
f.close()We were able to make roughly one current measurement every 200 milliseconds (time measured approximately using the function time.strftime() from standard python library time), using the code below :
import time
f = open("I-Data.txt", "a")
for index in range(iterations):
current = xsmu_driver.CM_getReading( filterLength = 1 )
t = time.strftime('%H:%M:%S')
f.write(str(current) + "," + t + '\n')
f.close()But time stamps obtained this way include the time taken for the communication between the PQMS and the computer, and the time taken to execute any python instructions, etc.
We have obtained the following plot of Measured Current vs Number of Datapoints, for CM_RANGE_1mA on a 6.2 V Zener Diode forward biased using a Voltage Source with a value 0.67 V.

In the above plot we want to replace the X-Axis (Number of Datapoints) by the precise time stamp at which each datapoint was generated (ignoring the communication time with the computer, the python script execution time and other possible overheads).