ZED-F9P-Integration Manual
UBX-18010802 - R02
3 Getting started Page 11 of 114
Advance Information
3 Getting started
This part provides the key requirements for enabling RTK operation with the ZED-F9P. Following an
overview of RTCM message support and basic receiver configuration the user is guided through the
procedures needed to establish RTK base or rover operation.
Figure 4: RTK system in a nutshell
The RTK rover needs RTCM corrections in order to achieve high precision results. These corrections
come from a local receiver (the base), or via a reference receiver. If the two receivers are local to each
other they are called the base and rover. If the rover is provided its corrections from a system such
as VRS/CORS it is provided its corrections from a service or reference receiver.
The corrections can be supplied to the ZED-F9P using several interfaces: UART, I2C, SPI, USB.
The link between the rover and the source of the corrections can be any form of wireless link: Cellular,
WIFI, Bluetooth, proprietary radio, ISM etc. The user only needs to ensure the RTCM messages arrive
at the I/O port selected on the ZED-F9P. This link will be bi-directional for a VRS services as the rover
has to provide its position usually every 30 seconds at least.
Instead of using two local receivers in a base and rover configuration you can use a correction
service that can be accessed over the internet. The rover receives corrections in RTCM format that
are provided over the internet via a NTRIP service. This requires that an NTRIP client processes
the corrections from an NTRIP server on the internet. This client will be implemented on a host
application connected to the rover. There are many open source variants of NTRIP clients available
that can be implemented on embedded or Windows, Linux, Android systems.