 Fri Mar 14 22:13:14 2025, elog-producer, 1st tests with beam, , TJ-Monopix2, 800 MeV, Low Flux Very Low, Proton, Unknown, , , , HV, None,
|
| APV25 latency 42 required for these input stretches |
|
Fri Mar 14 22:41:16 2025, elog-producer, 1st tests with beam, , TJ-Monopix2, 800 MeV, Low Flux Very Low, Proton, Unknown, , , , HV, None,
|
| ignored veto of tracker |
|
Fri Mar 14 22:48:01 2025, elog-producer, 1st tests with beam, , TJ-Monopix2, 800 MeV, Low Flux Very Low, Proton, Unknown, , , , HV, None,
|
| max trigger 75 -> 100 |
|
Fri Mar 14 23:21:26 2025, elog-producer, 1st tests with beam, , TJ-Monopix2, 800 MeV, Low Flux Very Low, Proton, Unknown, , , , HV, None,
|
| wrong trigger mode used for tracker |
|
Fri Mar 14 23:22:22 2025, elog-producer, 1st tests with beam, , TJ-Monopix2, 800 MeV, Low Flux Very Low, Proton, Unknown, , , , HV, None,
|
| changed telescope timing again to latency 40 |
|
Fri Mar 14 23:32:56 2025, elog-producer, 1st tests with beam, , TJ-Monopix2, 800 MeV, Low Flux Very Low, Proton, Unknown, , , , HV, None,
|
| 208 shows correlation |
|
Sat Mar 15 01:38:17 2025, elog-producer, Fast RO Test, 216, TJ-Monopix2, 800 MeV, Low Flux Medium, Proton, Unknown, , , , HV, None,
|
Fast RO for Monopix:
W02W01 8b10b error quite early
Delay = 2
rd_frz_delay = 2
LOAD_CONF=10
FREEZE_STOP_CONF=11
STOP_CONF=10 |
|
Sat Mar 15 01:51:31 2025, elog-producer, Fast RO Test, , TJ-Monopix2, 800 MeV, Low Flux Medium, Proton, Unknown, , , , HV, None,
|
| Run 219, Medium settings, fast RO, W02R01 to 8b10b a few minutes in |
|
Sat Mar 15 01:58:29 2025, elog-producer, Fast RO Test, , TJ-Monopix2, 800 MeV, Low Flux Medium, Proton, Unknown, , , , HV, None,
|
| Run 220, 8b10b error |
|
Sat Mar 15 02:34:31 2025, elog-producer, Fast RO Test, , TJ-Monopix2, 800 MeV, Low Flux Very Low, Proton, Unknown, , , , HV, None,
|
| Run 223, 8b10b error again |
|
Sat Mar 15 02:46:47 2025, elog-producer, energy scans, , TJ-Monopix2, 252.7 MeV, Low Flux Very Low, Proton, Unknown, , , , HV, None,
|
| sticking with fast RO settings |
|
Sat Mar 15 02:56:07 2025, elog-producer, energy scans, 225, TJ-Monopix2, 252.7 MeV, Low Flux Low, Proton, Unknown, , , , HV, None,
|
| 8b10b W02R01, 1 MHz rate (low flux low) |
|
Sat Mar 15 03:14:22 2025, elog-producer, energy scans, 226, TJ-Monopix2, 252.7 MeV, Low Flux Very Low, Proton, Unknown, , , , HV, None,
|
| Run 226 |
|
Tue Aug 5 14:43:42 2025, elog_producer, Castid, , TJ-Monopix2, 800 MeV, Low Flux Medium, Proton, Crap, , , , HV, None,
|
| test |
|
Tue Aug 5 16:02:12 2025, elog_producer, Castid, , TJ-Monopix2, 800 MeV, Low Flux Medium, Proton, Crap, , , , HV, None,
|
| manual test |
|
Tue Aug 5 16:12:07 2025, elog_producer, Castid, , TJ-Monopix2, 800 MeV, Low Flux Medium, Proton, Crap, , , , HV, None,
|
| Test debugging tests for debugging to test debugging |
|
Sat Aug 16 23:44:00 2025, Maximilian Babeluk, CASTID - Summary, , TJ-Monopix2, 800 MeV, , Proton, , , , , , ,
|
Summary for the CASTID shift RO Aug 16, 2025
We measured four TJ-Monopix2 DUTS with HV/HVC frontends using AIDA mode in a stacked telescope configuration. We used 800MeV protons at low flux settings from very low to high.
We took two high statistics runs on each of the 4 rates. Then we repeated the measurements at medium and high settings for following readout speeds (40 is the default): 30, 20, 10, 2 (minimum).
At increased readout speed, we shoudl be able to recover (part) of the efficiency drop at increased rates.
- Occasionally (maybe a few times an hour but in clusters) we got 8b/10b errors. If so, they all came from the W02R01 DUT using BDAQ board #063/50 and the TLU adapter 1. This is the main source of having 'crap' data
- About 3 times during the test beam, one of the chips (each time a different one) stopped sending data which was possible to recover with a power cycle.
|
|