System Integration Tool Basic Introduction

„System Integration Tool “2Content I.Nomenclature I.Nomenclature II.Introduction II.Introduction III.Implementation III.Implementation IV.Integration IV.Integration V.Control V.Control

„System Integration Tool “3 General remarks I added a number of additional slides that I haven‘t shown in the talk. This is due to the fact that some people might have missed it, so they basically add some additional points that I hope to have mentioned during the talk Hidden slides have not been shown during the talk.

„System Integration Tool “4 I.Nomenclature

„System Integration Tool “5 Nomenclature Functional: –Devices are named by their type and channel number: IsegHV01.Channel7„IsegHV01.Channel7“ Geographical: –Devices are named by their job within the dectector: L1_B01_S1_A/7_M1A_HV„L1_B01_S1_A/7_M1A_HV“ I. Nomenclature

„System Integration Tool “6 Remarks on last slide Detector geography follows official naming sceme defined in ATL-IP-ES-0007

„System Integration Tool “7 II.Introduction

„System Integration Tool “8 Reminder So what do we need in order to operate a detector Module? –HV –VDD –VDDA –More??? See next slide… II. Introduction

„System Integration Tool “9 Module operation BBM DCS-PCs CAN-Open protocol TCP/IP Environm. SC-OLink BOC Optoboard Door Cover T Data VPin VISet Regulator Station Wiener Module LV-PP4 T HVVDDVDDA Iseg HV-PP4 T Interlock System Distance from interaction point Sensors CAN-Open protocol VVDC BBIM II. Introduction

„System Integration Tool “10 Remarks on last slide The picture shows only a small part of the DCS and Detector hardware, as only one Module and one Optoboard are displayed.

„System Integration Tool “11 Chaos So now we have all this for a SINGLE Module! What a pain will it be for 1744 of them!?! How are we going to handle this? II. Introduction

Detector control stations Finite state machine (FSM) Front end integration tool (FIT) System integration tool (SIT) DAQ- DCS- communication (DDC) FIT: Functional part SIT: Geographical part Temperature monitoring High voltage Low voltage Layers Detector modules Detector modules Detector modules Detector modules Detector modules Detector modules Detector modules Detector modules Detector modules Detector modules Detector modules Detector modules Detector modules Detector modules Detector modules Detector modules Detector modules Detector modules Detector modules Detector modules Detector modules Detector modules Detector modules Detector modules Detector modules Detector Modules Data Acquisition (DAQ) Global control station Conditions data base Configuration data base Layers Bi-Staves or Bi-Sectors mapping set values store data JCOP tool Graphical user interface Data bases II. Introduction

„System Integration Tool “13 Remarks on last slide Not shown: –the Cond. DB relies on the SIT as well –Internal structure of the different DCS- software parts (see next slides)

„System Integration Tool “14 What the SIT does SITSystem Integration Tool Mapping between Detector parts and power supply channels, temperature sensors etc. Abstraction layer used by FSM and DDC Responsible for archiving and smoothing of values II. Introduction

„System Integration Tool “15 Overview of the DCS-Software System integration tool (SIT) Front end integration tool (FIT) Temperature monitoring Finite state machine (FSM) DAQ-DCS-communication (DDC) High voltage Low voltage Detector modules Detector modules Detector modules Detector modules Detector modules Detector modules Detector modules Detector modules Detector modules Detector modules Detector modules Detector modules Detector modules Detector modules Detector modules Detector modules Detector modules Detector modules Detector modules Detector modules Detector modules Detector modules Detector modules Detector modules Detector modules Detector Modules Bi-staves or discs Bi-staves or discs Bi-staves or discs Bi-staves or discs Bi-staves or discs Bi-staves or discs Bi-staves or discs Bi-staves or discs Bi-staves or discs Bi-staves or discs Bi-Staves or Bi-Sectors Layers PVSS based DCS Data base interface Functional part Geographical part II. Introduction

„System Integration Tool “16 Remarks on last slide DDC, FSM and DB all use the SIT as an interface layer to the different FITs The „data base interface“ doesn‘t exist in the form of an inclusive package. It is rather a set of various software tools.

„System Integration Tool “17 Sorry, what was the goal again? You… –don‘t want to know, which Iseg-channel might be connected to a certain module! –are not interested in the naming sceme of a regulator board! –don‘t even care what todays connectivity is! But… –you want to operate the HV, LV, Optical Link –you want to know your Modules‘ temperatures –you want to let the FSM do some work for you So let the software handle the details for you! –System Integration Tool (1. Step) –FSM(2. Step) II. Introduction

„System Integration Tool “18 III.Implementation

„System Integration Tool “19 How does it work? (1) PVSS uses so called „Data Points“ (DPs). Each DP has a unique name. If you switch on an Iseg-channel, you manipulate an element of one DP belonging to this Iseg-channel. What if the channel could have a second name, reflecting it‘s geographical assignment?What if the channel could have a second name, reflecting it‘s geographical assignment? III. Implementation

„System Integration Tool “20 Remarks on last slide DPs are allocated space on the hard drive, not in the main memory! –Persistency (that‘s good) –Slower than normal variables (that‘s bad) –Can be browsed like a folder tree Nodes of DPs are called „Data Point Elements“ (DPEs). Can be: –Structure –Int –Float –String –Bool –…

„System Integration Tool “21 How does it work? (2) PVSS DPs can have a second name, called „Alias“. Each alias has to be unique. With the alias, you can manipulate a DP in the same way, as if you would know it‘s name: IsegHV01.Channel7 L1_B01_S1_A/7_M1A_HV PowerTRUE VSet150 V IMon0.7 mA III. Implementation

„System Integration Tool “22 Remarks on last slide Aliases are very useful for our purposes: –Higher level panels and software parts can just use them instead of the DP name –The use of aliases is very fast

„System Integration Tool “23 How does it work? (3) Ok, but how does the system know, which alias to assign to which DP? –This can be done by hand for each DP… –Or with an XML-file containing the „mapping“ Once the aliases have been set, they can be used by everyone –DDC and FSM rely on them to be there! III. Implementation

„System Integration Tool “24 Structure of the SIT Two main parts Integration: –Defines connections between Detector parts and off- detector hardware –Facilitates automatic setting of archive and smoothing values for each connected device Control: –Uses the geographical Detector structure in order to control (switch on / off, change voltages etc.) –Provides a basic graphical representation of the Detector III. Implementation

„System Integration Tool “25 IV.Integration

„System Integration Tool “26 The main window (1) 2 buttons: –„Integration“ to open the integration navi panel –„Graphical Control“ to open the control navi panel IV. Integration

„System Integration Tool “27 Integration Navigation Just navigate to the PCC (Parallel Cooling Circuit: can be either a Bi-Stave or Bi-Sector) of your choice… IV. Integration

„System Integration Tool “28 Detector Integration IV. Integration

„System Integration Tool “29 Remarks on last slide You might have noticed the other 2 tabs: –Both are only for experts –Both currently don‘t work (as we are using a distributed system, ask me if you‘re interested in the details) –„Mapping“ would allow to assign aliases by hand –„Set Values“ would allow to set voltages etc…

„System Integration Tool “30 Example of an XML-file ATLPIX_3:Y1106S1_BBIM02A.Ibox0.Temp1 D1C_B01_S2_TOpto IV. Integration

„System Integration Tool “31 V.Control

„System Integration Tool “32 The main window (2) 2 buttons: –„Integration“ to open the integration navi panel –„Graphical Control“ to open the control navi panel V. Control

„System Integration Tool “33 Graphical Detector Overview V. Control

„System Integration Tool “34 Remarks on last slide Only connected Detector parts are activated (not greyed out) Left-click on an active part to navigate further into it Right-click on an active part to do the same but this time opening an independent panel (which will not close when it‘s mother panel is closed)

„System Integration Tool “35 User Interface V. Control

„System Integration Tool “36 Half Stave / Sector overview panel Displays all DCS-relevant data of one ROU (Read-Out Unit: Half Stave / Sector) Shows only monitoring values Allows to change values by using reference panels from the FITs (right-click on a voltage to open them) Trending can be accessed by right-clicking on the ROU name („L1_B01_S1_A/6“ in the picture) V. Control

„System Integration Tool “37 Remarks on last slide Only connected channels will be displayed (so if the panel is quite empty, check the mapping) Available readings

„System Integration Tool “38 FIT reference panels Allow setting of values, switching on/off of channels Are the same as in the FITs V. Control

„System Integration Tool “39 Module (reference) panel Displays all DCS-relevant data of one Detector Module Shows only monitoring values Allows to change values by using reference panels from the FITs (right-click on a voltage to open them) Is a reference itself, so you’ll see it at least 6 times on each ROU Trending can be accessed by right-clicking on the Module name („M3A“ in the picture) V. Control

„System Integration Tool “40 Trending V. Control

„System Integration Tool “41 VI.Backup

„System Integration Tool “42 What are all those SITs about (or a short history of the SIT) SIT-Modules –Able to control and integrate a set of single modules SIT-Common –Used for graphical representations on various system test and test beam setups SIT-Environment –Used for additional NTCs or humidity sensors that can‘t be assigned to one specific part of the detector SIT-Detector –Provides a 1 to 1 representation of the real pixel detector, thus being able to handle all 1744 modules at the same time –If we refer to the SIT, we always talk about this one VI. Backup

„System Integration Tool “43 A comparison of FITs, SIT and FSM FITs: Are responsible for one type of device only (like HV power supplies from Iseg) Do not know anything about the detector Are not aware of other FITs (so the Iseg does not know the Wiener) COULDThe detector COULD be operated by FITs only (but then we would need 100s of shifters knowing all details…) SIT: Knows the mapping between all connected devices Knows the detector (geography) Provides an interface for the data base, DDC and the FSM CANThe detector CAN be operated by SIT only (still we would need dozens of expert shifters…) VI. Backup FSM: Doesn‘t know much anything about the mapping Knows the detector (details)(for you) Allows „One-Button“- operation of the whole detector WILLThe detector WILL be operated by FSM only (one relaxed shifter without any necesarry expert knowledge…;-)