Choose GNSS RF record and replay when the buying task is to reproduce a captured signal environment. Choose a generated GNSS scenario when the task requires selecting conditions and changing them deliberately between comparisons. Both can provide repeatable RF inputs, but they do not supply the same control over the scenario. Buy the source capability your evaluation needs, not simply an instrument described as a “GNSS simulator.”
This distinction matters to integrators comparing reception-protection configurations for vehicles, robots or UAV equipment. The immediate purchase may be a test service, a replay unit or a scenario-generation system. It is separate from purchasing the protection product itself.
Start with the question the signal source must answer
If a vehicle encountered an unusual GNSS event and the team needs to expose two receiver configurations to that recorded RF environment, a compatible replay path can answer the immediate comparison. If the requirement is to compare a specified route under several independently selected signal conditions, the source must support generating and controlling those scenarios. Another uncontrolled drive is not an equivalent substitute.
Safran’s recorder and player range captures live RF for later laboratory playback. Its published product comparison distinguishes recording-only, playback-only and combined products. A quote for a recorder alone therefore does not necessarily complete a capture-and-repeat workflow.
Safran’s simulation overview separately describes creating scenarios with selected satellite, signal, date and motion parameters. This supports a different task: building the required test case rather than being limited to what was captured at one location and time. These are that manufacturer’s capabilities, not ResiNav products or test facilities.
Compare the deliverable, not the instrument label
Recording and simulation are not mutually exclusive product categories. LabSat’s SatGen description explains that generated GNSS RF I&Q or IF files can be replayed through LabSat hardware; it also describes NMEA output as a separate output format. A replay device may therefore play a field capture or a generated scenario. Ask which one is included in the offer.
The practical consequence is a scope decision. An existing compatible player may reduce the additional hardware purchase to supported scenario-generation software. Conversely, a software-only offer leaves the RF-delivery item unresolved if no suitable hardware is available. Neither conclusion means that every player accepts every file or that every software variant generates the required signals.
Repeatability and scenario control are different requirements
Replaying the same capture lets a team revisit the recorded input. It does not by itself provide independent control of the satellite geometry, motion and environmental conditions embedded in that capture. Some products provide editing, conversion or additional controls; those functions must be part of the selected configuration rather than inferred from the word “replay.”
Rohde & Schwarz’s GNSS simulation page describes customizable, repeatable scenarios and identifies interference-generation capabilities in particular instrument configurations. This is evidence that such options exist, not that every GNSS signal generator includes them.
For a reception-protection comparison, keep the required adverse condition explicit. A nominal GNSS scenario alone does not supply a requested interference case. A field capture is useful only to the extent that the required signals and event were captured within the recording system’s documented scope. Repeating an unsuitable input reliably does not make it a suitable test.
Two hypothetical orders show how the choice changes
Case A: repeat an observed event. An integrator already has a suitable RF recording and a documented compatible playback unit. The immediate requirement is to compare the same receiver configuration before and after a software change. The narrower purchase is the playback workflow and any missing access or integration items—not automatically a new field recorder or a full scenario-generation package. This example assumes the recording and player are suitable; it does not claim that a real recording contains a particular threat.
Case B: create a comparison that has not been recorded. Another team needs selected signal conditions along a defined simulated route. Its existing player can accept the relevant generated format, but the current quotation includes only playback hardware. The missing deliverable is supported scenario generation. If the player cannot accept that output, the order also needs a suitable RF-delivery configuration. Buying more storage or repeating the old recording would not provide the requested scenario control.
These examples are scope comparisons, not prices, supplier offers or test results. The purchasing condition that changes the order is whether a suitable recorded input already exists and whether the required changes can actually be generated and delivered.
Keep the protection item in the evaluation
The choice of source does not settle which hardware is tested. A recorded or generated signal fed after a protection unit does not exercise the unit it bypasses. The receiver evaluation guide already distinguishes receiver-only, antenna-electronics and antenna-inclusive boundaries. Use that decision alongside this source selection, without buying every test scope by default.
Keep the offered configuration specific: required recorded or generated inputs, playback or RF-generation hardware, enabled software functions and the exact device under test. A receiver position log can help explain an event, but it is not the same deliverable as the RF samples used by a recorder. Use lawful, authorized, controlled testing; this guide is not an instruction to transmit interference in an open environment.
For the reception-protection portion, compare the published configurations in the ResiNav catalogue, then continue through the relevant model’s existing enquiry route. ResiNav is an own-brand supplier. The third-party recorder, player and simulator examples do not establish that ResiNav sells those instruments, provides the associated test service or has validated a particular combination.
The resulting decision is concrete: retain a suitable replay path for an existing capture, add the missing capture function for a new event, or purchase supported scenario generation and RF delivery for conditions you need to control. Keep that evaluation purchase separate from the model you are evaluating.
NEXT STEP
Turn available platform information into an engineering review.
Use the Technology centre to frame the discussion, review relevant application scenarios, then send the available platform and receiver details for confirmation.