Controls

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

FAXTOR runs on the ALBA Tango / Sardana / Taurus control stack, CORA's second Tango / Sardana controls house-style after MAX IV. Device IO is a layer of Tango device servers (motors over IcePAP-class controllers, detectors via the Lima framework), with Sardana (a Pool of controllers / motors / measurement groups plus a MacroServer running scan macros) as the experiment-orchestration layer and Taurus as the operator UI. No public per-beamline device manifest is published, so the Tango / Sardana / IcePAP handles are not bound here, carried pending staff verification (CTRL-1); when bound they would be modelled as opaque edge handles over the ControlPort, the way the MX3 and ID32 heterogeneous-control precedents do. The fast continuous-rotation tomography acquisition (the rotary trajectory, the camera triggering, the flat / dark sequencing) runs through Sardana macros; that orchestration is the seam CORA's edge replaces, conducting over Tango / IcePAP rather than replacing Sardana. The Lima detector file-writing to the ALBA data store is plumbing CORA observes, not data it owns (see model.md).