André Augustinus 10 March 2003 DCS Workshop Detector Controls Layout Introduction

André Augustinus 10 March 2003DCS Workshop 2 Motivation  Capture the current state of knowledge on your controls layout Also triggered by “installation review”  Concentrate on the hardware layout of your control system  Get an idea on what, where, how many Radiation and accessibility for equipment in the cavern  See Robert’s talk this afternoon

André Augustinus 10 March 2003DCS Workshop 3 Method  Provided you with a drawing showing our knowledge (TDR, URD, presentations, discussions)  Appended a list of questions  Requested you to show today an update of the drawing and answers to the questions  Example for muon tracker

Detector CAEN ? PVSS II Detector Wiener PCI-CAN Wiener OPCserver Ethernet Database(s) OPC client DIM client ? Detector ?128 High VoltageLow VoltageEnvironment monitor PVSS II OPC client PVSS II OPC client ? ? OPCserver PVSS II OPC client User interface PVSS II Schneider OPCserver Gas system PLC ELMB Gas E C P EC HV LV Muon-Trk Control room (ACR) [FSM?] I/O device (PLC,Wago,ELMB?) ? PCI-CAN Wiener OPCserver PVSS II OPC client C VME (wiener?) 1 Crate Control 1 Geometry monitor DIMserver (?) ?? Geometry Air/Water cooling PLC(?) OPC/DIM Server (?) ? Detector Cooling ? E Detector ? ? 07/03/03 PCI-CAN Switch HV 444? C CAEN OPC Crocus 20 DDL

André Augustinus 10 March 2003DCS Workshop 5 CAEN OPCserver PVSS II Wiener OPCserver Ethernet User interface Database(s) OPC client DIM client PVSS II Schneider OPCserver PVSS II OPC client PVSS II OPC client [FSM?] DIMserver This depicts a task on one or more PC’s, there is no one-to- one correspondence between boxes and PC’s User interface; main console for detector operation Main PVSS tasks; interface to field layer, Finite State Machine, … Database tasks (reading and writing). Field and process layer, with their processes “Generic” architecture for the DCS “back end”

Detector CAEN ? PVSS II Detector Wiener PCI-CAN Wiener OPCserver Ethernet Database(s) OPC client DIM client ? Detector ?128 High VoltageLow VoltageEnvironment monitor PVSS II OPC client PVSS II OPC client ? ? OPCserver PVSS II OPC client User interface PVSS II Schneider OPCserver Gas system PLC ELMB Gas E C P EC HV LV Muon-Trk Control room (ACR) [FSM?] I/O device (PLC,Wago,ELMB?) ? PCI-CAN Wiener OPCserver PVSS II OPC client C VME (wiener?) 1 Crate Control 1 Geometry monitor DIMserver (?) ?? Geometry Air/Water cooling PLC(?) OPC/DIM Server (?) ? Detector Cooling ? E Detector ? ? 07/03/03 PCI-CAN Switch HV 444? C CAEN OPC Crocus 20 DDL

André Augustinus 10 March 2003DCS Workshop 7 E Ethernet C CAN bus P Profibus HV HV cables LV LV cables (+busbar) S Serial (RS232) Signal cable Other/Unknown Liquid or Gas Cable and/or Bus PCI-XYZ XYZ OPCserver PVSS II OPC client The interface to the equipment (e.g. CAN or Profibus interface). [ethernet interfaces are not indicated] The software interface to the equipment (e.g. commercial OPC server) The software interface at the client side (e.g. OPC client in PVSSII) This depicts a task on a PC, each box does not necessarily correspond to a single PC ISEG 1 This depicts equipment to be controlled. This indicates the number of units (usually crates) This depicts the communication media or type of cable (see table) C 3 This indicates the number of busses or cables Alice Control Room (ACR) Counting Rooms in PX25 (CR1 – CR4) and Plug Cavern, outside L3 magnet Cavern, inside L3 magnet Areas at ALICE Detector HV This depicts the cable from the equipment to the hardware (see table) 3 This indicates the number of cables or channels This depicts the hardware connected Explanation of the detector drawings, field and process layer

André Augustinus 10 March 2003DCS Workshop 8 Final remarks  The information presented today should be reflected in your URD’s  Please send me a copy of your slides