ZED-F9R - Integration manual
Message type
Description
RTCM 1075
GPS MSM5
RTCM 1077
GPS MSM7
RTCM 1084
GLONASS MSM4
RTCM 1085
GLONASS MSM5
RTCM 1087
GLONASS MSM7
RTCM 1094
Galileo MSM4
RTCM 1095
Galileo MSM5
RTCM 1097
Galileo MSM7
RTCM 1124
BeiDou MSM4
RTCM 1125
BeiDou MSM5
RTCM 1127
BeiDou MSM7
RTCM 1230
GLONASS code-phase biases
Table 4: ZED-F9R supported input RTCM version 3.3 messages
3.1.5.2 NTRIP - networked transport of RTCM via internet protocol
Networked Transport of RTCM via internet protocol, or NTRIP, is an open standard protocol for
streaming differential data over the internet in accordance with specifications published by RTCM.
There are three major parts to the NTRIP system: The NTRIP client, the NTRIP server, and the NTRIP
caster:
1.
The NTRIP server is a PC or an on-board computer running NTRIP server software
communicating directly with a GNSS reference station. The NTRIP server serves as the
intermediary between the GNSS receiver (NTRIP Source) streaming correction data and the
NTRIP caster.
2.
The NTRIP caster is an HTTP server which receives streaming correction data from one or
more NTRIP servers and in turn streams the correction data to one or more NTRIP clients via
the internet.
3.
The NTRIP client receives streaming correction data from the NTRIP caster to apply as real-
time corrections to a GNSS receiver.
u-center GNSS evaluation software
provides an NTRIP client application that can help to evaluate a
ZED-F9R design. The u-center NTRIP client connects over the internet to an NTRIP service provider,
using access credentials such as user name and password from the service provider. The u-center
NTRIP client then forwards the RTCM 3.3 corrections to a ZED-F9R receiver connected to the local
u-center application. RTCM corrections from a virtual reference service are also supported by the u-
center NTRIP client.
3.1.6 Navigation configuration
This section presents various configuration options related to the navigation engine. These options
can be configured through CFG-NAVSPG-* configuration keys.
3.1.6.1 Platform settings
u-blox receivers support different dynamic platform models (see the table below) to adjust the
navigation engine to the expected application environment. These platform settings can be
changed dynamically without performing a power cycle or reset. The settings improve the receiver's
interpretation of the measurements and thus provide a more accurate position output. Setting the
receiver to an unsuitable platform model for the given application environment is likely to result in
a loss of receiver performance and position accuracy.
UBX-20039643 - R01
3 Receiver functionality
Page 13 of 105
C1-Public
Advance information
