Experimental Areas Controls Review
 AB/CO Viewpoint
Vito Baggiolini
(on behalf of the CESAR team and several people in CO)
Color Code + Conventions
• Red:
already done or no problems anticipated
not yet 100% clear (potential non-critical
problem)
critical problem, to be addressed urgently
Vito Baggiolini AB/CO
• Green:
• Orange:
AB/CO Review 19.09.2005
2
Standard Controls (“StdCtrls”)
• CESAR uses Standard CO controls where possible
• Responsibilities:
– CO: tools / services / components + support
– Users (CESAR, BDI, OP): usage, configuration
AB/CO Review 19.09.2005
Vito Baggiolini AB/CO
– JAPC: Communication services to the equipment on top of
CMW
– Middle tier services (data concentrators & elaborators, APIs,..)
– On-line monitoring system for Logging, Fixed Displays,
Statistics, SDDS
– LHC Logging
– Laser Alarm system
– GUI building components (Java Dataviewer, Frame, beans,
knobs, working sets, ...)
– Console manager
– FESA, CMW, CMW-to-SL_Equip gateway
3
CESAR Project (Applications EA + CNGS)
• State at the end of Run 2004
–
–
–
–
Successfully tested in PCR, operationally used in West Area
Some functionality missing
Performance bottleneck
Need to adapt some parts to new “standard controls”
• Ongoing Work 2005/06
– Address the above points
– Adapt to external changes (migration to FESA, new timing,
new access system, new standard controls services, …)
– FTEs in 2004: 1.7 (CO/AP), 0.5 (ATB/EA), 3 2nd Jobs (OP/SPS)
– FTEs in 2005: 1.1 (CO/AP), 0.3 (ATB/EA)
– FTEs in 2006 (until startup): 2 (CO/AP), 0.3 (ATB/EA), ?? (OP/SPS)
CESAR Team is currently working on LEIR…
AB/CO Review 19.09.2005
Vito Baggiolini AB/CO
• Resources
4
Equipment control affecting CO:
For reference
Item
Eqpts
H/W
FESW
Role CO
New BDI eqpt-ortd HW
XSCI,FISC,
XDWC,
XION,SCAL
2005
FESA
Cesar
Lau’s
adaptations
New BDI eqpt-ortd HW
XCET
4Q05
FESA
New GUI
Dry r.2
New BDI eqpt-ortd HW
XEMC
1Q06
FESA
New GUI
start-up
VME-based CEDAR
XCED
mid-06
FESA
New GUI
3Q06
MAGEA *)
Power
supplies
OK
FESA?
Cesar Adapt
Dry r.2
Dry r.1
Continue till 2007 with existing SL-Equip/Nodal software
Eqpt Bus based HW
port to FESA
XWCA,
Position contr
(colls, tax, …)
as now
FESA
Cesar
adaptations
1Q07
In/out motorisations
e.g. ABSMIO
ok
FESA
PLC
FE softw,
Upgr GUI
Dry r.1
Other PLC-based items
e.g. IGOR
ok
FESA
PLC
FE softw,
New GUI
Dry r.1
Access control via PLC
Between CO and TS
Dry r.1
Vito Baggiolini AB/CO
VME EQ-bus master
Slide
Date
*) Decision in October 2005
AB/CO Review 19.09.2005
5
Equipment control affecting CO:
Item
Eqpts
H/W
FESW
For reference
Role CO
New BDI eqpt-ortd HW
XSCI,FISC,
2005
FESA
Cesar
CO implication well-defined
and
agreed
on:
XDWC,
adaptations
Date
Dry r.1
XION,SCAL
• Equipment converted
to FESA (or not yet supported by CESAR)
XCET
New BDI–eqpt-ortd
HW
4Q05
New team
GUI
Add functionality
or
adapt CESAR
systemFESA
 CESAR
Dry r.2
XEMC
New BDI–eqpt-ortd
HW
1Q06
FESA development
 Equipment
groupsFESA
New GUI
start-up
– Exception:
PLCs:XCED
First FESA implementation
VME-based
CEDAR
mid-06
FESA CO/FC,
New GUI
3Q06
MAGEA *)
Dry r.2
(maintenance  BDI/SW)
VME• EQ-bus
CO +master
CESAR
Power
supplies
OK
FESA?
Cesar Adapt
Continue till 2007
with existing
SL-Equip/Nodal software
do not implement
specialist
applications
XWCA,
as now
FESA
Cesar
standard
controls
solutions
 Equipment
Groups 1Q07
Position contr
adaptations

CO/AP
(colls, tax, …)
– BUT: Minor changes
in CESARok
GUIs where
usefulFEsoftw,
CESAR
e.g. ABSMIO
In/out motorisations
FESA
Dry r.1
Other PLC-based items
e.g. IGOR
ok
Access control via PLC
Between CO and TS
PLC
Upgr GUI
FESA
PLC
FE softw,
New GUI
Dry r.1
Dry r.1
Vito Baggiolini AB/CO
Eqpt Bus–based
HW
To be
done with
port to FESA
– Tools + Support
*) Decision in October 2005
AB/CO Review 19.09.2005
6
BDI expert and diagnostics software
Has been discussed extensively in two meetings between CO, Lau’s
BDI, EA, PO and OP,
organised by H.Schmickler (01/03 and 17/05).
Slide
This software will be based on 5 approaches, 3 of which involve CO:
No expert GUIs requested for PLC’s!
• Minor additions to CESAR GUIs
• Working sets & knobs (for PLC)
configuration of WS & knobs by BDI/EA
• Integration of Jython scripts into Cesar GUI
 BDI
 BDI/SW
 Cesar team
 CO
 CO
The VME equipment bus (and MAGEA?) will still use SL-equip and nodal in 2006,
but will be moved to FESA navigator and expert GUIS a.s.a.p. (for 2007?)
 Nodal is still required at least in 2006, CMW gateway to be stabilised !!
The FESA PLC software will be provided by CO/FC by October
Integration in common platform coordinated by BDI/EA with help from CO/AP
AB/CO Review 19.09.2005
Vito Baggiolini AB/CO
• FESA navigator (simple get/set/sub)
• FESA expert programs (incl. sequences of commands)
7
BDI expert and diagnostics software
Has been discussed extensively in two meetings between CO, BDI, EA, PO and OP,
organised by H.Schmickler (01/03 and 17/05).
This software will be based on 5 approaches, 3 of which involve CO:
No expert GUIs requested for PLC’s!
• Minor additions to CESAR GUIs  Agreed
• Working sets & knobs (for PLC)
configuration of WS & knobs by BDI/EA
• Integration of Jython scripts into Cesar GUI
on.
 BDI
 BDI/SW
 Cesar team
 CO
 CO
The VME equipment bus (and MAGEA?) will still use SL-equip and nodal in 2006,
but will be moved to FESA navigator and expert GUIS a.s.a.p. (for 2007?)
 Nodal is still required at least in 2006, CMW gateway to be stabilised !!
The FESA PLC software will be provided by CO/FC by October
Integration in common platform coordinated by BDI/EA with help from CO/AP
AB/CO Review 19.09.2005
Vito Baggiolini AB/CO
• FESA navigator (simple get/set/sub)
• FESA expert programs (incl. sequences of commands)
8
BDI expert and diagnostics software
Has been discussed extensively in two meetings between CO, BDI, EA, PO and OP,
organised by H.Schmickler (01/03 and 17/05).
This software will be based on 5 approaches, 3 of which involve CO:
 Nodal Support
• FESA
navigator
(simpleNodal
get/set/sub)
 BDI
 CO/IN
will support
language on HP-UX 10.20 through
2006
• FESA(But
expert
programs (incl.
sequences
of commands)
 BDI/SW
no piquet-style
support
can be provided)
No expert GUIs requested for PLC’s!
 Compatibility with new timing needs to be confirmed
• Minor
additions to CESAR GUIs
 Cesar team
CMW-to-SL_Equip
•Working
sets & knobsGateway
(for PLC)
 CO
configuration
of WSnow
& knobs
by BDI/EA
 CMW gateway
deployed
on each VME FE, “reliability should be OK”.
• Integration
of isJython
scripts
into CesarCO/FC
GUI needs to invest
 COwork on GW.
 If MAGEA
not ported
to VME/FESA,
The VME equipment bus (and MAGEA?) will still use SL-equip and nodal in 2006,
but will be moved to FESA navigator and expert GUIS a.s.a.p. (for 2007?)
 Nodal is still required at least in 2006, CMW gateway to be stabilised !!
The FESA PLC software will be provided by CO/FC by October
Integration in common platform coordinated by BDI/EA with help from CO/AP
AB/CO Review 19.09.2005
Vito Baggiolini AB/CO
(CMW gateway cannot be deployed on old PC-486 front-ends)
9
BDI expert and diagnostics software
Has been discussed extensively in two meetings between CO, BDI, EA, PO and OP,
organised by H.Schmickler (01/03 and 17/05).
This software will be based on 5 approaches, 3 of which involve CO:
No expert GUIs requested for PLC’s!
• Minor additions to CESAR GUIs
• Working sets & knobs (for PLC)
configuration of WS & knobs by BDI/EA
• Integration of Jython scripts into Cesar GUI
 BDI
 BDI/SW
 Cesar team
 CO
 CO
The VME equipment bus (and MAGEA?) will still use SL-equip and nodal in 2006,
 Agreed
but will be moved to FESA navigator and expert GUIS a.s.a.p. (for
2007?) on.
 Nodal is still required at least in 2006, CMW gateway to be
stabilised !!
(StdCtrls)
The FESA PLC software will be provided by CO/FC by October
Integration in common platform coordinated by BDI/EA with help from CO/AP
AB/CO Review 19.09.2005
Vito Baggiolini AB/CO
• FESA navigator (simple get/set/sub)
• FESA expert programs (incl. sequences of commands)
10
Applications for beam line operators,users:




Jython integration
Access control application program
Reading of Radiation monitors
Settings management
Lau’s
Slide
 Surveillance, alarms, fixed displays, teletext
 Long term maintenance and adaptation to new requirements
(apart from configuration – done by ATB-EA)
Very active participation of CO experts in commissioning,
tests and dry runs is essential
AB/CO Review 19.09.2005
Vito Baggiolini AB/CO
 Logging (surveillance, measurements,
set-actions)
 Printing of GUIs
 User documentation & Training for operators and EA+BDI experts
11
Applications for beam line operators,users:
Jython integration  new StdCtrls (CESAR, CO/AP, CO/IN )
Access control application program  adaptations (CESAR)
Reading of Radiation monitors  CESAR (StdCtrls, CO/AP)
Settings management  CESAR (functionality as in old Nodal System),
(additional requirements under discussion)  CESAR
 Surveillance  CESAR (StdCtrls, CO/AP),
alarms  LASER,
fixed displays  CESAR, (StdCtrls, CO/AP), teletext  old system (CO/IN)
 Logging (surveillance, measurements  LHC logging (StdCtrls, CO/DM),
set-actions CESAR)




 User documentation & Training for operators and EA+BDI experts
 CESAR
 Long term maintenance and adaptation to new requirements
(apart from configuration – done by ATB-EA)
Very active participation of CO experts in commissioning,
tests and dry runs is essential
AB/CO Review 19.09.2005
Vito Baggiolini AB/CO
 Printing of GUIs  StdCtrls (CO/IN) (OK for experimental physicists?)
12
Applications for beam line operators,users:




Jython integration
Access control application program
Reading of Radiation monitors
Settings management
 Surveillance, alarms, fixed displays, teletext
 Long term maintenance and adaptation to new requirements
(apart from configuration – done by ATB-EA)
Very active participation of CO experts in commissioning,
tests and dry runs is essential
AB/CO Review 19.09.2005
Vito Baggiolini AB/CO
Long term maintenance responsibility
 Logging (surveillance, measurements, actions)
• CESAR Control System Core  maintained and extended by CO/AP
 Printing of GUIs
• Technology upgrades  mostly CO (some details to be discussed)
 User documentation & Training for operators and EA+BDI experts
• GUIs  maintained and extended by OP/SPS, ATB/EA
• Configuration data (XML, Databases)  ATB/EA
13
Other CO responsibilities:
Lau’s
Slide
 Long term maintenance & support for all software under CO responsibility
 Timing with 5 events, that should ‘always’ be present (also for dry runs),
including VME hardware, software and support
 Tools to populate & maintain configuration database (AB/CO/DM)
 Transmission of beam line status to the users (“STDBLK, NSTDBLK”)
Vito Baggiolini AB/CO
 Provides and supports PC’s for CCC and areas
 Console manager
AB/CO Review 19.09.2005
14
Other CO responsibilities:
Vito Baggiolini AB/CO
 Long term maintenance & support for all software under CO responsibility
 Timing with 5 events, that should ‘always’ be present (also for dry runs),
including VME hardware, software and support
 discussed & agreed (CO/HT)
 Tools to populate & maintain configuration database (AB/CO/DM)
 Now implemented with MS Access, to be ported to standard technology
 Transmission of beam line status to the users (“STDBLK, NSTDBLK”)
 online monitoring + SDDS (StdCtrls, CO/AP), small additions to CESAR
 Provides and supports PC’s for CCC and areas  StdCtrls, CO/IN
 Console manager  StdCtrls, CO/AP
AB/CO Review 19.09.2005
15
EAST Area: Needs for 2006 and beyond:
All the needs we have for the North Area, apart from the
upgrade related items.
Lau’s
Slide
This includes:
Maintenance of existing software
Timing
PC configuration and maintenance in EBCR
Control consoles in CCC
However, the CCC is far from the East Area,
To be evaluated when
the lack of remote control becomes serious handicap.
request comes.
Instrumentation is very limited
 CO priorities?
At the EA day a controls upgrade
project will be presented for 2007
AB/CO Review 19.09.2005
the
Vito Baggiolini AB/CO




16
For reference
Lau’s
Slide
Equipment
#
Responsibility of CO
TBID
1
Read, log & display, fit,
orthogonal scans with magnets upstream the target
‘BLM’ (used as ion chambers)
2-4
Read, log & display
Horn/Reflector
1/1
On, Off, Reset, change current by max. 10%, change
polarity, grounding; switch valve (water cooling);
Read, log & display water cooling system parameters
Helium Tube
2
Read, log & display of Oxymeter
Shutter
1
Read, log & display position, move shutter for Access
Decay Tube
1
Read, log & display pressure
Muon Monitors
2 x (17-34 fixed +1 motorized)
36-70
Read, log & display intensity in each monitor, display
profiles; set or scan position of motorized monitor
Temp. Probes
40-56
Read, log & display
Timing + data interchange
GPS time stamp for every extraction, data interchange
between CERN and Gran Sasso
Alarms, Interlocks, ACCESS
AB/CO Review 19.09.2005
Vito Baggiolini AB/CO
CNGS Equipment Control:
17
For reference
CNGS Equipment Control:
Equipment
# Responsibility of CO
[Detailed analysis of requirements still ongoing]
TBID
1
Read, log & display, fit,
orthogonal scans with magnets upstream the target
Standard Controls Requirements
2-4 Read, log & display
• Read/Control  WorkingSets/Knobs (StdCtrls, CO/AP)
Horn/Reflector
1/1 On, Off, Reset, change current by max. 10%, change
• Display  Fixed Displays (StdCtrls, CO/AP)
polarity, grounding; switch valve (water cooling);
• Logging  Monitoring Service
(StdCtrls,
Read, log
& display CO/AP),
water cooling system parameters
LHC Logging
(StdCtrls,
CO/DM)
Helium Tube
2 Read,
log & display
of Oxymeter
• Profile display  Emittance/Profiles project (OP/SPS)?
Shutter
1 Read, log & display position, move shutter for Access
• Scan  CESAR
Decay
1 Read, 
log SPS/LHC
& display pressure
• Tube
Alarms  LASER, Interlocks
interlocks,
36-70
Access  SPS/LHC
access
Muon Monitors
Read, log & display intensity in each monitor, display
profiles;
set UNICOS
or scan position of motorized monitor
2 x (17-34
fixed +1 motorizedexpert
)
• Horn/Reflector
control
with
‘BLM’ (used as ion chambers)
40-56
Read, log & display
LHC Logging?
Alarms, 
Interlocks,
ACCESS (To be analyzed)
Vito Baggiolini AB/CO
Temp. Probes
AB/CO Review 19.09.2005
18
Special
Timing
+ data Requirements
interchange
•
GPS time stamp for every extraction, data interchange
and Gran
Sasso
Data exchange between between
CERN CERN
and Gran
Sasso
Conclusions
• Requirements for SPS-EA clear and well managed
– Good and solid collaboration
– No worries for Control System Core
– We need “our” CESAR GUI developers (from OP/SPS) in 1st half 2006
for new equipment and missing functionality + CNGS work
– Long-term maintenance clear, details to be defined
• East Area for 2007 not yet taken into account
• CNGS (secondary beamline)
• If we get “our” GUI developers and if LEIR work stops end of 2005,
we can handle Dry Runs, CNGS and SPS Operations in 2006.
AB/CO Review 19.09.2005
Vito Baggiolini AB/CO
– Good and promising collaboration
– Overall requirements understood (detailed analysis ongoing)
– No problems anticipated, mostly standard controls
19
Vito Baggiolini AB/CO
AB/CO Review 19.09.2005
20