HCAL DCS

1
HCAL DCS

• Shuichi Kunori
• U of Maryland
• 06-Mar-2006

2
HCAL Readout
Stefan Piperov
3
Configuration setting and read back by DCS
HCAL FE Parameters

• 3 main run modes
• Source calibration mode (HCAL partitioned, local
  R/O)
• Laser-to-HPD calibration mode
• Normal (beam) mode
• 132 RBX having 100 bytes of settings each
• TTC Rx
• lt32 bytes of setting, not used now
• 4 RMs having
• 18 FE channels with 3 bit pedestal 5 bit delay
• HV and BV for HPD (10 bit each)
• This gives 13.2 Kbytes per run mode or
• In total 3132100 lt 50 KBytes

Store the setting and read back in Conditions DB
per run.
4
HCAL Monitor by DCS
Information from Segej Sergueev
   During the normal data taking the HCAL DCS
will monitor followingvalues   Per each
HPDHV, BV, Ihv, Ibv - single precision floats (4
bytes) ,1 byte of status.In total 17 bytes
108 RBXs 4 RMs 7344    Per each group of HF
PMTsHV, Ihv - single precision floats (4 bytes)
,1 byte of status.In total 9 bytes 48 (?)
groups 432 bytes   Per each RBXlow voltage
values LV1, LV2 - single precision floats (4
bytes),temperatures T1,T2,T3,T4,T5 - single
precision floats (4 bytes),CCM status error
bytes,In total 30 bytes 132 3960   Per
each HV module2 HV module status bytes In total
108482 312 bytes   This gives 12048 bytes
per measurement. Measurements could followwith
maximum rate 1 Hz.   I think we could suppress
this data flow by applying of the "Deadband"
filtering for data change (as it is called in
PVSS) by sendingonly data having difference from
previous measurement more than given"dead band"
value. For example if to apply 5 of "dead band"
we willreduce data flow more than 10
times.Regards    Sergej
HPD/PMT HV, LV QIE LV Temp. etc. 12kbytes/m
eas _at_ 1Hz max. 20Mbytes/day _at_ 1/60 Hz Not much
data, but it may pileup And never look
at Need to store them in different partition
for easy archival and removal.
5
Dataflow diagram
Tasks DB schema (Yuyi, G., Lee, L, Shuichi K.,
G.L.) XML Loader (Yuyi G., G. L.) DCS Monitoring
(Sergey. S., G.L.) C to Oracle interface (Fedor
R., G.L.)
6
HCAL DCS Architecture

• FNAL/JINR (Sergueev)
• Heterogeneous components drivers, OS, hardware
  protocols, trigger types are mostly different.
• Each system has a uniform interface with DCS
  through a DIM server (except LV)
• Expert clients for diagnostics, etc.
• PVSS JCOP FW as main control toolkit

RCMS
Local Run control
Central DCS (PVSS)
SOAP?
HCAL DCS (PVSS)
OPC client
DIM client
LV Laser Source
HV ..
7
Communication Hardware
RS422 interface

Host PC


Commercial RS422 fan-out


RS422
RS422

2 RS/RS custom hubs per HB-,HB,HE-
CCM in RBX
8
HCAL infrastructure HW

• HV power supply monitoring
• LV power supplies monitoring
• LV tº on-board monitoring
• LED calibration
• Charge injection calibration
• Parameter downloading
• Source calibration
• Laser calibration
• HF radiation monitoring

RBX parameters DB
Laser
HV
LV1
?
Source motor drivers
RadMon
HV
9
CCM structure
Command

Response

Reset

Line Power

Optocouplers
Voltage
regu
lator



To ROBOX power supply

FPGA

Serial link core

• CCM
• Bipolar FPGA
• Optically insulated interface
• Up to 16 analog inputs
• 8 bit ADC
• I2C interface
• Digital I/O

Control



Digital outputs
Digital inputs
Channel
Input
Output
Address
registers

registers

register

I2C core



ADC

Multiplexer

Controls board

Analog inputs
Internal RBX serial bus
10
Control Clock Monitor
PZT222A Transistor (3 total)
TTCrx
ACTEL FPGA A54SX32A
ACTEL FPGA A54SX72A
LV Regulator (7 total)
Temp Sensor AD570
OpAmp OP184
FRAM (Ramtron Tested)
RS 485 DS36276 (3 total)
Optocoupler 6N134
QPLL (2 total)
Analog MUX ADG 706
MC100VELT22 CMOS diff LVPECL (7 total)
AD670 8-bit A/D (Analog Devices Tested)
MC100LVEP111 (2 total)
11
RS/RS Custom Hub
ACTEL FPGA A54SX32A
LV Regulator (2 total)
PZT222A Transistor
OpAmp OP184
QPLL1
LVDS Receiver DS26LS32 (3 total)
LVDS Driver DS26LS31 (5 total)
12
Custom Hub
13
RBX parameters

• FNAL/JINR ( Sergueev)
• Hardware custom hubs, CCM
• 3 main run modes (source,laser,beam)
• 132 RBX having 100 bytes each (TTC Rx,
  pedestal, delay, HV, BV
• This gives 13.2 Kbytes per run mode
• Server/clients tested at H2/SX5
• Configuration tool, tester, debugger

14
CCM configuring tool
15
Map/Delay editing tool
16
V,I,Temperature monitor

• 6 Temp Sensors
• 2 V, 2 I
• CCM digitizes
• Read out through RS links
• Available to expert clients and DCS via DIM for
  status, trending and alarms

17
Migration to PVSS

• FNAL/JINR ( Sergueev)
• Define partitions (hierarchy)
• FSM tools (state definitions/transitions)
• Start development Jan 05
• HCAL dedicated integration Feb05
• Functioning prototype by Jun 05
• Ready for the slice/magnet test in common mode

18
Hardware Partitions
By detector
HCAL DCS SV
HE
HB
HF
HO
IS
HF-
HF
HB-
HB
HO2-
HO1-
HO01
HO02
HO1
HO2
RoCr1
RoCr12
RBX1
RBX18
HV1
HV18
RBX1
RBX6
RM1
RM4
Map
Core1
Core4
Map
LV1
LV2
LV1
LV2
CCM
Calib
HV
BV
tº
19
Hardware Tree
20
Logical FSM Partitions
HCAL DCS SV
By trigger sector
HBEa
HBEb
HBEc
HF
HO
IS
HF-
HF
HE-
HB-
HB
HE
HV
CCM
RAS
RoCr1
RoCr12
RBX1
RBX6
HV1
HV18
RM1
RM4
Map
Core1
Core4
Map
LV1
LV2
LV1
LV2
CCM
Calib
HV
BV
tº
HBEa,b,c 120 degree trigger sectors IS
InfraStructure (source, laser, cooling..)
21
Logical/FSM
22
HV monitoring

• FNAL/JINR ( Sergueev )
• Custom PS for HVBV and for HF PMTs (2 types of
  HV module)
• HOHBHE-108 RBXs, 18 HV PS crates
• HF 72 channels,2 HV PS crates
• RS-485 communication
• DIM Server/Client tested
• Monitoring exercised at H2
  

23
HCAL DCS states

• Signals
• Commands
• LV status
• HV status
• FE status

• Wait
• Error detected
• Load cmd
• Off cmd

• Wait lt 10s
• Finished
• Timed-out

Standby
FE loading
Off
On

• Wait
• Standby cmd

Error

• Wait
• Error detected
• Off cmd
• Standby cmd

• Panic Error
• Severe Error
• Error

24
Error states

• Error from
• On trip detected
• Load time-out or HV trip
• Standby LV/HV trip
• Exit to
• Standby trip RBX not loaded
• Off severe error
• On trip RBX loaded

--- without a command.
Signals FE error LV trip HV trip Out of
tolerance?
Standby
Load
On
off
Off
FE error
HV error1
LV error
HV error2
LVHV error
Panic error
Automatic action - Off
25
Common and partitioned modes
Local run control
CMS run control
Central DCS
DAQ
?
Status
?
supervisor
Commands
CMS Infrastructure (racks, cooling, etc)
HCAL
ECAL
Muons
HO
HF
HB
HE
HCAL infra-struct.
HE
HE-
Wedge1
Wedge18
PVSS II JCOP FW
Laser
RM1
RM4
Source
HV,LV,T,Params
Commands,Status
26
Communications Hardware Status

• Rocket ports All delivered, install as needed.
• Custom Hubs All delivered, installed at HE-
• LAN Cables delay of CERN delivery
• RBX/CCM - done for HE-
• HV - Install as needed
• LV - CANbus Interlock (use LAN cables) done for
  HE-
• Other HE- only
• Patch panels in development
• RA source controller to drives, cables
  installed.
• Laser fibers installed

27
Software Status

• Jan 05 replace C emulator with PVSS
• DIM communication with Run Control
• RBX parameters (local config DB)
• RBX T,V
• HV
• Feb 05 state definitions and dedicated HCAL
  integration
• Feb 05 source driver DIM servers in C
• Dec 04 laser DIM servers in BC
• Mar 05 source control in PVSS (July)
• Apr 05 laser control in PVSS (July)
• May 05 LV control/monitor in PVSS (Nov)
• Jun 05 HCAL DCS Integration with JCOP FW (HV,
  FE), completed

28
Plans/Issues

• Systems need exercising soon.
• Debugging hardware and/or software?
• How to run in partitioned mode?
• Integration of components with new RC