o3gk当時のDAQ Channelsについて調査
全ては無理なのでprmとsrmを例として調査しました。
値はdata rateの合計で示している。

o3gk:
 PRM(Tower+Payload): 34,816
 SRMT: 24,576
 SRP: 43.008

比較のため、K-Log#17079のDAQ channels全データ量で再度算出:
Tower:
 変更前(OK): 70,912
 変更後(NG): 26,980
Payload:
 変更前(OK): 48,640
 変更後(NG): 64,000

さらに2021/06/05の検証時の結果も追記
 TOWER_MASTER_origin(OK): 70.912
 TOWER_MASTER_ng(NG): 26,980
 TOWER_MASTER_neworigin(NG): 50,944
 TOWER_MASTER_Only2K (OK): 69,376

まだ想定の範囲ではあるが、上記のデータからデータの総量が64Kを境界として、跨ぐとDAQ Timing Errorが発生しているようにも見える。

---

Survey of DAQ Channels at the time of o3gk
I can't do everything, so I investigated prm and srm as examples.
Values are shown as the sum of data rate.

o3gk:
 PRM(Tower+Payload): 34,816
 SRMT: 24,576
 SRP: 43.008

Calculated again with the total data rate of all DAQ channels in K-Log#17079 for comparison:
Tower:
 Before change (OK): 70,912
 After change (NG): 26,980
Payload:
 Before change(OK): 48,640
 After change(NG): 64,000

The results of the verification on 2021/06/05 were also added.
 TOWER_MASTER_origin(OK): 70.912
 TOWER_MASTER_ng(NG): 26,980
 TOWER_MASTER_neworigin(NG): 50,944
 TOWER_MASTER_Only2K (OK): 69,376

From the above data, it seems that the DAQ Timing Error occurs when the total amount of data crosses the 64K boundary.