WhiteLabelUSVGNSS software
Available for evaluation & licensingKeep vessel position
consistent across your systems.
Give navigation, charting and remote operator tools one shared, supervised position interface.
Module guide
What it receives. What your systems receive.
- What it is
- A shared vessel-position layer for navigation, charting and operator tools.
- Core input
- Positioning input from the selected GNSS receiver or simulation source.
- Core output
- A normalised position state, with validity, freshness and health supervision.
- Simulation / real integration
- SIM / REAL-compatible behaviour helps test consumers against the position-state interface.
Where it sits
A defined interface inside your vessel system.
- 01
GNSS receiver
Positioning input from the selected GNSS receiver or simulation source.
- 02
WhiteLabelUSV GNSS
The module’s processing and supervision layer.
- 03
Charting, navigation & operator tools
A normalised position state, with validity, freshness and health supervision.
The problem it addresses
Position data needs a clear contract.
A receiver supplies positioning input. Your software still needs to know whether that input is valid, current and suitable for use. The GNSS layer normalises receiver input and supervises the state passed to vessel systems.
Core capabilities
- Integration-ready position output
- Input normalisation
- Position-state validity
- Freshness supervision
- Health supervision
- Stable downstream interface
- SIM / REAL-compatible behaviour
- White-label integration
See an integration example
Integration example
A connection may remain open while position messages stop changing. The integration should consider freshness and validity as well as connection status.
Evaluate your integration
Start with the actual interface.
- Prepare
- Share the receiver model, available messages, update rates and required position fields. Include loss-of-fix and stale-input cases in the evaluation.
- Confirm
- Supported formats and transports, runtime and deployment requirements, output contract and any hardware-adapter work.
- Test
- Normal operation, invalid or stale inputs where applicable, interrupted connections and the required recovery behaviour.
- Agree before production
- Commercial licensing, integration responsibilities and acceptance criteria for the complete system.
GNSS questions
Before you evaluate.
Does the module replace the GNSS receiver?
No. It is the software layer that normalises and supervises positioning input.
Does it improve the receiver’s physical positioning accuracy?
The module is presented as a position-state and supervision layer. Receiver accuracy, correction services and antenna installation should be assessed separately.
Which messages and receiver models can we use?
Share the receiver model and available message formats for compatibility assessment. The detailed interface belongs in the package documentation and agreed integration scope.
How should consumers handle stale positions?
Consumers should use validity and freshness information in their own operating logic. Agree the required timeouts and degraded behaviour during integration planning.
Next: evaluation
See how GNSS fits your system.
Evaluate the software against your own inputs and integration requirements.