GNSS integration on mining trucks, construction equipment, remote-control platforms and other heavy off-road vehicles is not only an antenna-selection task. The antenna, receiver, cable route, power supply, controller, navigation output and operating environment form one engineering boundary. Start by deciding whether the purchase must add position reporting, working-point guidance, automatic assistance or interference mitigation within an existing system.
Buy the machine function you need, not just a GNSS box
A haul-truck position record, an excavator’s bucket-to-design display and automatic blade control are different deliverables. For a mining or construction fleet, first decide which output must change. If the existing machine already performs the required job and the new concern is interference at its GNSS input, scope a reception-path upgrade. If the required job is not available today, an anti-jamming component alone is not a complete machine-function purchase.
For position reporting, buy the reporting chain. A fleet team that needs to locate a truck or record its route needs an applicable position source, a data connection and the display or logging service that consumes it. That requirement does not, by itself, justify a bucket sensor package or automatic hydraulic control. Keep any GNSS interference-mitigation item separate from communications and fleet-software inclusions when comparing offers.
For excavation or grading guidance, buy the working-point solution. A roof antenna’s position is not automatically the bucket cutting edge or blade position. The package must account for the machine and tool geometry and any motion sensors, reference setup and display needed by that implementation. Caterpillar describes its 2D system as indicate-only depth and slope guidance, while its 3D offering relates bucket positioning to design files. The purchasing consequence is to choose the required job reference: a local depth/slope task need not automatically become a site-wide GNSS design purchase. Confirm the complete supplier configuration, not only the antenna line item.
For automatic assistance, require that function explicitly. A screen showing a target does not establish that the machine will move a boom, bucket or blade to it. Leica lists excavator guidance and semi-automatic movement functions separately. If automatic assistance is required, the quotation must identify the supported machine, controlled functions and required control integration. An operator-guidance offer is not an equivalent substitute unless the buyer deliberately accepts manual control.
Do not move a receiver or antenna to a more convenient surface without checking the intended system. Trimble’s on-machine comparison distinguishes cab/chassis, blade and boom mounting as well as compatible field software. This illustrates why hardware placement and the application package are linked; it does not establish a mounting approval or software relationship for a ResiNav product.
A useful purchase split: consider an existing excavator whose design display and operator guidance already meet the job requirement. If an identified GNSS reception problem is the reason for the new purchase, compare a candidate mitigation configuration and its confirmed connection items against that existing chain. Do not automatically repurchase the display or a correction subscription. Conversely, if the buyer now wants automatic bucket movement, keep the machine-control upgrade in the order scope; a reception-path change does not supply it. This is an illustrative decision, not a tested installation.
Use the ResiNav product catalogue for the interference-mitigation portion and the public model datasheets to screen documented configurations. The manufacturer examples above are not ResiNav compatibility, precision, productivity or safety claims. A model’s suitability for the installed receiver and machine remains configuration-specific; missing public information remains unknown, not confirmed non-support. For the separate receiver/correction purchase, see what anti-jamming and RTK purchases each provide.
Map the installation and RF environment
Heavy equipment can combine large metal structures, changing obstructions, severe vibration, shock, dust, temperature variation, long cable routes and electrical noise. Antenna placement should be reviewed against cabins, booms, buckets, counterweights, masts and service equipment. The review should identify likely metallic shadowing, self-interference and maintenance-damage modes without converting a conceptual risk into an unsupported performance claim.
- Proposed antenna position and mounting envelope
- Obstructions and moving structures around the antenna
- Cable length, routing, protection, strain relief and grounding approach
- Service access and connector protection
- Documented vibration, shock, temperature and ingress requirements
- Potential onboard interference sources, including power and drive systems
The applicable environmental limits must come from verified product records. Unknown values should remain open engineering questions.
Confirm receiver and signal-path requirements
Before selecting a ResiNav configuration, document the receiver model, constellations, frequency bands, channel or array architecture, connectors and interface expectations. Element count is a useful catalogue filter, but it is not a substitute for receiver compatibility or installation review. The product decision should connect the RF environment through the antenna and receiver to the platform controller and navigation output.
The existing element-count and channel-count guide explains what engineers should confirm, while the antenna–receiver–platform integration guide provides a broader system boundary.
Document power, interfaces and platform behavior
| Review area | Inputs to document | Why it matters |
|---|---|---|
| Receiver | Model, constellations, frequency bands and channel architecture | Establishes the compatibility questions for engineering review |
| Installation | Mounting position, envelope, cable route, connector protection and grounding | Defines physical constraints and maintenance risks |
| Power | Supply conditions, transients, grounding and startup behavior | Clarifies the platform electrical boundary |
| Interfaces | Connectors, data protocol, timing, status and controller expectations | Connects the navigation output to the receiving subsystem |
| Evidence | Verified values, pending questions and required documents | Prevents assumptions from being treated as confirmed specifications |
Build a requirements and evidence register
A short register can separate requirements, assumptions and verified evidence. For each item, record the source, responsible owner and current status. This helps an engineering team identify which questions can be answered from current product documentation and which require an installation or system review.
- Define the operating environment and the platform role.
- Identify the receiver, constellations, frequency bands and channel requirements.
- Document mounting, cable, interface, power and maintenance constraints.
- Separate verified product data from assumptions and open questions.
- Define the documents or checks needed before configuration approval.
For additional installation detail, use the GNSS installation documentation checklist and the GNSS interference environment guide.
What to include in an RFQ
An engineering RFQ should provide enough context to review a candidate without guessing. Include the platform type and application, receiver, installation constraints, interfaces, power requirements, quantity, target schedule, destination region and documentation needs. Use the GNSS anti-jamming RFQ checklist before submitting the ResiNav engineering enquiry form.
Frequently asked questions
Does this guide select a product for a mining vehicle?
No. It identifies the platform, receiver, installation and evidence inputs required for an engineering review. Final product configuration and suitability require confirmation.
Is element count enough to choose an anti-jamming configuration?
No. Element count is a catalogue filter. Receiver compatibility, frequency bands, channel architecture, mounting, interfaces, power and environmental requirements also need review.
What installation information should be provided first?
Provide the proposed antenna position, mounting envelope, cable route, connector and grounding constraints, service access and documented environmental requirements.
Does the application description prove deployment or performance?
No. The application context is an engineering reference and does not claim a certified deployment, customer project, measured detection rate, guaranteed accuracy or suitability without confirmation.
Review the Engineering & Mining Vehicles application page, browse the ResiNav product catalogue, or contact ResiNav to discuss documented integration requirements.
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.