DAQ Meeting/20180524

From PREX Wiki
Jump to: navigation, search

Back to Main Page >> DAQ Documentation Portal >> DAQ Meetings

previous meeting << >> following meeting

Logistic information

 BlueJeans calling instructions:
 Toll-Free Number (U.S.&  Canada):  888-240-2560
 International toll number:         408-740-7256
 Bluejeans CODE:                  475 839 391
 Bluejeans link: https://bluejeans.com/475839391


  • Chandan, Tyler, Cameron : Verify signals coming into counting house Helicity DAQ are all what we expect
  • Bob : Set up RHRS ROC (read out controller) and DAQ and add to TS (trigger supervisor control)
  • Bob : Set up LHRS ROC and DAQ, add QWeak ADCs, connect to RHRS, and add to TS (should be harder)
  • Long-range plan :
    • Finish setting up all DAQ components to Trigger Supervisor Control (TSC) and verify all components work as intended
    • PAN, post-PAN and PAN-guin (Parity Analyze software) should all be rewritten, primarily to bring its functionality into the current group's control.


  • Morning - 9AM - Chandan, Tyler, Cameron : Verify signals coming into counting house Helicity DAQ are all what we expect.
    • We checked the signals coming out of the 4 modules in the Helicity DAQ (documented in the Helicity Control Board User’s Guide - Draft 2) and they behaved as expected (see figures 5 and beyond in the guide for visualization).
    • There are 4 separate signals (from left to right).
      • Pattern Sync (previously called, and currently labelled as QRT/Quartet, also called T_Stable): Logic spike for the duration of the first window of each helicity quartet. This signal can also be called T_Stable since when it is not true the Pockels Cell is stable.
      • T_Settle (previously called, and currently labelled as MPS/Master Pulse): Narrow spikes at the beginning of each individual helicity window. Indicates the time the DAQs will not collect data allowing for the Pockels Cell to settle. This signal goes to the users.
      • HEL (the delayed helicity signal, not the helicity signal sent to Pockels cell): Logic spike signal indicating the actual helicity state.
      • Pair Sync: On, off, on, off cycling logic spikes which cycle matching time with the helicity window and which tell you whether you are in the first or second window of any given pair (and consequently the position in a quartet, since quartets are just a pair and its converse in sequence). This signal toggle between 0 and 1, other wise it looks like the helicity signal. It is used to make T_Stable (the integration window). It goes to the users.
  • Morning - 10AM - Bob : Run RHRS .crl in CODA and see what happens.
    • It doesn't work, so we went to go see what is happening with the wires and crates on the RHRS itself (descriptions of different kinds of crates and modules.
    • The RHRS VME crate (located on the top level of the RHRS hut, in a free-standing VME crate) has, from left to right:
      • An MVME 6100 (required CPU for interfacing with QWeak ADCs) ROC.
        • ROC Number 26 in software, hardware number is in the config files (likely not changed, even if in fact the CPU was swapped out recently, since it worked in CODA using the preset .crl config files).
        • It had been modified (probably replaced by someone else in the last two years) so that its boot scripts were all wrong.
        • We copied the boot script information from files stored in adaq3 (using a laptop next to the VME with login information written on it to SSH into the counting house ADAQ3).
        • To access the boot sequence remotely we needed to enter via telnet using a serial port. This required plugging in the appropriate proprietary networking cable and telnetting into the nearby portserver (named hatserv3) (connection port number 2) via the available laptop's connection to ADAQ3.
      • A TI (Trigger Interface) board (used for connecting via RS45 flat cable number 21 to the LHRS and sending both sets of signals to the counting house).
      • An ELEXIO board.
      • Two QWeak VME ADCs.
        • Both were missing their EXT input NIM logic trigger (MPS/T_Settle) signals.
        • We re-connected them, shuttling the T_Settle/MPS signal from NIM logic outputs in the Helicity NIM module.
        • The Helicity NIM module is also located in the top floor of the RHRS hut, but closer to the stairwell in the Helicity NIM crate.
      • One Happex Timer - which was missing its T_Settle/MPS signal (similarly obtained from the NIM crate, using a TTL signal output instead).
    • A parallel VME crate with two Happex Timing Boards (HTB).
      • These boards receive a signal from the QWeak ADCs through a small flat set of wires and can be used as a diagnostic for the T_Settle/MPS receipt of signal for the QWeak ADCs.
      • We saw that there was no real data coming from the RHRS ROC at first, and the two lights on each HTB were both green (CODA kind of complained and the data was mostly null 0x0000 values).
      • We noticed that the Helicity NIM crate near the stairs was off, turned it on, and immediately the HTB top lights turned yellow and the data began to flow from the QWeak ADCs to the ROC to CODA.
  • Morning - 11AM - Bob : We look at the situation of the LHRS.
    • The LHRS ROC is number 25 in software, it is located on the bottom level of the LHRS hut, and it lacks QWeak ADCs (need two, one per each 8 signals we want to read from detectors).
    • We connect the RS45 number 21 cable connection into the LHRS ROC's TI board.
    • We need to find a ~5m long RS45 cable (preferably shielded) to connect from the loose end on the RHRS into the RHRS TI board.
    • The TI boards need to have resistor caps if they are the end of a chain (this applies to the Counting House and Injector TI boards).
  • To do tomorrow - Bob : Finish the LHRS connections.
    • Connect the trigger-in TTL signal from the T_Settle/MPS helicity NIM crate into the LHRS ROC 25, as well as into two new QWeak ADCs (NIM signal).
    • Connect the flat RS45 cable number 21 between the L and R HRSs.
    • Make sure that the LHRS ROC connects to the ASAQ3 CODA in the counting house, and make sure that the ROC's hardware RAM ROC code is correctly set in Prex.crl.
      • First run the Prex.crl standalone.
      • Next connect TS control with the Prex_ts.crl (if possible, troubleshoot).
      • Then merge all of (LHRS->RHRS + Injector) -> Counting House all work together under TS control.