Distributed sensors —
a single context of the spectrum.
A new-generation ML/SDR platform: detection, direction finding, analysis, communications.
Development directions
Multichannel coherent receive and MUSIC over a circular array: the direction comes from raw IQ, not from signal levels.
- 0.2–1.5°
- bearing spread · 107 field measurements
- 24–1766 MHz
- coherent receive, five channels
- ≈2/s
- bearings per source, no demodulation
Our own physical and link layers: GMSK, convolutional coding with Viterbi, ChaCha20-Poly1305, TDMA. Both ends derive the hop order from the key — nothing is exchanged.
- 26 kHz
- occupied bandwidth · GMSK 25 000 sym/s
- 2.3 %
- time on air: 83 s per hour
- +2.27 dB
- decode threshold, measured on air
We extract signal features — temporal, spectral, structural — and classify the emitter by them. We catch the whole family through invariants of behaviour rather than a list of known signatures.
- 24 MHz – 6 GHz
- survey range
- 854 Hz
- resolution: 65 536 bins / 56 MHz
- 0.5–1.6 MHz
- one burst's bandwidth — a family invariant
In development
ELINTIR SL-2 Concept
The SL-1 modem computes its whole physical layer on the host, in Python — and at 25 000 symbols per second that is the right call: with a one-second slot, decoding takes 12–20 ms, so the host idles almost all of the time. The high-rate mode does not work that way: 15.36 million symbols per second will not pass through USB into Python, the chain has to live in the FPGA itself. And on the SL-1 die the stock firmware already holds 72 of 80 multiplier slices — eight free where twenty are needed. SL-2 is the same modem and the same radio on a die it fits on.
Chips on the board
- XC7K325T Kintex-7 — 203 800 LUTs, 840 multiplier slices
- AD9361 — the same transceiver as in SL-1
- DDR3 — frame buffer between fabric and host
- Ethernet · USB 3 — link to the host
Protocols
- s.Link 1.0 — GMSK, convolutional 1/2 with Viterbi: station compatibility
- s.Link4k — 15.36 Msym/s at 30.72 MS/s
- ChaCha20-Poly1305 — channel encryption, 256-bit
- AXI-Stream — fabric to processor
In development
ELINTIR ZR-1 Concept
FPV control and video live at 2.4 and 5.8 GHz — above the ceiling of a coherent array, which stops at 1766 MHz. ZR-1 takes that band by another method: five directional antennas in a ring compare power, not phase. The unit says which sector the signal came from, and how much that sector can be trusted. Sectors from several units are crossed by the operator console.
Chips on the board
- AD9363 — RF transceiver, 70 MHz – 6 GHz, two receive inputs
- Zynq-7010 — FPGA and Cortex-A9: compute on the board itself
- SP6T — RF switch DC – 6 GHz, selects the sector
- BNO085 — magnetometer: where the ring is pointed
- GNSS — position and time
Protocols
- libiio — transceiver control and the IQ stream
- I²C · GPIO — compass and sector switch
- s.Link — reporting: GMSK, convolutional 1/2 with Viterbi
- ChaCha20-Poly1305 — channel encryption, 256-bit
In development
ELINTIR ZR-47 In design
What matters in ZR-47 is what it receives with. Eight RF converters sit on one die and digitise the antenna directly: there is no local oscillator at all. So the PLL phase jump on every retune — which on an ordinary receiver reshuffles the channel phases each time and forces a fresh calibration — does not exist here as a phenomenon. The die sees the whole band and computes a direction on every spectral bin, not on one.
Chips on the board
- XCZU47DR — eight RF ADCs, 14-bit @ 5.0 GSPS on one die
- PL + Cortex-A53 — fabric and processor on the same die
- TCM2-63WX+ — baluns for eight inputs
- eight RF DACs on the same die — built-in self-test
- on-die clock distribution — no external matched pairs
Protocols
- MTS — phase across eight channels, tile to tile
- AXI-Stream — processing on-die, no host
- QSFP28 — raw IQ offload
- s.Link — reporting to the operator
Company
Code that turns the spectrum into data.
ELINTIR works where digital signal processing meets applied engineering: algorithms, embedded software, operator interfaces. We carry a solution from the mathematics and a bench mock-up through to verified operation on real hardware.
We build both our own products and custom modules that embed into a customer's existing system.
Contacts