Difference between revisions of "NikhefVeloTasks"
Jump to navigation
Jump to search
Line 6: | Line 6: | ||
* maintain SmsVacTool script and start it in Neon periods (running on vedcs02) | * maintain SmsVacTool script and start it in Neon periods (running on vedcs02) | ||
* check APDP in Neon periods (velo_user_panel) | * check APDP in Neon periods (velo_user_panel) | ||
− | * change status to ready for beam to ECS after interventions by the CERN vacuum group | + | * change status to ready for beam to ECS after interventions by the CERN vacuum group (?) |
== Motion ([https://lbtwiki.cern.ch/bin/view/VELO/VELOOperatingManuals#Motion_Closing twiki], [https://edms.cern.ch/ui/#!master/navigator/project?P:1380376323:1507145775:subDocs EDMS] == | == Motion ([https://lbtwiki.cern.ch/bin/view/VELO/VELOOperatingManuals#Motion_Closing twiki], [https://edms.cern.ch/ui/#!master/navigator/project?P:1380376323:1507145775:subDocs EDMS] == |
Revision as of 12:35, 15 December 2016
Vacuum (twiki, EDMS)
- answer questions of and perform discussions with the CERN vacuum group about the new vacuum control system (Rodrigo Ferreira, Giuseppe Bregliozzi, Paulo Gomes, Henrik Vestergard)
- maintain SmsVacTool script and start it in Neon periods (running on vedcs02)
- check APDP in Neon periods (velo_user_panel)
- change status to ready for beam to ECS after interventions by the CERN vacuum group (?)
Motion (twiki, EDMS
- perform potmeter calibration: WinCC-panel, data-analysis, upload results to motion-PLC (see manual) how often?
- discussions with CERN PH-DT group on the new motion control system (Giovanna Lehmann, Xavier Pons and Sylvain Ravat; (link to meeting)
- put detectors in place before/after Neon periods (see e.g. elog before, elog after)
Cooling (twiki, EDMS)
- be able to put CO2-pumps under gas for pump maintenance (see EDMS manuals, one for each pump)
- theory and practice: sub-cooling on input of pump, control PLC-screen, make and interprete trend plots, superheated CO2 (?), preheaters, SMS tool
- special plots for TL-pump (monitor TL_Diffp_plus in trending tree of velo_user_panel)
- check long-term behaviour of system (best: sensor NTC temperatures; simplest: coockie temperatures) , e.g. to reduce risks of thermal runaway (if cooling becomes worse we probably loose pressure due to clogged filters; watch pt104 and pt003 in vecool)
- maintain alarm levels in the alert system (PLC?)
- be standby 365, 24/5 to react when system switches to backup, or if anything else goes wrong
- maintain telephone numbers in PLC sms tool
- lend assistance to Seicar for chiller maintaince (phone, e-mail?)
- put system in correct state before/after Neon (setpoints, interlock, see elog)
- keep track of TinyTags data and dry air flow
- order spare parts and coordinate maintenance and repair
Common vacuuum/motion/cooling
- check UPS systems and maintain spares (?)
- maintain email lists of UPS systems (?)
- check VMC system after yearly AUG and diesel tests (?)
- update interlock settings before/after Neon period (see elog)
- take care of storage in Bld 169
- maintain manuals pages in VELO-twiki and EDMS documents
- participate in VELO run meeting on Tuesday morning
Velo upgrade
- co-coordination of WP5: keep track of anything that relates to modules such as sensors, readout, data tapes, markers, LV- and HV-cables, components (substrates, hybrids, ...)
- participate in module-0 meeting on Tuesday
- take care of wafer and glass parts in clean room storage at Nikhef