Engineering reference. This guidance is for commercial and industrial GNSS integrations. It does not provide universal cable-loss assumptions, compatibility guarantees, certification claims, deployment results or installation instructions.
An anti-jamming integration review is easier to perform when the complete RF path is documented as an engineering configuration rather than described only as an antenna and a receiver. The review record should identify the components between them, the evidence available for each component and every change that could alter the installed path.
ResiNav confirms the appropriate product configuration only after reviewing the current platform, receiver and installation documentation.
Why the RF path needs a traceable record
The antenna, cable, connector, adapter, filter, splitter or distribution device and receiver form one path. A record that identifies only the antenna model cannot establish whether later hardware changes, service work or cable substitutions altered the engineering assumptions used for the original review.
Documenting the path keeps engineering, procurement, installation and maintenance teams aligned. Each group can point to the same drawing revision, exact part number and unanswered question instead of relying on a verbal description of a “low-loss cable” or a “standard connector.”
Create an RF-path manifest
Create one controlled manifest for each receiver path. Link it to the applicable drawing, installation location and configuration revision. Include the following information for every inline item.
| RF-path item | Record before review | Evidence to retain |
|---|---|---|
| GNSS antenna | Exact model, output/interface details, mounting reference and drawing revision | Manufacturer documentation and current installation drawing |
| Cable assembly | Exact part number, actual routed length, cable revision and both end terminations | Supplier documentation, measured or controlled length record and assembly label |
| Connector or adapter | Connector series, gender, interface direction, adapter part number and intended location | Datasheet, assembly drawing and service record |
| Inline device | Filter, splitter, distribution device or protection device part number and placement | Manufacturer documentation and system schematic |
| Receiver input | Receiver model, input identifier and applicable interface-control documentation | Receiver documentation and project configuration record |
Use the current manufacturer documentation for the exact cable and component part numbers. Do not substitute an assumed loss-per-metre value, a generic connector description or a value copied from an unrelated platform.
Review the RF path with source documents
The engineering review should compare the documented path with the current antenna and receiver documentation. The question is not whether a component has a reassuring name; it is whether the recorded configuration, relevant GNSS frequency bands, interfaces and inline devices have documentary support for the specific platform.
If a loss or gain budget is required, establish it from the actual component documents, actual routed length and the relevant receiver information. Record the document revision and any unconfirmed values. Do not convert a preliminary calculation into a performance claim or an installation approval.
Treat these changes as review triggers
- Cable length, routing, part number or assembly revision changes.
- A connector is re-terminated, replaced or adapted.
- An adapter, filter, splitter, distribution device or protection device is added, removed or moved.
- The GNSS antenna, receiver model, receiver input or platform mounting arrangement changes.
- Installation, service or procurement records identify an uncertainty that cannot be reconciled with the approved configuration documents.
The purpose is change control, not administrative overhead. A small undocumented change can make a prior technical review difficult to apply to the installed platform.
Preserve maintenance and handover evidence
Keep the RF-path manifest with configuration photographs, drawing references, inspection date, responsible role and a list of open technical questions. Photographs should help identify routing and labelled assemblies; they do not replace manufacturer documentation or a controlled drawing.
For OEM programmes, include the manifest and its revision in the integration handover package. That provides a clear basis for later service, redesign or receiver replacement decisions.
Minimum RFQ information pack
Before submitting an RFQ, provide the platform role, intended installation environment, receiver model, available interface documentation, antenna and cable part numbers, relevant drawings, actual or controlled cable length, inline devices, connector/adaptor details and known constraints. Where a fact is not confirmed, identify it as unconfirmed rather than guessing.
ResiNav can use this evidence to discuss an appropriate engineering review path. A quotation request should not be treated as proof of compatibility, site performance or final installation approval.
Related engineering resources
- Antenna Placement for Industrial Robots and Automated Vehicles
- Resilient GNSS Receiver Evaluation Bench Tests
- Products
- Request a Quote
Frequently asked questions
Can a cable be described only as “low loss” for an engineering review?
No. The review needs the exact cable assembly or part number, actual or controlled length, connector/termination details, relevant documentation and its relationship to the receiver and antenna configuration.
Does replacing a connector require a new review?
It should be recorded as a configuration change. Whether further engineering review is required depends on the exact connector, termination, adapter use, affected interface and the current project documentation.
Can a cable change alone confirm or improve anti-jamming performance?
No. A cable change is one part of the RF path. Performance, compatibility and installation suitability require review of the complete documented system and applicable evidence.
When should an RF-path manifest be updated?
Update it whenever a listed path component, route, length, interface, receiver, antenna or supporting document revision changes, and whenever an open technical question is resolved.
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.