ZLE firmware

Basic

Input

parameter ChGain

Unique to x2730.

Sets the gain of the Variable Gain Amplifiers (VGA). Unit of Measure: dB

parameter InputDelay

Set input delay. The value is set at groups of 4 channels for x2745/x2740.

Unit: sample

parameter ChEnable

Enable the channels for the acquisition, according to the Index. When the channel is disabled, it does not give any data and its self-trigger is off.

• True: The channel is enabled for the acquisition

• False: The channel is disabled for the acquisition

parameter WaveSource

In normal mode, the acquired waveform represents a sequence of ADC samples, resulting from the A/D conversion of the analog input. For test purposes, it is possible to replace the ADC data with internal data generators.

• ADC_DATA

  • Data from the ADC (normal operating mode)

• ADC_TEST_TOGGLE

  • Toggle between 0x5555 and 0xAAAA (test mode)

• ADC_TEST_RAMP

  • 16-bit ramp pattern (test mode)

• ADC_TEST_SIN

  • 8-point sine wave test pattern

• ADC_TEST_PRBS

  • 16-bit PRBS generated by a 23-bit PRBS pattern generator (test mode)

• Ramp

  • Data from a ramp generator. It is actually a 16-bit field, where the 6 most significant bits identify the channel and the 10 less significant bits are the samples of a ramp from 0x000 up to 0x3FF (i.e. 0 to 1023). It is so a 10-bit ramp with offset given by “channel*1024”. For channel 0, it is a counter from 0 to 1023; for channel 1, it is a counter from 1024 to 2047, and so on

• IPE

  • Not implemented

• SquareWave

  • Internally generated programmable square wave

parameter DCOffset

A constant DC offset (controlled by a 16-bit DAC) is added to the analog input, individually for each channel, to adjust the position of the signal baseline (that is the “zero volt” of the analog input) within the dynamic range of the ADC. Because of the tolerance of the components, it is necessary to calibrate the offset DAC. The calibration is done by factory testing and normally it is not necessary to recalibrate the digitizer. It is however possible to perform a new calibration. The calibration parameters are stored in the flash memory of the board and loaded at power on. They are automatically applied by the internal logic every time the DCoffset parameter is written or read. DCoffset is expressed as a NUMBER number, in percent of the full-scale. When the DCoffset is 0, the baseline of the input signal is at 0 ADC counts. When the DCoffset is 100, the baseline of the input signal is at $2^{NBIT}-1$ ADC counts.

Unit of Measure: %

parameter Polarity

Allows to set the polarity of the input pulse.

• Positive

  • Positive polarity

• Negative

  • Negative polarity

parameter VGAGain

Unique to x2745.

Set the gain of the variable gain amplifier (VGA) in increments of 0.5 dB. Parameter settings are grouped every 16 channels, with 64 channels divided into 4 groups. The minimum can be set to 0 and the maximum to 40.

Trigger

parameter TriggerThr

Each channel of the digitizer has a digital leading-edge discriminator with programmable threshold able to self-trigger on the input pulses and generate a self-trigger signal (or an overthreshold signal) feeding the internal trigger logics or digitizer outputs. This parameter sets the trigger threshold. Typically, the value is relative to the baseline of the signal and the threshold is a 17-bit signed NUMBER number; in this case, the threshold automatically follows the baseline when the DCoffset parameter changes. Sometimes, it is preferable to set an absolute value for the threshold, referred to the ADC range. In this case, the threshold is unsigned NUMBER number.

ZLE

parameter PreTrigger

Number of samples coming before the position of the trigger in the waveform (i.e. size of the pre-trigger window).

Unit of Measure: Samples

parameter SupperThr

The ZLE algorithm further checks whether the ZLE suppression threshold (ZLESupprThreshold) is crossed and saves the overthreshold samples (under threshold in case of negative polarity), which are referred as “good” samples. In addition, also a programmable number of samples can be acquired before and after the over/under threshold (ChLookBackSamples and ChLookForwardSamples respectively). “Skipped” samples are discarded; only a word reporting the number of skipped samples is present in the final data. This parameter allows to set the ZLE data suppression threshold.

The figure below shows the parameters of the ZLE algorithm. The signal recording starts ChLookBackSamples samples before the ZLE threshold crossing (LBW in the picture) and stops ChLookForwardSamples samples after the crossing in the opposite direction (LFW in the picture). The recorded regions define the ROI (region of interest) of the algorithm. Outside the ROI the algorithm reports the number of skipped samples.

parameter LookBack

This parameter allows to set the ZLE look-back samples.

Unit of Measure: Samples

parameter LookForward

This parameter allows to set the ZLE look-forward samples.

Unit of Measure: Samples

parameter EnZLESuppr

When this bit is set, no ZLE data reduction is applied.

• True

  • ZLE Data reduction is enabled.

• False

  • ZLE Data reduction is disabled.

parameter ValueSource

Selection of the default sample value in the payload (baseline or register).

• Baseline

  • Default sample value is Baseline.

• Register

  • Default sample value is the value.

parameter ValueRegister

ZLE default sample value register.

Unit of Measure: ADC counts

parameter RecordLength

The waveform Size (i.e. size of the acquisition window). The actual size of the waveform will be automatically rounded to the closest allowed value. It is possible to get the exact size by reading back the parameter. The record length in time depends on wave resolution.

Unit of Measure: Samples

Debug

parameter TestPulsePeriod

The Test Pulse is a programmable square wave that can be used as an internal periodic trigger (mainly for test purposes) or to generate a logic test pulse (TTL or NIM) on the TRGOUT and GPIO outputs. This parameter sets the period of the Test Pulse.

Unit of Measure: ns

parameter TestPulseWidth

Width of the Test Pulse (time that the signal stays high = 1).

Unit of Measure: ns

parameter TestPulseLowLevel

Low level of the Test Pulse expressed in ADC counts

Unit of Measure: ADC counts

parameter TestPulseHighLevel

High level of the Test Pulse expressed in ADC counts

Unit of Measure: ADC counts

parameter DACoutMode

Selects the signal type to be sent in output on the front panel DAC connector.

• Static

  • DAC output stays at a fixed level, given by the DACoutStaticLevel parameter

• Ramp

  • The DAC output is driven by a 14-bit counter

• Sin5MHz

  • The DAC output is a sine wave at 5 MHz with fixed amplitude

• Square

  • Square wave with period and with set by TestPulsePeriod and TestPulseWidth and amplitude between TestPulseLoweLevel and TestPulseHighLevel.

• IPE

  • Not implemented

• ChInput

  • The DAC reproduces the input signal received by one input channel, selected by the DACoutChSelect parameter

• MemOccupancy

  • Level of the memory occupancy (not yet implemented)

• ChSum

  • The DAC reproduces the “analog” sum of all the digitizer inputs (not yet implemented)

• OverThrSum

  • The DAC output is proportional to the number of channels that are currently above the threshold

parameter DACoutStaticLevel

When DACoutMode = Static, this parameter sets the 14-bit level of the DAC static output.

parameter DACoutChSelect

When DACoutMode = ChInput, the DAC reproduces the input signal of the channel selected by this parameter.

parameter IPEAmplitude

The new digitizers are equipped with an Internal Pulse Emulator capable of generating exponential pulses. This parameter determines the amplitude of the pulse.

Unit of Measure: ADC counts

parameter IPEBaseline

Sets the offset of the exponantial pulses generated by the Internal Pulse Emulator.

Unit of Measure: ADC counts

parameter IPEDecayTime

Sets the decay time of the exponantial pulses generated by the Internal Pulse Emulator.

Unit of Measure: ns

parameter IPERate

Sets the rate of the exponantial pulses generated by the Internal Pulse Emulator.

Unit of Measure: Hz

parameter IPETimeMode

Selectes the time distribution of the Internal Pulse Emulator.

• ConstantRate

  • Pulse shapes are constant over time. It is possible to set the frequency using the IPERate parameter

• Poissonian

  • The pulse rate follows a Poisson distribution. The average frequency value can be configured using the IPERate parameter

Logic parameter

Run

parameter StartSource

Defines the source for the start of run. Multiple options are allowed, separated by “|”.

• EncodedClkIn

  • Start from CLK-IN/SYNC connector on the front panel. This is a 4-pin connector (LVDS signals) used to propagate the reference clock (typ. 62.5 MHz) and a Sync signal. The rising edge of the Sync starts the acquisition, that lasts until the Sync returns low (falling edge).

• SINlevel

  • Start from SIN (1=run, 0=stop)

• SINedge

  • Start from SIN (rising edge = run; stop from SW)

• SWcmd

  • Start from SW

• LVDS

  • Start from LVDS

• FirstTrigger

  • Start on 1st trigger (stop from SW)

• P0

  • Start from P0 (backplane)

parameter AcqTriggerSource

Defines the source for the Acquisition Trigger, which is the signal that opens the acquisition window and saves the waveforms in the memory buffers. Multiple options are allowed, separated by “|”.

• TrgIn

  • Front Panel TRGIN

• P0

  • Trigger from P0 (backplane)

• SwTrg

  • Software trigger

• LVDS

  • LVDS trgin

• ITLA

  • Internal Trigger Logic A: combination of channel self-triggers

• ITLB

  • Internal Trigger Logic B: combination of channel self-triggers

• ITLA_AND_ITLB

  • Second level Trigger logic making the AND of ITL A and B

• ITLA_OR_ITLB

  • Second level Trigger logic making the OR of ITL A and B

• EncodedClkIn

  • Not implemented (encoded CLK-IN trigger)

• GPIO

  • Front Panel GPIO

• TestPulse

  • Internal Test Pulse

• UserTrg

  • User custom trigger source

parameter EnAutoDisarmAcq

When enabled, the Auto Disarm option disarms the acquisition at the stop of run. When the start of run is controlled by an external signal, this option prevents the digitizer to restart without the intervention of the software.

• True

  • The acquisition is automatically disarmed after the stop. It is therefore necessary to rearm the digitizer (with the relevant command sent by the software) before starting a new run.

• False

  • The acquisition is not disarmed after the stop. Multiple transition of the start signal will produce multiple runs.

parameter RunDelay

When the start of run is controlled by a RUN signal that is propagated in daisy chain between the boards (for instance through the ClkIn- ClkOut or SIN-GPIO sync chain), it is necessary to compensate for the propagation delay and let the boards start exactly at the same time. The RunDelay parameter allows the start of the acquisition to be delayed by a given number of clock cycles with respect to the rising edge of the RUN signal. Assuming that the propagation delay is 2 cycles, the RunDelay setting will be 0 for the last board in the chain, 2 for the previous one, and so on up 2x(NB-1) for the first one.

Unit of Measure: ns

parameter BusyInSource

In a multi-board system, it might be necessary to prevent one board to accept a new trigger while another board is full and thus unable to accept the same trigger. For this reason, each board can generate a Busy signal to notify that it is unable to get a new trigger. If the busy/veto mechanism has some latency, it is advisable to generate the busy slightly before the digitizer become full. For this purpose, it is possible to assert the busy output when the acquisition memory reaches a certain level of occupancy (internally managed). The OR of the busy signals is typically used to stop the global trigger. It is possible to get the individual busy signals from each board and make an external OR logic or connect the boards with cables to propagate the Busy along the chain. Each board makes an OR between its internal busy and the busy input signal coming from the previous board, thus having a global Busy at the end of the line. This parameter defines the source of the Busy Input (schematized in the figure below)

• Disabled

  • The Busy is given by the Internal Busy only (Memory full or almost full)

• SIN

  • Busy input from SIN on front panel

• GPIO

  • Busy input coming from GPIO on front panel, used as a simple input. It is also possible to use GPIO as a wired OR (bidirectional). In this mode, the Busy line goes high as soon as one board drives it high. All the boards can read the Busy line and use it as a veto for the trigger

• LVDS

  • LVDS trgin

parameter TstampResetSource

Defines the source of the timestamp reset. Multiple options are allowed, separated by “|”. The timestamp of the board (internal counter running at 125 MHz) is typically reset at the start of each run, which corresponds to the “zero” of the timestamps. In Multi-board systems, the synchronization of the clock and RUN signals allows event data coming from different boards to be merged and correlated by the time stamp. However, it is possible to configure different ways to control the reset of the time stamp in the cases where it is necessary to synchronize it with an external global time stamping system.

• Start

  • Time stamp reset at the start of run

• SIN

  • SIN input

• GPIO

  • GPIO used as input

• EncodedClkIn

  • Not implemented (encoded in CLK-IN/SYNC)

parameter PauseTimeStamp

Allows the time stamp to either stop or run during the pauses of the acquisition

• Hold

  • The timestamp stops while pausing the acquisition

• Run

  • The timestamp runs while pausing the acquisition

parameter TriggerIDMode

The event data packet contains a 24-bit identifier called TriggerID. This can be the total trigger counter, the saved event counter or a pattern coming from the LVDS I/Os.

• TriggerCnt

  • The Event triggerID is associated to the total trigger counter. This is a 24-bit counter that is reset at the start of run and increased with every received trigger, including those ones that are not accepted. In this mode, events coming from multiple boards can be correlated by the triggerID that is supposed to by synchronized. There might be gaps due to lost triggers.

• EventCnt

  • The Event triggerID is a sequential number of the saved event. In this case, there are no gaps in the sequence, but it is not guaranteed that the trigger ID of multiple boards are aligned, thus it is not possible to use it for data correlation.

• LVDSpattern

  • The triggerID is taken from the 16 LVDS inputs at the time of the trigger arrival. The user can provide an external trigger pattern to correlate the event data between boards or even with other readout electronics

parameter EnTriggerOverlap

Allows a trigger occurring within the acquisition window of a previous trigger to be either accepted or rejected. When accepted, the previous window is prematurely closed and the new window immediately opened, without any dead time between the two.

• True

  • Triggers with overlapped acquisition windows are accepted.

• False

  • Triggers with overlapped acquisition windows are not accepted. The rejected triggers are counted by the total trigger counter, so that the trigger-ID in the event header allows for tracing the rejected triggers.

parameter EnMultiWindowRun

When the acquisition start and stop are controlled by an external “RUN” signal (e.g. feeding SIN), it is possible to configure the digitizer to work in two different modes:

The RUN signal acts as a start (rising edge) and stop (falling edge). Therefore, multiple transitions of the RUN signal cause multiple runs (provided that the Auto Disarm option is disabled). At every start of run, the timestamp is reset, and all the statistics and counters are cleared. Typically, the software produces different output files.

The RUN signal acts as “enable” of the acquisition: once the digitizer has been armed, the first rising edge of RUN starts the acquisition. When RUN goes down, the acquisition is “paused” rather than stopped. This means that all data and statistics are frozen, and the timestamp can be either stopped or left running, depending on the PauseTimeStamp parameter. The RUN signal can toggle multiple times within the same acquisition. The stop of the acquisition will be done by a software command. It is necessary to disarm and rearm the acquisition before starting a new run with the rising edge of the RUN signal.

• True

  • MultiWindow run is enabled. The RUN signal acts as start (first rising edge) and pause (subsequent falling edges) for the acquisition. The stop of the acquisition is always given by a software command

• False

  • The RUN signal acts as start and stop for the acquisition

parameter ClockSource

This is the source of the system clock. Multiple options are not allowed

• Internal

  • Local oscillator, 62.5 MHz

• FPClkIn

  • Front Panel Clock input

parameter EnClockOutFP

Enables clock output on Front Panel for the daisy chain propagation of the clock between multiple boards.

• True

  • Enabled

• False

  • Disabled

FrontPanel

parameter TrgOutMode

Selects the signal that is routed to the TRGOUT output. Multiple options are not allowed.

• Disabled

  • TRGOUT output disabled

• TrgIn

  • Propagation of Front Panel TRGIN (TRGOUT is a replica, with some delay, of the TRGIN signal)

• P0

  • Propagation of P0 trigger

• SwTrg

  • Software trigger

• LVDS

  • LVDS trgin

• ITLA

  • Internal Trigger Logic A: combination of channel self-triggers

• ITLB

  • Internal Trigger Logic B: combination of channel self-triggers

• ITLA_AND_ITLB

  • Second level Trigger logic making the AND of ITL A and B

• ITLA_OR_ITLB

  • Second level Trigger logic making the OR of ITL A and B

• EncodedClkIn

  • Not implemented (propagation of the Encoded CLK-IN trigger)

• Run

  • Propagation of the RUN signal (acquisition start/stop), before applying the delay given by the RunDelay parameter

• RefClk

  • Monitor of the 62.5 MHz clock (used for phase alignment)

• TestPulse

  • Internal Test Pulse

• Busy

  • Busy of the board

• UserTrgout

  • Trgout coming from the User Logic (open FPGA)

• Fixed0

  • 0 level signal

• Fixed1

  • 1 level signal

• SyncIn

  • SyncIn signal

• SIN

  • SIN connector signal

• GPIO

  • GPIO connector signal

• LBinClk

  • Internal Logic B clock signal

• AcceptTrg

  • Accepted triggers signal

• TrgClk

  • Tigger clock signal

parameter GPIOMode

Selects the signal that is routed to the GPIO, when this is used as output. Multiple options are not allowed. The GPIO on the front panel is a bidirectional signal that can used in three different ways:

As independent board output (each board drives its own GPIO)

As a shared input for the boards: the signal is driven high (= 1) or low (= 0) by an external source and connected in “short circuit” among multiple boards using “T” connectors at the inputs. The GPIO is not internally terminated, thus it is necessary to put a 50 Ohm terminator at the end of the line (last “T”of the chain)

As a shared bidirectional line, making a “wired OR”. One or more boards can simultaneously drive the signal high (= 1). If no board drives the GPIO, it remains low (= 0). All boards can read back the signal. It is necessary to put a 50 Ohm terminator at both ends of the line (first and last “T” of the chain). This mode can be used to generate, for instance, the global Busy and Veto logic for multiple boards.

• Disabled

  • GPIO disabled

• TrgIn

  • Propagation of Front Panel TRGIN (GPIO is a replica, with some delay, of the TRGIN signal)

• P0

  • Propagation of P0 trigger

• SIN

  • Propagation of SIN

• LVDS

  • LVDS trgin

• ITLA

  • Internal Trigger Logic A: combination of channel self-triggers

• ITLB

  • Internal Trigger Logic B: combination of channel self-triggers

• ITLA_AND_ITLB

  • Second level Trigger logic making the AND of ITL A and B

• ITLA_OR_ITLB

  • Second level Trigger logic making the OR of ITL A and B

• EncodedClkIn

  • Not implemented (propagation of the Encoded CLK-IN trigger)

• SwTrg

  • Software trigger

• Run

  • Propagation of RUN

• RefClk

  • Monitor of the 62.5 MHz clock (used for phase alignment)

• TestPulse

  • Internal Test Pulse

• Busy

  • Busy of the board

• UserGPO

  • GPO coming from the User Logic (open FPGA)

• Fixed0

  • 0 level signal

• Fixed1

  • 1 level signal

parameter SyncOutMode

In a multi-board system, it can be useful to propagate a synchronous signal together with the clock (to synchronize the start of the run, for example) on CLK OUT front panel connector. This parameter defines which signal must be sent out. Multiple options are not allowed.

• Disabled

  • SyncoutMode is disabled

• SyncIn

  • SyncIn signal (if provided with clkIn on CLK IN connector)

• TestPulse

  • Internal Test Pulse

• IntClk

  • Internal 62.5 MHz clock (for test purposes)

• Run

  • Propagation of RUN signal

• User

  • User customSyncoutMode

parameter IOlevel

Sets the electrical logic level of the LEMO I/Os (TRGIN, SIN, TRGOUT, GPIO).

Note that TRGIN and SIN are internally terminated to 50 Ohm, while GPIO and TRGOUT require the termination to 50 Ohms at the receiver

• NIM

  • NIM logic (0 = 0V, 1 = -0.8V, that is -16mA)

• TTL

  • Low Voltage TLL logic (0 = 0V, 1 = 3.3V)

parameter LVDSDirection

Assigns the direction to a quartet of LVDS I/Os.

• Input

  • The LVDS lines of the relevant quartet are used as input. The relevant LED on the front panel is OFF.

• Output

  • The LVDS lines of the relevant quartet are used as output. The relevant LED on the front panel lights-up.

parameter LVDSMode

The digitizer is equipped with 16 LVDS I/Os that can be programmed to be inputs or outputs by groups of 4 (quartets), depending on the LVDSDirection parameter. Once the direction has been selected, it is possible to select the functionality of the LVDS lines, individually for each quartet.

• SelfTriggers

  • This option is available only when the LVDS are set as outputs. Each LVDS line can be assigned to a combination of the 64 self-triggers, implemented as a masked OR, where the mask is set by the LVDSTrgMask parameter(16 independent masks, one per LVDS line)

• Sync

  • Whatever is the direction of the quartet, the 4 lines are rigidly assigned to specific acquisition signals: 0 = Run 1 = Trigger 2 = Busy 3= Veto It is possible to implement a daisy chain distribution of these signals using one quartet as input and another one as output

• IORegister

  • The LVDS lines of the quartet are statically controlled by the LVDSIOReg parameter. Use the SetValue function to set the relevant LVDS lines when programmed as output. Use GetValue to read the status of the LVDS lines when programmed as inputs.

• User

  • User custom.

parameter LVDSTrgMask

Each LVDS line can be assigned to a combination of the 64 self-triggers, implemented as a masked OR, where the mask is set by this parameter. There are 16 independent masks, one per LVDS line. Note that the trigger mask assignment does not imply the LVDS direction and mode settings. It is therefore necessary to set the Direction = Output and Mode = SelfTriggers to use the Self-Trigger propagation to the LVDS I/Os.

parameter LVDSIOReg

Set the status of the LVDS I/O for the quartets when they are programmed to be output and Mode = IORegister. This parameter reads out the status of the quartets in the case the LVDS I/O are programmed as inputs (possibly externally driven).

Veto

parameter VetoSource

Defines the source for the Veto, which is the signal that inhibits the acquisition trigger. Multiple options are allowed, separated by “|”. The VETO signal can be either active high or low, depending on the VetoPolarity parameter. When active low, it acts as a GATE for the trigger. It is possible to stretch the duration of the VETO by means of the parameter VetoWidth.

• Disabled

  • VETO is always OFF

• SIN

  • SIN on the front panel

• GPIO

  • GPIO on the front panel (used as input)

• LVDS

  • LVDS trgin

• P0

  • P0 (signal from the backplane)

• EncodedClkIn

  • Not implemented (encoded CLK-IN veto)

parameter VetoWidth

Whatever is the source of the VETO signal, it is possible to stretch the duration of the veto up to a given time by means of a re-triggerable monostable. When 0, the monostable is disabled and the veto lasts as long as the selected source is active.

Unit of Measure: ns

parameter VetoPolarity

Defines the polarity of the Veto

• ActiveHigh

  • Veto is active high. The signal acts as an “Inhibit” for the trigger

• ActiveLow

  • Veto is active low. The signal acts as a “Gate” the trigger

ITL

parameter ITLA/BMask

Enable Mask at the input of the ITLA/B.

parameter ITLA/BPairLogic

Pairs of channels can be combined with an OR or AND before feeding in the Main trigger Logic. This is typically used in the readout of tubes or scintillator bars, where the two ends are read in coincidence, for instance in position sensitive detectors (the coincidence window will be set by the SelfTriggerWidth parameter). When the AND/OR logic is applied, the two outputs of the Pair Logic blocks are identical.

Note that they are counted twice in the following Majority logic. If the Pair Logic is disabled (“NONE” option), the block is transparent, and the two outputs are just a replica of the inputs.

• OR

  • Both Pair Logic Outputs = OR of two consecutive self-triggers

• AND

  • Both Pair Logic Outputs = AND of two consecutive self-triggers

• NONE

  • Outputs = Inputs

parameter ITLA/BMainLogic

Each channel of the digitizer feature a digital bipolar triangular filter discriminator with programmable rise time and threshold able to self-trigger on the input pulses and generate a self-trigger signal. In DPP Mode, the channels acquire independently, so the channel self-trigger is used locally to acquire a waveform. The trigger threshold is then referred to the bipolar triangular filter, and the threshold crossing arms the event selection. The trigger fires at the zero crossing of the time filter signal. The user can see the derivative trace on the signal inspector. It is also possible to combine all the self-triggers of the board, according to a specific trigger logic. There are two independent logic blocks, ITLA and ITLB. Their output can be used separately to feed, for instance, AcqTrigger and TrgOut, or combined in a second level trigger logic to implement more complex trigger schemes. Therefore, the ITLs can either generate the local acquisition trigger, common to all the channels, for the acquisition of the waveform, or propagate the signal outside, through the TRGOUT, thus making it possible to combine triggers of multiple boards in an external trigger logic, that eventually feeds back the TRGIN of the digitizers. Each ITL is made of an input enable mask (64 bits, one per channel), an optional pairing logic that combines the self triggers of two consecutive channels (e.g. paired coincidence) and the main trigger logic that combines the 64 selftriggers with an OR, AND or Majority logic. The output can be linear (no stretching) or reshaped by a programmable gate generator, either re-triggerable or not and finally programmed for polarity (direct or inverted).

• OR

  • ITLOUT = masked OR of channel self-triggers

• AND

  • ITLOUT = masked AND of channel self-triggers

• Majority

  • ITLOUT = masked Majority of channel self-triggers

parameter ITLA/BMajorityLev

Defines the majority level of the Main Logic of the ITL A/B block. The majority output is calculated at every clock cycle, and it becomes TRUE when Nch >= MajLev, where Nch is the number of self-triggers active in that clock cycle and MajLev is the programmed majority level.

Note that when the Pair Logic is used to combine the self triggers two by two (AND/OR), each pair produces two identical signals that will be counted twice in the majority level.

parameter ITLA/BGateWidth

Width of the gate generator at the output of the ITLA/B block.

Unit of Measure: ns

parameter ITLA/BPolarity

Polarity of the gate generator output.

• Direct

  • Direct polarity

• Inverted

  • Inverted polarity

parameter ITLA/BEnRetrigger

Set the ITLA/B to be retriggerable.

• True

  • The ITLA/B is retriggerable

• False

  • The ITLA/B is not retriggerable

mask

parameter ITLConnect

Alternative to ITLAMask, ITLBMask. Determines if the channel partecipate in ITLA or ITLB

• Disabled

  • The channel is disabled

• ITLA

  • The channel participates in ITLA logic block

• ITLB

  • The channel participates in ITLB logic block