CSS Control System Studio

Transcription

1 CSS Control System Studio Introduction CSS Control System Studio Summary GSI February 11 th 2009 Matthias Clausen, Jan Hatje (DESY / MKS-2) Presented by: Matthias Clausen 1

2 Agenda of Today Introduction (Matthias Clausen) EPICS and DESY CSS History CSS Requirements CSS Technical Background (Jan Hatje) Eclipse Interfaces: DAL/ AAL CSS Main Tools (Matthias Clausen) Synoptic Display Studio (SDS) Archive Display (DataBrowser) CSS Core Tools I (Jan Hatje) Alarms Authentication and Authorization Remote Management CSS Core Tools II (Matthias Clausen) Name Server/ Name Space Browser Integrated development with CSS: CSS.DCT; CSS SNL Diagnostic Tools: casnooper 2

3 Introduction EPICS EPICS at DESY Control System Studio History Requirements 3

4 A brief Introduction to EPICS What is EPICS? EPICS = Experimental Physics and Industrial Control System The Collaboration Basic Concept Input Output Controller (IOC) Network Protocol (Channel Access - CA) Application 4

5 EPICS Collaboration < 2003: 150 EPICS user Licenses > 2003: open source 5

6 EPICS Collaboration: It s the people XFEL Collaboration Meeting Archamps Participants 34 Institutes 4 Companies 6

7 Breaking News: The EPICS Collaboration will grow even further As of February 1 st ITER announced that EPICS will be used as the baseline for the software environment for the ITER control system (Published via EPICS TechTalk on Feb. 10 th ) 7

8 ITER Statement The CODAC group initiated a number of actions in the first half of 2008 in order to select a software environment as a part of moving from the conceptual design to an engineering design of CODAC. The conclusion of all these activities is that ITER, being an experimental facility with a very long timeline, is better suited using an open source solution as compared to a commercial solution. Further, the reports conclude that technically, any of the candidate open-source solutions would work. However, due to market share and proven record the preferred solution would be EPICS. As a consequence, the CODAC group announces that EPICS will be used as the baseline for the software environment for the ITER control system within the scope of PCDH (Plant Control Design Handbook). Anders Wallander, 01-Feb

9 EPICS The Basic Concept CA-Client Applications CA ( Channel Access) - ip-based communication protocol IOC -Control loops -Sequence programs CA-Clients connect to IOC s via broadcast or name server IOC Operation Is independent from Network Connection Control Loops -Permanently running at sprecise scan time P T I/O -Local, or -On a field bus 9

10 Application Development Integrating new I/O devices Programmer Adding new databases for supported devices Process Engineer Get driver from EPICS site Prepare new IOC Load Image Write text file to load directory Configure Database Database Creation Tool Load IOC with -Operating System -EPICS core -Database 10

11 Advantages of the EPICS Way Code running on the IOC is very stable EPICS core software developed by core team (specialists) Core is tested on all main operating systems before any new release. Only specialists create new drivers Core and drivers are running in many installations worldwide Code is well tested and debugged Process engineers configure databases No code created IOC s only differ by databases the stable code remains the same Database configuration tools can be used by remote consulting/ engineering companies to create EPICS databases. (Database text files can be send via to DESY) 11

12 EPICS at DESY EPICS is in operation at DESY since more than 18 years. From the very beginning it is used for cryogenic controls. Which is process controls. Only a few years later (1993) EPICS was also introduced for the distributed PLCs of the utility controls group. Since then all of the cryogenic plants at DESY are or will be (2009) controlled by EPICS IOCs All of the utility controls are and will be using EPICS to supervise their extended PLC infrastructure for monitoring and controls. Like a SCADA system This applies also for the new projects: PETRA-III and the European XFEL 12

13 EPICS for Cryogenic Controls EPICS fulfills all the requirements of cryogenic control Process control System Control Loops on IOC Sequencer on IOC Process Control Applications Synoptic Display Archiver / Viewer Alarm-System / Alarm Display 13

14 EPICS for Utility Controls The utility controls group is using EPICS as a SCADA system Configuring EPICS databases Configuring display files Configuring alarm configuration files Configuring archive configuration files The utility controls group can use EPICS independent from the cryogenic controls group, which is providing the service to prepare: EPICS applications EPICS-IOC core software (including drivers) 14

15 Cryogenic and Utility Controls Cryogenic XFEL Utility System Support by Cryogenic Controls Group D/3 EPICS Application Development Application Development Application Configuration Application Configuration Application Configuration Database Configuration S Database Configuration Driver Development Database Configuration Driver Development S Utility Controls Group PLC Database Configuration 15

16 CSS Basic Requirements Looking back in History 16

17 New Developments: Operator Interface Motivation Current State XFEL Have a look at current operator interfaces: Many applications of different kind Implemented by different programmers Different look and feel Implemented in different programming languages GUI with text in specific languages ( difficulties for Japanese Operators) Running only on specific operating systems Running only in the context of a specific control system type Which kind of data/ information transfer are possible? Drag and drop basic information as string Cut and paste strings Drag and drop objects within the same program environment (Windows) 17

18 History 2005 EPICS Office An Initiative for a new Control System Office Framework 18

19 What is EPICS-Office? It is an environment / framework which enables you to create your control system applications. It shall provide interfaces to: Control System Data Control System Name Services Control System Logging Services Application Logging Services Application Management Services more It shall provide a generic infrastructure to built pluggable, component based applications: High level applications (XAL) User/ operator applications 19

20 History 2005 EPICS Office An Initiative for a new Control System Office Framework 2006 CSO Control System Office 20

21 CSO Interfaces Control System Data Access Name Services Logging Services Archive Data Utility Application Logging Services Application Management Services Trigger Updates, Monitor running CSO Instances, Stop CSO Instance Record/ Playback Relational Database Graphic Graphic Service Widgets Application/ Application Drag/ Drop 21

22 History 2005 EPICS Office An Initiative for a new Control System Office Framework 2006 CSO Control System Office Adding the Idea of Interfaces to the Control System(s) 2006 CSS Control System Studio Brain Storming DESY Focus: Information on your fingertip Decision to use Eclipse Decision to implement CSS-Core by specialists from University (C1-WPS) 22

23 New Developments: Control System Studio CSS Design Design Criteria: XFEL Common Look and Feel Information on your Fingertips Find related applications using <MB3> Drag and drop Java objects between (CSS compliant) applications Management of installed CSS installations Talking to control systems through interfaces rather than directly through control system specific API s Authentication/ Authorization Internationalization Do not preclude other implementations Integration by plugin 23

24 CSS Development / Collaborating - idea, coordination University of Hamburg, C1-WPS (Scientific contract, CoEUD project) CSS Core, Synoptic Display Studio DESY, ORNL (Kay Kasemir) Applications: Databrowser, PV Table, Name Space Browser, Alarm System, Cosylab (contract) Data Access Layer Josef Stefan Institute Student exchange 24