
PIXIE-4 User’s Manual
V2.69
©
XIA
2015. All rights reserved.
lxv
Disregard E filter requirement
In this mode, the energy filter requirement is ignored and any value can be entered for the
Window width
. The entered value is not modified by the software.
Use this mode if channels are independent so there is no need to wait for delays between
channels, or if a specified
Window width
is deemed sufficient and should not be modified
by the software.
Notes:
1) Any added coincidence window width will increase the time required to process an event
and thus reduce the maximum count rate.
2) In run types 0x100-0x301, pulses contributing during the readout of data (after the end of
the coincidence window) are lost. The readout may take several microseconds, longer if
waveforms are to be recorded.
7.6.2 Coincidences Between Modules
If more than one module is operated in the same PXI chassis, acceptance of events can also be
subject to the results of a system-wide (“global”) coincidence test. The result of the global test
is distributed over the TOKEN backplane line. This module coincidence test takes place in the
following steps:
After receiving a valid event trigger and waiting for the user defined coincidence window, each
module sends its channel hit pattern to slot 2 of the chassis using the PXI STAR trigger line
Each module determines the result of the local coincidence test based on its own 4 channels.
If enabled to do so, it signals the test result on the TOKEN line. If the local test passed, the
TOKEN line is left pulled up (3.3V, logic 1); else the TOKEN line is driven low (logic 0).
The module in slot 2, typically XIA’s PXI-PDM module, uses the up to 48 bit hit pattern from
up to 12 modules (slots 3-14) to make an accept/reject decision. If the hit pattern is acceptable,
the TOKEN line is left pulled up. If not acceptable, the TOKEN line is driven low (logic 0).
The decision criteria is based on a user defined control word, downloaded to the PXI-PDM by
its neighboring Pixie-4 module.
The acceptance decisions implemented in the current PDM firmware are described in detail in
the Pixie Viewer online help. For example, if the control word is 0x13 (0x14, 0x15, etc) events
are only acceptable if at least 3, (4, 5, etc) channels are hit. If the control word is 0x0200,
channel 0, but not 1, 2, and 3 must be hit in each module 0 and 1. The current firmware does
not claim to cover all cases. Please contact XIA to request additional cases or to obtain verilog
source code to write custom PDM firmware.
Each module, after waiting ~100ns for the global accept/reject decision to be made, captures
the status of the TOKEN line and puts it in the event hit pattern. The hit pattern also contains
the status of the backplane STATUS line, the result of the local coincidence test, and the status
of the front panel input at this moment. Depending on user settings, the event will be recorded
or discarded if the TOKEN and/or LOCAL bits are set in the hit pattern.
A full implementation of this feature thus requires an additional module in slot 2 of the chassis,
receiving hit patterns over the PXI STAR Trigger lines, making a coincidence decision, and
signaling the result on the TOKEN line. This can be XIA’s PXI-PDM module or any other
compatible PXI module. A limited coincidence decision can be made with Pixie-4 modules