...
--> check in eudaq Run Control, that Produce TLU is connected
5. Start DUT data producer(s) if not running telescope by itself.
- For standard RCE based DUT readout, this should be just starting rceOfflineProducer on esadutdaq1. starting from an ar-eudaq console terminal
ssh -Y esadutdaq1 -l beam [pw=TestBeamUser]
cd ~/daq/rce
source ./scripts/setup-env.sh rceOfflineProducer -r 0 -i 192.168.1.1 -d ar-eudaq - For YARR based readout (for beam rigger runs), login
to pixel@172.27.104.52 as inssh the-XY TLUProducer case, then pixel@esadutlbnl1 (pw=Testbeam)
cd YarrEudaqProducer
bin/YarrProducer -h configs/controller/specCfgExtTrigger.json -c configs/connectivity/example_rd53a_setup.json -s configs/scans/rd53a/std_exttrigger.json -r 172.20.100.8/start_1.sh
6. Configure EUDAQ in eudaq Run Control
- select init file (should just use the default example) and init; then select Config file
(Caladium only exercise config: no-beam: ni_autotrig;
beam: ni_coins, June test beam 2018, ni_coins_YARR)
- Press Config
- wait till all Connections are green (OK)
7. Start Run
- Press Start (wait till all green)
--> check, that Trigger and Event Built numbers are increasing
--> check OnlineMonitor, and reset (upper left x-button)
8. Stop
- Re-configure (5.) and Re-Run (6.)
OR
- Terminate and press "Reset" in MI26.exe at NI crate to stop sensors --> check 2.0 Amps
...
- For HSIO2-module communication: Ground wire between HSIO2 LV supply Molex pigtail and pixel module LV PSU ground
- For HSIO2-TLU communication: Lemo cable between TLU trig0 TTL and any of the HSIO2 main board LEMO bank socket
If you are not running the system from the ESA console next to the EUDET, but from some public nodes at SLAC, you need to first hop onto an ESA public machine on the 172.27.100 subnet and login as yourself e.g.
...
ssh -Y esadutdaq1 -l beam [pw=TestBeamUser]
cd ~/daq/rce
source ./scripts/setup-env.sh...