Difference: July2019DESYTBlog (2 vs. 3)

Revision 32019-07-23 - AtlasjSilicon

  META TOPICPARENT 
 name="July2019DESYTestbeam" 

 July 2019 DESY Testbeam log page 

 July 22, 2019 

8:00 breakfast meeting with Andre

8:40 registered DACHS card at bld. 6

9:30 received DACHS card

13:00 safety training (only listen, no test)
- META TOPICPARENT
+ name="July2019DESYTestbeam"
-<
<
+:00 setup
->
>
+:00 setup (there were many problem)
-<
<
+ about setup
->
>
+:00 completed YARR system setup
->
>
+ July 23, 2019
->
>
+:00 YARR producer lauched.

1:30 RunControl PC could communicate with NI crate (telescope)

2:00 Norway 3D module did not work. it did not give signal.

3:00 revealed that RunControl PC could not communicate with YARR producer. (YARR producer did not accept orders from RC PC.)

10:00 the above issues is resolved. we were able to go with combines telescope + FEI4 system into auto trigger run.

16:00 issues about communication with RC PC and BDAQ is resolved. But issue about Event Build happened. It was that the data from BDAQ is different with data by making from Event Build.)
 YARR system
 constraction YARR system

login user:testbeam
-<
<
+the YARR pc IP address -> 192.168.22.199
->
>
+the YARR PC IP address -> 192.168.22.199
-<
<
+( BDAQ IP -> 192.168.22.198 )
->
>
+( BDAQ PC IP -> 192.168.22.198 )
 ( Run Control PC IP -> 192.168.22.1 )

( NI crate IP -> 192.168.22.2 )

install new software ( https://yarr.readthedocs.io/en/latest/install/ )

and

install new firmware ( https://yarr.web.cern.ch/yarr/firmware/ -> "2019_07_21-rd53a_ohio_3chip_1tlu-xpressk7_325.bit" )

source /opt/Xilinux/Vivado/2016.02/settings64.sh

python flash.sh (@ ~/work/yarr_rd53a/YARR-FW(Yarr is a symbolic link with Yarr-fw_20190722)/script)

select #6 (rd53a_ohio_3chip_1tlu_xpressk7_160.bit)

if finish, reboot.

./bin/scanConsole -r configs/controller/specCfg.json -c configs/connectivity/example_rd53a_setup.json -s configs/scans/rd53a/std_digitalscan.json -p (@ ~/work/yarr_rd53a/Yarr) <- this is like rd53a_test
->
>
+if it happend some problems, confirm seup. I wrote especcially careful things. when regulator mode... 
 jumper is inserted at VINA (at PWR A) and VIND (at PWR D).
  cables cnnecting with RD53A power is propely hot or GND side.
  current 480~500 mA (KEK53-9 1.85V)
  voltage drop between ~~~ and ~~~
  if it happends that voltage difference between 2 hot side pins of 4 pin, you do short by jumper inserting at JP PWR.
  GND of XpressK7 need to be GND of RD53A power
  
 
nothing problem -> tune RD53A

this time, we used automatically tuning software by using below command.

./scripts/tune_rd53a.sh 1500 1500 10000 10 configs/controller/specCfg.json configs/connectivity/example_rd53a_setup.json

wait for 15~20min. if finish, do noise scan.

./primlist/scan53.sh noisescan KEK53-9 -m 1

./primlist/scan53.sh noisescan KEK53-9

 set producer, communicate with Run Control PC 

How to set YARR producer

read "README.md @~/work/yarr_rd53a/YarrEudaqProducer_20190722/

communicate with Run Control PC (The HOSTNAME variable needs to be set)

Run Control PCが命令を出すと，YARR producerがdescript? figure?を書き，memoryがoverして動作が重くなった．

->??

Can NOT communicate BDAQ producer and RunControl PC
 memo
 producer, communication between run control PC and BDAQ PC

cards for read out some module by creating Nakamura working test

multi module working test

--   Koji Nakamura  - 2019-07-22 

 Comments 

 
  (Edit - Preview)
 
<--/commentPlugin-->

View topic | History: r18 < r17 < r16 < r15 | More topic actions...