...
14:25 Ended Run 428 for access.
15:10 Restarted datataking after access with same setup as before with single chip for Run 430.
15:30 Ended Run 430 to add 2nd RD53a.
RD53A timing setup adustments, Added a Lemo-T to the TLU beam trigger input to send a signal to HSIO2 Ext trigger LEMO port to allow cosmic telescope to be driven by the beam trigger independently with cosmicGui. Also took out the lemo on first module's HitOR just in case that might be a noise source.
15:10 Restarted datataking after access with same setup as before with single chip for Run 430.
15:30 Ended Run 430 to add 2nd RD53a.
15:35 Started Run 434 with both RD53a in DUT and data looked good. The L1 time between the two devices differed by a few BX, not clear why.
16:25 MCC called for a short beam off which we just ran through.
16:26: Started Run 441 with both RD53a with two FE-ID set distinctively.
16:50 Tried to run Cosmic Telescope with cosmicGui withe "scintillator trigger" being the beam trigger over LEMO, but no triggers seen. Upon checking Event Log from Sep/2016 session, it was noted there that the beam trigger came over with BNC cable was NIM. HSIO2 LEMO trigger is expecting TTL.
17:56 End Run 447 to request for access. Changed the RD53a scope monitor scale and
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 (#SPEC1) going. Texted Timon that we need to run start_0 in addition to bring up SPEC#0.
19:25 Ended 456 to start Run 457 with both RD53a.
15:35 Started Run 434 with both RD53a in DUT and data looked good. The L1 time between the two devices differed by a few BX, not clear why.