The line-scan detector sits at the core of every scanning X-ray system, yet getting it to cooperate with your software and hardware is rarely straightforward: network protocols, synchronization with conveyor motion, calibration and multi-energy modes all come into play. We handle that work for you, backed by deep hands-on experience integrating industrial line-scan detectors.
We have spent a great deal of time working with industrial line-scan detector systems and their vendor SDKs, learning their quirks from real projects rather than from the manual — the acquisition protocol with its command and image channels over the network, IP and card addressing, multi-energy modes and the correction workflows.
What we learned carries over to other line-scan detectors too: the underlying principles of data acquisition, synchronization and calibration are broadly the same. Whichever manufacturer your project settles on, we will integrate that detector and hand you a clean, synchronized stream ready for the image-processing pipeline.
From bringing up the network link to handing a synchronized, calibrated stream to your processing software.
Bringing up the link to the detector system — both the command channel and the image transmission channel over the network (UDP) — with real-time line capture, buffering and automatic reconnection on connection errors.
Triggering by integration time (a fixed acquisition period) or by encoder pulses locked to conveyor travel (pulses per unit length, trigger divider), plus the geometric offset between detector lines for dual-view setups.
Offset and gain calibration, run on-board (inside the detector) or off-board (in software) with coefficients written back, stored to and retrieved from non-volatile memory, per energy channel and view.
Support for multi-energy (dual energy) modes and driving several detector lines at once, with per-energy-channel sensitivity and filtering modes (averaging / summation).
IP setup, detector-card addressing and operating multiple cards within one system, including card count and per-card configuration.
C++ and .NET interfaces, plus high-speed camera interface support — delivered as a driver/adapter with a well-defined API that drops into your existing software.
We have spent a great deal of time working with industrial line-scan detector systems and their vendor SDKs. We understand their quirks from real projects rather than from the manual:
What we learned carries over to other line-scan detectors too — the underlying principles of data acquisition, synchronization and calibration are broadly the same. Whichever manufacturer your project settles on, we will integrate that detector.
scan trigger
We can:
A documented API/adapter delivered together with source code for your team — no lock-in to the contractor.
The same acquisition, synchronization and calibration principles apply whichever industrial line-scan detector your project settles on.
Reliable real-time capture with no dropped lines, correct alignment to object motion and a calibrated image ready for processing.
Tell us the detector model (or the one you're weighing up) and describe the system — we'll gauge the integration effort and propose a solution. Email info@xraydetect.com.