RHIC PS Controls
original document by jvz
last updated on 5/3/00 by am
Introduction
This document describes the management of RHIC PS software during the current
commissioning phase and contains general helpful description of the software.
System Status (as of 5/3/00)
-
Blue ring supplies
-
used with the beam
-
operations may need to start ( or stop and restart ) certain servers if
-
requested by PS group or
-
indicated by alarms on the RHIC Alarm Display
-
controls for blue supplies should be considered operational - call for
Controls help if PS group needs it
-
Yellow supplies
-
being used by PS group
-
operations may need to start ( or stop and restart ) certain servers if
-
requested by PS group or
-
indicated by alarms on the RHIC Alarm Display
-
controls for yellow supplies should be considered operational - call for
Controls help if PS group needs it
System Components
All the software components needed to manage the RHIC Power Supplies are
listed under the 'RHIC PS Testing...' menu in StartUp. This menu
includes user interface applications as well as servers.
Applications
-
psall - a tool for PS diagnostics and control. Work
with one building at a time. Displays PS status and currents.
-
Power Supply Monitor & Control ( psmac) - mainly used to displays
PS status. Offers quick overview of full system status which can
be expanded to show a more detailed view.
-
Power Supply Quench Reset - used by PS group for reset of QPA assemblies
after faults
-
PMViewer - Post mortem data viewer. Used to display data that
is captured by control system after PS faults. The system can also
capture PS ramp data on request. PS references and measurements can
be examined. This system is generally used by the PS group.
-
Snapshot Info - examine setup of the Snapshot/PM system
-
AlarmDisplay - a version of the AlarmDisplay with display filters
set up for PS testing
-
Sequencer - Blue and Yellow versions available. This drives
the whole ramping process. Instructions in the use of the sequencer
are included in the following sections.
Servers
Unless noted otherwise, all of these servers
should be started and stopped from StartUp as user mcr.
-
wfgManager - Blue & Yellow versions available. Must be
running to support ramping of any kind ( even here2inj or here2park operations
). If a wfgManager needs to be restarted, proper stopping and initialization
steps must be followed. An alarm will be displayed on the RHIC Alarm
Display if one of the wfgManagers stops running.
-
PSServer - reports PS status to psall and psmac applications.
Can be stopped and restarted without any special initialization procedure.
It sometimes fails and needs to be restarted (we're working on making it
more reliable)
-
MagnetMonitor - retrieves PS currents for the psall application.
It sometimes stops getting fresh information and the currents on psall
stop updating. The fix is to stop and restart the MagnetMonitor from
StartUp. No special initialization steps are required.
-
EventMonitor - used by the Sequencer to watch for event link events.
Can be stopped and started with StartUp.
-
snapshotServer - watches for PS faults or other events that can
trigger saving of PS data. Can be stopped and restarted without any
special initialization steps.
-
RampManager - supports editing of ramp files. Not needed for
the repetitive ramping that is being used for PS testing. Can be
stopped and restarted without any special initialization steps.
-
KnobManager - manage assignment of RTDL frames to logical 'knobs'.
Not available in StartUp yet.
-
cmLogServer - a message logging system used by some of the other
servers. Not available in StartUp yet.
Starting Ramping (used only during testing)
-
Work with the Wfg Manager pet page to bring supplies to injection level
-
Go to pet page:
-
RHIC / Ring / Magnets / wfgman for
Blue Ring
-
RHIC / Ring / Magnets / wfgman2 for Yellow Ring
-
Initialize wfg manager as described bellow
-
Reset sddsfile
-
to 'ramp1' for Blue wfgManager
-
to 'ramp4' for Yellow wfgManager
-
f any of the previous steps failed, check for problems in the system (
e.g. Is an FEC down? ) and try to correct the problem before proceeding.
Read the Error Recovery section below.
-
Click on 'Auxramp->here2park'
-
Click on 'Auxramp->here2inj'
-
Once power supplies are at injection, work with the Sequencer to start
ramping
-
Click on 'Start multi MiniRamp sequence'
Stopping Ramping (used only during testing)
Just uncheck the "Keep ramping" button in the Sequencer.
Initializing wfg manager
Click in sequence on the following buttons on the right side of the wfgman
pet page. Monitor the status of each step in the Message: field on
the pet page:
-
Init WFGs
-
Load saturation
-
Connect stop
-
Load Limits
Stopping and restarting wfg manager
Wfg Manager should be stopped from its pet page:
-
select Disconnect command from Disconnect menu,
-
select Die command from Disconnect menu.
After this wfg manager should be restarted from StartUp and initialization
steps in the section above should be followed.
Recovering from Errors
You may become aware of system problems due to alarms on the AlarmDisplay
or errors that appear in the Message: area on the wfgManager page.
wfgManager Errors Reported
Information needs to be added to this document to describe proper response
to errors reported by wfgManager. In many cases Message: field on the pet
page will describe the cause.
Common ones are:
-
not properly initializing wfg manger or not loading ramp file,
-
trying to execute command when wfgs are ramping,
-
problems with fec: Message field usually displays comTools message.
FEC Down
-
Stop ramping (see instructions above)
-
A special response is required for FECs 4b-ps1, 4b-ps2, and 4b-ps3.
The wfgs in these front ends drive RTDL frames that are used throughout
the system.
-
Inform PS group. If 4b-ps3 is being rebooted, inform RF group too.
-
Select disconnect from wfgManager pet pages
-
4b-ps1 - Disconnect from blue wfgman page
-
4b-ps2 - Disconnect from yellow wfgman page
-
4b-ps3 - Disconnect from both blue and yellow
-
Reboot FEC
-
Follow the wfg initialization steps in the Start Ramping section above
( note: It's ok to invoke those steps globally, the wfgManager will only
initialize those FECs that require initialization )
wfgManager Down
start the wfgManager from StartUp
Follow the wfg Initialization steps in the section above
PSServer, MagnetMonitor, EventMonitor, RampManager, snapshotServer down
-
Restart from StartUp. No initialization required
Currents Not Updating on psall
-
MagnetMonitor program should be stopped and restarted