Versions Compared

Key

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

...

- look for deadtime
- check that the "partition" window (with the trigger-enable checkbox) is talking to the right XPM (currently "2" ... selects which XPM to use (across crates))
- HSD is not configured to do anything (Check the HSD config tab for no channels enabled)
- XPM is not configured to forward triggers to HSD ("LinkEnable" for that link on the XPM GUI)
- if hsd timing frames are not being received at 926kHz (status here), click TxLink Reset in XPM window
- L0Delay set to 99
- The HSD configuration partition number does not match platform number in .cnf file (Check the HSD "base" tab)
- DST Select (in PART window) set to "DontCare" (could be Dontcare/Internal)
- also check that HEADERCNTL0 is incrementing in "status" tab of HSD cfg window.
- check processes in lab3-base.cnf are running
- check health of XPM with:
- source launch_py, and exit from python prompt to get env
- camonitor DAQ:LAB2:XPM:2:LinkRxRcv0
- run psdaq/build/psdaq/pgp/kcu1500/app/kcuStatus and kcuDmaStatus
in kcuDmaStatus "blockspause" and "blocksfree" determine whether or
not deadtime is set. if blocksfree drops below blockspause then it
will assert deadtime. in hsd window "pgp last rx opcode" 0 means no
backpressure, 1 means backpressure
- in hsd window timepausecnt is number of clocks we are dead
- in hsd expert window "full threshold(events)" sets threshold for hsd deadtime
- in hsd status window "fex free events" and "raw free events" are the current free events.
- in hsd status window "write fifo count" is number of timing headers waiting for HSD data to associate.

...