1 / 15

Control servers for ATCA based LLRF system

Control servers for ATCA based LLRF system. Piotr Pucyk - DESY , Warsaw University of Technology Jaroslaw Szewinski – Warsaw University of Technology. Agenda. Requirements LLRF servers classification ATCA computation power for LLRF servers Servers topology in ATCA based LLRF system

dennis-mcclain
Télécharger la présentation

Control servers for ATCA based LLRF system

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 servers for ATCA based LLRF system Piotr Pucyk - DESY, Warsaw University of Technology Jaroslaw Szewinski – Warsaw University of Technology

  2. Agenda • Requirements • LLRF servers classification • ATCA computation power for LLRF servers • Servers topology in ATCA based LLRF system • Possible control systems • Development environment • Time schedule and summary

  3. Requirements • What servers should do and should not do ? • Missing contribution from Jaroslaw Szewinski

  4. What control software do we need? GUI, external apps • Finite state machines for automation • Front-end servers for hardware maintenance, configuration and diagnostics • Front-end servers for controller and low level applications (execution nodes for state machines) • Middle layer servers for high level applications • DAQ servers or interfaces to DAQ • GUI panels, interfaces to Matlab, C, etc. DAQ High level apps, FSM End-node for FSM, controller server Diagnostics maintenance

  5. Different CPUs in ATCA based LLRF system Embedded processors AMC module processors mainframes ATCA blades Computation power - Low processing power - FPGA resources + close to the hardware • + serious processing power - uses AMC slot on carrier + PCIe, GbE • + server class processing power • No PCIe until now • Huge processing power • DAQ, storage • Post processing • GbE

  6. ATCA Carrier board ATCA CPU blade Mainframe blades AMC CPU CPU CPU CPU CPU CPU CPU CPU CPU CPU IO AMC (FPGA) CPU CPU CPU CPU CPU CPU CPU CPU CPU FPGA FPGA embedded CPU Possible topology of LLRF servers Front-end middle layer Simple FSM FSM, DAQ GbE PCIe Middle layer FSM Front-end Front-end GbE

  7. Possible control systems • DOOCS • EPICS • TINE • Dedicated software • Missing contribution from Jaroslaw Szewinski

  8. What we can reuse, what we have to develop • Reuse • Old communication scheme (one software interface – many hardware drivers), memory description map • Tools for debugging and configuration • Some existing server’s source code • New development • Diagnostics, maintenance interfaces (inc. IPMI, crate management) • FSM framework for high level apps • New communication channels

  9. Development environment & tools • Linux platform • Language parsers, server wizards • Scripting languages • … • Missing contribution from Jaroslaw Szewinski

  10. Schedule, manpower • Before we start: • Development environment, control system, communication libraries, FSM framework. • Development schedule strongly depends on other tasks • Configuration and maintenance servers (when carrier board and at least one AMC is debugged and ready for firmware implementation - 3-5.2008 ?) • Finite state machines and procedures – starting from 1.2008 ? • Controller server, and low level applications interface servers (parallel to controller development and low level applications) • Minimum Manpower • 1 fulltime programmer for front-ends, 1 fulltime for FSM and high level apps, 1-2 students for help • A lot of support from MCS group !!!

  11. Backup slides

  12. TCP Server TCP/IP FPGA Internal Interface LPT VME Memory map description File / parser Eth ??? Other Applications Hardware Channels Engine User Applications Old System Scheme

  13. Client on remote machine TCP/IP Virtex II PRO Linux on PPC User mode TCP server Kernel mode driver Hardware FPGA II Core Internal Interface bus Linux on PowerPC • User applications access hardware through the driver • Kernel mode driver has access to the FPGA • FPGA has defined hardware interface

  14. DOOCS patterns http://flash.desy.de/sites/site_vuvfel/content/e403/e1644/e1136/e1137/infoboxContent1796/tesla2006-10.pdf

  15. DOOCS patterns (2)

More Related