system integration tool

System Integration ToolBasic Introduction

„System Integration Tool “ 2

ContentContent

• I.I. NomenclatureNomenclature

• II.II. IntroductionIntroduction

• III.III. ImplementationImplementation

• IV.IV. IntegrationIntegration

• V.V. ControlControl

„System Integration Tool “ 5

Nomenclature

• Functional:– Devices are named by their type and channel

number:• „IsegHV01.Channel7IsegHV01.Channel7“

• Geographical:– Devices are named by their job within the

dectector:• „L1_B01_S1_A/7_M1A_HVL1_B01_S1_A/7_M1A_HV“

I.I. NomenclatureNomenclature

„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.II. IntroductionIntroduction

„System Integration Tool “ 9

Module operation

BBM

DCS-PCsCAN-Open protocol TCP/IP

Environm.

SC-OLink

BOC

Optoboard

Door

Cover

T

Data

DataVPin VISet

RegulatorStation

Wiener

Module

LV-PP4

T

HV VDD VDDA

Iseg

HV-PP4

T

Interlock

System

Dis

tanc

e fr

om in

tera

ctio

n po

int

Sensors

CAN-Open protocol

VVDC

BBIM

II.II. IntroductionIntroduction

„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.II. IntroductionIntroduction

Detectorcontrolstations

Finitestate

machine(FSM)

Front endintegration

tool (FIT)

System

integration

tool (SIT)

DAQ-DCS-

communication(DDC)

FIT: Functional partFIT: Functional part

SIT: Geographical partSIT: Geographical part

Temperaturemonitoring

High voltage

Low voltage

LayersLayersLayers

Detectormodules

Detectormodules

Detectormodules

Detectormodules

Detectormodules

Detectormodules

Detectormodules

Detectormodules

Detectormodules

Detectormodules

Detectormodules

Detectormodules

Detectormodules

Detectormodules

Detectormodules

Detectormodules

Detectormodules

Detectormodules

Detectormodules

Detectormodules

Detectormodules

Detectormodules

Detectormodules

Detectormodules

Detectormodules

DetectorModules

DataAcquisition

(DAQ)

Global controlstation

Conditionsdata base

Configurationdata base

Layers

Bi-Staves orBi-Sectors

mappingset values

storedata

JCOP tool

Graphical userinterface

Data basesData bases

II.II. IntroductionIntroduction

„System Integration Tool “ 14

What the SIT does

• SSystem IIntegration TTool

• 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.II. IntroductionIntroduction

„System Integration Tool “ 15

Overview of the DCS-Software

System integration tool

(SIT)Front end

integration tool(FIT)

Temperaturemonitoring

Finitestate

machine(FSM)

DAQ-DCS-communication (DDC)

High voltage

Low voltage

Detectormodules

Detectormodules

Detectormodules

Detectormodules

Detectormodules

Detectormodules

Detectormodules

Detectormodules

Detectormodules

Detectormodules

Detectormodules

Detectormodules

Detectormodules

Detectormodules

Detectormodules

Detectormodules

Detectormodules

Detectormodules

Detectormodules

Detectormodules

Detectormodules

Detectormodules

Detectormodules

Detectormodules

Detectormodules

DetectorModules

Bi-staves ordiscs

Bi-staves ordiscs

Bi-staves ordiscs

Bi-staves ordiscs

Bi-staves ordiscs

Bi-staves ordiscs

Bi-staves ordiscs

Bi-staves ordiscs

Bi-staves ordiscs

Bi-staves ordiscs

Bi-Staves orBi-Sectors

LayersLayersLayersLayers

PVSS based DCSPVSS based DCS

Data base interface

Functional p

art

Functional p

art

Geographical p

art

Geographical p

art

II.II. IntroductionIntroduction

„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.II. IntroductionIntroduction

„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 What if the channel could have a second name, reflecting it‘s a second name, reflecting it‘s geographical assignment?geographical assignment?

III.III. ImplementationImplementation

„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

Power TRUE

VSet 150 V

IMon 0.7 mA

III.III. ImplementationImplementation

„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.III. ImplementationImplementation

„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.III. ImplementationImplementation

„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.IV. IntegrationIntegration

„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.IV. IntegrationIntegration

„System Integration Tool “ 28

Detector IntegrationIV.IV. IntegrationIntegration

„System Integration Tool “ 30

Example of an XML-file

ATLPIX_3:Y1106S1_BBIM02A.Ibox0.Temp1

D1C_B01_S2_TOpto

IV.IV. IntegrationIntegration

„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.V. ControlControl

„System Integration Tool “ 33

Graphical Detector OverviewV.V. ControlControl

„System Integration Tool “ 35

User InterfaceUser InterfaceV.V. ControlControl

„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.V. ControlControl

„System Integration Tool “ 38

FIT reference panels

• Allow setting of values, switching on/off of channels

• Are the same as in the FITs

V.V. ControlControl

„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.V. ControlControl

„System Integration Tool “ 40

TrendingV.V. ControlControl