1 1999/Ph 514: EPICS Overview EPICS Experimental Physics and Industrial Control System (EPICS) Overview Bob Dalesio LANL.

Slides:



Advertisements
Similar presentations
Control System Studio (CSS)
Advertisements

1 1999/Ph 514: Channel Access Concepts EPICS Channel Access Concepts Bob Dalesio LANL.
EPICS Architecture Version 3 Channel Access Client (CAC) Connection Data Transfers WAN/LAN/Local Connection Data Transfers Channel Access Server (CAS)
EPICS Noboru Yaamamoto Jan 27, 2009 for EPICS seminar at RRCAT, Indore Installing EPICS.
© 2002 ABB Automation Technology Products AB BSE ppt Industrial IT The Aspect Object Architecture Overview.
A U.S. Department of Energy Office of Science Laboratory Operated by The University of Chicago Argonne National Laboratory Office of Science U.S. Department.
9-12 Oct 2000PCaPAC 2000, DESY Hamburg Epics to TINE translator Matthias Clausen, DESY Hamburg Phil Duval, DESY Hamburg Zoltan Kakucs, DESY Hamburg.
16 - Nov. 2000EPICS Workshop Oak Ridge1 Epics to TINE translator Matthias Clausen, DESY Hamburg Phil Duval, DESY Hamburg Zoltan Kakucs, DESY Hamburg.
Pete Owens MICE Controls & Monitoring Workshop 25th September 2006 MICE Control and Monitoring: General Architecture Subsystem Integration User Interface.
V4 – Executive Summary 1.Provide online add/delete of I/O to support continuous operation. 2.Provide redundant control of remote I/O to support improved.
OPC Overview OPC Device Support (PLC Gateway for 3.14) Ralph Lange – EPICS Collaboration Meeting at SLAC, April 2005.
Integrating Acquired Subsystems Bob Dalesio 09/21/99.
March 2004 At A Glance ITOS is a highly configurable low-cost control and monitoring system. Benefits Extreme low cost Database driven - ITOS software.
Experimental Physics and Industrial Control System (EPICS) Alarm Handler (ALH) Bob Dalesio, August 14, 1999.
Experimental Physics and Industrial Control System (EPICS) Overview Bob Dalesio, Dec, 2002.
Berliner Elektronenspeicherringgesellschaft für Synchrotronstrahlung mbH (BESSY) Accelerator and Experiment Control and Monitor Systems Ralph Lange BESSY,
1 Progress of the Controls for BEPCII EPICS Seminar Presented by J. Zhao 20 August, 2002.
SCADA. 3-Oct-15 Contents.. Introduction Hardware Architecture Software Architecture Functionality Conclusion References.
NCSX NCSX Preliminary Design Review ‒ October 7-9, 2003 G. Oliaro 1 G. Oliaro - WBS 5 Central Instrumentation/Data Acquisition and Controls Princeton Plasma.
Experimental Physics and Industrial Control System (EPICS) Database Bob Dalesio, June 27,2001.
CLS: Control System E. Matias, R. Berg, G. Wright, T. Wilson, T. Johnson, R. Tanner and H. Zhang Canadian Light Source University of Saskatchewan Invited.
Ralph Lange: OPC Gateway (Device Support) OPC Gateway (Device Support) Ralph Lange – EPICS Collaboration Meeting March SSRF.
Experimental Physics and Industrial Control System (EPICS) Overview Bob Dalesio, June 24, 2001.
IMPLEMENTATION OF SOFTWARE INPUT OUTPUT CONTROLLERS FOR THE STAR EXPERIMENT J. M. Burns, M. Cherney*, J. Fujita* Creighton University, Department of Physics,
SNS Integrated Control System EPICS Recent Applications and Future Directions Bob Dalesio June 12, 2001.
Introduction to EPICS (Ned Arnold, John Maclean).
EPICS Direction to Support Large Projects and Incorporate New Technology Leo R. Dalesio 09/21/99.
Experimental Physics and Industrial Control System (EPICS) Overview Bob Dalesio, May 11, 2000.
A U.S. Department of Energy Office of Science Laboratory Operated by The University of Chicago Argonne National Laboratory Office of Science U.S. Department.
1 Channel Access Concepts – EPICS Training – K.Furukawa – Mar EPICS Channel Access Concepts Kazuro Furukawa, KEK, ( ) (Bob Dalesio, LANL,
Managed by UT-Battelle for the Department of Energy Kay Kasemir ORNL/SNS Jan Control System Studio, CSS Overview.
ATF Control System and Interface to sub-systems Nobuhiro Terunuma, KEK 21/Nov/2007.
EEDEED Tuesday, May 18, VBA & Process Variables  System Overview  Setup (What installations are needed)  What are Process Variables and what.
March 2008EPICS Meeting in Shanghai1 KEKB Control System Status Mar Tatsuro NAKAMURA KEKB Control Group, KEK.
OS Services And Networking Support Juan Wang Qi Pan Department of Computer Science Southeastern University August 1999.
3.14 Work List IOC Core Channel Access. Changes to IOC Core Online add/delete of record instances Tool to support online add/delete OS independent layer.
Writing a Channel Access Client in EPICS Bob Dalesio, April 5, 2000.
Online Software 8-July-98 Commissioning Working Group DØ Workshop S. Fuess Objective: Define for you, the customers of the Online system, the products.
Writing a Channel Access Client in EPICS Bob Dalesio, April 5, 2000.
EPICS EPICS Limitations Bob Dalesio Marty Kraimer.
EPICS Release 3.15 Bob Dalesio May 19, Features for 3.15 Support for large arrays - done for rsrv in 3.14 Channel access priorities - planned to.
LANLLEDA, LANSCE*, AFEL ANLAPS, 25 of 37beamlines, IPNS JLABCEBAF, FEL, Halls A.B.C. LBLALS, BaBar, Heavy ion Fusion, Gammasphere, SLACPEP II*, NLC** ORNLSNS,
Control System Overview J. Frederick Bartlett Fermilab June 1,1999.
Controls & Monitoring Overview J. Leaver 03/06/2009.
ICALEPCS 2005 Geneva, Oct. 12 The ALMA Telescope Control SystemA. Farris The ALMA Telescope Control System Allen Farris Ralph Marson Jeff Kern National.
EDM collaboration meeting WBS 9.0: Slow controls, Simulations, DAQ/data analysis Chris Gould- North Carolina State University and Triangle Universities.
EPICS Release 3.15 Bob Dalesio May 19, Features for 3.15 Support for large arrays Channel access priorities Portable server replacement of rsrv.
Connecting LabVIEW to EPICS network
Jan Hatje, DESY CSS – Control System Studio EPICS collaboration meeting CSS – Control System Studio Update EPICS collaboration meeting 2008 Shanghai.
Stanford Linear Accelerator Center Ron Chestnut EPICS Collaboration Mtg May 21-23, SLAC EPICS Projects Yesteryear, Today, and Tomorrow.
Jefferson Lab Report Karen S. White 11/14/00. Overview  Status of Jefferson Lab Control System  Work In Progress  Transitioning to Operations.
B. Dalesio, N. Arnold, M. Kraimer, E. Norum, A. Johnson EPICS Collaboration Meeting December 8-10, 2004 Roadmap for IOC.
11 th February 2008Brian Martlew EPICS for MICE Status of the MICE slow control system Brian Martlew STFC, Daresbury Laboratory.
1 1999/Ph 514: Supported Hardware EPICS Supported Hardware Ned D. Arnold APS.
EPICS Noboru Yaamamoto July 11, 2006 for EPICS seminar at VECC,Kolkata Installing EPICS.
1 Channel Access Concepts – IHEP EPICS Training – K.F – Aug EPICS Channel Access Concepts Kazuro Furukawa, KEK (Bob Dalesio, LANL)
Control System Overview J. Frederick Bartlett Fermilab June 1,1999.
An Introduction to Epics/Tango Steve Hunt Alceli EPICS Meeting 2008 INFN Legnaro 15 Oct 17:15.
Fermilab Control System Jim Patrick - AD/Controls MaRIE Meeting March 9, 2016.
Redundancy in the Control System of DESY’s Cryogenic Facility. M. Bieler, M. Clausen, J. Penning, B. Schoeneburg, DESY ARW 2013, Melbourne,
EPIC S Noboru Yaamamoto July 11, 2006 for EPICS seminar at VECC,Kolkata Installing EPICS.
Laboratorio per dottorandi 2017 Particle Accelerators Control System
ATF/ATF2 Control System
by Prasad Mane (05IT6012) School of Information Technology
Experimental Physics and Industrial Control System (EPICS) Overview
The Online Detector Control at the BaBar experiment at SLAC
Writing a Channel Access Client in EPICS
Channel Access Concepts
EPICS: Experimental Physics and Industrial Control System
STATEL an easy way to transfer data
Presentation transcript:

1 1999/Ph 514: EPICS Overview EPICS Experimental Physics and Industrial Control System (EPICS) Overview Bob Dalesio LANL

2 1999/Ph 514: EPICS Overview EPICS Outline u Introduction: What is EPICS u The Collaboration u Software / Hardware Architecture u The Client/Server Model over the Channel Access Protocol u A Look at the Principal Data Store - Process Database u A Look at Some Channel Access Clients Display Managers (EDD/DM and MEDM) Alarm Handler State Notation Language u Conclusions

3 1999/Ph 514: EPICS Overview EPICS Introduction: What is EPICS? u A collaboration of the controls groups of many research organizations that use the EPICS tool-kit. u A distributed architecture that supports a wide range of solutions from small test stands to large integrated facilities. u A set of tools that reduces software application and maintenance costs by providing: Configuration tools in place of programming A large installed base of tested software A modular design that supports incremental upgrades Well defined interfaces for extensions at every level

4 1999/Ph 514: EPICS Overview EPICS The EPICS Collaboration u Over 100 independent projects in North America, Europe and Asia u Applications in particle physics, astronomy, and industrial control u Distribute software over the network u Independent development, co-development and incremental development of code done by members u Problem reporting and resolution via exploders u Documentation available on WWW sites u Large collaboration meetings to report new work, discuss future directions, explore new applications, and explore new requirements for existing codes u Small design groups from multiple labs meet to discuss design issues on significant codes: Channel Access, CDEV, Archiving and MMI

5 1999/Ph 514: EPICS Overview EPICS Accelerator Programs Using EPICS u The Advanced Photon Source and ANL u The Thomas Jefferson National Accelerator Newport News, Va. u Proton Storage LANSCE u Injection Linac for KEKB KEK u Advanced Free Electron LANL u Duke Free Electron Laser and Mark III Duke University u Heavy Ion Fusion Test LBL u Intense Pulsed Neutron ANL u HERA Cryogenic Plant and Tesla Test DESY u RF and Beamline Control for the SLAC u Bates Linear Bates MIT u Racetrack University of Athens u BESSY BESSY

6 1999/Ph 514: EPICS Overview EPICS Astronomy Programs Using EPICS u Gemini 8 Meter NOAO (Hawaii, Chile) u Kitt Peak NOAO (Arizona) u William Herschel La Palma (Canary Islands) u United Kingdom Infrared JAC (Hawaii) u Cal Tech u Japanese National Large Telescope u Keck CARA (Hawaii)

7 1999/Ph 514: EPICS Overview EPICS Detector Programs Using EPICS u PHENIX RHIC u STAR RHIC u Detector Halls A, B & TJNAF u LBL u Babar PEP II u FNAL

8 1999/Ph 514: EPICS Overview EPICS Industrial Use of EPICS u GM Fuel Cell Test LANL u Agile Manufacturing Allied Signal u Plant Knolls Atomic Power Laboratory u Flight Jet Propulsion Laboratory u Liquefied Natural Gas BG & E u Western Lake Superior Waste Water Treatment Plant u St. Louis County - Potable Water Distribution Network u Bechtel-Parsons-Brinkerhoff’s Fire Ventilation Test Facility u The Advanced Micro Devices Wafer Fabrication - Clean Room u Citgo Oil Product Storage and Movement Facility u Saphania Oil Field Well Head and Extraction u Las Vegas - Potable Water Distribution Network

9 1999/Ph 514: EPICS Overview EPICS Data Acquisition Commercial Applications u Pratt & Whitney Engine Test Facility u Lockheed Martin u NASA Langley Wind Tunnel u United Technologies Engine Test Facility u McDonnell Douglas Component Test Facility

/Ph 514: EPICS Overview EPICS Project Status Throughout the Collaboration u APS 300, IOC20 wsreliable operation* u HERA Cryo 6,0004 IOCs1 wsreliable operation u Tesla Test Inj 6004 IOCs2 wsreliable operation u KeckII 1,5002 IOCs2 wsreliable operation u PSR 2,5004 IOCs6 wsreliable operation u Duke FEL 2,5006 IOCs3 wsreliable operation u PEP II RF 8,4008 IOCs2 wsreliable operation u BESSY 15,00015 IOCs4 wsreliable operation u APS Beamline 15,00022 IOCs10 wsreliable operation u Jlab 180,00081 IOCs30 wsMostly reliable* * Jlab has software problems under 1% of downtime - mostly at restart. Hardware problems are still over budget (2%) with power supplies and Bira Crate Controllers. *APS has one IOC loss every 2 weeks - tracking down. Under 1% down time.

/Ph 514: EPICS Overview EPICS Distributed Architecture u EPICS is physically a flat architecture of front-end controllers and operator workstations that communicate via TCP/IP and UDP System scales through the addition of new computers Physical hierarchy is made through bridges, routers, or a gateway Network bandwidth is the primary limiting factor u EPICS software architecture is client/server based - with independent data stores providing read/write access directly between any two points Local name services mean automatic integration of new components Point-to-point communication supports automation

/Ph 514: EPICS Overview EPICS Distributed Hardware Configuration Workstations: Sun HP DEC/Alpha Silicon Graphics PC I/O Controllers: VME, VXI, PCI, ISA Field I/O Remote I/O and Signal Conditioning: CAN-Bus, Industry Pack VME, VXI, PCI, ISA CAMAC, GPIB Profibus, Bitbus, Serial Allen-Bradley, Modbus Field I/O

/Ph 514: EPICS Overview EPICS Standard Operating System Software Configurations Workstations OS: SunOS, Solaris HPUX DEC-UNIX SGIX Windows NT Linux I/O Controllers OS: vxWorks Field I/O

/Ph 514: EPICS Overview EPICS Distributed Software Architecture ca-server process DB device sup ca-client CDEV vxWorks, UNIX WindowsNT, VMS UNIX ca-client CORBA ACE vxWorks WindowsNT Solaris ca-server vxWorks only

/Ph 514: EPICS Overview EPICS Many tools are available in the EPICS tool-kit u EPICS tools are connected via the Channel Access client/server libraries u Server Interfaces: Process Database Gateway (CA-Client - GDD Library - Portable server on Solaris) u Client Interfaces Process Database Links Sequencer (programmed with State Notation Language) Data Visualization Packages Data Analysis Packages Modeling and Automation Packages

/Ph 514: EPICS Overview EPICS Channel Access Client/Server Libraries Sequencer Channel Access Client LAN/WAN Operator Interface Channel Access Client Database Links Channel Access Client Channel Access Server EPICS Process Database Client: Provides read/write connections to any subsystem on the network with a channel access server Server: Provides read/write connections to information in this node to any client on the network through channel access client calls Services: Dynamic Channel Location, Get, Put, Monitor Access Control, Connection Monitoring, Automatic Reconnect Conversion to client types, Composite Data Structures Platforms: UNIX, vxWorks, VMS (Client only), Windows NT TCP/IP & UDP

/Ph 514: EPICS Overview EPICS Channel Access Sequencer Channel Access Client LAN/WAN Operator Interface Channel Access Client Database Links Channel Access Client Channel Access Server EPICS Process Database Performance: over 10 Mbit Ethernet Gets Propagation Delay2 mS Throughput7.8K /sec Puts Propagation Delay1 mS Throughput17K /sec Monitors Propagation Delay Dependent Throughput10K / sec (Typically 10% channels have monitors) (memory use in IOC - 2 Meg / 60 connections) (30% network load for 10K monitors / second) Increase bandwidth with Routers, Bridges, Higher speed networks and EPICS gateway TCP/IP & UDP

/Ph 514: EPICS Overview EPICS EPICS Process Database Provides Data Acquisition and Control ca-server process DB dev support ca-client Record types are the basic elements: AI, AO, BI, BO, Motor, CALC, PID, SUB etc.… Records consist of fields for: SCHEDULE, I/O, CONVERT, ALARM, MONITOR Fields hold runtime values: VALUE, TIMESTAMP, ALARM CONDITION, etc.… New record types are easily added Configured using CAPFAST, GDCT, JDCT, Relational DB, Text Editor at the workstation Loaded as ASCII records into vxWorks at boot time Most fields can be read/written through the channel access client interface during operation LAN A Channel Access server provides connection, get, put, and monitor services to this database A Channel Access client provides access to process DBs in other IOCs

/Ph 514: EPICS Overview EPICS EPICS Process Database ca-server process DB dev support ca-client Record execution time varies from record type to record type AI on a is ~12,000/second (50% idle) AI on a is ~6,000/second (50% idle) Fastest periodic scan rate is dependent on vxWorks clock tick (typically 60 Hz) Interrupt scanning is limited by the CPU bandwidth (interrupt delay ~33usec) Name resolution - 10,000/second - runs at the lowest priority 2,500 records use around 1 Megabyte of memory Assignment to particular physical I/O is distinct from process logic - ASCII device type LAN

/Ph 514: EPICS Overview EPICS Channel Access Client Codes Provide a Variety of Functionality Visualization: EDD/DM, MEDM, Dataviews, SL-GMS, tcl/TK, Visual Basic, Visual C++, Labview, IDL, SAMMI JAVA Alarm Handler : ALH State Programming : SNL Other Clients : PV-Wave, Mathmatica, Matlab, Probe, Orbit Lock, Correlation Plots, Striptool, X-Orbit, SAD, CNLS-net SDDS, ARTEMIS, Archivers, Save/Restore Operator Interface Channel Access Client LAN

/Ph 514: EPICS Overview EPICS EDD/DM An Interactive Display Editor and High Performance Display Manager EDD is an interactive display editor for creating operator screens DM is a display manager to activate screens created using EDD Connections are made to channels - typically record-name DM monitors channels and only updates the screen when there are changes Monitors from channel access are cached - not queued ASCII display formats can be read/written for version upgrades/text editing Operator Interface Channel Access Client LAN The Channel Access Client provides name resolution, monitors and puts to any data stores with a CA server

/Ph 514: EPICS Overview EPICS EDD/DM An Interactive Display Editor and High Performance Display Manager Static objects include: text, line, box, oval Monitor objects include: text, bars, meters, indicators Control objects include: text, slider, menu, buttons Plot objects include: strip chart, Cartesian plots, smith charts Related display call-up includes parameter passing Color Rules are available for all objects independent of dynamic channel Visibility modifiers are available for static objects DM does 2,000 updates per second on a SPARC IPC 2 second display call-up for 100 dynamic and 1000 static elements Operator Interface Channel Access Client LAN The Channel Access Client provides name resolution, monitors and puts to any data stores with a CA server

/Ph 514: EPICS Overview EPICS The Alarm Handler Alarm Viewing, Logging and Annunciation Alarms are detected in the data stores - most commonly the process database Alarms are configured into an alarm hierarchy Logging, annunciation, acknowledgment and collection is configured for each group All lower levels of the hierarchy inherit the disable status from above Operator logging tracks alarm disable, alarm acknowledge and silence commands 500 Alarm condition changes per second can be handled on a SPARC IPC Operator Interface Channel Access Client LAN The Channel Access Client provides name resolution, monitors alarm changes, writes group alarm status

/Ph 514: EPICS Overview EPICS State Notation Language A State Machine Implementation in EPICS Operator Interface Channel Access Client LAN The Channel Access Client provides name resolution, monitors and writes to state programs SNL is preprocessed to be converted to C code Constructs are provided for easy channel access interface Construct are provided to define state programs, state sets and transitions SNL implements the Mealy Model - actions are only taken on transition SNL runs in the vxWorks environment Events are supported for synchronizing state sets within a state program SNL does not have a server The process database is used for variables to be exported

/Ph 514: EPICS Overview EPICS New Developments u New developments take advantage of changes in technology and improve functionality, ease of use, and performance while reducing cost u Support large user facilities with real-time data to hundreds of workstations through the development of a gateway (ANL/LANL) u Provide the ability to add/delete records in the process database during operation to support continuous operations (KEK/LANL/ANL) u Support a single computer solution for small experiments and small portions of larger installations (DESY/LANL) u Provide native windows NT capabilities to lower cost and provide data to every desktop (LANL) u Create a modern JAVA based MMI attempting to maintain the performance while increasing the functionality and ease of use (LANL L-12) u Provide a distributed archiving/archive retrieval capability to better support analysis and operations (TJNAF/LANL/DESY)

/Ph 514: EPICS Overview EPICS EPICS Collaboration : Cooperative Development of a Scaleable, Flexible Tool-kit u The fundamental performance and functionality is scaleable and easily configured u Clean interfaces for clients, new record types, data stores and hardware promote independent development, support ease of reintegration, and protect against obsolescence u Cooperative collaboration gives members laboratories a larger pool of talent to support their controls u Continual improvements allow members to expand functionality, performance, reliability and function while taking advantage of latest technology