Presentation is loading. Please wait.

Presentation is loading. Please wait.

ICS interfaces Timo Korhonen ICS www.europeanspallationsource.se Apr 22, 2015.

Similar presentations


Presentation on theme: "ICS interfaces Timo Korhonen ICS www.europeanspallationsource.se Apr 22, 2015."— Presentation transcript:

1 ICS interfaces Timo Korhonen ICS www.europeanspallationsource.se Apr 22, 2015

2 Overview 2 Controls interfaces Hardware platforms for I/O High-speed digital platform Middle range I/O Industrial I/O Timing and beam mode data Signals to connect Data archiving Alarms

3 Controls interfaces 3 Control system interfaces include Hardware for I/O signals, cabling Control and data requirements Speeds, accuracies, data amounts Interfaces to controls services Naming Configuration management Data archiving and retrieval GUIs for device operation Requirements for operating ESS Every signal in control room comes through the control system! Many other details that cannot all be covered today.

4 Hardware platforms for I/O 4 Control system must cover a spectrum of I/O requirements Fast, real-time signal processing State-of-the-art technology, evolving fast FPGA-based processing MHz to GHz range of signal acquisition Middle-range I/O requires synchronization, kHz range I/O Non-real time industrial I/O Typically PLC-based Off-the-shelf devices Serial, Ethernet or other fieldbus devices More detail can be found herehere

5 Fast, real-time signal acquisition 5 The high-end platform for ESS is MTCA.4 Consider this when you have requirements like: Signal acquisition faster than 100 kHz (100 kSPS) Precision timing pulses or clocks, RF synchronised Fast preprocessing of signals (with FPGA) Tight synchronisation with beam pulses Typical uses in LLRF and instrumentation Probably not much else Final design and selection of components underway To be done with stakeholders Crate and CPU standards will be provided by ICS

6 Middle-range I/O 6 High-end platform is expensive and centralized Use only where absolutely needed Some applications still need time synchronization Especially in a pulsed machine! PLCs are not ideal for this (asynchronous cycle times) EtherCAT is a good solution for this range Uses Ethernet cabling, special protocol Can run on a PC or a MTCA IOC Loop times of several kHz possible Distributed I/O (reduce cabling) Cost effective Many I/O modules, several manufacturers Widely used in the EPICS community

7 Industrial I/O 7 PLC is the standard choice for most industrial-type I/O High reliability Established technology A huge selection of I/O modules available Recommended manufacturer will be announced soon For safety applications, Siemens has already been awarded a framework contract For general, non-safety applications contract will be awarded within a few weeks Use for most I/O that does not need to be beam- synchronous E.g., vacuum, cryogenics, etc. Local (slow) protection

8 “Other” I/O 8 There is still a large number of devices not covered yet Serial devices (RS-232, RS-485) Use MOXA ethernet-to-serial converter Ethernet-based devices Ethernet as a fieldbus, use StreamDevice & ASYN Motion control For prototyping, use GeoBrick (Delta Tau) Final selection of hardware under evaluation Cameras GigE, 10GBE, CameraLink(HS) EPICS AreaDetector supports a large device base Contact ICS before making a selection

9 Cabling 9 We need to think and decide who does Cabling from devices to the I/O components MTCA.4 crates EtherCAT and PLC I/O terminals ICS will provide lists of supported I/O types I/O terminals for EtherCAT (exists already in fact) PLCs (as soon as vendor announced) – catalogue Timing – electrical, optical triggers, precision MTCA.4 case-by-case (typically end user defined) From the signal interface to control room is ICS responsibility Ethernet, timing, etc. networks

10 Timing 10 Synchronisation will be provided by ICS to all subsystems that need it Event system (Micro-Research Finland) One (could be more) central master (Event Generator) Several timing receivers Timing system distributes High-precision trigger signals Many possible electrical interfaces Synchronous data E.g. Beam mode data Timestamps For EPICS process variables More details: a presentation, if requested?

11 EPICS 11 All I/O signals will go to EPICS IOCs to be Monitored or manipulated by operators or system experts Archived for later analysis Used in physics or other applications to run the accelerator As a system owner, think: What signals you need to operate the devices? Currents, temperatures, status, on/off, etc. Speed? Precision? Do you want to check what happened a while ago? Archiving service provided by ICS How do I operate my device? Startup, calibration, operation modes, etc.

12 EPICS (continued) 12 How do I operate my device? Startup, calibration, operation modes, etc. Dependency on beam modes E.g., operating a wirescanner – only with low intensity beam When should operator take an action if something is not in a normal state? Alarm service provided by ICS, “soft” protection Beyond EPICS scope: need to protect the device from damage (local protection) Is it OK to have beam? (machine protection, beam interlock)

13 Summary 13 A lot of discussion revolves around the high-end platform But that is only a part of the story work-intensive and critical part, but still Other areas tend to get too little attention try to set up a comprehensive set of solutions We have selected MTCA.4 for the high-end Knowing that there will be issues to solve But they can be solved We try to establish and leverage collaborations Mutual help between institutes Other areas are equally, if not even more urgent Need to keep going there, too Start prototyping (in our new lab)

14 14 Questions?

15 EPICS IOC Control & Monitoring Control Services High- Level Application Control & Monitoring Control Services High- Level Application RF Cell/ Power Supply ICS Scope ( including programming for most WPs) ACCSYS WP8, WP2, WP6, WP 17 Controlled System/Device EPICS IOC Control & Monitoring Control Services High- Level Application Control & Monitoring Control Services High- Level Application Motion Controller* Motion Controller* ACCSYS WP4, WP5, WP7, WP10 Controlled System/Device EPICS IOC Control & Monitoring Control Services High- Level Application Control & Monitoring Control Services High- Level Application PLC Controller** PLC Controller** ACCSYS WP3, WP4, WP5, WP6, WP10, WP11, WP 12, WP15, WP16 EPICS IOC Control & Monitoring Control Services High- Level Application Control & Monitoring Control Services High- Level Application Controlled System/Device ACCSYS WP3, WP6, WP7, WP 12 * Motion Controllers. Standardization and prototyping under ICS scope. Cost under AD scope. ** PLC Controllers. Standardization and programming under ICS scope. Cost under AD scope AD Scope AD – ICS Interfaces and Division of Responsibilities March 2015


Download ppt "ICS interfaces Timo Korhonen ICS www.europeanspallationsource.se Apr 22, 2015."

Similar presentations


Ads by Google