1 / 22

Contents

Epics to TINE translator Matthias Clausen, DESY Hamburg Phil Duval, DESY Hamburg Zoltan Kakucs, DESY Hamburg. Contents. Accelerator Controls at DESY EPICS and its CA History of creating EPICS to TINE translator Naming convention Mode of operation Conclusions, summary and future. Past

malcolm-patton
Download Presentation

Contents

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. Epics to TINE translatorMatthias Clausen, DESY HamburgPhil Duval, DESY HamburgZoltan Kakucs, DESY Hamburg PCaPAC 2000, DESY Hamburg

  2. Contents • Accelerator Controls at DESY • EPICS and its CA • History of creating EPICS to TINE translator • Naming convention • Mode of operation • Conclusions, summary and future PCaPAC 2000, DESY Hamburg

  3. Past hampered by the “many-control-systems” syndrome different subsystems controlled by completely different means no possibility of intercommunication (HERA) Today practically all subsystems of HERA in fact controlled by TINE important exceptions include: Proton Vacuum cryogenics control the super conducting electron RF cavities the power subsystems (EPICS) The cooling subsystems (EPICS) Accelerator Controls at DESY PCaPAC 2000, DESY Hamburg

  4. What is EPICS? (Experimental Physics and Industrial Control System) • Process control and data acquisition software toolkit • Application Developers can create a control system with it • Running under the real-time operating system VxWorks • Physically a flat architecture of front-end controllers and operator workstations that communicate via TCP/IP and UDP • Software architecture is client/server based Basic components: • Operator Interface • I/O Controller • Local area network • Channel Access PCaPAC 2000, DESY Hamburg

  5. What is Channel Access (CA) • Network protocol • A callable interface (library of subroutines) • Integrates software modules into the control system • CA server >>> connection, get, put,and monitor services • CA client >>> access to process DB-s in other IOC-s • Communication between databases is accomplished using the CA client library • Standardized communication path to a field(s) within a record (process variable) in any IOC database(s). • All access to the database is via the database access routines. PCaPAC 2000, DESY Hamburg

  6. EPICS data to TINE in the past • EPICS tools connected via the CA C/S libraries • CA libraries linked to any third party program (TINE based application) • Visual Basic Application using the ACOP (Accelerator Component Object Programming) library; last one has built-in the CA functions • Unrealized Client-Side Tool Utility • EPICS client-side tools are generic • EPICS client-side tools used only with EPICS PCaPAC 2000, DESY Hamburg

  7. “Old way” ACOP Application UNIX or WindowsNT TINE client CA function ca-client ca-server VME crate OS: vxWorks Appl: EPICS PCaPAC 2000, DESY Hamburg

  8. Disadvantages of using “old way“ • Unfriendly update of distributed CA libraries and DLL-s • Special VBA using CA functions • No naming service available • Low priority clients consume resources in critical machines PCaPAC 2000, DESY Hamburg

  9. First Ideas • Integrate the EPICS IOC-s into the HERA mainstream • Build new server, runs directly on the EPICS IOC • The server module resides in each one of the system controllers along with that controller’s portion of the distributed EPICS context • TINE view of the hardware control to the rest of the CS • Control via channel access remain as before • Use well implemented local calls like dbpf, dbgf • Each server module has its own “mapped” record list PCaPAC 2000, DESY Hamburg

  10. Requirements • Excellent performance without disturbing the real-time control loops in and between subsystems • A maximum level of functional flexibility • Less additional programming • Fit seamlessly into TINE systematics (Alarm, Archive, Naming, Permit, …) • Bypass local Channel Access Protocol PCaPAC 2000, DESY Hamburg

  11. PC Windows NT VBA Applic TINE Sun Solaris MEDM CA PC Windows NT X-Session CA I/O Controllers vxWorks EPICS CA Server TINE Server I/O Controllers vxWorks EPICS CA Server Field I/O Field I/O Configuration PCaPAC 2000, DESY Hamburg

  12. WINDOWS NT WORKSTATION user program user program Channel Access Repeater TINE Client Channel Access Client TINE server Channel Access server Channel Access client C program database access library SNL sequence DATABASE database library record support device support device drivers IOC PCaPAC 2000, DESY Hamburg

  13. Naming convention • Database is the heart of an IOC (records) • Unique record names across all IOC-s attached to the same TCP/IP subnet. • Form: <record name>[.<field name>] • Each record type has a fixed set of fields: common / specific • Access to the database is via the channel or database access routines (exception recSup, devSup) PCaPAC 2000, DESY Hamburg

  14. Naming convention 2 • Each server module has a mapped record list • the real PV names are mapped to TINE registered names • EPICS record names 28 chars, field 4 chars field • TINE device names 16 chars, properties 32 chars • TINE names registered as devices • Register devices with their truncated TINE names: • List of PV’s and the correspondent TINE names • Dynamically Need to truncate !!!! PCaPAC 2000, DESY Hamburg

  15. Mode of operation • TINE client requires data • Search for TINE device in the local list or reconstruct PV name • Search and get data (database access routines) • Local conversion corresponding TINE client requested data type format • Respond to the request and send the data to the client • No need to know the location or other attributes of the data. PCaPAC 2000, DESY Hamburg

  16. Mode of operation 2 • The server is able to send any value to any client TINE application • The multiple instances of the server in a control system respond to a request for data by searching for the registered device • Name servicing possibility • Local access data functionality • Directly access to the database access layer PCaPAC 2000, DESY Hamburg

  17. Extended support for different data types • Data type conversions are performed in the server • Using EPICS CA standard data types defined in db_access.h like DBR_STRING, _DOUBLE, _FLOAT, _LONG, _CHAR • Converting of different data types was possible without major changes in EPICS or TINE code • Care should be taken to ensure there is sufficient sized reserved space for all supported data format PCaPAC 2000, DESY Hamburg

  18. Composites • New requirements were identified • Extended set of interfaces, additionally set of PV’s • Set of arranged TINE devices • Identified through collective names • Configuration files, contains the composite names and the members of each composite device • User can set up his own sets • Easily scaleable PCaPAC 2000, DESY Hamburg

  19. Conclusions, Summary and Future • First tests >>> monitor 250 channels by one IOC (stably run) • Weather station data transparent to TINE (archive) • Possibility to communicate to the EPICS IOC’s through: CA protocol / “TINE-Way” • Integrate existing EPICS systems without rebooting • Port the EPICS database into TINE control system • Keep alive TINE user friendly environment (no special VBA) • Restarting of the TINE-Server without booting the system PCaPAC 2000, DESY Hamburg

  20. PCaPAC 2000, DESY Hamburg

  21. PCaPAC 2000, DESY Hamburg

  22. Why use? • Intercommunication between two different control systems • Flexible and friendly updateable • TINE server library in the unbundled tree of the EPICS system (similar base tree) • Automatically update together with new EPICS releases • No more distributing new channel access libraries • No need special TINE graphical interfaces • No use of CA subnet-dependent connections • Following the trend of using Windows in control systems • TINE has the naming service built-in. PCaPAC 2000, DESY Hamburg

More Related