Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • (done) Move to Rogue 6: v 1.0.0
  • current configuration time is long at 34s
    • some progress on this: now 10s according to Ric (check that we're down to 2-3 seconds that rogue sees?)
  • fiber-power monitoring on the detector side and kcu1500
    • not there yet on march 22, 2024
    • (done for the detector as of v1.1.5 of epix-hr-m-320k)
  • (done?) have to manually lock the lanes between ASICs and managing FPGA by running 1000 events: feels awkward-ish
    • what does epixHR do?
  • not all lanes in an ASIC lock (can perhaps be fixed with improved delay settings)
    • most have 3-5 lanes that don't function or are unstable (out of 24) for unit 0xbf
  • data is currently scrambled (not natural order)
    • ric is descrambling ASICS in software, but would like to move to firmware
  • (done) remove epixViewer imports in _Root.py
  • on May 11, 2024 lost timing link from epixM to xpm7 (had to power cycle).  Include Julian's latest link fixes in your firmware.
  • need eye-scanning for all transceiver links
  • add batcherEventBuilder to kcu1500
    • use Lcls2EpixHrXilinxKcu1500Pgp4_10Gbps, which contains a BEB
    • make the ePixM devGui compatible
  • (done) remove 8 bytes of null padding between timing header elements
  • fix set-registers-before-each-charge-injection-event issue
    • Implement FPGA registers to rearm ASICs on each event when test register is true?
  • (done) Split prepareChargeInjection() into 2 functions, the first taking first and last column (as now) and the second taking a 384 element numpy array (e.g., setupChargeInjection(self, asicIndex, lane_selected, pulserValue))
  • (done) Since the scan work, normal data taking runs now see dropped and short frames from ASIC 0
  • DAQ has no environmental monitoring support as yet
    • needs board re-spin (boards in layout on March 22, 2024)
  • (fixed by Dawood in late Aug 2024, according to Alex) need new config object when swapping detectors to pick up per-detector delay settings
  • will epixM automatically increase charge with each injection pulse like epixHR?  Dionisio thinks probably not (will double-check with Lorenzo).
  • (done?) zmq server port gone with rogue6?  needs to be re-added?
  • need to know common-mode "bank" info
    • each lane?
    • other structures for ADC?
  • v1.1.5 of epix-hr-m-320k introduced per detector instance yaml files, which implies that if a detector is swapped out, either:
    • the configDb for the given detector alias must be reinitialized, or
    • a different detector alias and configDb instance must be set up
      • requires corresponding .cnf changes

...