PHOS DCS workshop 09122005

1
PHOS DCS workshop 09-12-2005

• Dieter RöhrichMatthias Richter
• Sebastian Bablok
• Department of Physics and Technology, University
  of Bergen, Norway

2
TOC

• DCS in Alice
• OPC PVSS
• DIM overview
• Front-End-Electronics in DCS
• Communication chain (overview)
• FedAPI
• InterComLayer (ICL)
• FeeServer
• ControlEngine (CE)
• Case study DCS board for LED controlling
• Outlook / next steps

3
TOC

• DCS in Alice
• OPC PVSS
• DIM overview
• Front-End-Electronics in DCS
• Communication chain (overview)
• FedAPI
• InterComLayer (ICL)
• FeeServer
• ControlEngine (CE)
• Case study DCS board for LED controlling
• Outlook / next steps

4
DCS in Alice
ECSFSM
Database
PVSS II
PVSS II OPC Client
PVSS II DIM Client
PVSS II OPC Client
...
control layer
DB
middle layer
Temp
field devices
LV
FEE(Dim server)
5
TOC

• DCS in Alice
• OPC PVSS
• DIM overview
• Front-End-Electronics in DCS
• Communication chain (overview)
• FedAPI
• InterComLayer (ICL)
• FeeServer
• ControlEngine (CE)
• Case study DCS board for LED controlling
• Outlook / next steps

6
DCS in Alice
7
OPC - PVSS
Example PVSS integration of the TPC,by Uli
Frankenfeld
8
TOC

• DCS in Alice
• OPC PVSS
• DIM overview
• Front-End-Electronics in DCS
• Communication chain (overview)
• FedAPI
• InterComLayer (ICL)
• FeeServer
• ControlEngine (CE)
• Case study DCS board for LED controlling
• Outlook / next steps

9
DIM overview
DIM Client
Request Service
DIM Name-Server - DIM_DNS_NODE
Service Info
Register Service
Subscribe to Service
Service Data
/
Commands
DIM Server
10
DIM overview

• Principle
• implements the client-server paradigm
• uses TCP/IP over ethernet as transportation layer
  
• needs unique identifiers (names) inside one DIM
  domain
• domain is determined by DimNameServer (one per
  DIM domain)
• DimNameServer surveys domain
• DimServer
• provides services (int-, float-, - values or
  complex data structures)
• updates services at subscribed clients (on
  change, on request, timed updated, )
• accepts commands
• DimClients
• subscribes to services
• sends commands to DimServer

11
TOC

• DCS in Alice
• OPC PVSS
• DIM overview
• Front-End-Electronics in DCS
• Communication chain (overview)
• FedAPI
• InterComLayer (ICL)
• FeeServer
• ControlEngine (CE)
• Case study DCS board for LED controlling
• Outlook / next steps

12
Front-End-Electronics in DCSControl and monitor
channels
Supervisory Layer
Load configuration data from file OR
database
Front-End Device Interface (FED)
Config. File
Control Layer
Config. DB
Front-End Electronics Interface (FEE)
Cmd / ACK Channel
Field Layer
Service Channel
Internal Bus Systems
Message Channel
13
Front-End-Electronics in DCSworking principle

• communication between functional layers based on
  DIM framework (Distributed Information
  Management System)
• a FEE subsystem is controlled by a
  Front-End-Electronics-Server (FeeServer)
• running on the DCS board embedded computer
• consists of a detector independent core and the
  ControlEngine(CE) carrying out device specific
  tasks
• collects and publishes monitoring data
• configures the Front-end electronics
• InterComLayer connects to all FeeServers of the
  PHOS
• collects, filters and transports monitoring data
• sends configuration data
• connects to configuration data base

14
Front-End-Electronics in DCSSoftware Interfaces
.
15
Front-End-Electronics in DCSComponents and
Interfaces
PVSS FED Client
FEE ROOT Debug GUI (ROOT framework)
FEE ROOT Client
USB connector
FEE Client
FED Client
FED API(DIM)
U2F API
FED API(DIM)
FEE API(DIM)
Configuration Database
DB API
FEE API(DIM)
RCU (Motherboard)
CE-RCU API
FEE-CE API
DCS board
16
TOC

• DCS in Alice
• OPC PVSS
• DIM overview
• Front-End-Electronics in DCS
• Communication chain (overview)
• FedAPI
• InterComLayer (ICL)
• FeeServer
• ControlEngine (CE)
• Case study DCS board for LED controlling
• Outlook / next steps

17
FedAPI
PVSS FED Client
control layer
FED API (DIM)

• Implementing components inside PHOS
• PVSS (as FedClient)
• InterComLayer (in its FedServer module)
• consists of DIM channels (commands, services)
• for details see http//alicedcs.web.cern.ch/aliced
  cs/Documents/
• Incoming commands (PVSS ? FedServer)
• ConfigureFERO (Configuration of front - end -
  electronics)
• target name list of tags
• ControlFERO (Control of front - end -
  electronics)
• target name data block
• ConfigureFeeCom (Configuration of
  FeeCommunication chain)
• command ID optional int value optional
  float value target name
• ControlFeeCom (Control of FeeCommunication
  chain)
• command ID optional tag target name

middle layer
FED Server
ICL
...
18
FedAPI
PVSS FED Client
control layer
FED API (DIM)
middle layer
FED Server

• Outgoing services (FedServer ? PVSS)
• Grouped Service channel(s)
• updated int value updated float value
  FeeService name
• Single service channel(s)
• updated int value updated float value
• Acknowledge channel(s)
• ACK / error-code (int) result data
• Message channel
• event type detector source
  description date
• unsigned int char4 char256
  char256 char20

ICL
...
19
TOC

• DCS in Alice
• OPC PVSS
• DIM overview
• Front-End-Electronics in DCS
• Communication chain (overview)
• FedAPI
• InterComLayer (ICL)
• FeeServer
• ControlEngine (CE)
• Case study DCS board for LED controlling
• Outlook / next steps

20
InterComLayer
FED Server
ICL
FeeClient
DB
FEE API
FeeServer

• fetches configuration data from DB
• distributes commands and configuration to
  FeeServers (DCS boards)
• collects monitored values of DCS board (temp,
  voltage, )
• log messages to the PVSS system and file (own
  and from FeeServers)
• communication based on DIM

DCS board
21
TOC

• DCS in Alice
• OPC PVSS
• DIM overview
• Front-End-Electronics in DCS
• Communication chain (overview)
• FedAPI
• InterComLayer (ICL)
• FeeServer
• ControlEngine (CE)
• Case study DCS board for LED controlling
• Outlook / next steps

22
FeeServer
FED Server
ICL
FeeClient
FEE API

• runs on the DCS boards
• cross-compiled for armLinux
• delivers configuration and command data via the
  ControlEngineto the front-end-electronics
  (supported by device driver)
• watchdog for executed commands
• monitors values (using a deadband to reduce
  network traffic)
• provides log messages to upper layers

23
TOC

• DCS in Alice
• OPC PVSS
• DIM overview
• Front-End-Electronics in DCS
• Communication chain (overview)
• FedAPI
• InterComLayer (ICL)
• FeeServer
• ControlEngine (CE)
• Case study DCS board for LED controlling
• Outlook / next steps

24
CE Access of Hardware Data Points
Update function
FeeServer ControlEngine
Hardware Data Point
Set function

• ControlEngine provides
• unified service handling
• handling two property functions per registered
  data point Update and Set
• setting of Data Point value through
  FEESVR_SET_FERO_DATA command group
• detector specific command group, command ids and
  implementation customizable
• PVSS can subscribe to Data Point service to
  read/monitor current value and send commands via
  InterComLayer, e.g. a 'Set value' command for a
  Data Point
• Set functions customized by detector group
  (detector specific part)

25
RCU ControlEngine/ GUI
FEE API(DIM)

• FEE configuration fully
• standard FEC monitoring
• fully specified command set e.g. CE commands,
  RCU commands,Data Point set commands, detector
  specific commands

RCU
CE-RCU API
FeeServer
FEE-CE API
CE
DCS board
DCS board/ FEE hardware
DCS computer
Fee Client
26
TOC

• DCS in Alice
• OPC PVSS
• DIM overview
• Front-End-Electronics in DCS
• Communication chain (overview)
• FedAPI
• InterComLayer (ICL)
• FeeServer
• ControlEngine (CE)
• Case study DCS board for LED controlling
• Outlook / next steps

27
Case study LED controlling (using the DCS board
to LED VME crate)
DCS
DCS board
VME crate (with LED controller boards)
LEDS
28
Case study LED controlling (using the DCS board
to LED VME crate)
ethernet connector
TTCrx
bus connectors
Trigger link
29
Case study LED controlling
FEE ROOT Debug GUI (ROOT framework)
PVSS(state control / archiving) FED Client
Archive Database
FEE ROOT Client
FED Client
FED API(DIM)
FED API(DIM)
LED - control system
LED CE - API
FEE-CE API
DCS board
30
Case study LED controllinghardware architecture
ethernet
DCS board
LED - control system
Linux
devicedriver
custom bus
31
Case study LED controllingsoftware
infrastructure
FED API(DIM)
LED CE - API
DCS board
Linux
LED - control system
devicedriver
FEE-CE API
32
TOC

• DCS in Alice
• OPC PVSS
• DIM overview
• Front-End-Electronics in DCS
• Communication chain (overview)
• FedAPI
• InterComLayer (ICL)
• FeeServer
• ControlEngine (CE)
• Case study DCS board for LED controlling
• Outlook / next steps

33
Outlook / next steps

• Adapting ControlEngine for PHOS - most parts
  can be taken from TPC
• Connection of FedServer - module (InterComLayer)
  to PVSS - FedAPI
• Data for Configuration Database - structure
  and construction, - expected data volume per
  configuration
• Usage of DCS board as controller in LED-VME crate
  ???
• Performance tests

34
Thank you
and Merry Christmas !!!