Cosylab work-package

Various issues for MIL-BUS based FESA classes and API unification for movable devices

Here a list of issues and a time estimate for each of them:

CEHV:

• https://git.acc.gsi.de/fesa-classes/Cehv/issues/6 (2 days)

PPOS:

• https://git.acc.gsi.de/fesa-classes/Ppos/issues/2 (0.5 days)
• https://git.acc.gsi.de/fesa-classes/Ppos/issues/6 (0.5 days)
• https://git.acc.gsi.de/fesa-classes/Ppos/issues/7 (3 days)
• https://git.acc.gsi.de/fesa-classes/Ppos/issues/9 (0.5 days)

DGX:

• https://git.acc.gsi.de/fesa-classes/DgxProfile/issues/11 (3 days)
• https://git.acc.gsi.de/fesa-classes/DgxProfile/issues/9 (0.5 days)
• https://git.acc.gsi.de/fesa-classes/DgxProfile/issues/2 (0.5 days)

Movable Device API:

• Review draft of Movable Device API (0.5 days)
• Once the API is in a final state, implement + Test movable Device API for
  • PPOS (5 days)
  • DSSTepperMotor (5 days)
  • SRFS (only the Property-design, since it not yet functional) (2 days)
  • Cryring Steppers (To be checked if that should be part of this project) (5 days)

Required time total: 28 days (~6 person-weeks)

Hardware for testing:

• PPOS: hardware and SCU is in place, connected and running. Ask Ulrich Pop if it is fine to move any device.
• CEHV: hardware and SCU are connected (Second system still offline). Testing to be coordinated with Jon Rossbach.
• DGX: Status not clear, Rok will coordinate with Beam Diagnostics.
• DSSTepperMotor: To be coordinated with Beam Diagnostics.
• SRFS: SW can be prepared, hardware still has basic communication issues
• Cryring Steppers: Maintained by Solveigh, not clear yet if we are supposed to do anything about them.