DCS & Communication Software for the TPC Front-end Electronics

1. DCS & Communication Softwarefor the TPC Front-end Electronics Matthias Richter Sebastian Bablok Department of Physics and Technology, University of Bergen, Norway Benjamin Schockert Center for Technology Transfer and Telecommunications, University of Applied Sciences Worms, Germany TPC Front-end-electronics meeting, Cern, Nov 22,2005

2. PVSS II (FED - Client) FED Server InterComLayer FEE Client Cmd / ACK Channel FeeServer FeeServer FeeServer Service Channel Message Channel Hardware Device Hardware Device Hardware Device Software architecture Supervisory Layer Load configuration data from fileOR database Front-End Device Interface (FED) Config. File Control Layer Config. DB Front-End Electronics Interface (FEE) Field Layer Internal Bus Systems

3. Status of the components

4. Configuration Data Encoding • CE provides 2 alternative formats of Configuration Data: • Usage of CE Command Set to write to RCU memory • Each single operation corresponds to one DIM command • Low performance, but flexibility for development • But: multiple operations can also be stacked into one DIM transaction if desired • Message Buffer Format (data exchange interface between DCS board and RCU – previously presented, see talk TPC FEE meeting Jan 05) • allows to encode multiple operations into one command block even on the level of data exchange between DCS board and RCU • 2 alternative ways of data archiving: • As BLOBs • Archiving of individual parameters and data preparation on-the-fly

5. Next steps • Data base interface: Specifications discussed with the DCS group; implementation ongoing • File access as fall back solution available • performance tests of data base access • FedAPI implementation in progress • PVSS – InterComLayer communication using the FedAPI • Handling of States for RCU and FECs in the FeeServer ControlEngine • Optimization 2005 2006 2007 I. II. III. V. IV. VI.

6. Open issues • Data base structure and structure of config data has to be defined • Creation, Handling, Archiving • communication: ControlEngine – Monitoring and Safety Module (MSM): data publishing fully functional but sophisticated error handling/notification scheme necessary • mass tests and scaling of behaviour with 216 DCS board nodes connect to the InterComLayer

7. Documentation and Download • http://www.ift.uib.no/~kjeks/wiki • General Overview • Download (Source code packages, programs for the DCS board) • CE command specification • CE service specification • Setup recipe • FAQ • Source code and documentation of FeeServer core and InterComLayer: https://www.ztt.fh-worms.de/download/alice • anyway: drop an email to us if there is something mysterious with the software or you couldn't find what you want: • Matthias.Richter@ift.uib.no, Sebastian.Bablok@ift.uib.no,Schockert@ztt.fh-worms.de

8. FED Server FeeServer InterCom Layer FEE Client CE Components and APIs PVSSFED Client FEE ROOT Debug GUI(ROOT framework) FEE ROOT Client USB connector FEE Client FED Client FED API(DIM) FEE API(DIM) FED API(DIM) U2F API Configuration Database DB API FEE API(DIM) RCU (Motherboard) CE-RCU API FEE-CE API DCS board