1 / 13

Detector Control System at the GIF++

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. Hardware Status (July 2014). GIF. B. 190. Material installed

rowena
Download Presentation

Detector Control System at the GIF++

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 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 A. Polini, M. Romano

  2. Hardware Status (July 2014) GIF B. 190 Materialinstalled • 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) HVboard A-1526N(6ch 15 kV+) A. Polini, M. Romano

  3. Test Location in B190 (old GIF) (i) HV + CMS GIF Setup 128 ch ADC ENV+ Det monitoring HV - New from CMS Muon New from CMS Muon 2 CAEN Mainframes + 2 HVA3516(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 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) 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 DCSWinCC software being developed. New DCSSoftware developer/contact Marino Romano (Aida+INFN Bologna). 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 developedusing RD51 DCS project as skeleton Added FSM based features Made some tweak to RD51 panels • Removed the dependencies to the old naming conventions A. Polini, M. Romano

  7. Software Status (ii) mainPanel.pnl Using RD51 DCS projectasskeleton AddedFSM 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) A. Polini, M. Romano

  8. Plans and Outlook Status: 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 (ENVsensors 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 A. Polini, M. Romano

  9. Backup 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 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) A. Polini, M. Romano

  12. FSM UI (work in progress) Top Node HV operation Node Channel operation Node 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… A. Polini, M. Romano

More Related