1 / 9

Control System Interfaces

Control System Interfaces. Kay Rehlich XFEL Collaboration Meeting April 2013. XFEL Interfaces Overview. TINE Client C and Java. DOOCS C++. DOOCS Java. Karabo C++. E. E. E. k. k. k. k. Ti. Ti. Ti. Ti. Ti. Ti. D. D. D. D. D. Ta. Ta. DOOCS Server. TINE Server.

tien
Télécharger la présentation

Control System Interfaces

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. Control System Interfaces Kay Rehlich XFEL Collaboration Meeting April 2013

  2. XFEL Interfaces Overview TINE Client C and Java DOOCS C++ DOOCS Java Karabo C++ E E E k k k k Ti Ti Ti Ti Ti Ti D D D D D Ta Ta DOOCS Server TINE Server DOOCS Server Karabo Server EPICS Server TANGO Server Undulator Beckhoff DAQ DAQ XFEL Collaboration Meeting April 2013 Kay Rehlich, DESY

  3. Example: TINE - DOOCS Interface DOOCS Java e.g. jddd Standard Application Programming Interface API Get(adr, dataIn, dataOut) Equipment Name Server ENS Adr  protocol, server adr E k Ti Ti Ti D D Ta jdoocs Data transformation to uniform format Native libraries of the control systems TINE Server DOOCS Server DAQ XFEL Collaboration Meeting April 2013 Kay Rehlich, DESY

  4. TINE - DOOCS Interface: Data Types • In total ~ 90 data types • 75 % can be translated TINE  DOOCS • 25 % are special types e.g. for archiving • A data type can hold a single bit … up to 32MB (image) • Data types can be quite complex: • Archive types, images, … • The API provides many functions like: • get_float_2D ( row, col )  has to be implemented for all types XFEL Collaboration Meeting April 2013 Kay Rehlich, DESY

  5. Special Features (1): Addressing with Wild-cards • BPM simulation server • ADR = XFEL.DIAG/BPM/*/Y All controls interfaces should support this, If not it has to be simulated XFEL Collaboration Meeting April 2013 Kay Rehlich, DESY

  6. Special Features (2): Addressing with System Mask SASE xx Inj 2 All sections belonging to SASE2 e- beam lines All e- beam lines System Mask: XFEL Collaboration Meeting April 2013 Kay Rehlich, DESY

  7. Address Conventions • DOOCS: facility/device/location/property • TINE: context/server/device/property • TANGO: domain/family/member/property • EPICS: flat, no standard definition • Requires entries in the DOOCS name server • karabo: device(=facility/device/location)/property • DOOCS addresses require static entry in karabo-DB XFEL Collaboration Meeting April 2013 Kay Rehlich, DESY

  8. Undulator Interface per Section Control System Interface Dynamic configuration of locations and properties DOOCS Undulator Server Request Port: List of ports n 1 r Publisher Port: Sends changed data D 0MQ Gateway n 1 UND 1 UND n . . . Beckhoff Controller UND 1 UND n . . . M M M M Impl. By Andreas Beckmann XFEL Collaboration Meeting April 2013 Kay Rehlich, DESY

  9. DOOCS  karabo Demo • First prototypes demonstrated on both control systems • JAVA interface is next step karabo GUI DOOCS ddd Karabo Camera Server DOOCS Camera Server XFEL Collaboration Meeting April 2013 Kay Rehlich, DESY

More Related