Download presentation
Presentation is loading. Please wait.
Published byCornelius King Modified over 9 years ago
1
ITER – Interlocks Luis Fernandez December 2014 Central Interlock System CIS v0
2
CERN PLC Workshop – ITER IO 4-5 December 2014 Why CIS v0? 2 Objectives Assessment of the methodology Validation of technical solutions Definition of strategy for Operation from Interlock Desk Non-Critical interface with CODAC Timestamp and Archiving
3
CERN PLC Workshop – ITER IO 4-5 December 2014 Slow Interlock Prototype 3 Before the CIS v0 there was the Slow Interlock Prototype, our first test platform.
4
CERN PLC Workshop – ITER IO 4-5 December 2014 CIS prototype (test platform) 4 Two network branches connected All PLC reachable from CIS CIS 1: Full Redundant CIS 2: Full Redundant + RIO 4 PIS configurations: PIS 21: Full redundant + RIO PIS 11: CPU + 2 x CP + RIO PIS 12a: CPU + CP + RIO PIS 12b: CPU + CP Test I/O for measure Response Time Each PLC keeps track of the following times: Execution of safety program CPU execution Communication
5
CERN PLC Workshop – ITER IO 4-5 December 2014 TEST Cases 5 1.Configuration Parameters: Safety program execution cycle Priority Communication load 2.PLC-PLC communications in Safety Program
6
CERN PLC Workshop – ITER IO 4-5 December 2014 TEST Cases 6 1.Configuration Parameters: Safety program execution cycle Priority Communication load 2.PLC-PLC communications in Safety Program 3.Behavior of the Fault-tolerant configuration
7
CERN PLC Workshop – ITER IO 4-5 December 2014 TEST Cases 7 1.Configuration Parameters: Safety program execution cycle Priority Communication load 2.PLC-PLC communications in Safety Program 3.Behavior of the Fault-tolerant configuration 4.Effect of an increasing number of partners in the architecture
8
CERN PLC Workshop – ITER IO 4-5 December 2014 TEST Cases 8 1.Configuration Parameters: Safety program execution cycle Priority Communication load 2.PLC-PLC communications in Safety Program 3.Behavior of the Fault-tolerant configuration 4.Effect of an increasing number of partners in the architecture 5.Complexity in the safety matrix
9
CERN PLC Workshop – ITER IO 4-5 December 2014 TEST Cases 9 1.Configuration Parameters: Safety program execution cycle Priority Communication load 2.PLC-PLC communications in Safety Program 3.Behavior of the Fault-tolerant configuration 4.Effect of an increasing number of partners in the architecture 5.Complexity in the safety matrix 6.Addition of Remote Inputs / Outputs
10
CERN PLC Workshop – ITER IO 4-5 December 2014 Conclusions from test platform 10 [11] 1.Management of complex situation Failures are isolated from the rest of the system; the problems of one partner will not affect the performance of the whole system. 2.No advantage of hardwired connections (from I/O to I/O) compared to network. No advantage in terms of performance, maintainability, cubicle space, integration and scalability. 3.While the CPU can manage the configuration within one cycle interrupt, the response time of the central functions is almost independent from the number of partners and the communication functions. 4.The restoration of the functionality after a master switch over requires 700ms as a minimum, and with four communication instances per PIS (2 F_SEND/2F_RCV) the system can assure restoration times below 1 second. 5.The performance of a central function is below 350ms and local functions based in digital inputs have a performance below 150 ms. 6.The use of analogue inputs can double the time required for a digital input, below 225 ms
11
CERN PLC Workshop – ITER IO 4-5 December 2014 CIS Architecture 11
12
CERN PLC Workshop – ITER IO 4-5 December 2014 CIS v.0 Architecture 12
13
CERN PLC Workshop – ITER IO 4-5 December 2014 ITER magnets 13
14
CERN PLC Workshop – ITER IO 4-5 December 2014 Interlock Function Context 14 ITER Magnet powering system Magnets are distributed over 21 electrical circuits: 1 Toroidal Field 6 Poloidal Field 5 Central Solenoid 9 Correction Coil Main components: Superconducting Magnets Power Converter Protective Make Switch Fast Discharge Unit Switching Network Unit Quench Detection System Cryogenics/Vacuum
15
CERN PLC Workshop – ITER IO 4-5 December 2014 CIS v0 Architecture 15 Protection Modules: Coil Protection Module Hardwired Loops Supervision Architecture: Supervisor Module CIS Operation Station Critical Interlock Logging System Engineering Workstation CODAC Interface Module Simulation Interface: Magnets PBS 11 CPSS PBS 41 Cryo PBS 34 PCS PBS 47
16
CERN PLC Workshop – ITER IO 4-5 December 2014 CPM functions 16
17
CERN PLC Workshop – ITER IO 4-5 December 2014 Supervision Module 17 WinCC OA Server: Retrieve data from: CPM PIS (Simulator PLC) Provide data: CIS Desk CILS CODAC Interface Manual Commands: Permit Inhibits Reset Overrides Time Synchronization
18
CERN PLC Workshop – ITER IO 4-5 December 2014 CIS Desk 18 WinCC OA Client Routinely operations Monitoring Alarms Function Reset Permits / Inhibits Critical actions Overrides: Masking of Events Disabling functions Forcing Actions Monitoring of ICS
19
CERN PLC Workshop – ITER IO 4-5 December 2014 CIS Desk 19 Operation Display
20
CERN PLC Workshop – ITER IO 4-5 December 2014 CIS Desk 20 Powering Display
21
CERN PLC Workshop – ITER IO 4-5 December 2014 CIS Desk 21 Override Display
22
CERN PLC Workshop – ITER IO 4-5 December 2014 CODAC Interface 22 Non Critical Interface Supervisor Module CODAC Interface Module CODAC Gateway Information per CKT: Power Permit Override Status
23
CERN PLC Workshop – ITER IO 4-5 December 2014 Layout 23
24
CERN PLC Workshop – ITER IO 4-5 December 2014 CIS v.0 Design (Hardware) 24 Cubicle design for 2 Cubicles and 1 19” rack carried out: Cubicle 1 – Contains the CPM module, Remote I/O’s and Interface PLC for sending data to CODAC Gateway CPM ModuleRemote I/OsInterface PLC
25
CERN PLC Workshop – ITER IO 4-5 December 2014 CIS v.0 Design (Hardware) 25 Cubicle design for 2 Cubicles and 1 19” rack carried out: Cubicle 2 – Contains the Simulator module, Remote I/O’s and DLIB boxes and CIN-P1 and CIN-P2 switches. CIN-P1 CIN-P2 Simulator PLC Remote I/Os DLIB’s
26
CERN PLC Workshop – ITER IO 4-5 December 2014 CIS v.0 Design (Hardware) 26 Cubicle design for 2 Cubicles and 1 19” rack carried out: 19” rack - Houses the Engineering workstation, Supervisor module, CIS desk and the CODAC gateway along with the CIN-A switch CODAC Gateway CIS Desk + CILS Supervisor module CIN-A Engineering WS/Simulator HMI
27
CERN PLC Workshop – ITER IO 4-5 December 2014 CIS v.0 Design (Software) 27 Software used for CIS V.0: Engineering workstation comprises the following software for development of the functional logic code and Simulator HMI : Siemens STEP 7 V 5.5, CFC V7.0 – For defining the hardware configuration, parameterization and Communication logic Siemens Safety Matrix – For defining the Interlock logic for the Magnet Siemens WinCC Flexible – For defining the HMI for Simulator
28
CERN PLC Workshop – ITER IO 4-5 December 2014 CIS v.0 Design (Software) 28 Software used for CIS V.0: Supervisor module and the CIS desk comprises the following software for development of the Interlock HMI: Siemens WinCC OA – For defining HMI screens, Time stamping and data archiving in CIS V.0
29
CERN PLC Workshop – ITER IO 4-5 December 2014 CIS V.0 Next steps 29 Carry out the endurance tests for the Interface boxes and capture the results Information from the Interface boxes to be read via Profinet and data to be interpreted for diagnostic purpose Achieve the time stamping for the events in the CIS desk Carry out performance tests on the CIS V.0 similar to tests carried out in the Slow Interlock Prototype Use the CIS V.0 as a platform to demonstrate all the proposed processes for integrating, upgrading and maintaining the ICS. Use the CIS V.0 as a platform to help in developing and improving the CIS V.1 The CIS V0 shall be shipped to Korea in December 2014 to facilitate study for CIS V.1
30
CERN PLC Workshop – ITER IO 4-5 December 2014 Thanks 30
Similar presentations
© 2024 SlidePlayer.com Inc.
All rights reserved.