Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Motor .DISP (disabled) field needs a workaround (or an upstream fix) #1158

Open
ZLLentz opened this issue Aug 30, 2023 · 0 comments
Open

Motor .DISP (disabled) field needs a workaround (or an upstream fix) #1158

ZLLentz opened this issue Aug 30, 2023 · 0 comments

Comments

@ZLLentz
Copy link
Member

ZLLentz commented Aug 30, 2023

Current Behavior

In [2]: sp1k4.zone_plate_x.disabled.enum_strs

In [3]: sp1k4.zone_plate_x.disabled.pvname
Out[3]: 'TMO:SPEC:MMS:03.DISP'

In [4]: type(sp1k4.zone_plate_x.disabled)
Out[4]: ophyd.signal.EpicsSignal

In [5]: exit
(pcds-5.7.3)zlentz@psbuild-rhel7-02:~/github/typhos(master -)$ caget TMO:SPEC:MMS:03.DISP
TMO:SPEC:MMS:03.DISP           0
(pcds-5.7.3)zlentz@psbuild-rhel7-02:~/github/typhos(master -)$ caget -d 31 TMO:SPEC:MMS:03.DISP
TMO:SPEC:MMS:03.DISP
    Native data type: DBF_CHAR
    Request type:     DBR_CTRL_ENUM
    Element count:    1
    Value:            Enum Index Overflow (0)
    Status:           NO_ALARM
    Severity:         NO_ALARM
    Enums:            ( 0)

seems to be universal across all 2 motor records I've checked (ims, beckhoff)

Expected Behavior

the signal should report that this can be disabled or not disabled as a two option enum

Context / environment

makes the typhos screen not look/work great

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant