Data Sheet

NEO-M8P - Data Sheet
UBX-15016656 - R06 Early Production Information Functional description
Page 13 of 30
dynamic ‘seeding’ of the algorithm can be used to detect time shifted replay attacks on the received message
data. See u-blox 8 / u-blox M8 Receiver Description Including Protocol Specification [2] for more information.
1.12 Geofencing
The geofencing feature allows for the configuration of up to four circular areas (geofences) on the earth's
surface. The receiver will then evaluate for each of these areas whether the current position lies within the area
or not and signal the state via UBX messaging and PIO toggling. Geofencing can be configured using the UBX-
CFG-GEOFENCE message; the geofence evaluation is active whenever there is at least one geofence configured.
The NEO-M8P module uses pin 16 as the GEOFENCE_STAT status pin. This is asserted active low to indicate
any position within the combined geofence areas.
Figure 4: Illustration of the Geofence boundary
1.13 TIMEPULSE
A configurable time pulse signal is available with the NEO-M8P modules.
The TIMEPULSE output generates pulse trains synchronized with a GPS or UTC time grid with intervals
configurable over a wide frequency range. Thus it may be used as a low frequency time synchronization pulse or
as a high frequency reference signal.
The NEO-M8P time pulse output is configured using messages for “TIMEPULSE2.” This pin has a secondary
function during start-up (initiation of “SAFEBOOT” mode for firmware recovery) and should not normally
be held LO during start-up.
By default the time pulse signal is disabled and if required can be activated using UBX-CFG-TP5. For more
information see the u-blox 8 / u-blox M8 Receiver Description including Protocol Specification [2].
1.14 Protocols and interfaces
Protocol
Type
NMEA 0183 V4.0
(V2.1,V2.3 and V4.1 configurable)
Input/output, ASCII
UBX Input/output, binary, u-blox proprietary
RTCM 3.2 Input , for RTK
RTCM 3.2 Output (NEO-M8P-2 only)
Table 4: Available Protocols
All protocols are available on UART, USB, DDC (I
2
C compliant) and SPI. For specification of the various protocols
see the u-blox 8 / u-blox M8 Receiver Description Including Protocol Specification [2].
When NMEA protocol is used, version V4.1 is needed to provide all the related RTK information flags.
1.15 Interfaces
A number of interfaces are provided either for data communication or memory access. The embedded firmware
uses these interfaces according to their respective protocol specifications.