User guide for Muon shifter part 2 : control of LV, HV, TELL1 Preliminary version 9-July-08 (to be checked by Michela) I have.
Download
Report
Transcript User guide for Muon shifter part 2 : control of LV, HV, TELL1 Preliminary version 9-July-08 (to be checked by Michela) I have.
User guide for Muon shifter
part 2 : control of LV, HV, TELL1
Preliminary version 9-July-08 (to be checked by Michela)
I have simply put together the instructions (written by
Michela Lenzi) in the Muon Twiki page :
https://twiki.cern.ch/twiki/bin/view/LHCb/MuonCommi
ssioningHrdw
to have everything in ppt format
1
LV control
For any problem: contact M. Lenzi/G.Passaleva
To control LV you should:
Log on into lbts.cern.ch PC (online interface to
the rest of the world)
From lbts you make a remote desktop
connection to computer UI01
On UI01 you should look into 'MyComputer'
going trough G: -> online -> ecs -> muon ->
Shortcuts
Then you click on the shortcut of the pvss
project you need (LV side A or C, depending on
what you want to do).
2
LV control
PVSS project Developer: M. Lenzi
To start/stop pvss project please read the
instructions at
http://lblogbook.cern.ch/MUON/181
The PVSS project has its FSM and to
control anything you need, first of all, to
'take' privileges....
Then you can navigate the panels trough
the Quadrant and stations that you need to
work on.
3
Maraton issues
Experts: M. Lenzi, P. Ciambrone. For any hardware problem please
contact P.Ciambrone.
Sometimes the Maraton goes into a funny state: it shows errors that are
unlikely to be real hardware failures. In those cases you should carefully
check :
- that the OPC server is running correctly and the RCM is talking
communicating correctly
- that the communication btw the RCM and the Maraton is correct
OPC server restart can be done only with administrator privileges (ask M.
Lenzi)
To exit from real funny situation the following chain of actions has proved
to help:
turn off PVSS and OPC server Reboot RCM crate Restart PVSS and
OPC server Poer cycle the Maraton After each step you need to check
that the communication is going as expected.
Latest maraton known problem: last november! Since then everything is
running smoothly.
4
How to start/stop pvss projects
for HV, LV and Tell1
All the projects have been configured as services, so that they will start
automatically (included the FSM) after a reboot of the machine.
If you want to start/stop manually: (N.B. all projects run as muon_oper
and all the muon group has the permissions to start/stop projects, so you
can do from your account, you don't need to use my account)
for windows projects (MULVA01, MULVC01, MUHVA02, MUHVC02):
1) login using your account on the machine where the project runs
2) open the service+ tool panel
3) - to start the project: start the service ProjectName (e.g. MUHVA02) to stop the project: start the service ProjectName-Stop (e.g. MUHVA02Stop). Please, do not stop the project by stopping the service
ProjectName (use ProjectName-Stop to stop it cleanly).
4) log off from the machine and take the control of the project using the
shortcut to the project from the machine UI01
5
New instructions to start/stop pvss projects
for HV, LV and Tell1
for linux projects (MUDAQL1):
1) login using your account on the machine where the project runs
2) to start the project: type the command sudo /sbin/service pvss_mp start - to stop the
project: type the command sudo /sbin/service pvss_mp stop
3) log off from the machine and take the control of the project using the shortcut to the
project from the machine UI01 for linux HV PNPI projects (MUHVA01, MUHVC01): a special
script has to be used to start/stop the PNPI system, included the hvcard driver and Dim
server:
1) login using your account on the machine where the project runs and go in the directory
/localhost/pvss
2) to start: execute the script ./startPNPI to start the hostcard driver, the dim server and the
pvss project or execute the script ./startDimPVSS to start only dim server and pvss project.
- wait and be patience for a few minutes until you get the message "PNPI system
initialization finished" - to stop: execute the script ./stopPNPI to stop the hostcard driver, the
dim server and the pvss project or execute the script ./stopDimPVSS to stop only dim server
and pvss project.
3) log off from the machine and take the control of the project from UI01
see https://twiki.cern.ch/twiki/bin/view/LHCb/LinuxPvssAutoStartup and
https://twiki.cern.ch/twiki/bin/view/LHCb/WindowsPvssAutoStartup for more detailed
instructions.
6
Computers for control of LV, HV, Temp & Press
Item/Stat/side PCName SystemNumber SystemName ProjectName
T&P
LV/C
LV/A
HV/C
HV/C
HV/A
HV/A
MUDCS01w 270
MUDCSSEN MUDCSSEN
MULVC01w 210
MUDCSLVC MUDCSLVC
MULVA01w 211
MUDCSLVA
MUDCSLVA
MUHVC01 212
MUHVC01
MUHVC01
MUHVC02w 213
MUHVC02
MUHVC02
MUHVA01 214
MUHVA01
MUHVA01
MUHVA02w 215
MUHVA02
MUHVA02
The shortcuts that should be used can be found under :
g:\\online\ecs\shortcuts\MUON
7
UF/PNPI system operation (M. Lenzi)
Four recipes have been stored in the Configuration DB and can be applied
sending FSM commands: Go_STANDBY1, Go_STANDBY2, Go_READY, Reset:
COMMAND
Go_STANDBY1
V0Set (RDB)
(V)
V0Set (Master)
(V)
Ramp Up = 3V/s
2200
2400
Trip time = 1s
Ramp Dw = 50V/s
I0Set:
Go_STANDBY2
2400
2600
- 200uA (master channels)
- 1uA (gap channels)
Go_READY
2500
2700
Reset
0
0
- 3uA (4 gaps channels)
Contact me if you want
to change these
settings!
8
First instructions to start learning how to
operate the UF/PNPI system using PVSS
project:
1. Login on UI01 (windows)
machine in the LHCb online
cluster
2. Go to folder
G:\online\ecs\Shortcuts\MUON
and click on MUHVC01_UI_FSM
The panel in Figure will appear
3. Right-click on MUONPC_HV
9
4. Take the
control of the
project
Note: red locks mean that somebody else has the control: you
can monitor the status but you cannot operate the system
Please remember to release the control (ReleaseAll)
when you don’t need it anymore
10
5. Switch on masters with the command Go_STANDBY1
For experts only
(please contact
me before using)
11
Master operational panel:
12
6. wait until the state of PNPI_MASTERS is STANDBY1
7. send the command Go_STANDBY1 to one quadrant, e.g. Q3
13
Quadrant monitoring panel:
14
Station monitoring panel:
15
8. Wait until the state of Quadrant Q3 is STANDBY1
16
9. Send the command Go_STANDBY1 to the next quadrant, e.g. Q4:
17
10. Wait until Q4 is in state STANDBY1
11. Repeat the procedure from step 5 to step 10 for the commands
Go_STANDBY2 and then Go_READY
18
Region monitoring panel:
19
Chamber monitoring panel:
Vmon and IMon are stored
in PVSS archive DB
20
General remarks:
- Operate the system from UI01 machine: do not login on muhvc01
machine, do not start pvss, dim server, dns, etc. from your account
- Remember to release the control of the project before leaving
- Be patient: when you send a command, wait until the command has
been executed (and the FSM states have changed accordingly) before
sending further commands
- If you want to do more sophisticated operations, i.e. change recipe
settings, change archive DB settings, run auto-detection procedure for
masters, save/load master Id from Configuration DB, etc. please ask me:
do not try to do it by yourself before learning how to do it.
- If you see some problems please contact me so that I can investigate
immediately (it is hard to reproduce and understand a problem the day
after..)
21
- If you are not able to switch on channels, most of the times is because the
boards are off (solution: click on “Switch on all modules”)
Switch On/Off
all boards
22
HV control (CAEN)
CAEN & PNPI controls will be unified in a single control
structure.
Michela is working on this and will update the instruction file
when this integration will be completed.
23
Contact persons :
- Michela Lenzi
- Email: [email protected]
- Tel. +39 055 4572257
- Giovanni Passaleva
- Email: [email protected]
- Tel. +39 055 4572596
24