Automated QA upload result.

Automated QA upload result.

Automated QA upload result.

Automated QA upload result.

1. The DHCP Server (router) PC must be turned on and working before turnning on the RFSoCs
   • Once they turned on without the proper IP Address asignment, they are unabled to connect via LAN → We need to have a power cycle (turn off the lack power).
   • Linux DHCP server can stop to work for DHCP assignment unexpectedly. It's safe to restart the dhcp service before turn the RFSoCs on (it happened for kea-dhcp4).
2. Whenever change the host PC handling the RFSoCs, we need to reset their configurations in the babicon, especially the host name (e.g. 192.168.0.3 (QA PC) → 192.168.0.1 (RFSoCDAQ))
3. ttd can esilly stop working. if the trigger count is not increasing with the proper trigger input, consider reprograming the ttd with its init command in telnet.
4. gtr stoped working this time. Maybe we just ignore its proper working procedure. But, it didn't ssend the trigger signal even though it blinks the trigger output to the ttd (right red, green led blinks). It might be related to the busy-out from the ttd and busy-in on the gtr
5. So far, we took the data with a common coincidence electronic by adding the busy-out from the ttd

片付け完了（11:30） 一部箱が無い？ ねじケースの蓋がない

最終データ取得 Events = 66213

インターネットの通信速度がデータ取得レートに大きく関わりそう? RFSoCDAQを直接LANポートにつないでみる。(テストベンチ内) そうでもなかったが一応上がった？ 40 Hz → 49.7 Hz

DUTの位置がズレてたため再調整 全てのRFSoCで同期信号を確認 一部ノイズあり

調整後データ取得開始

【注意】ケーブルが長い

RFSoCDAQPCがGTR,TTD,RFSoCに接続できない状態だったので、 RFSoCDAQPCを再起動し、ネットワークを再構築しました。

RFSoC04が接続不良で青いボタンが点灯し、04のみネットワーク接続できない状態になっていました。 一度電源を落とし、04をしっかり指し直した結果、RFSoC全てでうまく接続するようになりました。

組立＆ケーブリング完了 (00:50)

AstroPix Data taking 終了(23:10)

The test beam data are saved in /home/epicuser/data/2026-02_KEK and /home/data/2026-02_KEK

From 22:00, we disassembled the oscilloscope from wave runner 3, 4, 5.

Automated QA upload result.

Automated QA upload result.

Automated QA upload result.

Automated QA upload result.