-
Notifications
You must be signed in to change notification settings - Fork 1
lakeshore support not waiting to reach temperature #118
Comments
The default support looks for |
Changing the |
Implemented local workaround as quick solution in user's directory:
|
TODO: Factor these changes into the Device for this object. Look at |
note: We have learned that ophyd is designed specifically to not use EPICS CA monitors. Instead, to get the immediate value of any |
clarification: in #118 (comment), signal is the readback value of the controller set point (confirms the controller knows the temperature we want the controller to maintain) while temperature is the value from the temperature sensor (the readback). |
Compare our Lakeshore support with similar from NSLS-II/CSX: https://github.com/NSLS-II-CSX/xf23id1_profiles/blob/master/profile_collection/startup/csx1/devices/lakeshore.py Looks as if our EPICS database is different, thus different device-specific PVs, on top of the different PV name scheme used at NSLS-II. |
With changeset 64abd0b , this code is ready for testing. |
Tried a simple test:
Lakeshore is not connected. More diagnostics:
So, when lakeshore is not connected, the EPICS support reports a temperature of |
Testing the support now:
Indicated success:False at end of wait. But it was settled within 1 degree! |
retesting
The temperature reporting is weird. Oscillates between 0 and temperature readback. Not sure this is a problem to solve in bluesky, certainly not part of this issue. Declare success with waiting to reach temperature. |
When scanning the
lakeshore.loop1
object through a list of temperatures, we observed that thelakeshore.loop1.wait_until_settled()
method was not waiting.The text was updated successfully, but these errors were encountered: