ZED-F9K - Integration manual
•
Unknown
- There is no valid position solution or the position uncertainty does not allow for
unambiguous state evaluation
The position solution uncertainty (standard deviation) is multiplied with the configured confidence
sigma level number and taken into account when evaluating the geofence state (red circle in figure
below).
Figure 9: Geofence states
The combined state for all geofences is evaluated as the combination (Union) of all geofences:
•
Inside
- The position lies inside of at least one geofence
•
Outside
- The position lies outside of all geofences
•
Unknown
- All remaining states
A pin is made available to indicate the status of the geofence. See the
.
3.4 Communication interfaces
u-blox receivers are equipped with a communication interface which is multi-protocol capable. The
interface ports can be used to transmit GNSS measurements, monitor status information and
configure the receiver.
A protocol (e.g. UBX, NMEA) can be assigned to several ports simultaneously, each configured with
individual settings (e.g. baud rate, message rates, etc.). More than one protocol (e.g. UBX protocol
and NMEA) can be assigned to a single port (multi-protocol capability), which is particularly useful
for debugging purposes.
The ZED-F9K provides UART1, UART2, SPI, I2C and USB interfaces for communication with a
host CPU. The interfaces are configured via the configuration methods described in the ZED-F9K
interface description [
].
The following table shows the port numbers reported in the UBX-MON-COMMS messages.
Port no.
UBX-MON-COMMS portId
Electrical interface
0
0x0000
I2C
1
0x0100
UART1
2
0x0201
UART2
3
0x0300
USB
4
0x0400
SPI
Table 14: Port number assignment
It is important to isolate interface pins when VCC is removed. They can be allowed to float or
they can be connected to a high impedance.
Example isolation circuit is shown below.
UBX-20046189 - R01
3 Receiver functionality
Page 34 of 105
C1-Public
Early production information
