u-blox ZED-F9P, Integration Manual

Page: 31 / 110

ZED-F9P - Integration manual
•
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 GEOFENCE_STAT interface .
3.4.4 Using a PIO for geofence state output
This feature can be used for example for waking up a sleeping host when a defined geofence
condition is reached. The receiver will toggle the assigned pin according to the
combined
geofence
state. Due to hardware restrictions, the geofence unknown state is not configurable and is always
be represented as HIGH. If the receiver is in software backup or in a reset, the pin will go to HIGH
accordingly. The meaning of the LOW state can be configured using the CFG-GEOFENCE-PINPOL
configuration item.
The CFG-GEOFENCE-PIN configuration item refers to a PIO and not a physical device pin.
The PIO number must be set so that it is mapped to the assigned geofence state device pin.
The ZED-F9P is assigned PIO3 that is assigned to module pin 19.
3.5 Logging
3.5.1 Introduction
The logging feature allows position fixes and arbitrary byte strings from the host to be logged in
flash memory attached to the receiver. Logging of position fixes happens independently of the host
system, and can continue while the host is powered down.
The following table lists all the logging-related messages:
Message Description
UBX-LOG-CREATE Creates a log file and activates the logging system
UBX-LOG-ERASE Erases a log file and deactivates the logging subsystem
UBX-LOG-INFO Provides information about the logging system
UBX-LOG-STRING Enables a host process to write a string of bytes to the log file
Table 18: Logging control and configuration messages
Message Description
UBX-LOG-RETRIEVE Starts the log retrieval process
UBX-LOG-RETRIEVEPOS A position log entry returned by the receiver
UBX-LOG-RETRIEVEPOSEXTRA Odometer position data
UBX-LOG-RETRIEVESTRING A byte string log entry returned by the receiver
UBX-LOG-FINDTIME Finds the index of the first entry (given time)
Table 19: Logging retrieval messages
3.5.2 Setting the logging system up
An empty log can be created using the UBX-LOG-CREATE message and a log can be deleted with
the UBX-LOG-ERASE message. The logging system will only be running if a log is in existence, so
most logging messages will be rejected with a UBX-ACK-NAK message if there is no log present.
Only one log can be created at any one time, therefore a UBX-ACK-NAK message will be returned,
if a log already exists. The message specifies the maximum size of the log in bytes (with some pre-
set values provided). Both the logging subsystem and the receiver file-store have implementation
overheads, so total space available for log entries will be somewhat smaller than the size specified.
UBX-18010802 - R08 3 Receiver functionality Page 31 of 110
Early production information