Difference: VELOZapTest2008 (1 vs. 32)

Revision 322008-10-08 - PaulaCollins

Line: 1 to 1
 
META TOPICPARENT name="LHCbVELO"

OBSOLETE 2008 Zap Test Twiki Pages ..... GO TO NEW PAGES HERE

Line: 45 to 45
 VELO meeting 21 Dec 07 , LHCb week /VELO 23 Jan 08
Added:
>
>

PREVIOUS WORK

Here are selection of references on beam accidents and studies from other experiments - CMS stress test of modules * beamloss.pdf: CDF_beamloss

 

GEOMETRY OF SETUP

Module 48 is mounted sideways with Phi-sensor ZapTestSetup14Apr2008_thumb.jpgdownstream towards dump. It can be moved out of the beam line towards the right when looking downstream. Only two positions are possible: in or out. As of April 14, 2008, the module cannot be moved into the beam line, see here the arrangement. Only the attached extension with alumina view screen can go into the beam line. To see a high resolution picture of setup as of 14 Apr 2008, click on image

Line: 183 to 191
 
META FILEATTACHMENT attachment="runplan.pdf" attr="" comment="run plan for zap test" date="1215352012" name="runplan.pdf" path="\\cern.ch\dfs\Users\m\massi\Public\runplan.pdf" size="94947" stream="\\cern.ch\dfs\Users\m\massi\Public\runplan.pdf" user="Main.MassiFL" version="1"
META FILEATTACHMENT attachment="zaptest.pdf" attr="" comment="setup sketch for zap test" date="1215352402" name="zaptest.pdf" path="\\cern.ch\dfs\Users\m\massi\Desktop\zaptest.pdf" size="90171" stream="\\cern.ch\dfs\Users\m\massi\Desktop\zaptest.pdf" user="Main.MassiFL" version="1"
META FILEATTACHMENT attachment="VELO_data.htm" attr="" comment="Booster beam settings for VELO" date="1216740286" name="VELO_data.htm" path="VELO_data.htm" size="8998" stream="VELO_data.htm" user="Main.MassiFL" version="1"
Added:
>
>
META FILEATTACHMENT attachment="beamloss.pdf" attr="" comment="CDF_beamloss" date="1223456440" name="beamloss.pdf" path="\\cern.ch\dfs\Users\c\collinsp\Desktop\th\beamloss.pdf" size="262372" stream="\\cern.ch\dfs\Users\c\collinsp\Desktop\th\beamloss.pdf" user="Main.PaulaCollins" version="1"

Revision 312008-10-01 - MassiFL

Line: 1 to 1
 
META TOPICPARENT name="LHCbVELO"
Changed:
<
<

2008 Zap Test Twiki Pages

>
>

OBSOLETE 2008 Zap Test Twiki Pages ..... GO TO NEW PAGES HERE

  links: CERN home, LHCb home, Massi home, Zap Test Pictures, Zap Test electronic logbook

Revision 302008-09-30 - MassiFL

Line: 1 to 1
 
META TOPICPARENT name="LHCbVELO"

2008 Zap Test Twiki Pages

Revision 292008-09-18 - MassiFL

Line: 1 to 1
 
META TOPICPARENT name="LHCbVELO"

2008 Zap Test Twiki Pages

links: CERN home, LHCb home, Massi home, Zap Test Pictures, Zap Test electronic logbook

Changed:
<
<

WORK TO BE DONE

>
>

ZAP TEST 2009 GOALS AND MODIFICATIONS

  1. Agreement to carry on with zap test setup at PS Booster next year. Use winter shutdown to upgrade.
  2. Move Tell1 crate outside: 50m control cables with repeaters.
  3. Replace camera with a newer, better one.
  4. Add cooling for irradiated module.
  5. More diagnostics ?
    • trigger for bunch arrival ?
    • fast analog monitor of biasat Silicon and/or LV at the beetle ?
    • ...

WORK TO BE DONE (no longer valid... to be updated)

 
  1. make a precise run plan and procedure (Massi)
  2. make a Shot Sheet (Massi), to be filled in by the shifters, 1 sheet per shot

Revision 282008-07-22 - MassiFL

Line: 1 to 1
 
META TOPICPARENT name="LHCbVELO"

2008 Zap Test Twiki Pages

Line: 40 to 40
  Sketch of setup can be found here.
Added:
>
>

ZAP TEST DESK

The Zap Test Desk (control desk) is located in some obscure corner of the Booster 'salle electronique' 361-1-012.
 

CABLING

Power cables:

Line: 153 to 156
 
  • You can also get the display directly via http://ab-dep-op.web.cern.ch/ab-dep-op/vistar.php?usr=PSB, but then there is a larger and changing latency between the machine basic period and what you see in the Vistar. On the other hand, the web based display does show the header information (not the case for the console display).
  • PS Booster Control Room: 76671 (76672, ..., 76677)
  • Beam parameters are logged just for us! Only the 'massi' account has access to ssh massi@cs-ccr-dev1. The data are stored in the newest files /acc/java/data/psb/eqpsurvey/BTM_V*.xml_* (in fact BTM_VELO_PICKUP.xml_log* and BTM_Velo.xml_log*), but are not kept permanently. I will take care of castoring regularly. I also run a script on cs-ccr-dev1 which continuously copies the logfile tails to my public directory: ~massi/public/www/tmp. As lhcbvelo you can just type the command script '~/ZapTest2008/booster' and get these tails to see if it's updating properly.
Changed:
<
<
  • A table with the different settings generated on user MDPSB for the VELO high-rate test can be seen here.
>
>
  • A table with the different settings generated on user MDPSB for the VELO high-rate test can be seen here.
 
Line: 166 to 171
 
META FILEATTACHMENT attachment="shotsheet.pdf" attr="" comment="shot sheet for zap test" date="1215419830" name="shotsheet.pdf" path="shotsheet.pdf" size="147644" stream="shotsheet.pdf" user="Main.MassiFL" version="2"
META FILEATTACHMENT attachment="runplan.pdf" attr="" comment="run plan for zap test" date="1215352012" name="runplan.pdf" path="\\cern.ch\dfs\Users\m\massi\Public\runplan.pdf" size="94947" stream="\\cern.ch\dfs\Users\m\massi\Public\runplan.pdf" user="Main.MassiFL" version="1"
META FILEATTACHMENT attachment="zaptest.pdf" attr="" comment="setup sketch for zap test" date="1215352402" name="zaptest.pdf" path="\\cern.ch\dfs\Users\m\massi\Desktop\zaptest.pdf" size="90171" stream="\\cern.ch\dfs\Users\m\massi\Desktop\zaptest.pdf" user="Main.MassiFL" version="1"
Changed:
<
<
META FILEATTACHMENT attachment="VELO_data.mht" attr="" comment="" date="1216130247" name="VELO_data.mht" path="\\cern.ch\dfs\Users\m\massi\Desktop\VELO_data.mht" size="13717" stream="\\cern.ch\dfs\Users\m\massi\Desktop\VELO_data.mht" user="Main.MassiFL" version="1"
>
>
META FILEATTACHMENT attachment="VELO_data.htm" attr="" comment="Booster beam settings for VELO" date="1216740286" name="VELO_data.htm" path="VELO_data.htm" size="8998" stream="VELO_data.htm" user="Main.MassiFL" version="1"

Revision 272008-07-15 - MassiFL

Line: 1 to 1
 
META TOPICPARENT name="LHCbVELO"

2008 Zap Test Twiki Pages

Line: 153 to 153
 
  • You can also get the display directly via http://ab-dep-op.web.cern.ch/ab-dep-op/vistar.php?usr=PSB, but then there is a larger and changing latency between the machine basic period and what you see in the Vistar. On the other hand, the web based display does show the header information (not the case for the console display).
  • PS Booster Control Room: 76671 (76672, ..., 76677)
  • Beam parameters are logged just for us! Only the 'massi' account has access to ssh massi@cs-ccr-dev1. The data are stored in the newest files /acc/java/data/psb/eqpsurvey/BTM_V*.xml_* (in fact BTM_VELO_PICKUP.xml_log* and BTM_Velo.xml_log*), but are not kept permanently. I will take care of castoring regularly. I also run a script on cs-ccr-dev1 which continuously copies the logfile tails to my public directory: ~massi/public/www/tmp. As lhcbvelo you can just type the command script '~/ZapTest2008/booster' and get these tails to see if it's updating properly.
Added:
>
>
  • A table with the different settings generated on user MDPSB for the VELO high-rate test can be seen here.
 

-- MassiFL - 26 Mar 2008

Line: 163 to 166
 
META FILEATTACHMENT attachment="shotsheet.pdf" attr="" comment="shot sheet for zap test" date="1215419830" name="shotsheet.pdf" path="shotsheet.pdf" size="147644" stream="shotsheet.pdf" user="Main.MassiFL" version="2"
META FILEATTACHMENT attachment="runplan.pdf" attr="" comment="run plan for zap test" date="1215352012" name="runplan.pdf" path="\\cern.ch\dfs\Users\m\massi\Public\runplan.pdf" size="94947" stream="\\cern.ch\dfs\Users\m\massi\Public\runplan.pdf" user="Main.MassiFL" version="1"
META FILEATTACHMENT attachment="zaptest.pdf" attr="" comment="setup sketch for zap test" date="1215352402" name="zaptest.pdf" path="\\cern.ch\dfs\Users\m\massi\Desktop\zaptest.pdf" size="90171" stream="\\cern.ch\dfs\Users\m\massi\Desktop\zaptest.pdf" user="Main.MassiFL" version="1"
Added:
>
>
META FILEATTACHMENT attachment="VELO_data.mht" attr="" comment="" date="1216130247" name="VELO_data.mht" path="\\cern.ch\dfs\Users\m\massi\Desktop\VELO_data.mht" size="13717" stream="\\cern.ch\dfs\Users\m\massi\Desktop\VELO_data.mht" user="Main.MassiFL" version="1"

Revision 262008-07-08 - MassiFL

Line: 1 to 1
 
META TOPICPARENT name="LHCbVELO"

2008 Zap Test Twiki Pages

Line: 152 to 152
 
  • There is a fairly fixed and reproducible delay between the Vistar basic period of the machine and the actual arrival of the beam shot. I determined in a test on May 30 that the shot arrives about 1 basic period before the latter is appearing on the Vistar.
  • You can also get the display directly via http://ab-dep-op.web.cern.ch/ab-dep-op/vistar.php?usr=PSB, but then there is a larger and changing latency between the machine basic period and what you see in the Vistar. On the other hand, the web based display does show the header information (not the case for the console display).
  • PS Booster Control Room: 76671 (76672, ..., 76677)
Changed:
<
<
  • Beam parameters are logged just for us! Only the 'massi' account has access to ssh massi@cs-ccr-dev1. The data are stored in the newest files /acc/java/data/psb/eqpsurvey/BTM_V*.xml_* (in fact BTM_VELO_PICKUP.xml_log* and BTM_Velo.xml_log*), but are not kept permanently. I will take care of castoring regularly. I also run a script on cs-ccr-dev1 which continuously copies the logfile tails to my public directory: ~massi/public/www/tmp. As lhcbvelo you can just type the command alias 'booster' and get these tails to see if it's updating properly.
>
>
  • Beam parameters are logged just for us! Only the 'massi' account has access to ssh massi@cs-ccr-dev1. The data are stored in the newest files /acc/java/data/psb/eqpsurvey/BTM_V*.xml_* (in fact BTM_VELO_PICKUP.xml_log* and BTM_Velo.xml_log*), but are not kept permanently. I will take care of castoring regularly. I also run a script on cs-ccr-dev1 which continuously copies the logfile tails to my public directory: ~massi/public/www/tmp. As lhcbvelo you can just type the command script '~/ZapTest2008/booster' and get these tails to see if it's updating properly.
 

-- MassiFL - 26 Mar 2008

Revision 252008-07-08 - MassiFL

Line: 1 to 1
 
META TOPICPARENT name="LHCbVELO"

2008 Zap Test Twiki Pages

Line: 152 to 152
 
  • There is a fairly fixed and reproducible delay between the Vistar basic period of the machine and the actual arrival of the beam shot. I determined in a test on May 30 that the shot arrives about 1 basic period before the latter is appearing on the Vistar.
  • You can also get the display directly via http://ab-dep-op.web.cern.ch/ab-dep-op/vistar.php?usr=PSB, but then there is a larger and changing latency between the machine basic period and what you see in the Vistar. On the other hand, the web based display does show the header information (not the case for the console display).
  • PS Booster Control Room: 76671 (76672, ..., 76677)
Changed:
<
<
  • Beam parameters are logged just for us! Only massi has access via his 'massi' account by: ssh massi@cs-ccr-dev1. The data are stored in the newest files /acc/java/data/psb/eqpsurvey/BTM_V*.xml_* (in fact BTM_VELO_PICKUP.xml_log* and BTM_Velo.xml_log*), but are not kept permanently. I will take care of castoring regularly.
>
>
  • Beam parameters are logged just for us! Only the 'massi' account has access to ssh massi@cs-ccr-dev1. The data are stored in the newest files /acc/java/data/psb/eqpsurvey/BTM_V*.xml_* (in fact BTM_VELO_PICKUP.xml_log* and BTM_Velo.xml_log*), but are not kept permanently. I will take care of castoring regularly. I also run a script on cs-ccr-dev1 which continuously copies the logfile tails to my public directory: ~massi/public/www/tmp. As lhcbvelo you can just type the command alias 'booster' and get these tails to see if it's updating properly.
 

-- MassiFL - 26 Mar 2008

Revision 242008-07-07 - MassiFL

Line: 1 to 1
 
META TOPICPARENT name="LHCbVELO"

2008 Zap Test Twiki Pages

Line: 160 to 160
 
META FILEATTACHMENT attachment="ZapTestSetup14Apr2008.jpg" attr="h" comment="VELO Zap Preparation Setup as of 14-Apr-2008" date="1208174918" name="ZapTestSetup14Apr2008.jpg" path="ZapTestSetup14Apr2008.jpg" size="849849" stream="ZapTestSetup14Apr2008.jpg" user="Main.MassiFL" version="1"
META FILEATTACHMENT attachment="VELO_HIGHT_RATE.jpg" attr="" comment="2D view of module with screen as extension" date="1208514188" name="VELO_HIGHT_RATE.jpg" path="VELO_HIGHT_RATE.jpg" size="3664317" stream="VELO_HIGHT_RATE.jpg" user="Main.MassiFL" version="1"
Changed:
<
<
META FILEATTACHMENT attachment="shotsheet.pdf" attr="" comment="shot sheet for zap test" date="1215351720" name="shotsheet.pdf" path="\\cern.ch\dfs\Users\m\massi\Desktop\shotsheet.pdf" size="143701" stream="\\cern.ch\dfs\Users\m\massi\Desktop\shotsheet.pdf" user="Main.MassiFL" version="1"
>
>
META FILEATTACHMENT attachment="shotsheet.pdf" attr="" comment="shot sheet for zap test" date="1215419830" name="shotsheet.pdf" path="shotsheet.pdf" size="147644" stream="shotsheet.pdf" user="Main.MassiFL" version="2"
 
META FILEATTACHMENT attachment="runplan.pdf" attr="" comment="run plan for zap test" date="1215352012" name="runplan.pdf" path="\\cern.ch\dfs\Users\m\massi\Public\runplan.pdf" size="94947" stream="\\cern.ch\dfs\Users\m\massi\Public\runplan.pdf" user="Main.MassiFL" version="1"
META FILEATTACHMENT attachment="zaptest.pdf" attr="" comment="setup sketch for zap test" date="1215352402" name="zaptest.pdf" path="\\cern.ch\dfs\Users\m\massi\Desktop\zaptest.pdf" size="90171" stream="\\cern.ch\dfs\Users\m\massi\Desktop\zaptest.pdf" user="Main.MassiFL" version="1"

Revision 232008-07-06 - MassiFL

Line: 1 to 1
 
META TOPICPARENT name="LHCbVELO"

2008 Zap Test Twiki Pages

Line: 7 to 7
 

WORK TO BE DONE

Changed:
<
<
  • Install labview to control IV scans (Jan B)
  • Install labview to control one radmon sensor continuously (Jan B, Maurice Glaser)
  • Set up delays (help from Olaf B, week 28 Apr - 2 Mar) STARTED
  • Write down initial values of LVPS currents (before any irradiation on sensors)
  • Take reference IV scans
>
>
  1. make a precise run plan and procedure (Massi)
  2. make a Shot Sheet (Massi), to be filled in by the shifters, 1 sheet per shot
  3. install labview control for IV scans (Jan)
  4. make 'continuous' the labview monitoring for Radmon (Jan)
  5. finalize digitization delay scan (and produce optimal parameters) (Olaf)
  6. make tell1.cfg file (for tell1_daq) and/or python script for easy data-taking .
    • We will take noise runs of ~10k events with a single pulsed channel (last channel, #127) per Beetle.
    • check that ch127 are never a bad channel
    • Remember: we power up the 16 R and the 16 Phi chips, but we only read out 8 R (0 to 7) and 8 Phi chips (8 to 15), hence need only to config those (minimize heat dissipation).
    • Would be handy to have a single command for taking such a file (with a time-stamped filename).
  7. make online analysis macro to display average noise vs electronics channel, TP distribution for ch127 (with averages and rms). Any more ideas welcome that could help seeing online if there is an effect of the beam shot in the detector.
  8. re-install Tell1+crate and ECS mezzanine (Massi+Jan)
    • test motion, check camera image
    • take final pictures of setup
    • take pictures of LVPS front when module powered
    • close and strengthen shielding
    • write down data cable connectivity
  9. take and check data during installation
  10. take reference IV scans
 

MOTIVATION

Line: 24 to 38
 

Module 48 is mounted sideways with Phi-sensor ZapTestSetup14Apr2008_thumb.jpgdownstream towards dump. It can be moved out of the beam line towards the right when looking downstream. Only two positions are possible: in or out. As of April 14, 2008, the module cannot be moved into the beam line, see here the arrangement. Only the attached extension with alumina view screen can go into the beam line. To see a high resolution picture of setup as of 14 Apr 2008, click on image

Added:
>
>
Sketch of setup can be found here.
 

CABLING

Line: 145 to 160
 
META FILEATTACHMENT attachment="ZapTestSetup14Apr2008.jpg" attr="h" comment="VELO Zap Preparation Setup as of 14-Apr-2008" date="1208174918" name="ZapTestSetup14Apr2008.jpg" path="ZapTestSetup14Apr2008.jpg" size="849849" stream="ZapTestSetup14Apr2008.jpg" user="Main.MassiFL" version="1"
META FILEATTACHMENT attachment="VELO_HIGHT_RATE.jpg" attr="" comment="2D view of module with screen as extension" date="1208514188" name="VELO_HIGHT_RATE.jpg" path="VELO_HIGHT_RATE.jpg" size="3664317" stream="VELO_HIGHT_RATE.jpg" user="Main.MassiFL" version="1"
Added:
>
>
META FILEATTACHMENT attachment="shotsheet.pdf" attr="" comment="shot sheet for zap test" date="1215351720" name="shotsheet.pdf" path="\\cern.ch\dfs\Users\m\massi\Desktop\shotsheet.pdf" size="143701" stream="\\cern.ch\dfs\Users\m\massi\Desktop\shotsheet.pdf" user="Main.MassiFL" version="1"
META FILEATTACHMENT attachment="runplan.pdf" attr="" comment="run plan for zap test" date="1215352012" name="runplan.pdf" path="\\cern.ch\dfs\Users\m\massi\Public\runplan.pdf" size="94947" stream="\\cern.ch\dfs\Users\m\massi\Public\runplan.pdf" user="Main.MassiFL" version="1"
META FILEATTACHMENT attachment="zaptest.pdf" attr="" comment="setup sketch for zap test" date="1215352402" name="zaptest.pdf" path="\\cern.ch\dfs\Users\m\massi\Desktop\zaptest.pdf" size="90171" stream="\\cern.ch\dfs\Users\m\massi\Desktop\zaptest.pdf" user="Main.MassiFL" version="1"

Revision 222008-07-01 - MassiFL

Line: 1 to 1
 
META TOPICPARENT name="LHCbVELO"

2008 Zap Test Twiki Pages

Line: 102 to 102
 

TAKING RADMON DATA

Changed:
<
<
  • Important: always connect back the sensor to the GND banana after your measurement. Some radmon sensors have a very different sensitivity to integrated dose when left floating! They must be short-circuited in order to match the calibration curve!
  • By labview control:
    • gfgf
>
>
  • Important: always short the radmon sensors to the GND after your measurement. Some radmon sensors have a very different sensitivity to integrated dose when left floating! They must be short-circuited in order to match the calibration curve!
  • By Labview control:
    • connect the radmon and NTC cat7 cables to the two cat7 Agilent34970A inputs (cables are labeled).
    • start C:\PH-Radmon-Acq Folder\PH-Radmon-Acq.vi, click up-left white arrow, load Velo_rad_ntc.txt (in C:\PH-Radmon-Acq Folder\SM config\TOTEM), press start button. When it is finished, it goes to Cmpl voltage, then press stop.
    • IMPORTANT: Now you must start another labview program, C:\PH-Radmon-Acq Folder\hp34970a\hp34970a_all_CLOSE.vi. Press left-upper white arrow once. This will ensure that the switches in Agilent34970A are all set to ground teh radmon sensors.
    • The data you have just taken are appended to the files in C:\PH-Radmon-Acq Folder\data\VELO\Board_160, e.g. PH_CMRP_5.txt.
 
  • Manual operation:
Added:
>
>
    • connect the radmon cat7 to the radmon banana box, such that all sensors are shorted to GND.
 
    • Pt100, C1-REM and C2-LAAS are all done with a fixed source current and quite long powered-up time. Just configure the Keithley to give the desired source current, then connect the corresponding sensor into the Keithley (labeled Radmon) and measure the voltage.
    • Pt100: 10 s at 1 mA
    • C1-REM: 2 s at -0.16 mA
Line: 123 to 127
 
      1. start sweep by pressing SWEEP : this takes a very quick sweep, less than 1 s
      2. data is retrieved by pressing RECALL and toggling with the up/down arrows
    • If the data points look correct (3 points at about 50 to 100 ms intervals) connect the sensor cable and take a real SWEEP. Write down Time, Voltage and Current of each of the three points.
Changed:
<
<

>
>
    • Measure each sensor sequentially, one by one.
    • IMPORTANT: after your manual measurement of each sensor always connect back the sensor to the GND banana. * For the NTCs, connect the cat7 to the NTC banana box and trivially measure the resistance of the four NTCs.
 

Machine interface

  • I defined the alias 'psb' to run the PSBooster Vistar (javaws _NOCLICK_http://abwww.cern.ch/ap/dist/psb/psb-fixdisplay/PRO/PSBFixedDisplay.jnlp) which allows to view the machine cycle: it highlights the 'basic period number' (BPNM) that the machine is executing (what beam sent where). This Vistar only works if you login to pcvelo01 as velo.

Revision 212008-07-01 - MassiFL

Line: 1 to 1
 
META TOPICPARENT name="LHCbVELO"

2008 Zap Test Twiki Pages

Line: 103 to 103
 

TAKING RADMON DATA

  • Important: always connect back the sensor to the GND banana after your measurement. Some radmon sensors have a very different sensitivity to integrated dose when left floating! They must be short-circuited in order to match the calibration curve!
Changed:
<
<
  • Currently done semi manually:
>
>
  • By labview control:
    • gfgf
  • Manual operation:
 
    • Pt100, C1-REM and C2-LAAS are all done with a fixed source current and quite long powered-up time. Just configure the Keithley to give the desired source current, then connect the corresponding sensor into the Keithley (labeled Radmon) and measure the voltage.
    • Pt100: 10 s at 1 mA
    • C1-REM: 2 s at -0.16 mA
Line: 121 to 123
 
      1. start sweep by pressing SWEEP : this takes a very quick sweep, less than 1 s
      2. data is retrieved by pressing RECALL and toggling with the up/down arrows
    • If the data points look correct (3 points at about 50 to 100 ms intervals) connect the sensor cable and take a real SWEEP. Write down Time, Voltage and Current of each of the three points.
Changed:
<
<
  • Future: labview will handle this.
>
>
 

Machine interface

Revision 202008-06-05 - MassiFL

Line: 1 to 1
 
META TOPICPARENT name="LHCbVELO"

2008 Zap Test Twiki Pages

Line: 93 to 93
 

RUN INSTRUCTIONS

Added:
>
>
  • Make sure the PSB data is being logged (see below under Machine interface). Make a backup if needed (!!details!!).
 
  • Take an IV scan from 0 to 300 V before and after every action (with LV off, for temperature reproducibility).
  • Write down NTC value.
  • Read out all Radmon sensors and put back short-circuit.
Changed:
<
<
  • whenever there is a reasonably long access (> 15 minutes), try reading out the LVPS voltages and currents.
  • when taking a beam shot, write down where the shot hits the view screen (using the grid letter-numbering, be as precise as you can)
>
>
  • Whenever there is a reasonably long access (> 15 minutes), try reading out the LVPS voltages and currents with Beetles configured and unconfigured.
  • When taking a beam shot, write down where the shot hits the view screen (using the grid letter-numbering, be as precise as you can)
 

TAKING RADMON DATA

Line: 129 to 130
 
  • There is a fairly fixed and reproducible delay between the Vistar basic period of the machine and the actual arrival of the beam shot. I determined in a test on May 30 that the shot arrives about 1 basic period before the latter is appearing on the Vistar.
  • You can also get the display directly via http://ab-dep-op.web.cern.ch/ab-dep-op/vistar.php?usr=PSB, but then there is a larger and changing latency between the machine basic period and what you see in the Vistar. On the other hand, the web based display does show the header information (not the case for the console display).
  • PS Booster Control Room: 76671 (76672, ..., 76677)
Changed:
<
<
  • Beam parameters are logged just for us! Only massi has access via his 'massi' account by: ssh massi@cs-ccr-dev1. The data are stored in the newest files /acc/java/data/psb/eqpsurvey/BTM_Velo.xml_* , but are not kept permanently. I will take care of castoring regularly.
>
>
  • Beam parameters are logged just for us! Only massi has access via his 'massi' account by: ssh massi@cs-ccr-dev1. The data are stored in the newest files /acc/java/data/psb/eqpsurvey/BTM_V*.xml_* (in fact BTM_VELO_PICKUP.xml_log* and BTM_Velo.xml_log*), but are not kept permanently. I will take care of castoring regularly.
 

-- MassiFL - 26 Mar 2008

Revision 192008-05-30 - MassiFL

Line: 1 to 1
 
META TOPICPARENT name="LHCbVELO"

2008 Zap Test Twiki Pages

Line: 124 to 124
 

Machine interface

Changed:
<
<
  • I defined the alias 'psb' to run the PSBooster Vistar (javaws _NOCLICK_http://abwww.cern.ch/ap/dist/psb/psb-fixdisplay/PRO/PSBFixedDisplay.jnlp) which allows to view the machine cycle. For the moment this only works if you login to pcvelo01 as velo. Further explanations coming up...
>
>
  • I defined the alias 'psb' to run the PSBooster Vistar (javaws _NOCLICK_http://abwww.cern.ch/ap/dist/psb/psb-fixdisplay/PRO/PSBFixedDisplay.jnlp) which allows to view the machine cycle: it highlights the 'basic period number' (BPNM) that the machine is executing (what beam sent where). This Vistar only works if you login to pcvelo01 as velo.
  • Every beam that goes to destination BDUMP is ending up in our area (unless the user is called ZERO, in which case there was no beam, only a destination...). When we will be shooting on our module there should be no other beam than ours going to BDUMP (except if ZERO). We will have to synchronize the insertion of the module and its retraction quite carefully.
  • There is a fairly fixed and reproducible delay between the Vistar basic period of the machine and the actual arrival of the beam shot. I determined in a test on May 30 that the shot arrives about 1 basic period before the latter is appearing on the Vistar.
 
  • You can also get the display directly via http://ab-dep-op.web.cern.ch/ab-dep-op/vistar.php?usr=PSB, but then there is a larger and changing latency between the machine basic period and what you see in the Vistar. On the other hand, the web based display does show the header information (not the case for the console display).
  • PS Booster Control Room: 76671 (76672, ..., 76677)
Added:
>
>
  • Beam parameters are logged just for us! Only massi has access via his 'massi' account by: ssh massi@cs-ccr-dev1. The data are stored in the newest files /acc/java/data/psb/eqpsurvey/BTM_Velo.xml_* , but are not kept permanently. I will take care of castoring regularly.
 

-- MassiFL - 26 Mar 2008

Revision 182008-05-30 - MassiFL

Line: 1 to 1
 
META TOPICPARENT name="LHCbVELO"

2008 Zap Test Twiki Pages

Line: 124 to 124
 

Machine interface

Changed:
<
<
  • I defined the alias psb to run the PSBooster Vistar (javaws _NOCLICK_http://abwww.cern.ch/ap/dist/psb/psb-fixdisplay/PRO/PSBFixedDisplay.jnlp) which allows to view the machine cycle. For the moment this only works if you login to pcvelo01 as velo. Further explanations coming up...
>
>
  • I defined the alias 'psb' to run the PSBooster Vistar (javaws _NOCLICK_http://abwww.cern.ch/ap/dist/psb/psb-fixdisplay/PRO/PSBFixedDisplay.jnlp) which allows to view the machine cycle. For the moment this only works if you login to pcvelo01 as velo. Further explanations coming up...
  • You can also get the display directly via http://ab-dep-op.web.cern.ch/ab-dep-op/vistar.php?usr=PSB, but then there is a larger and changing latency between the machine basic period and what you see in the Vistar. On the other hand, the web based display does show the header information (not the case for the console display).
 
  • PS Booster Control Room: 76671 (76672, ..., 76677)

Revision 172008-05-25 - MassiFL

Line: 1 to 1
 
META TOPICPARENT name="LHCbVELO"

2008 Zap Test Twiki Pages

Line: 43 to 43
  Radmon wiring (banana socket number upstairs vs PCB serigraphy):
  • Nr ..... PCB serigraphy
Changed:
<
<
  • 1 ..... S1
  • 2 ..... GND
  • 3 ..... D3
  • 4 ..... D2
  • 5 ..... IC1-C1
  • 6 ..... IC1-C2
  • 7 ..... IC1-C3
  • 8 ..... GND
>
>
  • 1 ..... S1 ............. PT100
  • 2 ..... GND .......... GND
  • 3 ..... D3 ............ BPW34
  • 4 ..... D2 ............ CMRP
  • 5 ..... IC1-C1 ...... REM
  • 6 ..... IC1-C2 ...... LAAS
  • 7 ..... IC1-C3 ...... REM
  • 8 ..... GND ..........GND
  Video and pneumatic control (located in rack XXX):
  • Two coax cables with N-type connectors used for +/- wires of motion control (switch is indicated)
Line: 73 to 73
 TELL1 / CONFIG - RUN:
  • ssh velo@pctell024
  • cd /home/velo/massi/tell1daq2.0zaptest/tell1lib_release_v2.0/ccpc_daq
Changed:
<
<
  • ./daq_tell1 anyconfigfile.cfg
  • config files: ls *.cfg
>
>
  • ./daq_tell1 ~/massi/anyconfigfile.cfg
  • config files: ls -ltr ~/massi/*.cfg
 
  • relevant C-codes in /home/velo/massi/tell1daq2.0zaptest/tell1lib_release_v2.0/tell1lib/velo and common

DATA ANALYSIS (Sorry, no Toxygen documentation for software)

Line: 125 to 125
 

Machine interface

  • I defined the alias psb to run the PSBooster Vistar (javaws _NOCLICK_http://abwww.cern.ch/ap/dist/psb/psb-fixdisplay/PRO/PSBFixedDisplay.jnlp) which allows to view the machine cycle. For the moment this only works if you login to pcvelo01 as velo. Further explanations coming up...
Added:
>
>
  • PS Booster Control Room: 76671 (76672, ..., 76677)
 

-- MassiFL - 26 Mar 2008

Revision 162008-05-20 - MassiFL

Line: 1 to 1
 
META TOPICPARENT name="LHCbVELO"

2008 Zap Test Twiki Pages

Line: 99 to 99
 
  • whenever there is a reasonably long access (> 15 minutes), try reading out the LVPS voltages and currents.
  • when taking a beam shot, write down where the shot hits the view screen (using the grid letter-numbering, be as precise as you can)
Added:
>
>

TAKING RADMON DATA

  • Important: always connect back the sensor to the GND banana after your measurement. Some radmon sensors have a very different sensitivity to integrated dose when left floating! They must be short-circuited in order to match the calibration curve!
  • Currently done semi manually:
    • Pt100, C1-REM and C2-LAAS are all done with a fixed source current and quite long powered-up time. Just configure the Keithley to give the desired source current, then connect the corresponding sensor into the Keithley (labeled Radmon) and measure the voltage.
    • Pt100: 10 s at 1 mA
    • C1-REM: 2 s at -0.16 mA
    • C2-LAAS: 2 s at -0.10 mA
    • D3-BPW34 and D2-CMRP are read out with a fast pulse (about 50 ms), booking the voltage value before, during and after the pulse. The keithley labeled radmon has a programmed 3-point sweep which is ready to use.
    • Optional: you can inspect (or change, but it's already configured!) the sweep data as follows:
      1. press "I" button under SOURCE
      2. press CONFIG, then SWEEP, then ENTER (on blinking TYPE)
      3. select CUSTOM with L/R arrows, then ENTER.
      4. you can now ENTER on blinking #-POINTS or move to ADJUST-POINTS and play with the arrows to read (or change) values
      5. use EXIT to go up the menu tree
    • Compulsory: try first the sweep with a cable short between - and +:
      1. press "I" button under SOURCE
      2. set output to ON
      3. start sweep by pressing SWEEP : this takes a very quick sweep, less than 1 s
      4. data is retrieved by pressing RECALL and toggling with the up/down arrows
    • If the data points look correct (3 points at about 50 to 100 ms intervals) connect the sensor cable and take a real SWEEP. Write down Time, Voltage and Current of each of the three points.
  • Future: labview will handle this.

 

Machine interface

  • I defined the alias psb to run the PSBooster Vistar (javaws _NOCLICK_http://abwww.cern.ch/ap/dist/psb/psb-fixdisplay/PRO/PSBFixedDisplay.jnlp) which allows to view the machine cycle. For the moment this only works if you login to pcvelo01 as velo. Further explanations coming up...

Revision 152008-05-14 - MassiFL

Line: 1 to 1
 
META TOPICPARENT name="LHCbVELO"

2008 Zap Test Twiki Pages

Line: 99 to 99
 
  • whenever there is a reasonably long access (> 15 minutes), try reading out the LVPS voltages and currents.
  • when taking a beam shot, write down where the shot hits the view screen (using the grid letter-numbering, be as precise as you can)
Added:
>
>

Machine interface

  • I defined the alias psb to run the PSBooster Vistar (javaws _NOCLICK_http://abwww.cern.ch/ap/dist/psb/psb-fixdisplay/PRO/PSBFixedDisplay.jnlp) which allows to view the machine cycle. For the moment this only works if you login to pcvelo01 as velo. Further explanations coming up...
 -- MassiFL - 26 Mar 2008

Revision 142008-04-21 - MassiFL

Line: 1 to 1
 
META TOPICPARENT name="LHCbVELO"

2008 Zap Test Twiki Pages

Changed:
<
<
links: CERN home, LHCb home, Massi home, Zap Test Pictures
>
>
links: CERN home, LHCb home, Massi home, Zap Test Pictures, Zap Test electronic logbook
 

WORK TO BE DONE

Revision 132008-04-18 - MassiFL

Line: 1 to 1
 
META TOPICPARENT name="LHCbVELO"

2008 Zap Test Twiki Pages

Line: 21 to 21
 

GEOMETRY OF SETUP

Changed:
<
<

Module 48 is mounted sideways with Phi-sensor ZapTestSetup14Apr2008_thumb.jpgdownstream towards dump. It can be moved out of the beam line towards the right when looking downstream. Only two positions are possible: in or out. As of April 14, 2008, the module cannot be moved into the beam line. Only the attached extension with alumina view screen can go into the beam line. To see a high resolution picture of setup as of 14 Apr 2008, click on image

>
>

Module 48 is mounted sideways with Phi-sensor ZapTestSetup14Apr2008_thumb.jpgdownstream towards dump. It can be moved out of the beam line towards the right when looking downstream. Only two positions are possible: in or out. As of April 14, 2008, the module cannot be moved into the beam line, see here the arrangement. Only the attached extension with alumina view screen can go into the beam line. To see a high resolution picture of setup as of 14 Apr 2008, click on image

 

CABLING

Line: 78 to 78
 

DATA ANALYSIS (Sorry, no Toxygen documentation for software)

Changed:
<
<
  • ssh lhcbvelo@pcvelo01
  • SetupProject Vetra v5r1
  • cd cmtuser/Vetra_v5r1/Velo/Vetra/v5r1/cmt/
  • source setup.csh
  • cd ../job
  • ls -ltr /scratch/velodata/
  • vi ../options/ZapTestNZS.opts (set proper input file)
  • ../slc4_amd64_gcc34/Vetra.exe ../options/ZapTestNZS.opts > mylog
  • vi mylog (any severe ERROR messages ?)
  • ls *.root
  • root (open a TBrowser)
>
>
  • ssh lhcbvelo@pcvelo01
  • SetupProject Vetra v5r1
  • cd cmtuser/Vetra_v5r1/Velo/Vetra/v5r1/cmt/
  • source setup.csh
  • cd ../job
  • ls -ltr /scratch/velodata/
  • vi ../options/ZapTestNZS.opts   (set proper input file)
  • ../slc4_amd64_gcc34/Vetra.exe ../options/ZapTestNZS.opts > mylog
  • vi mylog  (any severe ERROR messages ?)
  • ls *.root
  • root  (open a TBrowser)
 

RUN INSTRUCTIONS

Line: 102 to 102
 

META FILEATTACHMENT attachment="ZapTestSetup14Apr2008.jpg" attr="h" comment="VELO Zap Preparation Setup as of 14-Apr-2008" date="1208174918" name="ZapTestSetup14Apr2008.jpg" path="ZapTestSetup14Apr2008.jpg" size="849849" stream="ZapTestSetup14Apr2008.jpg" user="Main.MassiFL" version="1"
Added:
>
>
META FILEATTACHMENT attachment="VELO_HIGHT_RATE.jpg" attr="" comment="2D view of module with screen as extension" date="1208514188" name="VELO_HIGHT_RATE.jpg" path="VELO_HIGHT_RATE.jpg" size="3664317" stream="VELO_HIGHT_RATE.jpg" user="Main.MassiFL" version="1"

Revision 122008-04-18 - MassiFL

Line: 1 to 1
 
META TOPICPARENT name="LHCbVELO"

2008 Zap Test Twiki Pages

Line: 6 to 6
 

WORK TO BE DONE

Changed:
<
<
  • Install labview to control IV scans (Jan B, when ?)
  • Check out radmon with Maurice Glaser (week 14 Apr)
  • Set up delays (help from Olaf B, week 28 Apr - 2 Mar)
>
>
  • Install labview to control IV scans (Jan B)
  • Install labview to control one radmon sensor continuously (Jan B, Maurice Glaser)
  • Set up delays (help from Olaf B, week 28 Apr - 2 Mar) STARTED
 
  • Write down initial values of LVPS currents (before any irradiation on sensors)
Added:
>
>
  • Take reference IV scans
 

MOTIVATION

Revision 112008-04-14 - MassiFL

Line: 1 to 1
 
META TOPICPARENT name="LHCbVELO"

2008 Zap Test Twiki Pages

Changed:
<
<
links: CERN home, LHCb home, Massi home
>
>
links: CERN home, LHCb home, Massi home, Zap Test Pictures
 
Changed:
<
<

Still to do list

>
>

WORK TO BE DONE

 
Changed:
<
<
  • Install labview to control IV scans (Jan B)
  • Check out radmon with Maurice Glaser
  • Set up delays (help from Olaf B)
>
>
  • Install labview to control IV scans (Jan B, when ?)
  • Check out radmon with Maurice Glaser (week 14 Apr)
  • Set up delays (help from Olaf B, week 28 Apr - 2 Mar)
 
  • Write down initial values of LVPS currents (before any irradiation on sensors)
Changed:
<
<

Motivation

>
>

MOTIVATION

  Study behaviour of one or more VELO modules under exposure to high rates of charged particles and under various HV/LV conditions. See presentations: VELO Workshop 13-14 Dec 07 , VELO meeting 21 Dec 07 , LHCb week /VELO 23 Jan 08
Changed:
<
<

Geometry of setup

>
>

GEOMETRY OF SETUP

 
Changed:
<
<
Module 48 is mounted sideways with Phi-sensor downstream towards dump.
>
>

Module 48 is mounted sideways with Phi-sensor ZapTestSetup14Apr2008_thumb.jpgdownstream towards dump. It can be moved out of the beam line towards the right when looking downstream. Only two positions are possible: in or out. As of April 14, 2008, the module cannot be moved into the beam line. Only the attached extension with alumina view screen can go into the beam line. To see a high resolution picture of setup as of 14 Apr 2008, click on image

 
Deleted:
<
<
It can be moved out of the beam line towards the right when looking downstream.
 
Changed:
<
<

Cabling

>
>

CABLING

  Power cables:
  • 2717269A => 220VAC for CCPCrepeater, Tell1 and fan, and light bulb for camera.
Line: 51 to 50
 
  • 7 ..... IC1-C3
  • 8 ..... GND

Changed:
<
<

DAQ stuff

>
>
Video and pneumatic control (located in rack XXX):
  • Two coax cables with N-type connectors used for +/- wires of motion control (switch is indicated)
  • Video signal comes through small plastic box with switch (to open/close diaphragm in front of camera)
  • Video Monitor sits above the racks
Cables, alumina view screen and camera borrowed from Bernd Dehning's setup.

DAQ STUFF

  ONLINE / EVENTBUILDING:
Line: 92 to 98
 
  • when taking a beam shot, write down where the shot hits the view screen (using the grid letter-numbering, be as precise as you can)

-- MassiFL - 26 Mar 2008 \ No newline at end of file

Added:
>
>

META FILEATTACHMENT attachment="ZapTestSetup14Apr2008.jpg" attr="h" comment="VELO Zap Preparation Setup as of 14-Apr-2008" date="1208174918" name="ZapTestSetup14Apr2008.jpg" path="ZapTestSetup14Apr2008.jpg" size="849849" stream="ZapTestSetup14Apr2008.jpg" user="Main.MassiFL" version="1"

Revision 102008-04-14 - MassiFL

Line: 1 to 1
 
META TOPICPARENT name="LHCbVELO"

2008 Zap Test Twiki Pages

links: CERN home, LHCb home, Massi home

Added:
>
>

Still to do list

  • Install labview to control IV scans (Jan B)
  • Check out radmon with Maurice Glaser
  • Set up delays (help from Olaf B)
  • Write down initial values of LVPS currents (before any irradiation on sensors)
 

Motivation

Study behaviour of one or more VELO modules under exposure to high rates of charged particles and under various HV/LV conditions.

Revision 92008-04-10 - MassiFL

Line: 1 to 1
 
META TOPICPARENT name="LHCbVELO"

2008 Zap Test Twiki Pages

links: CERN home, LHCb home, Massi home

Added:
>
>

Motivation

Study behaviour of one or more VELO modules under exposure to high rates of charged particles and under various HV/LV conditions. See presentations: VELO Workshop 13-14 Dec 07 , VELO meeting 21 Dec 07 , LHCb week /VELO 23 Jan 08

 

Geometry of setup

Module 48 is mounted sideways with Phi-sensor downstream towards dump.

Line: 26 to 33
 
  • 2717267A => Phi sensor high voltage
  • 2717268A => R sensor high voltage
Changed:
<
<
Radmon wiring:
  • Box Nr upstairs Radmon PCB serigraphy
  • 2, 8 GND
  • 3 D3
  • 7 IC1-C3
  • 1 S1
  • 4 D2
  • 5 IC1-C1
  • 6 IC1-C2
>
>
Radmon wiring (banana socket number upstairs vs PCB serigraphy):
  • Nr ..... PCB serigraphy
  • 1 ..... S1
  • 2 ..... GND
  • 3 ..... D3
  • 4 ..... D2
  • 5 ..... IC1-C1
  • 6 ..... IC1-C2
  • 7 ..... IC1-C3
  • 8 ..... GND
 

DAQ stuff

Line: 70 to 78
 

RUN INSTRUCTIONS

Changed:
<
<
  • Take an IV scan from 0 to 300 V before and after every action (with LV off, for temperature reproducibility). Write down NTC value.
>
>
  • Take an IV scan from 0 to 300 V before and after every action (with LV off, for temperature reproducibility).
  • Write down NTC value.
  • Read out all Radmon sensors and put back short-circuit.
  • whenever there is a reasonably long access (> 15 minutes), try reading out the LVPS voltages and currents.
  • when taking a beam shot, write down where the shot hits the view screen (using the grid letter-numbering, be as precise as you can)
  -- MassiFL - 26 Mar 2008

Revision 82008-04-10 - MassiFL

Line: 1 to 1
 
META TOPICPARENT name="LHCbVELO"

2008 Zap Test Twiki Pages

Line: 13 to 13
 

Cabling

Power cables:

Changed:
<
<
  • 2717269A => 220VAC for CCPCrepeater, Tell1 and fan
>
>
  • 2717269A => 220VAC for CCPCrepeater, Tell1 and fan, and light bulb for camera.
 
  • 2717270A => 220VAC for LVPS-Phi and LVPS-R

Cat7/RJ45 cables:

  • 2717227A => Gbit-card output port1
  • 2717228A => CCPCrepeater network
  • 2717236A => R-side repeater board temperature cable (check!)
Changed:
<
<
  • 2717237A => phi-side repeater board temperature cable (check!)
>
>
  • 2717237A => Radmon
  Brown BNC cables:
  • 2717267A => Phi sensor high voltage
  • 2717268A => R sensor high voltage
Added:
>
>
Radmon wiring:
  • Box Nr upstairs Radmon PCB serigraphy
  • 2, 8 GND
  • 3 D3
  • 7 IC1-C3
  • 1 S1
  • 4 D2
  • 5 IC1-C1
  • 6 IC1-C2

 

DAQ stuff

ONLINE / EVENTBUILDING:

Line: 40 to 50
 TELL1 / CONFIG - RUN:
  • ssh velo@pctell024
  • cd /home/velo/massi/tell1daq2.0zaptest/tell1lib_release_v2.0/ccpc_daq
Changed:
<
<
  • ./daq_tell1
>
>
  • ./daq_tell1 anyconfigfile.cfg
 
  • config files: ls *.cfg
  • relevant C-codes in /home/velo/massi/tell1daq2.0zaptest/tell1lib_release_v2.0/tell1lib/velo and common

Revision 72008-04-07 - MassiFL

Line: 1 to 1
 
META TOPICPARENT name="LHCbVELO"

2008 Zap Test Twiki Pages

Line: 44 to 44
 
  • config files: ls *.cfg
  • relevant C-codes in /home/velo/massi/tell1daq2.0zaptest/tell1lib_release_v2.0/tell1lib/velo and common
Changed:
<
<

DATA ANALYSIS

>
>

DATA ANALYSIS (Sorry, no Toxygen documentation for software)

 

Revision 62008-04-07 - MassiFL

Line: 1 to 1
 
META TOPICPARENT name="LHCbVELO"

2008 Zap Test Twiki Pages

Line: 57 to 57
 
  • ls *.root
  • root (open a TBrowser)
Added:
>
>

RUN INSTRUCTIONS

  • Take an IV scan from 0 to 300 V before and after every action (with LV off, for temperature reproducibility). Write down NTC value.
 -- MassiFL - 26 Mar 2008

Revision 52008-03-28 - MassiFL

Line: 1 to 1
 
META TOPICPARENT name="LHCbVELO"

2008 Zap Test Twiki Pages

Line: 17 to 17
 
  • 2717270A => 220VAC for LVPS-Phi and LVPS-R

Cat7/RJ45 cables:

Changed:
<
<
  • 2717227A => CCPCrepeater network
  • 2717228A => Gbit-card output port1
>
>
  • 2717227A => Gbit-card output port1
  • 2717228A => CCPCrepeater network
 
  • 2717236A => R-side repeater board temperature cable (check!)
  • 2717237A => phi-side repeater board temperature cable (check!)
Line: 26 to 26
 
  • 2717267A => Phi sensor high voltage
  • 2717268A => R sensor high voltage
Added:
>
>

DAQ stuff

ONLINE / EVENTBUILDING:

  • ssh velo@pcvelo01
  • less $ONLINETASKSROOT/options/VeloDatafileLocation.opts
  • ls /scratch/velodata/
  • cd /home/velo/cmtuser/Online_v4r6/Online/OnlineTasks/job
  • ./hltrx.sh
  • killall Gaudi.exe logViewer
  • sudo tshark -i eth1

TELL1 / CONFIG - RUN:

  • ssh velo@pctell024
  • cd /home/velo/massi/tell1daq2.0zaptest/tell1lib_release_v2.0/ccpc_daq
  • ./daq_tell1
  • config files: ls *.cfg
  • relevant C-codes in /home/velo/massi/tell1daq2.0zaptest/tell1lib_release_v2.0/tell1lib/velo and common

DATA ANALYSIS

  • ssh lhcbvelo@pcvelo01
  • SetupProject Vetra v5r1
  • cd cmtuser/Vetra_v5r1/Velo/Vetra/v5r1/cmt/
  • source setup.csh
  • cd ../job
  • ls -ltr /scratch/velodata/
  • vi ../options/ZapTestNZS.opts (set proper input file)
  • ../slc4_amd64_gcc34/Vetra.exe ../options/ZapTestNZS.opts > mylog
  • vi mylog (any severe ERROR messages ?)
  • ls *.root
  • root (open a TBrowser)
 -- MassiFL - 26 Mar 2008 \ No newline at end of file

Revision 42008-03-28 - MassiFL

Line: 1 to 1
 
META TOPICPARENT name="LHCbVELO"

2008 Zap Test Twiki Pages

Added:
>
>
links: CERN home, LHCb home, Massi home
 

Geometry of setup

Module 48 is mounted sideways with Phi-sensor downstream towards dump.

Revision 32008-03-27 - MassiFL

Line: 1 to 1
 
META TOPICPARENT name="LHCbVELO"

2008 Zap Test Twiki Pages

Line: 17 to 17
 Cat7/RJ45 cables:
  • 2717227A => CCPCrepeater network
  • 2717228A => Gbit-card output port1
Changed:
<
<
  • 2717236A => xxx repeater board temperature cable
  • 2717237A => xxx repeater board temperature cable
>
>
  • 2717236A => R-side repeater board temperature cable (check!)
  • 2717237A => phi-side repeater board temperature cable (check!)
  Brown BNC cables:
Changed:
<
<
  • 2717267A => xxx sensor high voltage
  • 2717268A => xxx sensor high voltage
>
>
  • 2717267A => Phi sensor high voltage
  • 2717268A => R sensor high voltage
  -- MassiFL - 26 Mar 2008

Revision 22008-03-27 - MassiFL

Line: 1 to 1
 
META TOPICPARENT name="LHCbVELO"
Changed:
<
<
2008 Zap Test Twiki Pages
>
>

2008 Zap Test Twiki Pages

Geometry of setup

Module 48 is mounted sideways with Phi-sensor downstream towards dump.

It can be moved out of the beam line towards the right when looking downstream.

 

Cabling

Power cables:

Changed:
<
<
  • 2717269A => 220VAC for CCPCrepeater and Tell1
>
>
  • 2717269A => 220VAC for CCPCrepeater, Tell1 and fan
 
  • 2717270A => 220VAC for LVPS-Phi and LVPS-R

Cat7/RJ45 cables:

Revision 12008-03-26 - MassiFL

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="LHCbVELO"
2008 Zap Test Twiki Pages

Cabling

Power cables:

  • 2717269A => 220VAC for CCPCrepeater and Tell1
  • 2717270A => 220VAC for LVPS-Phi and LVPS-R

Cat7/RJ45 cables:

  • 2717227A => CCPCrepeater network
  • 2717228A => Gbit-card output port1
  • 2717236A => xxx repeater board temperature cable
  • 2717237A => xxx repeater board temperature cable

Brown BNC cables:

  • 2717267A => xxx sensor high voltage
  • 2717268A => xxx sensor high voltage

-- MassiFL - 26 Mar 2008

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback