Page History

...

Matt recommends configuring the AxiStreamBatcherEventBuilder with a timeout value near what you expect the latency to be.  If something in the triggering is causing you to drop images, you'll likely see it in the batcher event builder statistics (dropCounts, labelled TimeoutDropCnt in devGui).  If you are dropping images, then eventually those FIFOs will fill up waiting for image data, and then deadtime will be asserted.  This should not be confused with "DropCount" in the FEB.  Larry Ruckman writes about the latter: "Caused by either software back pressure reaching FEB receiver (and need to drop the data) or clink framing error. Always if this condition happens, the the data and timing message will get out out sync because data has dropped before event builder. You will need to execute a "StopRun" to flush out the buffers then "StartRun" to re-synchronize the data/timingMsg alignment".

devGui is often helpful for seeing the state of the system and testing/debugging.  Unfortunately, it currently issues 'spf 0' at startup, which puts the camera in 8-bit/pixel mode while leaving the FEB's DataMode alone.  Giacamo has requested that image acquisition be done with 12-bit/pixel mode.  Just be sure to have a consistent state before starting to run with devGui.

...