An RF anti-jamming device is not automatically a replacement for a GNSS timing receiver. If your equipment needs a pulse-per-second output or a network time service, identify the device that will provide that output first. Then decide whether an additional RF protection stage can fit the timing system’s signal path and time-error budget.
This distinction matters when retaining a working timing installation. A product can have relevant GNSS RF specifications without establishing the time accuracy of the receiver, distribution equipment or final clock endpoint. Conversely, a timing receiver’s published accuracy does not by itself describe an installation after an external RF stage has been added.
Choose the output you are actually buying
Start at the equipment that consumes time, not at the antenna connector. A GNSS RF output carries the satellite signal onward to a receiver. A 1PPS output is a timing pulse; its association with a date and second may require a separate time message. A network time service requires the appropriate clock and network implementation. These are different purchasing boundaries.
For example, NovAtel’s timing documentation distinguishes receiver logs, 1PPS, variable-frequency outputs and event inputs. This illustrates why a named timing interface must be specified; it is not evidence that a ResiNav product implements those interfaces or is compatible with that receiver.
| What the installation needs | Purchasing route | What the RF product alone does not establish |
|---|---|---|
| Keep an existing timing receiver and its working time outputs, while evaluating RF interference protection. | Screen an external RF protection configuration against the receiver input, then qualify its effect on the complete timing path. | The receiver’s resulting time error, calibration settings or behavior during mitigation and recovery. |
| A new receiver that produces the required timing signals. | Compare timing receivers and their documented interference features before deciding whether an additional RF stage is needed. | An RF output is not a substitute for a specified timing pulse, time message or other required clock interface. |
| A delivered network time service at downstream equipment. | Define the time server or clock, distribution network and endpoint requirement as a system purchase. | RF protection does not establish the network protocol, endpoint accuracy or performance of the distribution path. |
Dedicated timing receivers are a real product category: the Septentrio mosaic-T is one published example with receiver-level interference mitigation. It is an alternative category to evaluate, not a claim of interchangeability with ResiNav hardware. For the broader RF antenna-versus-terminal distinction, see the GNSS architecture comparison.
Separate RF path delay from the remaining time error
An added RF stage can introduce propagation or processing delay. The procurement question is not simply whether its latency number is small. It is how much error remains at the required timing output, under the conditions in which that output must be used.
A fixed, characterized delay may be compensable if the specific timing receiver and calibration procedure support that adjustment. Unknown delay, variation with operating conditions, and uncertainty after compensation cannot simply be removed from the budget. Confirm which effects a quoted number includes and where it is measured. Do not equate RF path latency with a guaranteed endpoint clock error.
NovAtel’s GAJT-310 latency discussion explicitly treats latency as relevant to timing-device integration. Its model-specific statements are not a latency specification or a calibration exemption for any ResiNav model.
A time-error allowance can change the buying decision
Illustrative requirement: maximum absolute time error of 100 ns at a specified equipment input.
Assumed allocation: 60 ns for the bounded contributions of the receiver, distribution and other existing elements; 10 ns retained as design margin.
Remaining allowance: 100 − 60 − 10 = 30 ns for the residual contribution associated with the proposed added RF path.
Hypothetical budgeting example, not a ResiNav measurement or product specification. Every contribution here is assumed to be a worst-case absolute error bound referred to the same endpoint, reference and operating conditions. The arithmetic adds bounds conservatively; it does not assume statistically independent errors.
Under those assumptions, a supported 20 ns residual bound would leave 10 ns of that RF allowance unused. A 40 ns bound would exceed it. An unknown bound supports neither conclusion. These comparisons cannot be made by inserting a typical latency figure or an RMS accuracy value into a worst-case budget without establishing that the quantities are comparable.
This gives the buyer a concrete choice: retain the proposed RF configuration if the complete timing path can meet the requirement; evaluate a different configuration or timing architecture if a demonstrated bound cannot fit; or keep timing suitability unresolved when the necessary bound is not available. More antenna elements do not answer that timing question.
Buy calibration coverage for the installed path, not just a label
A “calibrated” device need not include every delay in the installed assembly. Microchip’s BlueSky GNSS Firewall calibration-options document provides a useful concrete example: its standard calibration uses factory antenna and cable characteristics and excludes site-specific antenna and cable delays. Its precision option defines a wider measured assembly, while assigning a particular PPS input-cable delay to the customer.
The purchasing implication is to agree the measurement boundary. A device-only offer and an offer that covers the installed antenna, cables, protection equipment and receiver adjustment are not necessarily equivalent deliverables. Identify the included items and residual uncertainty before comparing prices. This is a suggested comparison method, not a statement that ResiNav supplies a timing-calibration service.
Where a ResiNav product fits in an initial screen
The published RN2501-AJS-4CH-DPA product record identifies BDS B1 and GPS L1 operation, RF output frequencies of 1561.098 MHz and 1575.42 MHz, and 50 Ω output impedance. Those facts can support an initial RF-input comparison when the proposed timing receiver uses those signals. They do not establish timing-receiver compatibility or an endpoint time-error bound.
Use the public English datasheet directory to identify the exact model document. The cited RN2501 record does not establish a timing-path latency or residual-error specification for this proposed use. Treat that as an open qualification item, not proof of support or lack of support. If another signal set is required, compare documented configurations in the product directory rather than assuming the RF frequencies are interchangeable.
Make the enquiry about a timing requirement
State the required time output and endpoint error limit in the enquiry, alongside the proposed receiver and RF product. For example: “We plan to retain receiver X and its existing timing output. Our endpoint limit is ±100 ns under the stated conditions; our provisional allocation leaves 30 ns for the added RF path’s residual contribution. Is there applicable characterization for this configuration, and what calibration scope would be needed?” The numbers are illustrative; replace them with the project’s requirement and justified allocation.
Use the receiver interface guide for the pulse, message and port definitions, and the receiver compatibility guide for the RF input and bias boundary. The next purchasing decision is whether the proposed configuration can satisfy a defined timing budget—not whether an RF protection product can be assumed to replace a clock.