Presentation is loading. Please wait.

Presentation is loading. Please wait.

24.07.2006Cédric Potterat - LPHE Monday Meeting1 PVSS for VELO and TELL1 at EPFL.

Similar presentations


Presentation on theme: "24.07.2006Cédric Potterat - LPHE Monday Meeting1 PVSS for VELO and TELL1 at EPFL."— Presentation transcript:

1 24.07.2006Cédric Potterat - LPHE Monday Meeting1 PVSS for VELO and TELL1 at EPFL

2 24.07.2006 Cédric Potterat - LPHE Monday Meeting 2 outlines Introduction to PVSS Introduction to SMI++ and FSM (ECS control) VELO – Hybrid’s Low Voltage TELL1  DIM, fwCcpc, fwHw  Present Developments Outlooks

3 24.07.2006 Cédric Potterat - LPHE Monday Meeting 3 PVSS – CERN Historically at CERN the control of equipment not used directly for data acquisition has been called "slow control" In many applications it has become possible to use commercial off-the-shelf (COTS) solutions, with the advantage that the physics community does not need to develop or maintain them. PVSS (Prozeßvisualisierungs- und Steuerungssystem), from the Austrian company ETM, was selected after a formal tender process in 1999 for use in the slow control systems of the four LHC experiments. (eng: Process visualization and control system) CERN provides:  A global PVSS Framework LHCb provides:  Specific PVSS components Volume 45, number 5, June 2005

4 24.07.2006 Cédric Potterat - LPHE Monday Meeting 4 PVSS Features – Structure Open Architecture  We can write our own managers  It can be interfaced to anything (FSM, DIM)

5 24.07.2006 Cédric Potterat - LPHE Monday Meeting 5 PVSS Features – Distributivity Highly Distributed  130 Systems (PCs) tested  No major problem found

6 24.07.2006 Cédric Potterat - LPHE Monday Meeting 6 PVSS Features - Datapoint Concept DP type  DP Standard Interface  All data of all sub-systems defined as Configs

7 24.07.2006 Cédric Potterat - LPHE Monday Meeting 7 Building User Interfaces Static Part  Drag & Drop Dynamic part  Control Scripts ("C" like)  few useful calls for accessing DPs: dpGet (string dpName, value) dpSet (string dpName, value) dpConnect (string call-back, string dpName)  few useful calls for accessing Widgets: getValue (string widgetName, string widgetProperty, ) setValue (string widgetName, string widgetProperty, )

8 24.07.2006 Cédric Potterat - LPHE Monday Meeting 8 Central Hierarchy - ECS... To Devices (HW or SW) Commands Status & Alarms ECS DCS DAQ DetDcs1 DetDcs N SubSys 1 SubSys 2 Dev 1 Dev 2 Dev 3 DetDaq 1 SubSysN Dev N LHC T.S.... GAS DSS Abstract levels

9 24.07.2006 Cédric Potterat - LPHE Monday Meeting 9 Central Hierarchy - ECS VELOA DCS INFDCSHVDAIDAQHLTLHC VELOA HV VELOA DAI VELOA DAQ VELOA LV VELOA TEMP VELOA FEE VELOA TELL1 ECS VELOC DCS VELOC HV VELOC DAI VELOC DAQ VELOC LV VELOC TEMP VELOC FEE VELOC TELL1 VELOAVELOC VELO TFC L0

10 24.07.2006 Cédric Potterat - LPHE Monday Meeting 10 FSM – SMI++ PVSS II does not have tools specifically for:  Abstract behavior modeling Finite State Machines (FSM)  Automation & Error Recovery Expert System But… FSM (SMI++) does State Management Interface (SMI++ which was developed for the DELPHI experiment) is used to control the FSM

11 24.07.2006 Cédric Potterat - LPHE Monday Meeting 11 FSM – SMI++ Device Level: Proxies  C, C++, PVSS ctrl scripts  drive the hardware: deduce State handle Commands Abstract Levels: Domains  Internal objects  Dedicated language  Implement the logical model User Interfaces  For User Interaction

12 24.07.2006 Cédric Potterat - LPHE Monday Meeting 12 FSM – SMI++ SMI++ - The Language  SML – State Management Language Finite State Logic  Objects are described as FSMs their main attribute is a STATE Parallelism  Actions can be sent in parallel to several objects. Tests on the state of objects can block if the objects are still “transiting” Asynchronous  Actions can be triggered by logical conditions on the state of other objects

13 24.07.2006 Cédric Potterat - LPHE Monday Meeting 13 FSM – PVSS basic Panel ECS DCS DAQ LHC...

14 24.07.2006 Cédric Potterat - LPHE Monday Meeting 14 LV – VELO Project Aim:  Control the Low Voltage Power Supplies for the Hybrids  Each Hybrid gets 3 LV Channels (-5.5V, 5.5V and 6V) LV Devices – CAEN:  Crate: SY2527 with a BranchController (A1676A)  esayCarte: ESAY3000 with five A3009 Boards (12 channels) plugged in

15 24.07.2006 Cédric Potterat - LPHE Monday Meeting 15 LV – VELO Project Main Panel:  Control the state, the voltage of all the hybrids Hybrid Panel:  Control the state, the voltage of its three channels Channel Panel:  Control the state, the voltage FSM Hierarchy Velo_C Velo_A Hyb 1Hyb 2Hyb N Channel 1 Channel 2Channel 3

16 24.07.2006 Cédric Potterat - LPHE Monday Meeting 16 LV – FSM Channel FSM State: very basic ERROR OFF RAMPING_UP RAMPING_DOWN READY Switch_OFF Switch_ON Recover An error

17 24.07.2006 Cédric Potterat - LPHE Monday Meeting 17 LV – VELO Project This PVSS project:  developed with a simulator  successfully tested with real hardware  waiting for new information about the power supplies that will be used

18 24.07.2006 Cédric Potterat - LPHE Monday Meeting 18 TELL1 – PVSS Project We are attending to a crucial point in Switzerland History and Symbol

19 24.07.2006 Cédric Potterat - LPHE Monday Meeting 19 TELL1 – PVSS – Outlines We focus on the description (DPT, Panels) of a VeLo Tell1. (VeLo TELL1 is now completely described (registers, settings, addresses)) The access to the configuration database and recipe definition interface is finished We put hands on the FSM (Rules, Panels)

20 24.07.2006 Cédric Potterat - LPHE Monday Meeting 20 TELL1 – PVSS Project Optical Receiver PP- FPGAs Sync Link- FPGA GBE ECS Interface Power TTC IF

21 24.07.2006 Cédric Potterat - LPHE Monday Meeting 21 TELL1 – PVSS Tools DIM fwDim (C. Gaspar) http://dim.web.cern.ch/dim/ ccserv (S. Koestner) fwCcpc (S. Koestner - R. Fernandes) http://lhcb-online.web.cern.ch/lhcb-online/ecs/PVSS_CCPC/default.html fwHw (R. Fernandes) http://lhcb-online.web.cern.ch/lhcb-online/ecs/FWHW/default.html

22 24.07.2006 Cédric Potterat - LPHE Monday Meeting 22 DIM Distributed Information Management System  Publish/Subscribe mechanism Servers publish Services. Clients subscribe to Services:  On change or at regular intervals Clients can send commands to Servers  Services A set of data  any type or size  Identified by a name  A Name Server Keeps a list of available Services

23 24.07.2006 Cédric Potterat - LPHE Monday Meeting 23 DIM Some Characteristics  Transparency DIM clients do not know where their interlocutors are. DIM components can move from one machine to another, all connections are transparently re-established.  Available on mixed environments: UNIX (HP-UX, Sun-OS, Sun-Solaris, IBM-AIX, DEC-OSF, Linux), Windows, VMS, Real-time OSs (OS9, LynxOS, VxWorks)  API available in “C”, C++ and Java  Easy to Use One “call” and a process can become a server or a client. Monitoring and Visualization Tools Available. Documentation and examples at: http://www.cern.ch/dimhttp://www.cern.ch/dim

24 24.07.2006 Cédric Potterat - LPHE Monday Meeting 24 PVSS  DIM FwDIM component:  Server is a DIM Server  Client is a PVSS Manager (PVSS00dim)  Correspondence: PVSS DPs  DIM Services Can be setup graphically via fwDIM panel Or via a script library  When setup When Server updates Service data goes into DP Writing to DP will send a DIM Command  Documentation at: http://www.cern.ch/lhcb-online/ecs/fw/FwDim.html

25 24.07.2006 Cédric Potterat - LPHE Monday Meeting 25 - parallel bus (8/16/32 bits) - I2C bus (4 distinct lines) - JTAG (3 chains) Server runs on embedded PC (i486 compatible,133 MHz). Access to 3 bus-types via Plx/PCI bridge to gluecard: Server is built on various software layers with the aim to hide as much as possible hardware complexity. (e.g. no need for users to read the docs of Tell1 components) - Ccpc server: A generic DIM server ( ccserv ) running in a credit-card PC, which allows access to all features of the CCPC/glue card including access to any chips over I2C, JTAG and parallel bus. CCPC – PVSS Interface: the server (S.Koestner)

26 24.07.2006 Cédric Potterat - LPHE Monday Meeting 26 CCPC – PVSS Interface: the Client fwCcpc provides:  Dim client (PVSS00dim)  control panels which can access every CCPC connected to the same Name Server (DIM_DNS_NODE)  Functions for reading, writing the registers of each type (I 2 C, LBUS,…)

27 24.07.2006 Cédric Potterat - LPHE Monday Meeting 27 fwHw (R. Ferrandes) All the TELL1 components are described as a type And TELL1 is build up with all these components

28 24.07.2006 Cédric Potterat - LPHE Monday Meeting 28 fwHw TELL1address TELL1 components structure Registers Register’s settings To subscribe all the registers of the selected component to the server

29 24.07.2006 Cédric Potterat - LPHE Monday Meeting 29 fwHw Scripts can be executed All the TELL1 board is now described in PVSS as a DPT, and complete TELL1’s can be created as DP (correct name, addresses…) according to the “ECS Interface Library User Guide” (H. Gong, A. Gong, H. Lei and G. Haefeli) (S. Koestner & C. Potterat)

30 24.07.2006 Cédric Potterat - LPHE Monday Meeting 30 TELL1 – Setup ~ 500 (commands) ~ 1000 (writings/readings) Client >% dns & Name Server (DIM_DNS_NODE = lphe1pc60) lphe1tell7 TCP/IP lphe1pc7 (windows) lphe1pc60 (linux) Server (ccserv)

31 24.07.2006 Cédric Potterat - LPHE Monday Meeting 31 TELL1 – PVSS Goals:  Create FSM to control all the TELL1’s (Rules, Panels) (S.Koestner)  Create Panels which can replace the “console_tell1 ”, which will be called from the FSM panels (C.Potterat)

32 24.07.2006 Cédric Potterat - LPHE Monday Meeting 32 FSM - State Diagram DAQ Domains: RUNNING ERRORUNKNOWN READY NOT_READY Start Configure Stop Reset Recover The possible states of the Tell1: From NOT_READY to READY the configuration of the Tell1 is done  a compilation of applying recipes, pulling trigger lines and hardcoded sequences on the server side, which is the main job. The transition from Ready to Running is less massive (e.g. enabling triggers). UNKNOWN appears if ECS control is lost (e.g. server crashes)

33 24.07.2006 Cédric Potterat - LPHE Monday Meeting 33 TELL1 – FSM 1st and basic FSM Panel to be used for the 1st test (in development)

34 24.07.2006 Cédric Potterat - LPHE Monday Meeting 34 The Actual Rates console_tell1

35 24.07.2006 Cédric Potterat - LPHE Monday Meeting 35 The Event Monitor Counters console_tell1

36 24.07.2006 Cédric Potterat - LPHE Monday Meeting 36 The Pedestals console_tell1

37 24.07.2006 Cédric Potterat - LPHE Monday Meeting 37 console_tell1 The Linear Common Mode Suppression's (LCMS) Average and Slope

38 24.07.2006 Cédric Potterat - LPHE Monday Meeting 38 The last 128 MEP in the MEP buffer, and all the information attached to. console_tell1

39 24.07.2006 Cédric Potterat - LPHE Monday Meeting 39 Global information about the TELL1, the server (ccserv) and PVSS components console_tell1

40 24.07.2006 Cédric Potterat - LPHE Monday Meeting 40 Outlook Continue to create panels to control or monitor the TELL1’s registers  PP and SyncLink FPGA (C.Potterat)  GBE, TTCRx and FEM (S.Koestner) Update the DP according to the latest ECS doc (C.Potterat) Provide a fwTELL1 component including the FSM, the ccpc client and all the current panels  http://lhcb-online.web.cern.ch/lhcb-online/ecs/PVSS_TELL1/default.html http://lhcb-online.web.cern.ch/lhcb-online/ecs/PVSS_TELL1/default.html (all the current versions and tutorials about fwCcpc, fwHw and TELL1’s FSM are available on this web page)

41 24.07.2006 Cédric Potterat - LPHE Monday Meeting 41

42 24.07.2006Cédric Potterat - LPHE Monday Meeting42 Back up

43 24.07.2006Cédric Potterat - LPHE Monday Meeting43 CCPC Client : how it works

44 24.07.2006 Cédric Potterat - LPHE Monday Meeting 44 PVSS Client (LBUS): Choose ccpc from the list of running servers Choose type (width) of local bus 32,16,8 bits Determines number of words (e.g. 4 bytes for 32 bit bus) to be read or written. ‘Data in’ (to be written) must have the exact size. Masked write operation can be defined (e.g. reset registers on fpga). leave empty if not required Indicates success of operation

45 24.07.2006 Cédric Potterat - LPHE Monday Meeting 45 PVSS Client (GBE): Gigabit Ethernet card accessed over a 16 bit bus. MAC registers however 32 bits. Interface to be used as if it were a 32 bit bus. (1 word = 4 bytes) The addresses to be given in the address field correspond to the addresses given in the Intel MAC data sheet (same functionalities as LBUS)

46 24.07.2006 Cédric Potterat - LPHE Monday Meeting 46 PVSS Client (I2C): Some hardware can just be written in pages (e.g. EEPROMs on Tell1 with a pagesize of 16 bytes) This will be respected on the server side. Leave empty if no pagesize is required. Combined: Subaddress and data is written in one go (usual). Separated: Subaddress is written first to pointer register. (it is the one you have to provide in the address field) Shift register: One byte has to be specified. This is shifted then by the server. (periodic pattern)

47 24.07.2006 Cédric Potterat - LPHE Monday Meeting 47 PVSS Client (JTAG): Number of bits to be shifted Indicates the state of the state machine. Data is shifted with the least significant bits first. Missing MSBs are replaced by zeros. Data must be a multiple of 2 to represent byte stream. Select JTAG chain

48 24.07.2006 Cédric Potterat - LPHE Monday Meeting 48 PVSS Client (GPIO): Interface to the 9 GPIO lines should be used just by experts only! (click and try could harm hardware) Declaring and enabling GPIO lines Apply value to GPIO lines (high, low) Get current status of GPIO lines

49 24.07.2006 Cédric Potterat - LPHE Monday Meeting 49 PVSS Client (Command): Emulates a shell on the Ccpc: Commandline tools of the ccpc can be launched to crosscheck the results obtained from the server. Everlasting commands like ‘ping’ are timed out after 10 seconds. Does not follow change of directories.

50 24.07.2006 Cédric Potterat - LPHE Monday Meeting 50 PVSS Client (Advanced): CONTROL scripts using the PVSS or framework libraries can be edited and executed directly.

51 24.07.2006 Cédric Potterat - LPHE Monday Meeting 51 PVSS Client (Advanced): Downloads firmware to EPC16 (pof and jam is provided) Actions for jam can be propagated. Loads FPGAs directly from EPC16 Content of the registers and memory blocks is written from the.cfg file to the FPGAs PS: Jumper can be set such that FPGAs can be programmed directly without EPC16!


Download ppt "24.07.2006Cédric Potterat - LPHE Monday Meeting1 PVSS for VELO and TELL1 at EPFL."

Similar presentations


Ads by Google