Page History
...
epix10ka_0026_20210510164634_mfxc00118_r0372-MfxEndstation-0-Epix10ka2M-0-seg00-cc057-AHL-H-fit-r014-c353-ibr02-ibc50.png
Explanation from Dan
Code Block | ||||
---|---|---|---|---|
| ||||
Dubrovin, Mikhail
Tue 6/8/2021 3:33 PM
Dan,
This is mfxc0018 run 372 calib-cycle 8 (counting from 0).
The gap in time between events happens twice in this cc.
There may be different question to ask, what is a trigger signal for pulser intensity increment?
Mikhail
Damiani, Daniel S. <ddamiani@slac.stanford.edu>
Tue 6/8/2021 4:47 PM
The pulser increments intensity each time the camera does a “normal” (a.k.a not the ghost correction acquistions) acquisition cycle. The acquisition is triggered by a run trigger, generated by the evr firmware blob in the pgpcard and sent over the fiber to the detector. This is constantly running at 120 Hz (event code 40) even if the daq is not in a running state.
Dan
Hart, Philip Adam <philiph@slac.stanford.edu>
Tue 6/8/2021 5:02 PM
What happens during the flaky circumstances you note? From what Mikhail describes it sounds like we're running the pulser still but not the DAQ.
- Philip
Damiani, Daniel S. <ddamiani@slac.stanford.edu>
Wed 6/9/2021 4:25 AM
Hi, If the pgpcard is seeing event code 40s on it’s timing fiber it will still trigger acquisitions of the camera and increment the pulser. The running state of the daq has no affect on this. Generally the best we can do (which should be fine) is to assume pulser increments every three fiducials
Dan |
References
...
Overview
Content Tools