FOPI – Slow Control Content 1.FOPI experiment - Overview 2.GUIs for FOPI 3.System Design.

Post on 17-Jan-2016

221 views 0 download

Tags:

Transcript of FOPI – Slow Control Content 1.FOPI experiment - Overview 2.GUIs for FOPI 3.System Design.

FOPI – Slow ControlFOPI – Slow Control

Content1. FOPI experiment - Overview

2. GUIs for FOPI

3. System Design

FOPI - overviewFOPI - overview

CAVE BMesshütte

Server

WinXP-Client

Linux-Client

TCP/IP

CS

CS- GUI Objekte

- GUI Objekte

Esone Server

Ethernet – GPIB Controller

OPC Server(CAEN/TwinCAT)

Constant Fractions,

ca. 150 Stck.

Lambda, low-Voltage device

GPIB

CAEN - HV70 Channels

LeCroy – HV 1792

ChannelsCS -Interface Objekte

CAMAC

PT100 ca.

200Stck.

requirements for FOPI control systemrequirements for FOPI control system

- remote control and monitoring of power supplies (High/Low Voltage)

- archiving of measured values (voltage, currents, temperatures)

- archiving of hardware configuration/settings (ramp / trip time,

set points)

- distributed control system (Front End / Operator)

independant Front End

- User Management: several profiles access rights

- possibility to divide High Voltage channels into sectors

(RPC/CDC/Helitron)

- internal errors should be displayed for the user

- controlled and variable boot sequence

GUIs for FOPIGUIs for FOPI

FOPI Main PanelFOPI Main Panel

colour coding of LED

channel address of LEDshown by tip

statistic values

panel selection

• cross – section of the detector's drift chambers (CDC/RPC/Helitron)• mapping of CAEN HV channels

allocation between channels and sectors

• statistic values for each sector• panel selection allows user to open other panels• colour coding of LED informs user about channel's state• set all CAEN HV channels • display error history

RPC CDC Helitron

CAEN Power Supplies 1527& PT 100 sensors

channel state

channel output

password request

temperature of PT 100 sensor

detailled configuration

BoardInformation

• supplies RPC, CDC and Helitron• access via CAEN OPC server

and LabVIEW DSC Module• structure: crates/boards/channels• one PT 100 for each HV channel • user management by password

request (2 user profiles: admin/user)• additional board information• online trending for output values • background colour indicates

sector

area only visible afterarea only visible afterlogged in successfullylogged in successfully

area only visible afterarea only visible afterpush Board Infopush Board Info

Sector Panel for Sector Panel for CAEN HV channelsCAEN HV channels

double clickplot to openchannel panel

selection for sub detectors

- background colour indicates sector membership- allows user to open sub sector panels- set all channels mapped to sector- error history- colour of plot indicates alarm state

Trend, Alarm & Temperature Trend, Alarm & Temperature MonitorsMonitors

• displays trendings of measured and

configuration values access to log data of

DSC database via DSCTrend class

• editable time interval for trendings

• error display• divides High Voltage

channels by sectors

• Online - Trending oftemperature values

measured by PT 100• displays alarm state• variable update rate

• displays all occured alarms access to alarm data of DSC database viaDSCAlarm class

• displays alarm settings• unacknowledged alarms• generates alarm

documentation file• alarm summary

Lambda - Low Voltage devicesLambda - Low Voltage devicesFopi dedicated Mainpanel

• control of up to 5 Lambda – Genesys

• devices via GPIB bus

• supplies RPC detector

• use of the device - specific drivers

• possibility to auto - write all channels,

• archives voltage and current into a logfile

©A.Schwinn©A.Schwinn

Le Croy HV devicesLe Croy HV devices

• old hardware (1985)• control via ESONE Server on a

CAMAC Bus• very slow reaction time• output is written in output

buffer of the 2132 Interface

• device language is 16 Bit-coded and cryptic

• control of more than 1700 HV - Channels

• supply for photo - multiplier

©A.Schwinn©A.Schwinn

Constant FractionsConstant Fractions

• control of ca. 150 Constant Fraction "CF 8101" Discriminators

• control via ESONE Server on a CAMAC Bus

• CNAF´s are the CAMAC data words (Crate, Board, Address, Function)

• able to observe all values, and to recognize changes

• Enable/Disable boards to observe

• able to play a alarm-wav file on alarm

©A.Schwinn©A.Schwinn

System Design - overviewSystem Design - overview

hardware

server (device layer)

clients (application layer)

lxg0*.gsi.de lxi0*.gsi.de

GUI objects

kp1pc058.gsi.de

kp1pc065.gsi.deDSCEngine

CAENOPC - Server

DSC processes:-DSCInterface-DSCAlarm-DSCTagAttribute-DSCTrend-TwinCATInt

Lambda LV devices

CAEN SY1527HV

LeCroyHV

ESONE Serverse7_6e7_15

CAMAC

ESONE Dispatcher:

e7_6

e7_15

(Linux)

(Win XP)

(Linux)

GPIB

GENie Treiber

CS Frameworkcommercial softwarePCbus systems / networkshardware

GUI objectsGUI objects

device processes:- Constant Fractions

- LeCroy_2123_Interface

- Lambda_LV_Supplies

ConstantFractions

(Win XP)

Ethernet

TwinCATOPC - Server

BC9000 (PT 100)

SQL Server

Initializing the Slow ControlInitializing the Slow Control

channel address

temperaturesensor

sector path(layer2/layer3/…/lowest layer)

Default Alarm Limits (3)

profilepermission rangeUser List (2)

Mapping (5)

life line of object

event or action

length of stimulus

Client – Server communicationClient – Server communication

server client

Detector HierarchyDetector Hierarchy

channel layer

detector layerfixed

variable

m: number of sub detectors in HEL_nn: number of sub detectors in HELs: lowest layer of CDC

e.g. s = 0_0_0 depth = 5t: number of sub detectors

e.g. in lowest layer of CDC_0_0_0

x/y/z: any crate/board/channel number, depending on how many HV channels are used

Sub DetectorsSub Detectors

server client

filter Channels and UserList for sub detectors information concerning

the joining sectors (upper & lower layer) is needed

Panel BehaviourPanel Behaviour

client

CSCS requirements requirements

problem: DB entry with different parameters for each detector object ( fixed hierarchy)

solutions: a.) optional "data - in" parameter for "load process" – eventb.) class to create user- defined database entries by event

problem: DB entry for each channel object required ( truncate name.vi)solution: template DB entry as default for an object inherited by BaseProcess

additional parameter for load – process, e.g. „use default DB entry“ or „use database entry from instance“

Thanks for your attention!!!Thanks for your attention!!!