Eurotherm 2216e temperature controller

[prjemian]

• FIX device support for Eurotherm 2216e temperature controller (from USAXS) #559

[prjemian]

Test at USAXS with PV prefix 9idcLAX:tc1:

[prjemian]

usaxs@usaxscontrol /share1/USAXS_data $ caget 9idcLAX:tc1:SetPointTemp
Channel connect timed out: '9idcLAX:tc1:SetPointTemp' not found.
usaxs@usaxscontrol /share1/USAXS_data $ caget 9idcLAX:tc1:Temp1
Channel connect timed out: '9idcLAX:tc1:Temp1' not found.
usaxs@usaxscontrol /share1/USAXS_data $ caget 9idcLAX:tc1:ProgramNumber
Channel connect timed out: '9idcLAX:tc1:ProgramNumber' not found.

@jilavsky Is the Eurotherm 2216e temperature controller turned on? Is the IOC running?

usaxs@usaxscontrol /share1/USAXS_data $ caget 9idcLAX:alldone
Channel connect timed out: '9idcLAX:alldone' not found.

Appears the IOC is not running. Can it be started?

[jilavsky]

Nothing will run at 9ID until Monday. We have 12 hours long planned power shut down for sectors 8-11 on Saturday and beamline is ready to loose power by now - all hardware is off, except remotely controlled PCs which can be shut down tomorrow.
Sorry. Bad timing. Will start next week, likely Monday if you need it.

[prjemian]

Cannot test until at least 2022-01-10. Marking PR as draft until tested.

[prjemian]

Annotated screen capture of USAXS's GUI view of the Eurotherm controller:

• Temp1 and Temp2 provide no useful signal and are ignored.
• SetPointSensor provides the temperature in dC (deciCelsius). (Yuck!)
• Mode is always set to Auto (user is not likely to change it)
• SetPointTemp and SetPointTempWrite are the setpoint (read and write PVs, respectively)
• SetPointPower and SetPointPowerWrite are controlled by the Eurotherm. Just info here.
• Program and Status are ignored by the user.

[prjemian]

Workflow failure is due to caget command,libreadline library, and missing symbol tputs:

2022-01-10T19:13:14.2866060Z shell: /usr/bin/bash -e {0}
2022-01-10T19:13:14.2866385Z env:
2022-01-10T19:13:14.2866772Z   CONDA_PKGS_DIR: /home/runner/conda_pkgs_dir
2022-01-10T19:13:14.2867143Z   PY_VER: 3.9
2022-01-10T19:13:14.2867581Z   ENV_NAME: anaconda-test-env-py-3.9
2022-01-10T19:13:14.2868015Z   PV: gp:UPTIME
2022-01-10T19:13:14.2868336Z ##[endgroup]
2022-01-10T19:13:14.3857805Z caget: symbol lookup error: /usr/share/miniconda/envs/anaconda-test-env-py-3.9/epics/bin/linux-x86_64/../../lib/linux-x86_64/../../../lib/libreadline.so.8: undefined symbol: tputs
2022-01-10T19:13:14.3863712Z ##[error]Process completed with exit code 127.

[prjemian]

It's a conda problem: defaults channel installs readline 8.1.2 (fails) while conda-forge channel installs 8.1 (OK).

[prjemian]

test code:

from apstools.devices import Eurotherm2216e
from apstools.utils import listdevice

PV_PREFIX = "9idcLAX:tc1:"

euro = Eurotherm2216e(PV_PREFIX, name="euro")
euro.wait_for_connection()
print(f"device: {euro}")
print(f"components table:\n{listdevice(euro)}")
print(f"read table:\n{listdevice(euro, scope='read')}")
print(f"in position? {euro.inposition}")
print(f"position {euro.position}")

output

device: Eurotherm2216e(prefix='9idcLAX:tc1:', name='euro', settle_time=0.0, timeout=None, read_attrs=['readback', 'setpoint'], configuration_attrs=['done', 'tolerance', 'power', 'mode', 'program_number'], limits=None, egu='')
components table:
                  data name  value                  timestamp
0                      euro   22.7 2022-01-10 15:34:58.142613
1             euro_setpoint   20.0 2022-01-10 15:34:58.138898
2                 euro_done  False 2022-01-10 15:34:58.143886
3            euro_tolerance      1 2022-01-10 15:34:58.099342
4  euro_report_dmov_changes  False 2022-01-10 15:34:58.097656
5               euro_sensor  227.0 2022-01-10 15:34:57.567181
6                euro_power    0.0 2022-01-10 15:34:58.142232
7                 euro_mode    227 2022-01-10 15:34:58.142407
8       euro_program_number      4 2022-01-10 15:34:57.617181
read table:
       data name  value                  timestamp
0           euro   22.7 2022-01-10 15:34:58.142613
1  euro_setpoint   20.0 2022-01-10 15:34:58.138898
in position? False
position 22.700000000000003

[prjemian]

@jilavsky Looks like the BS support is working now. Once the workflows complete, I'll merge this PR. The new support is still not available for USAXS yet. Expected in a week or so. Waiting on all work in the v1.6.0 release (milestone & project) to be complete.