We have set the beam momentum to 3 GeV 

1. ssh bastion

2. ssh belle-control

3. ssh telescope-admin@tb-aconite
(password telescope++)

dann:

How to generate trigger from TLU through FTSW to detector systems
2014.1.6 Mikihiko Nakao

* step 1 - open monitor window to show the FTSW status

 [you@bastion03 ~]$ ssh telescope-admin@belle-rpc1
  (still only limited people has access to b2daq account:
   ask DAQ people or Katsuro Nakamura of SVD group)

 [b2daq@belle-rpc1 ~]$ ssh telescope-admin@ttd10
 [b2daq@ttd10 ~]$ statft -55 -i -c
   (55 is the FTSW board-id, -i -c are to show the status repeatedly)

* step 2 - initialize FTSW to accept TLU trigger

 [b2daq@ttd10 ~]$ trigft -55 tlu

* step 3 - start trigger at TLU

 [you@bastion03 ~]$ ssh belle-rpc2
 [you@belle-rpc2 ~]$ ssh telescope-admin@tb-aconite
  (ask Alan Campbell or somebody for the password)

 telescope-admin@tb-aconite:~$ cd eudaq-nakao/bin
 ...$ ./TLUControl.exe -a 4 -d 1 -i RJ45 -w 10 -n

 here, -a option gives the possible trigger coincidence
  (-a 1  --- dummy trigger generator from FTSW)
   -a 2  --- trigger counter 1 only
   -a 4  --- trigger counter 2 only
   -a 8  --- trigger counter 3 only
   -a 6  --- trigger counter 1 and 2
   -a 10 --- trigger counter 1 and 3
   -a 12 --- trigger counter 2 and 2
   -a 14 --- trigger counter 1 and 2 and 3
 other options are kept to be the same
   -d 1 -i RJ45 --- connection to FTSW
   -w 10        --- update frequency (10msec)
   -n           --- suppress messages

 This gives you output like:

   Status:    00,--,--,--,--,-- (0,0)
   Scalers:   0, 7, 0, 0    <== from FTSW-dummy and trigger counters 1, 2, 3
   Particles: 1
   Triggers:  0             <== actual trigger to be distributed to FTSW
   Entries:   0
   TS errors: 0, 0 (redundancy, re-read)
   Timestamp: 0x4f25a008 (1327865864) = 3.45791
   Time: 3.463 s, Freq: 0 Hz, Average: 0 Hz

- 

 HV=100V  I=4.5uA

 HV=100V  I=4.2uA

accidentally hit reset button on PC which ended this run abruptly...

5 GeV beam

 HV=100V  I=4.3uA

centered position

5GeV beam

narrow timing (trigger width), but 6 samples

Created bad strip masks for the AIDA config files

BEAM mode:

• height (z): -346 (initially: -357)
• horizontal (x): -255 

OFF BEAM mode (Parkposition):

• height (z): +37
• horizontal (x): -255 

Richard Thalmeier   Tel. 4801

Hao Yin  

New SIS driver version sis1100-2.13-3 installed on DAQPC. 

To install the driver call as root:

cd /lib/modules/2.6.18-371.3.1.el5/extra

/sbin/modprobe sis1100

Check if /dev/sis* are created.

Managed to run the AIDA setup with old TuxDAQ version from T. Obermayer.

Will now try to install a newer version, which also supports ADC delay scan and internal calibration.

HV=100V  I=3.7uA
position = 0 / -30 mm relative to initial (but again centered) no idea ---
3GeV beam, multipeak 6 samples
???narrow timing (trigger width)??? no idea ...

HV=100V  I=3.7uA
position = 0 / -30 mm relative to initial (but again centered) no idea ---
3GeV beam, multipeak 6 samples
???narrow timing (trigger width)??? no idea ...

HV at 300V; I at app. 11µA 4GeV, Single mode

Modules centered to beam but no hits at additional Strixel modul. Perhaps HV problems (High noise of Strixel almost did not change after biasing)

-> HV connection will be checked at next opportunity to enter area.

HV 300V, I ca. 11µA single mode

HV 300V, I 10µA

Beam Energy changed during the run between 2GeV - 5GeV - 4GeV

Latency perhaps not optimal set (has been 95) but exchanged trigger cable seems to require 93