VELQR. Develop & Analyse The validated GNSS research and development platform

The problem this solves

Most groups do not want another receiver. They want to answer a question: how does my algorithm behave under real signals, why does a receiver lose the solution in a specific situation, can another team reproduce my result.

Building the setup yourself consumes project time in hardware selection, drivers, data formats, synchronisation, buffering and toolchain maintenance. A closed receiver removes that work but also removes the access.

VELQR is built so that you research with the setup instead of researching the setup.

A single measurement campaign becomes a reusable research asset. Rare events can be preserved and reprocessed years later with new algorithms, VELQR makes real GNSS events repeatable even when the event itself is not.

Look inside the receiver

A conventional receiver tells you that the solution degraded. It rarely tells you why.

VELQR exposes the stages between signal and solution: correlation function shape, tracking loop behaviour, signal power and anomalies, code/carrier divergence, measurement quality. When a receiver loses lock under interference, you can observe where in the chain it happened and what the signal looked like at that moment, then replay the same recording with a different algorithm and watch the difference.

A reference receiver reports the failure. VELQR lets you examine the failure mechanism.

Every stage shown here is also a stage you can modify. Custom modules integrate through defined interfaces and run in real time alongside the core, without changing it and without disclosing your source.

Who it’s for

• Research groups and principal investigators
  A documented, citable experimental method: defined platform, documented configuration, archived raw dataset, identifiable software version. More scientific output from each measurement campaign, on a platform the next team can continue to use.
• Doctoral researchers and algorithm developers
  Less time on drivers and toolchains, full depth available when the analysis requires it. Concentrate on your algorithm instead of building a receiver around it.
• Corporate R&D
  Test proprietary algorithms against real and recorded signals early. Custom modules integrate as separate components, your implementation stays yours and stays out of the VELQR core.
• Laboratory engineers and system administrators
  A known system state instead of an individually grown laboratory installation: released configuration, documented acceptance run, defined support scope.
• Defence and critical infrastructure
  Investigate jamming and spoofing scenarios, evaluate countermeasures reproducibly, replay security-relevant events without repeating a field campaign.

Why VELQR

Compared with an open-source software receiver

Open-source receivers are capable and carry no licence cost. The integration, validation, documentation and long-term maintenance of the complete system stay with you.

Compared with a reference receiver

A reference receiver is optimised for precise, robust measurements in operational use. That is a different task from open algorithm development. A reference receiver delivers high-quality measurements. VELQR is the platform on which new routes to such measurements are developed and examined.

Compared with a low-cost SDR

An SDR delivers samples. What decides the outcome is whether the whole chain sustains the required bands, channels, data rates, synchronisation and stability, not device price alone. The VELQR Front-End is designed and released for sustained real-time operation with the VELQR receiver. It is the only front-end currently released for real-time operation on this platform. If your work requires live processing rather than post-processing of recorded files, this is the property that decides whether the experiment is possible at all, and it is not a property a general-purpose SDR is built to provide.

What you receive

• VELQR SOFTWARE RECEIVER
  Real-time and post-processing of all major GNSS constellations and frequency bands, with access to raw samples and processing stages, integrated signal and quality monitoring, and standard outputs including RINEX and MATLAB-oriented workflows.
• VELQR FRONT-END
  RF front-end matched to GNSS frequencies and to the sustained data rates a software receiver requires. Available in single-channel and dual channel versions, tested and calibrated, suitable for synchronised and repeatable measurement campaigns. It is the only front-end currently released for real-time operation with VELQR.
• VELQR STATION
  The processing unit the receiver is released on: defined hardware, released drivers, configured security exceptions, tested and accepted before delivery.
  Real-time signal processing depends on far more than nominal compute power. Antivirus software, background processes, power management, storage behaviour and driver versions all sit in the data path, and each of them can turn a working configuration into an unexplained failure. The Station exists so that this class of problem does not arrive in your project. You are not buying a computer , you are buying the absence of three days spent discovering that a security scanner was interrupting the sample stream.
• ACCEPTANCE RUN
  A documented commissioning run establishing the agreed system state, usable later as the reference point in any support case. Software, hardware and support come from IGASPIN. One contract, one point of contact.

Capabilities

• Signal coverage

• API and extensibility

C-based API framework. User-developed modules load and execute in real time
without modification of the core system. Direct access to acquisition,
tracking, measurement and navigation engines. Your components remain
separate, with no disclosure of your source code to third parties.

• Recorder and replay

Full raw-sample recording, replay of the identical signal under changed
configuration, reuse of the same dataset by multiple teams, and regression
testing of new software versions against historical real-world events.

• Integrated monitoring

Correlation function shape, signal power and anomalies, code/carrier divergence,
pseudorange and measurement quality indicators.

• Typical applications
  • GNSS interference, jamming and spoofing research
  • Multipath and signal quality analysis
  • Acquisition, tracking and PVT algorithm development
  • Ionospheric scintillation and GNSS reflectometry
  • Antenna diversity, heading and relative navigation
  • Replay-based regression testing
  • Precise positioning applications, including high-accuracy
    PNT, RTK, and PPP research
  • CRPA-based beamforming and spatial interference suppression
  • Indoor GNSS and weak-signal investigations
  • Research on
    quantum-resilient anti-jamming and anti-spoofing concepts,
    including quantum timing sources, atomic clocks, and quantum-inspired
    acquisition and tracking algorithms
  • Spaceborne GNSS research for
    LEO and satellite-based navigation, positioning, timing,
    and signal monitoring applications
  • Meta-signal processing and analysis, including multi-band signal combination, acquisition, tracking, and high-accuracy positioning.

Proof

The platform has been developed continuously under ESA, FFG, BMLV and EDF-funded research programmes, and forms the receiver core behind IGASPIN’s INDALOS interference monitoring system, the LOKI interference simulator and the RIDe product line.

How to start

VELQR is delivered as a complete, documented system configuration, commissioned with an acceptance run. The right starting point depends on what you want to investigate, a full system, a guided proof of value, or a defined post-processing engagement.
Academic and commercial licence terms are available, with reduced pricing for universities and public research institutions. Tell us your application, your signals and your timeline, and we will tell you honestly whether VELQR fits.

Discuss your experiment

1. Do you need to understand or modify how GNSS measurements are formed inside the receiver?
2. Do you need to repeat a real signal event exactly, with different algorithms or parameters?
3. Who currently takes responsibility for front-end, computer and software working reproducibly under your specific live load?

Resources

• Datasheet
• GNSS sample datasets

Bring us your experiment

Tell us what you need to observe, modify or prove. We will tell you whether VELQR is the right platform for it.

Discuss your experiment