when trying the Reach-option for temperature stabilisation (LakeShore 336), I found that even when the setpoint is reached with mK-accuracy, I need a rather high temperature accuracy range (e.g. 1.0K) so that the software moves on with the next sweep value. Also, this necessary accuracy range seems to increase with the setpoint (higher for 297K than 295K). I tried hold accuracy times 1s, 10s.
thank you for noticing this issue and posting it here on the Forum.
Looking at the Python code of the driver, it seems that the wrong value had been read-out for the reach-function.
I changed the driver and uploaded a new version. I can’t test it, because I don’t have the device here.
Can you please install the new driver using the Version Manager? You need to click Refresh online versions and then filter the devices for LakeShore_Modell33?