Difference: TestBeamDAQ (1 vs. 3)

Revision 32006-08-11 - MassiFL

Line: 1 to 1
 
META TOPICPARENT name="VELOTestbeam"
Deleted:
<
<
 The one and only guide.

Instructions to run the ECS/DAQ system of the testbeam setup.

Important thinguies to keep in mind:

Changed:
<
<
   1 - We run over 3 modules  without active cooling => be careful when configuring the beetles.

   2 - We take data with 6 TELL1 boards and the Readout supervisor (ODIN), using the old event builder => it is NOT guaranteed to be stable! large files will be produced if you run with non zero suppressed data.

   3 - The system is complicated to operate, so dont give up easily.

>
>
  1. We run over 3 modules without active cooling => be careful when configuring the beetles.
  2. We take data with 6 TELL1 boards and the Readout supervisor (ODIN), using the old event builder => it is NOT guaranteed to be stable! large files will be produced if you run with non zero suppressed data.
  3. The system is complicated to operate, so dont give up easily.
  4. These intructions are the Standard ones and can be altered during the next few days, soo keep up with the updates.
 
Deleted:
<
<
   4 - These intructions are the Standard ones and can be altered during the next few days, soo keep up with the updates.
 
Deleted:
<
<
 
  StartUp procedure.
Changed:
<
<
   Follow up this text if you powered off and on the crate.
>
>
Follow up this text if you powered off and on the crate.
 
Changed:
<
<
   1 - Be sure to make a clean exit on all PVSS panels if the are open... you do that by clicking exit or close buttons. DO NOT close with the common x on the corner of the window. It should be ok if they pop up back.

   2 - If  PVSS is not running you should start the project.

>
>
  1. Be sure to make a clean exit on all PVSS panels if the are open... you do that by clicking exit or close buttons. DO NOT close with the common x on the corner of the window. It should be ok if they pop up back.
  2. If PVSS is not running you should start the project.
  To start the pvss project:
Changed:
<
<
  Start a remote desktop to the  windows computer called lbh8wico01.cern.ch. 

  Search fot the PVSS project administrator (inside PVSS folder on programs).

  Select the VeloTestBeam2 project. Wait. Check if it's running. If it's running and you dont see it, probably somebody else started it on another session.

  If it's not running, click the green light button on the top of this window. this will start the whole project. Some windows will pop up. You should also get the PVSS console. whan it finishes you should be able to mess around with a pvss panel (one of the windows) called SingleCB2.

  This panel has several "tabs". there are two more important for the shifters. the one called Master Control and the  Temperatures.

  Note that that this project will also start the TFC panel which should run on Richard Jacobsson's machine. (lbontfc01.cern.ch) DONT TOUCH that  window yet. there is more than one way to control the tfc... So I will explain only one... (which is not the simplest).

  STOP. Follow up the procedure to configure the ReadOut Supervisor.

 

Configure ReadOutSupervisor

    Here is the way I suggest you to configure the readout supervisor. If the board has just been powered up the CCPC will be booting up. if you try to ssh to it you should receive back a connection refused. wait for some time and then you should be able to log in.

  to log in to the Test Beam ODIN you should type ssh tfc@odinv210 and type the expert password.  as soon as you log in run: source .VeloSetup

  WAIT. this will configure the fpgas on the read out supervisor. THIS MAY TAKE SEVERAL MINUTES. then the TFC_server will startup automatically. press enter to get the command prompt back.

  You are now on the state that you could use the TFC panel which starts up together with the pvss project. I ADVICE you to run in a remote machine. Here is my recipe:

  Open a remote desktop to the pcveloassembly1 machine. Check if PVSS is running. If  not, start the  project called VeloECS_prodCB.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

>
>
Start a remote desktop to the windows computer called lbh8wico01.cern.ch.
 
Changed:
<
<
 
>
>
Search fot the PVSS project administrator (inside PVSS folder on programs).
 
Changed:
<
<
 
>
>
Select the VeloTestBeam2 project. Wait. Check if it's running. If it's running and you dont see it, probably somebody else started it on another session.
 
Changed:
<
<
 
>
>
If it's not running, click the green light button on the top of this window. this will start the whole project. Some windows will pop up. You should also get the PVSS console. whan it finishes you should be able to mess around with a pvss panel (one of the windows) called SingleCB2.
 
Changed:
<
<
 
>
>
This panel has several "tabs". there are two more important for the shifters. the one called Master Control and the Temperatures.
 
Changed:
<
<
 
>
>
Note that that this project will also start the TFC panel which should run on Richard Jacobsson's machine. (lbontfc01.cern.ch) DONT TOUCH that window yet. there is more than one way to control the tfc... So I will explain only one... (which is not the simplest).
 
Changed:
<
<
 
>
>
STOP. Follow up the procedure to configure the ReadOut Supervisor.
 
Deleted:
<
<
 
 
Deleted:
<
<
 
 
Changed:
<
<
 
>
>
Configure ReadOutSupervisor
 
Changed:
<
<
 
>
>
Here is the way I suggest you to configure the readout supervisor. If the board has just been powered up the CCPC will be booting up. if you try to ssh to it you should receive back a connection refused. wait for some time and then you should be able to log in.
 
Changed:
<
<
 
>
>
to log in to the Test Beam ODIN you should type ssh tfc@odinv210 and type the expert password. as soon as you log in run: source .VeloSetup
 
Changed:
<
<
 
>
>
WAIT. this will configure the fpgas on the read out supervisor. THIS MAY TAKE SEVERAL MINUTES. then the TFC_server will startup automatically. press enter to get the command prompt back.
 
Changed:
<
<
 
>
>
You are now on the state that you could use the TFC panel which starts up together with the pvss project. I ADVICE you to run in a remote machine. Here is my recipe:
 
Changed:
<
<
 
>
>
Open a remote desktop to the pcveloassembly1 machine. Check if PVSS is running. If not, start the project called VeloECS _prodCB.
 
Changed:
<
<
 
>
>

 
Changed:
<
<
 
>
>
Instructions to change MEP factor and to go from ZS to NZS
 
Changed:
<
<
 
>
>
  1. TFC local Run ctrl in PVSS: do end_run
 
Changed:
<
<
 
>
>
MEP FACTOR CHANGE:
  1. in ODIN ccpc:
    1. [pclbcc07] /home/tfc/ODIN_V2 > vi .setup_MEP_Factor
    2. then in the line "lbus -p0x3001 0x1058" change p0x3001 to p0x0001 (3 is MEP=4, 0 is MEP=1)
  2. Then, [pclbcc07] /home/tfc/ODIN_V2 > source .setup_MEP_Factor
  3. in velotbdaq01 (DAQ PC #1), as root:
    1. [root@lbh8lx01 ~]# cd /DAQ/writeEventsToBinary/
    2. [root@lbh8lx01 writeEventsToBinary]# vi ebuild.cfg , change packing_factor from 4 to 1
  4. same thing in velotbdaq02 (DAQ PC #2).
 
Changed:
<
<
 
>
>
ZS->NZS:
  1. in velotbdaq01 (DAQ PC #1), as lhcbvelo:
    1. [lbh8lxco01] > cd /DAQ/tbDaqScripts
    2. [lbh8lxco01] /DAQ/tbDaqScripts > killall xterm
  2. take data with approriate script, e.g. for NZS only:
    1. [lbh8lxco01] /DAQ/tbDaqScripts > ./startOnlyNZSTELL1Daq
  3. change artifical dead time in the NIM crate, if needed (typically, set switch to 100 us for ZS and to 1 ms for NZS, but this may change)
 
Changed:
<
<
 
>
>
Restart data taking:
  1. TFC local Run ctrl in PVSS: do get_ready
  2. Send L0reset from Run Control in PVSS
  3. TFC local Run ctrl in PVSS: do start_run
 
Changed:
<
<
  
>
>
<!-- show_standard_title -->
 
Deleted:
<
<
 
 
Deleted:
<
<
 
 
Deleted:
<
<
 
 
Deleted:
<
<
 
 
Deleted:
<
<
 
 
Deleted:
<
<
 
 
Deleted:
<
<
 
  -- KazuyoshiAkiba - 07 Aug 2006 \ No newline at end of file

Revision 22006-08-07 - KazuyoshiAkiba

Line: 1 to 1
 
META TOPICPARENT name="VELOTestbeam"
Changed:
<
<
>
>
  The one and only guide.
Line: 54 to 54
    You are now on the state that you could use the TFC panel which starts up together with the pvss project. I ADVICE you to run in a remote machine. Here is my recipe:
Changed:
<
<
  Open a remote desktop to the pcveloassembly1 machine. Check if PVSS is running. If  not, start the  project called VeloECS _prodCB.
>
>
  Open a remote desktop to the pcveloassembly1 machine. Check if PVSS is running. If  not, start the  project called VeloECS_prodCB.

 

 

   

Revision 12006-08-07 - KazuyoshiAkiba

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="VELOTestbeam"

The one and only guide.

Instructions to run the ECS/DAQ system of the testbeam setup.

Important thinguies to keep in mind:

   1 - We run over 3 modules  without active cooling => be careful when configuring the beetles.

   2 - We take data with 6 TELL1 boards and the Readout supervisor (ODIN), using the old event builder => it is NOT guaranteed to be stable! large files will be produced if you run with non zero suppressed data.

   3 - The system is complicated to operate, so dont give up easily.

   4 - These intructions are the Standard ones and can be altered during the next few days, soo keep up with the updates.

 

StartUp procedure.

   Follow up this text if you powered off and on the crate.

   1 - Be sure to make a clean exit on all PVSS panels if the are open... you do that by clicking exit or close buttons. DO NOT close with the common x on the corner of the window. It should be ok if they pop up back.

   2 - If  PVSS is not running you should start the project.

To start the pvss project:

  Start a remote desktop to the  windows computer called lbh8wico01.cern.ch. 

  Search fot the PVSS project administrator (inside PVSS folder on programs).

  Select the VeloTestBeam2 project. Wait. Check if it's running. If it's running and you dont see it, probably somebody else started it on another session.

  If it's not running, click the green light button on the top of this window. this will start the whole project. Some windows will pop up. You should also get the PVSS console. whan it finishes you should be able to mess around with a pvss panel (one of the windows) called SingleCB2.

  This panel has several "tabs". there are two more important for the shifters. the one called Master Control and the  Temperatures.

  Note that that this project will also start the TFC panel which should run on Richard Jacobsson's machine. (lbontfc01.cern.ch) DONT TOUCH that  window yet. there is more than one way to control the tfc... So I will explain only one... (which is not the simplest).

  STOP. Follow up the procedure to configure the ReadOut Supervisor.

 

Configure ReadOutSupervisor

    Here is the way I suggest you to configure the readout supervisor. If the board has just been powered up the CCPC will be booting up. if you try to ssh to it you should receive back a connection refused. wait for some time and then you should be able to log in.

  to log in to the Test Beam ODIN you should type ssh tfc@odinv210 and type the expert password.  as soon as you log in run: source .VeloSetup

  WAIT. this will configure the fpgas on the read out supervisor. THIS MAY TAKE SEVERAL MINUTES. then the TFC_server will startup automatically. press enter to get the command prompt back.

  You are now on the state that you could use the TFC panel which starts up together with the pvss project. I ADVICE you to run in a remote machine. Here is my recipe:

  Open a remote desktop to the pcveloassembly1 machine. Check if PVSS is running. If  not, start the  project called VeloECS _prodCB.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

  

 

 

 

 

 

 

 

-- KazuyoshiAkiba - 07 Aug 2006

 
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