...
- Debug the RD53A 0x0A53 (C) setup
- Special timing tests
- Cosmic telescope self-trigger mode ? Recovering 2nd module ?
- Systematic RD53a data taking runs
- Cosmic telescope data runs to map out all device areas
Activities: Ben, Timon, AdrienneAdrien, William, Sanha, SD
9:45 AM Beam turned on with ~40 hits per beam on MIMOSA
...
17:56 End Run 447 to request for access. Changed the RD53a scope monitor scale and brought the LEMO T of beam trigger to an NIM->TTL module and led the TTL LEMO to HSIO-2 TRIG1 port. Also replaced the data/cmd cable for cosmic telescope module 2 which has somewhat ragged noise.
18:20 Upon restart, the beam trigger no longer was no longer firing. Had to access again to back out the beam trigger T to NIM-TTL for the cosmic telescope. The 2016/Sep Even log did say the NIM signal on the BNC cable for the TLU was already rather marginal in amplitude and the was the last feather broke the camel. Wie probably should undo the T spaghetti on the beam trigger to use the NIM fanout to distribute replicated NIM signals cleanly.
19:18 Started Run 456 with beam trigger working again. We followed the written procedure of start_1 and found that only got one RD53a (SPEC#1) going. Texted Timon that we need to run start_0 in addition to bring up SPEC#0.
...
- Continued accumulating statistics with the current 2 LBNL RD53a modules at 0 degrees
- Investigate cosmicGui setup and routing beam trigger to HSIO2 for independent Cosmic telescope runs
- Continue developing the beam vs 40Mhz clock phasing measurement