Controls

The control plane the beamline runs on, and the seam CORA's edge conducts over. Control plane: Tango / Sardana.

P01 runs on the PETRA III control system, which is Tango with Sardana as the scan / motion SCADA layer, NOT EPICS. This is CORA's second Tango / Sardana control floor (after MAX IV) and a sibling of the ESRF BLISS / Tango floor: the seam model that today reads "EPICS is the floor" generalizes here to "Tango / Sardana is the floor". In this stack a motion axis is a Tango motor device addressed by domain/family/member (p01/motor/.), a virtual / coupled axis is a vmexecutor or attributemotor device, and a scan is a Sardana macro run by the MacroServer over a Pool of controllers, with the MeasurementGroup defining the acquired channels. The handles in this descriptor are read from P01's public OnlineXML registry and carried confirm (CTRL-1). The NRS / RIXS acquisition (the high-resolution-monochromator energy scan or the KB-focused spectrometer scan, coupled to the detector readout) runs as a Sardana macro; that orchestration is the seam CORA's edge would conduct over its ControlPort, driving through or replacing the Sardana macro per routine (CTRL-2).

Name	Family	PV	Key specs	Replaceable	Status
OMS58Controllers	MotionController		protocol: Tango_oms58 OMS MAXv-58 stepper motor controllers (Tango module oms58); the dominant P01 motor controller, fleet-wide the most common PETRA III motor class (CTRL-1)		new confirm
TangoMotorControllers	MotionController		protocol: Tango_motor_tango generic Tango motor controllers (module motor_tango) backing the dcm and virtual-axis devices (CTRL-1)		new confirm
VirtualMotorExecutors	MotionController		protocol: Tango_vmexecutor Sardana virtual-motor executors (vmexecutor) computing the coupled energy / slit-center-gap pseudo axes (CTRL-1)		new confirm