Default Messages - u-blox ZED-F9P Integration Manual

F9 high precision gnss module
Hide thumbs Also See for ZED-F9P:
Table of Contents

Advertisement

3.7 Default messages

Interface
UART1 Output
UART1 Input
UART2 Output
UART2 Input
USB Output
USB Input
DDC
SPI
TIMEPULSE (1 Hz Nav)
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.
UBX-18010802 - R02
Advance Information
Settings
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.
38400 Baud, 8 bits, no parity bit, 1 stop bit. Automatically accepts the following protocols
without need of explicit configuration: UBX, NMEA, RTCM 3x.
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.
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.
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.
Automatically accepts following protocols without need of explicit configuration: UBX, NMEA,
RTCM 3x.
Fully compatible with the I
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.
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).
1 pulse per second, synchronized at rising edge, pulse length 100 ms
 
2
C industry standard, available for communication with an external
3 Getting started
ZED-F9P - Integration Manual
Page 29 of 114

Hide quick links:

Advertisement

Table of Contents
loading

This manual is also suitable for:

Zed-f9p-00b-00

Table of Contents