ZED-F9P-Integration Manual
UBX-18010802 - R02

4 Receiver description Page 33 of 114
Advance Information
Status Description
DONTKNOW Antenna power status is not known
Table 11: Antenna Power Status
4.4 Legacy configuration interface compatibility
There is interface backwards-compatibility for the legacy UBX-CFG configuration messages, such
as the UBX-CFG- NAV5 message. See Legacy UBX-CFG Message Fields Reference section in the
ZED-F9P Interface Description [2].
4.5 Serial Communication Ports Description
u-blox receivers come with a highly flexible communication interface. It supports the NMEA and the
proprietary UBX protocols, and is truly multi-port and multi-protocol capable. Each protocol (UBX,
NMEA) can be assigned to several ports at the same time (multi-port capability) with individual
settings (e.g. baud rate, message rates, etc.) for each port. It is even possible to assign more
than one protocol (e.g. UBX protocol and NMEA at the same time) to a single port (multi-protocol
capability), which is particularly useful for debugging purposes.
Port # Electrical Interface
0 DDC
(I²C
compatible)
1 UART1
2 UART2
3 USB
4 SPI
Table 12: Port Number assignment
The following table shows the port numbers reported in the UBX-MON-COMMS message.
Port # Electrical Interface
0x0000 DDC
(I²C
compatible)
0x0001 UART1
0x0102 UART2
0x0003 USB
0x0004 SPI
Table 13: Port Number assignment
4.5.1 TX-ready indication
This feature enables each port to define a corresponding pin, which indicates if bytes are ready
to be transmitted. By default, this feature is disabled. For USB, this feature is configurable but
might not behave as described below due to a different internal transmission mechanism. If the
number of pending bytes reaches the threshold configured for this port, the corresponding pin will
become active (configurable active-low or active-high), and stay active until the last bytes have
been transferred from software to hardware (note that this is not necessarily equal to all bytes
transmitted, i.e. after the pin has become inactive, up to 16 bytes can still need to be transferred
to the host).
The TX-ready pin can be selected from all PIOs which are not in use (see UBX-MON-HW3 for a list
of the PIOs and their mapping), each TX-ready pin is exclusively for one port and cannot be shared.
If the PIO is invalid or already in use, only the configuration for the TX-ready pin is ignored, the rest
of the port configuration is applied if valid. The acknowledge message does not indicate if the TX-
ready configuration is successfully set, it only indicates the successful configuration of the port. To
validate successful configuration of the TX-ready pin, the port configuration should be polled and
the settings of TX-ready feature verified (will be set to disabled/all zero if the settings are invalid).
To Next Page
Loading...
