
PIXIE-4 User’s Manual
V2.69
©
XIA
2015. All rights reserved.
lx
7.3 Run Synchronization
It is possible to make all Pixie-4 modules in a system start and stop runs at the same time by
using a wired-OR SYNC line on the PXI backplane. In all modules the variable SYNCHWAIT
has to be set to 1. If the run synchronization is not used SYNCHWAIT must be set to 0. The
variable is set by checking the corresponding checkbox in the
Run Control
tab of the Pixie
Viewer.
The run synchronization works as follows. When the host computer requests a run start, the
Pixie-4’s DSP will first execute a run initialization sequence (clearing memory etc). At the
beginning of the run initialization the DSP causes the SYNC line to be driven low. At the end
of the initialization, the DSP enters a waiting loop, and allows the SYNC line to be pulled high
by pullup resistors. As long as at least one of all modules is still in the initialization, the SYNC
line will be low. When all modules are done with the initialization and waiting loop, the SYNC
line will go high. The low->high transition will signal the DSP to break out of the loop and
begin taking data.
If the timers in all modules are to be synchronized at this point, set the variable INSYNCH to
0 by checking the corresponding checkbox in the
Run
tab of the Pixie Viewer. This instructs
the DSP to reset all timers to zero when coming out of the waiting loop. From then on they will
remain in synch if the system is operated from one master clock.
Whenever a module encounters an end-of-run condition and stops the run it will also drive the
SYNC line low. This will be detected in all other modules, and in turn stop the data acquisition.
Note that if the run synchronization is not operating properly and there was a run start request
with SYNCHWAIT=1, the DSP will be caught in an infinite loop. This can be recognized by
reading the variables INSYNCH and SYNCHWAIT. If after the run start request the DSP
continues to show INSYNCH=0 and SYNCHWAIT=1, it is stuck in the loop waiting for an
OK to begin the run. Besides rebooting, there is a software way to force the DSP to exit from
that loop and to lead it back to regular operation. See the Programmer’s Manual for details.
7.4 External Gate and Veto (GFLT)
It is common in larger applications to have dedicated external electronics to create event
triggers or vetoes. Besides the external trigger described in section 7.2.5, the Pixie-4 also
accepts a global first level trigger (GFLT). This signal acts as a validation for an event already
recognized by the Pixie-4. Using multiplicities and/or other information, the external logic
needs to make the decision whether to accept or reject a given event. If that decision can be
made within the filter time (energy filter rise time plus flat top) of all Pixie-4 channels involved,
then the GFLT function can be used. By definition, GLFT is a global signal that applies to all
channels.
In a second scenario, the acquisition may have to be inhibited for certain intervals. An example
is the on/off cycle of a neutron generator, and events may only be of interest if the generator is
off. This condition can also be accommodated by the GFLT function, but is often described as
vetoing the acquisition while the signal is on. We thus use the names GFTL and VETO
interchangeably.