André Augustinus 16 June 2003 DCS Workshop Detector DCS status Overview and news

DCS Workshop

André Augustinus16 June 2003

Detector DCS status

Overview and news

16 June 2003DCS Workshop 2André Augustinus

Overview Status of URD’s Hardware and layout

• Overview of the detectors sub systems• Cabling overview

Operational aspects• Control Hierarchy• Error situations and interlocks

Future• Prototyping in detectors and planning• Plans in central team

Other news Detector presentations


Acknowledgementsand apologies

Thanks to all detector groups that provided me with input for this overview

Apologies for the very short notice








User Requirements Status of the URDs and other sources of information

URD

ITS-pixel Recent URD; regular information exchange

ITS-drift Basic URD, no recent update

ITS-strip Basic URD, no recent update. No recent news

TPC Regular information exchange

TRD Recent URD; regular information exchange

TOF Some information, lack of written information

HMPID Regular information exchange



URD

PHOS Incomplete URD

PHOS-CPV Basic URD

Muon-Trk Recent URD; regular information exchange

Muon-Trg Regular information exchange

FMD No URD (yet), but information exchange

T0 No URD (yet), some information since last WS

V0 No URD (yet), good contact since last WS



URD

PMD No URD, very limited contact

ZDC No URD, very limited contact

ACORDE Early stage, limited contact

EMC Early stage, regular contact

Infrastructure Basic URD, central team








Overview ofdetector sub-systems

Will try to go quickly, concentrate on things that might need clarification

Will use overview drawings as last meeting Included all drawings for reference

AndréAugustinus

Cavern

Inside magnet

Counting room

10DCS Workshop 16 June 2003Detector

CAEN

CAEN OPCserver

PVSS II PVSS II

Detector

Wiener

PCI-CANWiener OPCserver

Ethernet

User interface

Database(s)

OPCclient

DIMclient

20

120

1..4

PVSS II

CoolingPlant

PLC

SchneiderOPCserver

1

1

4

High Voltage Low Voltage Detector Cooling

PVSS IIOPC client

PVSS IIOPC client

ITS-pixel

E C

HV LV

E

[FSM?]C

ontro

l roo

m

(AC

R)

Detector

10

PCI-VMEDIMserver

FEE

On-detectorelectronics

VME(wiener?)

2

PCI-VME

Optics


PVSS IIOPC client

C1 or 2

360

Crate Control

DDL

16/06/03

VR board(12 VR each)

240

LV20

JTAG

20?

Number of CAN busses will depend on performance

[to be tested]

AndréAugustinus

Cavern

Inside magnet

Counting room


CAEN

CAEN OPCserver

PVSS II PVSS II

Detector

AREM

DIM or OPCserver

Ethernet

User interface

Database(s)

OPCclient

DIMclient

288520

PVSS II

CoolingPlant

PLC

SchneiderOPCserver

1

6 6


PVSS IIOPC client

PVSS IIOPC client (?)

ITS-drift

E

HV LV

E

[FSM?]C

ontro

l roo

m

(AC

R)

Detector

?

DIMserver

FEE


72*12

10/03/03

E


PVSS IIOPC client

C

VME(wiener?)

2..4

DDL

Optics

VR

?

CAEN can be moved to CR; at the cost of longer HV cables [cost issue]

Where does these twisted pair go?

To VME?

Crate Control

AndréAugustinus

Cavern

Inside magnet

Counting room


CAEN

CAEN OPCserver

PVSS II PVSS II

Detector

CAEN(?)

CAEN OPCserver

Ethernet

User interface

Database(s)

OPCclient

DIMclient

450144

PVSS II

CoolingPlant

PLC

SchneiderOPCserver

11 5


PVSS IIOPC client

PVSS IIOPC client

ITS-strip

E E

HV LV

E

[FSM?]C

ontro

l roo

m

(AC

R)

Detector

?

?DIMserver

FEE



PVSS IIOPC client

C?

?

Crate Control

FEROM(VME? wiener?)

8+

?? OPCserver

PVSS IIOPC client

I/O device(PLC,Wago,ELMB?)

Detector

Temp. monitoring

??

DDL

28/02/03

No commentsso farCan these CAEN be moved to CR?Can these CAEN be moved to CR?

LV: Is Arem-Pro still an option?

AndréAugustinus

Cavern

Inside magnet

Counting room

13DCS Workshop 16 June 2003Chambers

ISEG

PCI-CANISEG OPCserver

PVSS II PVSS II

Chambers

Wiener


Ethernet

User interface

Database(s)

RCU

DIMserver

OPCclient

DIMclient

108288

1..3 1..22 ?

PVSS II

Chambers,detector

ELMB

1..18

~400?

PVSS IIRS232

HVrod

Heinzinger

4?

1

CoolingPlant (ch)

PLC

SchneiderOPCserver

1?

18?

3

22

1

216

High Voltage Low Voltage FEETemp. Monitor Chamber Cooling Very High Voltage

PVSS IIOPC client

PVSS IIOPC client

PCI-CANELMB OPCserver

PVSS IIOPC client

TPC(1)

C C

HV LV

EC E

HV

S

[FSM?]C

ontro

l roo

m

(AC

R)

108?

Chambers,detector

44

DD

L

16/06/03

EthernetSwitch

EthernetSwitch

?

?

E

E

ProfiBus is still a possible alternative

Controls interface under study

AndréAugustinus

Cavern

Inside magnet

Counting room

14DCS Workshop 16 June 2003

Ethernet

HVrod

“box”

?DIMserver (?)

?

12?

4

VHV Curr. Monitor

TPC(2)

CoolingPlant (rods)

PLC

Schneider/SiemensOPCserver

1

VHV rod Cooling

ThermalScreen(s)

PLC

18

Schneider/SiemensOPCserver

1?

Thermal Screen(s)

?DIMserver (?)

?

Laser calibr. syst.

PCI-ProfibusOPCserver (?)

2?

Pulser system

PS Laser

Mirrors,cameras

?

SchneiderOPCserver

Gas system

PLC

ELMBGas

E E E

CP

HVrod

4

CoolingPlant (TS)

Detector

P

Chambers

Gatingpulser

72?

Calibrationpulser

16/06/03

216

URD is being written

AndréAugustinus

Cavern

Inside magnet

Counting room


ISEG

PCI-CANISEG OPCserver

PVSS II PVSS II

Detector

Wiener


Ethernet

User interface

Database(s)

DCS board

DIMserver

OPCclient

DIMclient

18*(12+18)1080

1..10 1..50 1

PVSS II

10

50

540

High Voltage Low Voltage FEE

PVSS IIOPC client

PVSS IIOPC client

EthernetSwitch

540

EthernetSwitch

x

SchneiderOPCserver

Gas system

PLC

ELMBGas

[FSM?]

C C E E

E

EHV LV

TRDC

ontro

l roo

m

(AC

R)

CoolingPlant

PLC

SchneiderOPCserver

1?

Detector Cooling

E

Detector

?

Detector

?

DA

TA 2*540

16/06/03

Distribution Box

x

Network topology still under study

What kind of distribution box is this?

AndréAugustinus

Cavern

Inside magnet

Counting room


CAEN

CAEN OPCserver

PVSS II PVSS II

Detector

CAEN(?)

Ethernet

Database(s)

OPCclient

DIMclient

360?

3600

18

4

?

High Voltage Low Voltage

PVSS IIOPC client

User interface

PVSS II

SchneiderOPCserver

Gas system

PLC

ELMBGas

E

CP

E E

HV

LV

TOFC

ontro

l roo

m

(AC

R)

[FSM?]

distribution180

HV 180

CAEN OPCserver

PVSS IIOPC client

DC-DC

LV

360

DIMserver

FEE

DRM

CoolingPlant

PLC

SchneiderOPCserver

1?

Detector Cooling

?

E

Detector

?

Detector

?

E

72?


PVSS IIOPC client

C

VME(wiener?)

Crate Control

?

?

DDL

28/02/03

No realcomments so far

TOF presentationin a moment

AndréAugustinus

Cavern

Inside magnet

Counting room


CAEN

CAEN OPCserver

PVSS II PVSS II

Detector

Wiener


Ethernet

Database(s)

LiquidCirculation

OPCclient

DIMclient

12649

?


70

1 17

High Voltage Low Voltage Liquid Circulation Temp. Monitor

PVSS IIOPC client

PVSS IIOPC client

?? OPCserver

PVSS IIOPC client

SiemensOPCserver

PLC1

?

User interface

PVSS II

SchneiderOPCserver

Gas system

PLC

ELMBGas

E

CP

EE C

HV LV

HMPIDC

ontro

l roo

m

(AC

R)

[FSM?]


?

CoolingPlant

PLC

SchneiderOPCserver

1?

Detector Cooling

E

Detector

?

Detector

?

Detector

?

10/03/03

VME+NIM


?

1+1

Crate Control

PVSS IIOPC client

C

?

Can these CAEN be moved to CR?

(were originally projected in CR)

AndréAugustinus

Cavern

Inside magnet

Counting room


CAEN(?)

CAEN OPCserver

PVSS II PVSS II

Detector

Wiener(?)


Ethernet

Database(s)

OPCclient

DIMclient

??

?


?

? ?

High Voltage Low Voltage Temp. Monitor

PVSS IIOPC client

PVSS IIOPC client

?? OPCserver

PVSS IIOPC client

User interface

PVSS II

E C

HV LV

PHOSC

ontro

l roo

m

(AC

R)

[FSM?]


?

CoolingPlant

PLC(?)

OPC/DIMserver (?)

?

Detector Cooling

?

E

Detector

?

RCU

PCI-ProfibusDIMserver

?

10-20

FEE

E

DD

L

28/02/03

?

Can these CAEN be moved to CR?

Following activities in TPC

AndréAugustinus

Cavern

Inside magnet

Counting room


CAEN

CAEN OPCserver

PVSS II PVSS II

Detector

Wiener


Ethernet

Database(s)

OPCclient

DIMclient

4016?

?


?

1 5?

High Voltage Low Voltage Temp. Monitor

PVSS IIOPC client

PVSS IIOPC client

?? OPCserver

PVSS IIOPC client

User interface

PVSS II

SchneiderOPCserver

Gas system

PLC

ELMBGas

E

CP

E C

HV LV

PHOS-CPVC

ontro

l roo

m

(AC

R)

[FSM?]


?

Detector

?

28/02/03

?

Can this CAEN be moved to CR?

AndréAugustinus

Cavern

Counting room


CAEN

PVSS II PVSS II

Detector

Wiener


Ethernet

Database(s)

OPCclient

DIMclient

328

?

?

Detector

?

28

High Voltage Low Voltage Environment monitor

PVSS IIOPC client

PVSS IIOPC client

?? OPCserver

PVSS IIOPC client

User interface

PVSS II

SchneiderOPCserver

Gas system

PLC

ELMBGas

E

CP

E C

HV

LV

Muon-TrkC

ontro

l roo

m

(AC

R)

[FSM?]


?


PVSS IIOPC client

C

VME(wiener)

1

Crate Control

1

Geometrymonitor

DIMserver (?)

? ?

Geometry

Air/Watercooling

PLC(?)

OPC/DIMServer (?)

?

Detector Cooling

E

Detector

?

Detector

?

16/06/03

?

PCI-CAN

CAEN OPC

Switch

192

HV

C

?1

140

Crocus(on-detector crates)

DD

L20

repeater3

C48

Purpose build HV switch.Need a closer look!

AndréAugustinus

Cavern

Counting room


CAEN

CAEN OPCserver

PVSS II PVSS II

Detector

Wiener


Ethernet

Database(s)

OPCclient

DIMclient

16100

?

Detector

?

2 2

High Voltage Low Voltage Environment monitor

PVSS IIOPC client

PVSS IIOPC client

?? OPCserver

PVSS IIOPC client

User interface

PVSS II

SchneiderOPCserver

Gas system

PLC

ELMBGas

E

CP

E C

HV LV

Muon-TrgC

ontro

l roo

m

(AC

R)

[FSM?]


?

Crate Control

Efficiencysystem

Detector

?


PVSS IIOPC client

C

VME(wiener)

17

?

10/03/03

Can be moved to CR if really needed

AndréAugustinus

Cavern

Inside magnet

Counting room


CAEN ?

PVSS II PVSS II

Pre-amps

CAEN ?

Ethernet

Database(s)

OPCclient

DIMclient

14070

1 1


User interface

PVSS II

HV

LV

FMDC

ontro

l roo

m

(AC

R)

[FSM?]

Crate Control

CAEN OPCserver

PVSS IIOPC client

CAEN OPCserver

PVSS IIOPC client

FEE

Digitizers

10

Air cooling

?

Detector Cooling

Detector

?


PVSS IIOPC client

C

VME(wiener?)

?

10/03/03

10

FMD-RCUPCI? VME?

E E

PCI-ProfibusDIMserver

?E

20lvl0

E?

300?

DD

L

TTC

2

Following activities in TPC

?

Can this CAEN be moved to CR?

AndréAugustinus

Cavern

Inside magnet

Counting room


Detector(PMT)

CAEN(?)

PVSS II PVSS II

Detector(shoe box)

?

Ethernet

Database(s)

OPCclient

DIMclient

?24

? ?


User interface

PVSS II

HV LV

T0C

ontro

l roo

m

(AC

R)

[FSM?]


PVSS IIOPC client

Crate Control

??

PVSS II?

??

PVSS II?

DIMserver

FEE


?

Laser system

?

Laser calibr. syst.

Detector

?

C

VME(wiener?)

?

?

10/03/03

Can be shared with V0

Following activities in TOF

AndréAugustinus

Cavern

Inside magnet

Counting room


CAEN

PVSS II PVSS II

Ethernet

Database(s)

OPCclient

DIMclient

144+12

1

High Voltage

User interface

PVSS II

HV

V0C

ontro

l roo

m

(AC

R)

[FSM?]10/03/03

Crate Control

DIMserver

FEE

?


PVSS IIOPC client

C

VME(wiener?)

4?

?

CAEN OPCserver

PVSS IIOPC client

E

PMT

Opticalfibers

Front-Endelectronics

Maybe shared with T0

AndréAugustinus

Cavern

Inside magnet

Counting room


?

PVSS II PVSS II

Detector

?

Ethernet

Database(s)

OPCclient

DIMclient

5252

? ?


User interface

PVSS II

HV LV

PMDC

ontro

l roo

m

(AC

R)

[FSM?]

Crate Control

??

PVSS II?

??

PVSS II?


52

Temp. Monitor

?? OPCserver

PVSS IIOPC client


?

SchneiderOPCserver

Gas system

PLC

ELMBGas

E

CP

CoolingPlant

PLC

?

?

Detector Cooling

E

Detector

?

Detector

?


PVSS IIOPC client

C

VME(wiener?)

?

?

28/02/03

No commentsso far

AndréAugustinus

Cavern

Counting room


?

PVSS II PVSS II

Ethernet

Database(s)

OPCclient

DIMclient

50

?

High Voltage

User interface

PVSS II

HV

ZDCC

ontro

l roo

m

(AC

R)

[FSM?]

Crate Control

??

PVSS II?


PVSS IIOPC client

C

VME(wiener?)

?

?

16/06/03

No commentsso far

AndréAugustinus

Cavern

Counting room


?

PVSS II PVSS II

Detector

?

Ethernet

Database(s)

OPCclient

DIMclient

?128?

? ?


User interface

PVSS II

HV LV

Cosmics(ACORDE)

Con

trol r

oom

(A

CR

)[FSM?]

Crate Control

??

PVSS II?

??

PVSS II?


PVSS IIOPC client

C

VME(wiener?)

?

?

28/02/03

No commentsso far


Summary For many detectors we have more or less

detailed information For a few detectors we are lacking even very

basic information


CablingBackground: End of the year the RB26 doors will be closed Need to know what cables will go through

• TPC, TRD, TOF Started an effort to capture cabling

information, based on what we know• Inspired by pixel cabling overview last meeting


Cabling I will present examples for a few sub-systems

Question: Do we think this is a useful activity and should

be continued?


PC

ISEG ECH238

3

EHQ F 020p18

MagnetDoor

UXRack xxx

Detector

C 1..3

? m

Device

TPC; high voltage 10/03/2003

? m

1..3 CANBus[16 lines per cable, CERN standard. Scem xxx ]

18

E

ControlPC

1 Ethernet

? m

18 cables

CR xRack xxx

Should be some patch panel somewhere…


PC

Wiener PL500F

3

2..7V / 115A?

MagnetDoor

UXRack xxx

Detector

C 1..22

? m

Device

TPC; low voltage 10/03/2003

? m

1..22 CANBus[under discussion ]

72

E

ControlPC

1 Ethernet

? m

CR xRack xxx

Should be some patch panel somewhere…

[under discussion ]

72?

72 bus bars

72(?) sense wires


PC

Wiener PL500

4

5V / 50A20

MagnetDoor

UXRack xxx

30 m

TPCend

Detector

C 1..4

? m

Device

VR

board

120

60

6 x

ITS-pixel; low voltage 10/03/2003

Internalpatch panel

6 m 3 m 1 m

1..4 CANBus

240 sense wires

180 T signal cables

[s = 6 mm2]

[s = 1 mm2]

[s = 25 mm2] [shared withHigh Voltage andtemperature monitoring]

20

E

ControlPC

1 Ethernet

? m

60 MCM extenders20 cables 120 cables (Vdd, gnd)

120 cables (Vmcm, gnd)

CR xRack xxx

Vdd, gnd, 2 senseVmcm, gnd, 2 sense3 T_mcm

120240

180

180 T signal cables?

180

20

20

JTAG

20 JTAG control cables?


Cabling Can this be useful? A repository of (DCS related) cabling

• Can be used as input to the installation team Needs input from the detectors ‘Later’ detectors can be inspired by ‘earlier’

detectors


CablingSpecial case: Ethernet at detector level Some detectors envisage Ethernet on/in the

detector: • TPC, TRD, TOF, PHOS, FMD, T0• More detail in Peter’s talk

Technical issues• Must work in magnetic field and radiation• What will be the best topology


Cabling “Managerial” issues

• How to interface with rest of network• Who is responsible for what

Many efforts going on in this field to tackle technical aspects• When things become more clear we should get IT

division involved• choice of equipment, managerial aspects








Controls HierarchyECS

DCS DAQ Trig

ITS TPC TRD …

SPD SDD SSD HV LV Cool

RB24 RB26

Sec1Sec2

Sec3

“Node”

=“Control Unit”

in FSM


Controls hierarchy Reflects the operation of your detector Each “node” can be operated independently

• Should define a “node” for each entity that has to be the ability to be operated independently (e.g. in the case of a calibration run)

A “node” contains the logic of interaction between its children



DCS DAQ Trig

ITS TPC TRD …


RB24 RB26

Sec1Sec2

Sec3

Will there be a reason to operate the ITS as one single entity?

and/orIs there a ‘strong’ interaction between the ITS detectors?

thenthis ITS node should be defined


Controls hierarchy The lowest node reflects the smallest part of

your detector that logically could be operated independently• Note that we talk operation here; this is not the

smallest part of the detector you can switch off (e.g. in case of a problem); that will always be possible on the channel level !



DCS DAQ Trig

ITS TPC TRD …


RB24 RB26

Sec1Sec2

Sec3

Does it make sense to operate a single TPC sector; or does one only operate one half of the TPC at the same time?


Controls hierarchy One should try to match the ‘smallest

operable part’ of your detector for all sub systems, especially if they have to be operated simultanously

Chamber

HV1a HV1b

LV1

If all HV has to be on to operate the chamber; or if LV can only be switched on if both HV is on, it makes no sense to define both HV as individual nodesBetter to define all HV as one node


Controls hierarchy For operation it would be very convenient to

have the same subdivision for DCS and DAQ• So that one can ‘partition’ part of your detector

and run in stand alone (e.g. for calibration); both DCS and DAQ

• It is not logical to be able to operate one half of your detector while in DAQ you can only read out the whole detector

• Or, if the DAQ can run one sector in stand-alone while the DCS is only able to operate half of the detector


Controls hierarchy You can define as many intermediate levels in

your hierarchy as you need For each node you will have to define

• the states it can have,• the commands it can accept, • the logical behaviour it should have

Giacinto will talk in more detail on Finite State Machines


Error situationsand Interlocks

Various levels of protection of your equipment Inside your equipment (hardware)

• E.g. a current exceeding a given value will result in switching off that channel (trip)

In the DCS system (software)

Program an action on any set of readings (within a sub system or across sub systems)• E.g. if HV on one part of a chamber goes off, switch off the

rest of the chamber• E.g. if a rise of temperature is measured, switch off LV



Interlock (hardware)

Can be inside or across sub systems, or even from outside the detector• A trip on one channel, force also other channels

to trip• If the gas system fails, switch off the HV• If the cooling system fails, switch of the LV• An alarm system can switch off all your systems



Software actions give high flexibility in their implementation (delay’s, special ramp down, can act on the channel level)• But: are intrinsically less reliable

Hardware action are less flexible and usually act in a more ‘crude’ way• But: are highly reliable

Difficult to get good things of both…



This means work for you… For each event analyse what is the impact on

your detector and equipment Define what action needs to be taken and

evaluate the risk if the action is not taken This gives an indication how the action could

be implemented (hardware or software)








Prototyping HV and LV

• Less than half of the detectors have ‘final hardware’ and started prototyping

• only few with Framework/PVSS Gas and Cooling

• Outsourced to CERN groups (except PHOS cooling)

• Various stages of progress• Some in production, others in design


Prototyping Other systems

• Various stages of progress• Concentrating mainly on functionality rather than

controls aspects• To be followed case by case

As always:• Let us know what you are doing, and any remarks

you have !


Detector (DCS) planning Some information on beam tests etc. Pre-installation information in central planning Very little information on DCS needs at the

various stages Please let us know your needs in controls for

your beam tests, lab tests, pre-installation etc.• So that we can plan our work and your support


Central team Good news: We finally got (temporary…) lab space

• We will set up all ‘common solutions’• These set-up’s can be used as demonstration and

for debugging purposes Involved in TPC tests Major ‘proof of concept’ during pre-installation

of TPC in 2004


More news An effort started to redesign the Framework

• Simplify the internals (easier maintenance)• Simplify for the users (panels etc.)• Further integration of FSM

Ready by the end of the year• Coincides with a new version of PVSS (version 3)

If you use the framework, it is now to let us know your comments and remarks !!!


More news Current framework can still be used

• Your own created panels will need to be adapted to the new Framework

For FSM, if you can, wait for new Framework• It’s configuration and use will be simplified







Documents

André Augustinus 16 June 2003 DCS Workshop Detector DCS status Overview and news