Contents Menu Expand Light mode Dark mode Auto light/dark mode Auto light/dark, in light mode Auto light/dark, in dark mode Skip to content
Ndigo6G-12 User Guide
Logo
Ndigo6G-12 User Guide Download PDF
  • 1 Hardware
  • 2 Functionality
    • 2.1 ADC Modes
    • 2.2 Zero Suppression
    • 2.3 Trigger Setup
    • 2.4 Gating Blocks
    • 2.5 Auto Triggering Function Generator
    • 2.6 Averaging Mode
    • 2.7 Timing Generator (TiGer)
  • 3 Driver Programming API
    • 3.1 Constants
    • 3.2 Initialization
    • 3.3 Status information
    • 3.4 Configuration
    • 3.5 Runtime control
    • 3.6 Readout
  • 4 Packet Format
    • 4.1 Constants
    • 4.2 Output Structure crono_packet
    • 4.3 Utility macros
    • 4.4 Data encoding for ADC hits
    • 4.5 Data encoding for TDC hits
  • 5 C++-Example
    • 5.1 ndigo6g12_example.cpp
    • 5.2 ndigo6g12_app.h
    • 5.3 ndigo6g12_adc_single.cpp
    • 5.4 ndigo6g12_adc_dual.cpp
    • 5.5 ndigo6g12_adc_quad.cpp
    • 5.6 ndigo6g12_adc_averager.cpp
    • 5.7 ndigo6g12_tdc.cpp
    • 5.8 delay.h
  • 6 Technical Data
  • 7 Revision History
  • Erratum
  • Index
Back to top

Erratum¶

Up to firmware revision 1.24120, the retrigger feature of the gating blocks does not behave as intended. Instead of a gate being only extended by a retrigger event, the state of the gate is reset to inactive.

Up to firmware revision 1.24120 and in 4-channel mode, ndigo6g12_single_shot() only works properly if ndigo6g12_trigger_block::multi_shot_count == 1.

Previous
7 Revision History
Ndigo6G-12 User Guide (Rev. 1.0.1) | cronologic GmbH & Co. KG (Imprint)