Difference between revisions of "DAQ Testing/20190714"
From PREX Wiki
Jump to navigationJump to search (Created page with "Back to Main Page >> DAQ Documentation Portal >> DAQ Testing >> DAQ Commissioning Notes DAQ_Tes...") |
|||
| Line 8: | Line 8: | ||
==TS Synchronization Issues and Resolution== | ==TS Synchronization Issues and Resolution== | ||
| − | * | + | * [https://logbooks.jlab.org/entry/3704574 Issues recognized] |
| + | * [https://logbooks.jlab.org/entry/3703519 Paul reduces VQWK timeout (to avoid wrong timed data returns) and adds diagnostic words to CRL] - we start using the Helicity Signal added to HRS DAQs as a metric of in-time DAQ readout (timing of actual signals was always just fine) | ||
| + | * [https://logbooks.jlab.org/entry/3703831 Brainstorming], [https://logbooks.jlab.org/entry/3704039 solution proposed] - we ended up replacing the TS module during a day-down time and that resolved it completely | ||
[[Category:DAQ_Testing]] | [[Category:DAQ_Testing]] | ||
Latest revision as of 14:58, 24 September 2019
Back to Main Page >> DAQ Documentation Portal >> DAQ Testing >> DAQ Commissioning Notes
Previous Day of Testing << >> Next Day of Testing
July 14th, 2019 Testers: Cameron Clarke, Paul King, Bob Michaels
TS Synchronization Issues and Resolution
- Issues recognized
- Paul reduces VQWK timeout (to avoid wrong timed data returns) and adds diagnostic words to CRL - we start using the Helicity Signal added to HRS DAQs as a metric of in-time DAQ readout (timing of actual signals was always just fine)
- Brainstorming, solution proposed - we ended up replacing the TS module during a day-down time and that resolved it completely
