...

- ./STARTRUN
- wait approx. 20 sec. until all Connections ping (unitialized)
  
4. OpenStart TLUproducer on TLUproducer computer.  N.B. this is currently the YARR computer but we need to change this when the YARR folks are not at SLAC! (-BPN 6/1/2018)

- (if not done already: ssh -Y pixel@172.27.104.52; there is an ssh key so no password should be needed. pwd is: testbeam if sshkey fails)

- cd /local/pixel/eudaq/eudaq-1.7/bin

- ./TLUProducer.exe -r 172.27.100.8:44000

esadutdaq1  

- (if not done already: start a terminal on ar-eudaq and ssh -Y beam@esadutdaq1 (ask Su Dong or others for password)  

- cd eudaq-1.7/bin

- ./TLUProducer.exe -r 172.27.100.8:44000

--> 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 --> 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.   

...

 
6. Configure EUDAQ in eudaq Run Control
- select init file (can use the 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

Telescope operation (EUDAQ v1.5)

0. In ESA:

...

EUDAQ Online Framework

The

EUDAQ Online Framework

The EUDAQ software operation involves 3 types of main entities: 

...

While the DUT readout can be of variety of ways, the RCE readout setup is provided for at least ATLAS pixel users as a standard utility. As of AprJuly/20162018, the DUT RCE readout is upgrading from old the Gen-1 RCE + HSIO setup to a simpler HSIO-II setup with EUDAQ-1.7, with the dedicated ESADUTDAQ1 Sun server also upgraded to a fanless PC residing the beam tunnel near the EUDET area as the DUT RCE readout host. HSIO-II has the DTM mezzanine with the Gen-3 ZYNQ based RCE operating an Arch-Linux based Centos-7 on the ARMS CPU that communicates with external world via its native 1Gb/s Ethernet. More general information on HSIO-II/RCE can be found on the RCE Development Lab Twiki.

...

At least calibration actions will need X window displays so that the -Y qualifier through out is necessary. Then continue to hop onto the DUT readout node as dedicated user tbslacbeam:

  ssh -Y esadutdaq1 -l tbslacbeam
  cd ~/daq/rce 
  source ./scripts/setup-gen3.sh

For normal EUDAQ data taking, you need to start and announcing RCE DAQ as a data producer to EUDAQ run control node ar-eudaq with just one command:  

  rceOfflineProducer -r 0 -d 172.27.100.8     

If everything is run smoothly, once you brought up the overall DAQ with EUDET through EUDAQ run control node ar-eudaq, you should see the RCE data producer show up in the producer list. If RCE producer seems to be not behaving correctly even upon restarting, you can reboot the HSIO from the ESADUTADQ1 console with the command:

  rebootHSIO -r 0  

/rce 
  source ./scripts/setup-env.sh

For normal EUDAQ data taking, you need to start and announcing RCE DAQ as a data producer to EUDAQ run control node ar-eudaq with just one command:  

  rceOfflineProducer -r 0 -i 192.168.1.1 -d 172.27.100.8     

If everything is run smoothly, once you brought up the overall DAQ with EUDET through EUDAQ run control node ar-eudaq, you should see the RCE data producer show up in the producer listAfter ~ half a minute, you can restart the rceOfflineProducer as instructed above. In the very rare event that this still doesn't get you out of trouble due to the problem with the FPGA side of HSIO-II, you can power cycle the HSIO-II remotely from the EPICS controlled power strip which has a dedicated socket for the HSIO-II. 

Pixel Calibrations      

...