detector control system at the gif++ a. polini, m. romano (aida+infn bologna) on behalf of wp 8.5.3...

13
Detector Control System at the GIF++ A. Polini, M. Romano (AIDA+INFN Bologna) on behalf of WP 8.5.3 group Gif++ User Meeting 11/07/2014 Outline Status and latest developments Next Steps Gif++ CERN July 11th 2014 A. Polini, M. Romano 1

Upload: alvin-cross

Post on 17-Dec-2015

214 views

Category:

Documents


0 download

TRANSCRIPT

A. Polini, M. Romano 1

Detector Control System at the GIF++A. Polini, M. Romano (AIDA+INFN Bologna)

on behalf of WP 8.5.3 groupGif++ User Meeting 11/07/2014

Outline• Status and latest developments• Next Steps

Gif++ CERN July 11th 2014

A. Polini, M. Romano 2

Hardware Status (July 2014)• Material installed

– 1 CAEN mainframe (SY-1527 + PS A-1531 A-1532)– 1 (non EASY) HV board A-1526P (6ch 15 kV+)– 1 Branch Controller A-1676– 2 PC (courtesy of ATLAS DCS, spare of past generation)

DELL PowerEdge 1950

• Also installed (on loan from ATLAS Muons)– EASY 3000 Crate– 1 ADC A-3801 (128ch)

• Recently added: (from CMS Muons group)– 1 CAEN mainframe (SY-1527)– 1 (non EASY) HV board

A-1526N (6ch 15 kV+)

B. 190

GIF

Gif++ CERN July 11th 2014

A. Polini, M. Romano 3

Test Location in B190 (old GIF) (i)

• 2 CAEN Mainframes + 2 HV A3516 (P & N) boards, 6ch each, 12 KV• 1 branch controller A1676 + EASY crate + 1 ADC A3801 (128 ch) +

2 patch-panels (4x32 pair connectors 16x8 pairs)• All up and working

System being developed/used in conjunction with existing GIF

CMS GIF Setup

HV +

HV -New from

CMS MuonNew from

CMS Muon

128 ch ADCENV+ Detmonitoring

Gif++ CERN July 11th 2014

A. Polini, M. Romano 4

Test Location in B190 (old GIF) (ii)

• 2 computers (Dell PE-1950) installed in CMF (NSC ATLAS_GIF_DCS)• Hostnames: pcgifdcs01, pcgifdcs02• Windows 2008 Server R.2• PVSS 3.8 and WinCC-OA 3.11• More computers to come in September (when ATLAS DCS PCs are refurbished)

Gif++ CERN July 11th 2014

A. Polini, M. Romano 5

Overall Status and Latest Developments

• First steps in order to define protocols and intercommunication with GCS (Gilles/Roberto)

• First steps to define and allocate servive for Central Oracle data archiving (M. Gonzales, Martin J.)

• Common effort (NTUA), project for common developments within RD51 and AIDA.

• Expressed interest in GIF++ use and development from CMS Muon group. First meeting started.

• Dedicated DCS WinCC software being developed.• New DCS Software developer/contact Marino Romano

(Aida+INFN Bologna).

Gif++ CERN July 11th 2014

A. Polini, M. Romano 6

Software Status (i)• Collecting user requests and building up template

for the GIF++ project.• Running WinCC project on pcgifdcs02• OPC connection to the two CAEN Mainframes• Possibility of Monitoring/Setting HV/ADC boards.• User Interface and tools being developed using

RD51 DCS project as skeleton• Added FSM based features• Made some tweak to RD51 panels

– Removed the dependencies to the old naming conventions

Gif++ CERN July 11th 2014

A. Polini, M. Romano 7

Software Status (ii)• Using RD51 DCS project as skeleton• Added FSM basic features• Made some tweak to RD51 panels

– Removed the dependencies to the old naming conventions

• Group handling, settings and build FSM buttons should be used only by experts– Been working mainly on “Group handling”– More software details in backup slides (work in progress)Gif++ CERN July 11th 2014

A. Polini, M. Romano 8

Plans and OutlookStatus:• System in Building 190 getting close to be ready for preliminary

operation• Collaboration with RD-51, NTUA, CMS group established.• Options for synergies (existing GIF tests)• Software development ongoing: basic functionalities to control

the HW already available. System can be used to test parts of the final system (ENV sensors etc).

Next Steps:• Proceed in the development, define the operation constraints,

communication protocols and specifications following users’ requests

Schedule:• The whole system can be moved anytime to the final location

following the GIF++ detector and infrastructure schedule

Gif++ CERN July 11th 2014

A. Polini, M. Romano 9

Backup

Gif++ CERN July 11th 2014

A. Polini, M. Romano 10

selection.pnl (accessed via “Group Handling”)

• Current status:• Now an HV channel can be

assigned to multiple groups (the list of “parent” groups is saved in an user defined DPE in the fwCaenChannel DPT)

• It’s possible to remove a channel from the selected channels by right-clicking on it

• Added filter masks (device type, locations, dp name and alias)

• Made the panel smart enough to be able to assign both HV and ADC channels to the various groups

• Long-term TODO:• Revamp the authentication

protocol

Gif++ CERN July 11th 2014

A. Polini, M. Romano 11

generateFSM2.pnl (accessed via “Build FSM”)

• Still not working as intended– Generate FSM button: creates an FSM

(named as the string in the “FSM name” field)

• Loops over all groups• Creates a LU for each not-empty group• Create a DU for each HV in the group

– Remove FSM button: deletes the FSM named as the string in the “FSM name” field

– Open node button: opens the FSM UI for the selected FSM (just like the Open FSM button in the main panel)

Gif++ CERN July 11th 2014

A. Polini, M. Romano 12

FSM UI (work in progress)

Gif++ CERN July 11th 2014

A. Polini, M. Romano 13

FSM UI• Very basic setup:• The top node contains 4 logical units (1 for each not empty group) of type

HVOperation• Each HVOperation node contains the DUs (HV channels) assigned to the

corresponding group• Each HV channel can be operated both individually or in bulk (configure,

switch on/off, recover, etc.)• The table on the right shows the current monitored values as well as the

settings. Trends (with history, once we have a DB) can be displayed by right clicking on the cells

• Intermediate layers are expected to be inserted between the Top node of the group and the HVOperation nodes. Something like

Top Node

Group X

HV Operation

Enviromnent

etc…Gif++ CERN July 11th 2014