Difference: DAQ(oneOrManyTELL1s) (6 vs. 7)

Revision 72006-11-07 - JanBuytaertSecondary

Line: 1 to 1
 
META TOPICPARENT name="VELOTestbeam"
Changed:
<
<
Instructions to Acquire data:
>
>
Instructions to Acquire data:
  1 TELL1 - old Event Builder:
Line: 20 to 20
  go to /DAQ/oldEB/writeEventsToBinary
Changed:
<
<
to change tell1 you should do: on the /DAQ/oldEB/writeEventsToBinary/ directory you should edit the ebuild.cfg file and uncomment the tell1 you will use and comment back the tell1 you just used. dont change the board 0x0000000 it's the readout supervisor.
commented lines are marked with #

login to lbh8lxco01 as lhcbvelo, go insige tbDaqScripts, and run ./resetTell1s This will stop the data acquisition on all of them. ( the event builder gets confused if there are more sources than it's declared on the configuration file)

>
>
to change tell1 you should do: on the /DAQ/oldEB/writeEventsToBinary/ directory you should edit the ebuild.cfg file and uncomment the tell1 you will use and comment back the tell1 you just used. dont change the board 0x0000000 it's the readout supervisor. commented lines are marked with #

login to lbh8lxco01 as lhcbvelo, go insige tbDaqScripts, and run ./resetTell1s This will stop the data acquisition on all of them. ( the event builder gets confused if there are more sources than it's declared on the configuration file)

  go to the ACDCTell1Control panel. (dont ever close it!)
Line: 41 to 35
  To power the beetles: go to the master control on SingleCB.
Changed:
<
<
The on Control board @ #board click Get Ready
One of the channels should be highlighted in green.
Click main button LV on.
Check in happy pion what sensor type is connected to the Tell1 board and set the type on the highlighted channel.
(If you are taking data with the dummy module you should always use R config)
Click ON on button below highlighted channel.
>
>
The on Control board @ #board click Get Ready One of the channels should be highlighted in green. Click main button LV on. Check in happy pion what sensor type is connected to the Tell1 board and set the type on the highlighted channel. (If you are taking data with the dummy module you should always use R config) Click ON on button below highlighted channel.
 
Changed:
<
<
Master control on Single CB window. Control Board -> Get Ready -> LV on, then Beetle On (dummy module is R type)
>
>
Master control on Single CB window. Control Board -> Get Ready -> LV on, then Beetle On (dummy module is R type)
  go back to the terminal session on lbh8lx02
Line: 60 to 54
  ./writeEventsToBinary /misc/testbeamdata/TELL1NN_C#_D1#_D2#N_D3#N_D4#_RptN.bin 5000
Changed:
<
<
where NN should be replaced by tell1 number
D1,D2,D3,D4 means the connector to the tell1 counting from the top.
# cable number
RptN should be replaced by the repeater number.
>
>
where NN should be replaced by tell1 number D1,D2,D3,D4 means the connector to the tell1 counting from the top. # cable number RptN should be replaced by the repeater number.
  -- if you get an error with writeEventsToBinary, try resetTell1s in terminal, then reset in GUI, then configure correct Tell1 in GUI. Also check that the correct one is uncommented in ebuild.cfg

go back to the partition panel. start run.

Changed:
<
<
If you want to configure the module, it's another business. search the SingleCB panel open somewhere. go to the master control tab. click on NotReady or LVOFF button make a get ready. see if any cable shows life signs. if not try to read the LV instructions.
>
>
If you want to configure the module, it's another business. search the SingleCB panel open somewhere. go to the master control tab. click on NotReady or LVOFF button make a get ready. see if any cable shows life signs. if not try to read the LV instructions.
  then put LV on then look foryour cable on position. put it on. the dummy module is a R (rho) type.
Line: 75 to 71
  -- KazuyoshiAkiba - 03 Nov 2006
Changed:
<
<
How to operate all the tell1s and the new event builder. log in lbh8lx02 as daq password lhcbdaq
so source setupDAQ
>
>
How to operate all the tell1s and the new event builder. log in lbh8lx02 as daq password lhcbdaq so source setupDAQ
  load the recipe in the partition panel for the ODIN. use the recipe VeloTest09. follow the instructions above for it in case you think you are lost.

go for the ACDCTell1Control panel. click on the top level to configure/rest all of them...

Added:
>
>
before you start the event builder give a sensible name to the file

in the directory

/home/daq/cmtuser/Online/OnlineTasks/job

edit

../options/MDFWriterLite.opts

change the file which has the location

file:///misc/testbeamdata /velo....

 start the event builder by executing the script hltrx.sh
Changed:
<
<
do like this
go to OnlineTasks /job
>
>
do like this go to OnlineTasks /job
  do . hltrx.sh
 
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