Custom EPS screens

[jozamudi]

Description

Added BeckhofAxisEPSCustom class in epics_motor.py and BeckhofAxisEpicsCusom.ui to allow the use of a custom screen to show EPS information.

Motivation and Context

We want to be able to protect motion stages from running into each other.
pcdshub/lcls-plc-crixs-motion#71

we want to be able to display this EPS information on they typhos screen to make accessible for the users.

https://jira.slac.stanford.edu/browse/ECS-3966

How Has This Been Tested?

Used typhos 'pcdsdevices.epics_motor.BeckhoffAxisEPSCustom' to open typhos screen

Where Has This Been Documented?

EPS Screens can be placed here.
reg/g/pcds/epicsdev/screens/pydm/eps_screens/${beamline}/${name}

Pre-merge checklist

• Code works interactively
• Code contains descriptive docstrings, including context and API
• New/changed functions and methods are covered in the test suite where possible
• Test suite passes locally
• Test suite passes on GitHub Actions
• Ran docs/pre-release-notes.sh and created a pre-release documentation page
• Pre-release docs include context, functional descriptions, and contributors as appropriate

[ZLLentz]

I think this is a good idea, but before we merge I think we need to:

• finish the pre-merge checklist items
• add a screenshot of a screen in-use rather than with a "path not found" error for documentation purposes

More thoughts/questions:

• Is the standard path included here where we're going to start stashing EPS screens?
• Is there some reason why we cannot or should not use https://github.com/pcdshub/pcdswidgets/blob/master/pcdswidgets/eps_byteindicator.py in a more direct way here? Motors should theoretically have consistent PVs for enable/forward enable/backward enable

[jozamudi]

@ZLLentz The standard path was documented in the BeckhofAxisEPSCustom class declaration. I added the path in the PR. Is there a better path we can use?

I don't think there is a major reason why we could not use the eps_widget more directly. The only reason would be that some information might not be relevant to a motor that does not have those eps conditions implemented in the PLC.

[ZLLentz]

Sorry for my late reply- just small things to adjust here

[ZLLentz]

This fell off my radar for two reasons: the github notification interface dropped the mention of "review requested", and I got distracted with Monday things yesterday. I'm not sure why github demoted my involvement here from "review requested" to "mentioned", but it made my brain skip over this in the notifications list in favor of the other tickets... my bad.