EasyManuals Logo

u-blox ZED-F9P Integration Manual

u-blox ZED-F9P
114 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Page #29 background imageLoading...
Page #29 background image
ZED-F9P-Integration Manual
UBX-18010802 - R02
3 Getting started Page 29 of 114
Advance Information
3.7 Default messages
Interface Settings
UART1 Output 38400 Baud, 8 bits, no parity bit, 1 stop bit. Configured to transmit NMEA, UBX, RTCM 3x
protocols. But only the following NMEA (and no UBX) messages have been activated at start-
up: GGA, GLL, GSA, GSV, RMC, VTG, TXT.
UART1 Input 38400 Baud, 8 bits, no parity bit, 1 stop bit. Automatically accepts the following protocols
without need of explicit configuration: UBX, NMEA, RTCM 3x.
UART2 Output 38400 Baud, 8 bits, no parity bit, 1 stop bit.No host interface (UBX). Configured by default to
allow RTCM 3x as an output protocol. NMEA can also be configured as a protocol.
UART2 Input 38400 Baud, 8 bits, no parity bit, 1 stop bit. No Host interface (UBX). Configured by default to
allow RTCM 3x as an input protocol. NMEA can also be configured as an input protocol.
USB Output Configured to transmit NMEA, UBX, RTCM 3x protocols, but only the following NMEA (and no
UBX) messages have been activated at start-up: GGA, GLL, GSA, GSV, RMC, VTG, TXT.
USB Input Automatically accepts following protocols without need of explicit configuration: UBX, NMEA,
RTCM 3x.
DDC
Fully compatible with the I
2
C industry standard, available for communication with an external
host CPU or u-blox cellular modules, operated in slave mode only. Default messages activated
as in UART1. Input/output protocols available as in UART1. Maximum bit rate 400 kb/s.
SPI Allow communication to a host CPU, operated in slave mode only. Default messages activated
as in UART1. Input/output protocols available as in UART1. SPI is not available unless the
D_SEL interface is set up accordingly (see D_SEL interface).
TIMEPULSE (1 Hz Nav) 1 pulse per second, synchronized at rising edge, pulse length 100 ms
Table 8: Default messages
With firmware version HPG 1.00 it is possible to use UART2 as the RTCM 3x interface. RTCM
3x is the default input and output protocol. NMEA can also be configured as an input or output
protocol on UART 2.
Refer to the u-blox ZED-F9P Interface Description [2] for information about further settings.
If the receiver is configured to output RTCM messages on several ports, they must all have the
same RTCM message and message rate configuration otherwise the MSM multiple message
bit might not be set properly.
The ZED-F9P outputs NMEA 4.1 messages that includes satellite data for all GNSS bands
being received. This results in many more NMEA messages being output for each navigation
period. Ensure the UART1 baud rate being used is sufficient for the set Navigation rate and
the amount of GNSS signals being received.

Table of Contents

Other manuals for u-blox ZED-F9P

Questions and Answers:

Question and Answer IconNeed help?

Do you have a question about the u-blox ZED-F9P and is the answer not in the manual?

u-blox ZED-F9P Specifications

General IconGeneral
GNSSGPS, GLONASS, Galileo, BeiDou, QZSS, SBAS
Concurrent GNSS4
RTKYes
Velocity Accuracy0.05 m/s
Time Pulse Accuracy30 ns
Operating Temperature-40°C to +85°C
Supply Voltage2.7 V to 3.6 V
Channels184
Frequency BandsL1, L2
Dimensions22 mm x 17 mm x 2.4 mm
InterfacesUART, SPI, I2C

Related product manuals