Logs are the mechanism used to extract information from the receiver.

As of firmware 7.08 and later, Agriculture firmware versions support the same logs as OEM7 firmware streams.

Log Types

See the LOG command, for details about requesting logs.

The receiver is capable of generating three type of logs: synchronous, asynchronous and polled. The data for synchronous logs is generated on a regular schedule. In order to output the most current data as soon as it is available, asynchronous data is generated at irregular intervals. The data in polled logs is generated on demand. The following table outlines the log types and the valid triggers to use:

Log Type Triggers


Recommended Trigger

Illegal Trigger










See Message Time Stamps for information about how the message time stamp is set for each type of log.


  1. The maximum number of logs the OEM7 family of receivers can handle at a time is 128 logs for firmware versions 7.09.00 and greater or 80 logs for firmware versions prior to 7.09.00. If an attempt is made to log more than the maximum number of logs at a time, the receiver responds with an Insufficient Resources error. Note that RXSTATUSEVENTA logs are requested on most ports by default and these logs count against the maximum.

  2. Asynchronous logs, such as MATCHEDPOS, should only be logged ONCHANGED. Otherwise, the most current data is not output when it is available. This is especially true of the ONTIME trigger, which may result in inaccurate time tags.

  3. Use the ONNEW trigger with the MARKxTIME or MARKxPOS logs.

  4. Before the output of fields for logs, there is a header. See ASCII, Abbreviated ASCII and Binary.

Log Type Examples

For polled logs, the receiver only supports an offset that is:

  • smaller than the logging period

  • decimal values that are a multiple of the maximum logging rate defined by the receiver model. For more information see the LOG command.

The following are valid examples for a polled log:

log portstats ontime 4 2

log version once

For polled logs, the following examples are invalid:

log serialconfig ontime 1 2     [offset is larger than the logging period]

log serialconfig ontime 4 1.5   [offset is not an integer]

For synchronous and asynchronous logs, the receiver supports any offset that is both:

  • smaller than the logging period

  • a multiple of the minimum logging period

For example, if the receiver supports 20 Hz logging, the minimum logging period is 1/20 Hz or 0.05 s. The following are valid examples for a synchronous or asynchronous log, on a receiver that can log at rates up to 20 Hz:

log bestpos ontime 1        [1 Hz]

log bestpos ontime 1 0.1

log bestpos ontime 1 0.90

log avepos ontime 1 0.95

log avepos ontime 2         [0.5 Hz]

log avepos ontime 2 1.35

log avepos ontime 2 1.75

For synchronous and asynchronous logs, the following examples are invalid:

log bestpos ontime 1 0.08   [offset is not a multiple of the minimum logging period]

log bestpos ontime 1 1.05   [offset is larger than the logging period]