1 / 10

LHC Gas Control System Applications

This presentation outlines the Gas Control System (GCS) developed for handling gas management in experimental setups. It covers the GCS’s scope, which includes 23 standard gas systems, common devices like valves and flow meters, and a modular architecture comprising mixers, pumps, and analyzers. The objectives focus on creating homogenous end-user applications and turnkey control setups. The strategic use of industrial technologies and the UNICOS framework are discussed, as well as phases from requirements capture to application validation and operational support. Pros and cons highlight the benefits of open architecture versus the challenges of hardware configuration and software dependencies.

damisi
Télécharger la présentation

LHC Gas Control System Applications

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. LHC Gas Control System Applications G.Thomas, J.Ortola Vidal, J.Rochez EN-ICE Workshop23 April 2009

  2. Outline • Scope • Objectives • Strategy/Principles • Support and Maintenance • Pros & Cons

  3. GCS scope • 4 Experiments ~23 std gas systems to build • Commonalities • Standard devices • Valves, flow meters, mass flow controllers, etc… • Limited number of exotic devices (Webmas, ELMB ) • Modular architecture • Mixer, Distribution, Pump, Analysis, Purifier, etc… • Diversity • Optional modules • Options in modules

  4. GCS diversity

  5. GCS objectives • -> Provide homogeneous end-user applications • What we handle • Build turnkey control application • Supervision layer • Synoptic views and navigation, alarm handling, recipes, etc… • Process Control layer • I/O, steppers, interlock, common logic, etc… • Define and setup the control infrastructure for each Experiment • What we do not handle • Setup and configuration of hardware equipments and instrumentation

  6. GCS strategy/principles • Strategy • Gas systems’ architecture based on a generic model • Use industrial technologies • SCADA, PLC, fieldbuses • Use of UNICOS FW and code generator tools • Principles • Model-oriented design for both • Supervision & Process control layers • Tools • To produce automatically the PVSS and PLC code of any GCS instance

  7. Dev. Phases/interactions with customer EN-ICE • Capture of the functional requirements of the systems for the process & supervision layers • Agreement on the needs between provider & customer Provider (EN-ICE) Gas Expert (PH-DT1) EN-ICE Validation of the application in the lab • Design • Code implementation • Tests (logic, IO signals, etc…) • Packaging URD Release EN-ICE Installation of the new application in-situ • Loading of PLC application • Setup of PVSS application • Load of pre-defined parameters (recipes) • Pass the system to Gas experts Deployment PH-DT1 Tests of application before production • Hardware connection tests • Functional tests (critical interlocks, etc…) • Final tuning of thresholds & set points • Training of Gas team members Commissioning

  8. GCS operational support • Type of support cases • Bad configuration parameters (archive, deadband, stop of plc, etc…) • Exp.Infrastructure problems (remote access, dip setup, etc…) • Support level • First line (PH-DT1 gas piquet) • Second line support based on best effort (EN-ICE) • Tools • Remedy to handle bugs or requests • Savannah for bug & patch tracking

  9. GCS maintenance and upgrades • Type of upgrades • New version of software/firmware for PVSS (UNICOS FW) or PLC (baseline) • New system/modules to integrate • Bug fixes • Methodology • Any new request is first analyzed in URD before implemented • Validation done in lab • Tools • Configuration source code management tools (CVS, savannah)

  10. GCS Pros and Cons • Pros • Based on existing software control libraries (UNICOS FW). • Keep source code repository always up-to-date. • Keep homogeneity across systems. • Open architecture –extensibility/flexibility. • Autonomy of users during commissioning and operation. • Cons • Any modification requires an upgrade in various places. • No control on equipment setup and configuration. • Synchronization between PH-DT1 and EN-ICE for tests. • Software version dependencies.

More Related