SMART6 User Manual Rev 3
63
B.5 LOG Request Logs from the Receiver
Many different types of data can be logged using several different methods of triggering the log events. Every
log element can be directed to any combination of the three COM ports. The ONTIME trigger option requires
the addition of the
period
parameter. See the
OEM6 Family Firmware Reference Manual
for further
information and a complete list of data log structures. The
LOG
command
tables
in this section
show the
ASCII command format.
The optional parameter [hold] prevents a log from being removed when the
unlogall
command, with its
defaults, is issued. To remove a log that was invoked using the [hold] parameter requires the specific use of
the
unlog
command. To remove all logs that have the [hold] parameter, use the
UNLOGALL
command with
the
held
field set to 1.
The [port] parameter is optional. If [port] is not specified, [port] is defaulted to the port that the command was
received on.
Message ID: 1
Abbreviated ASCII Syntax:
LOG [port] message [trigger [period [offset [hold]]]]
Abbreviated ASCII Example 1:
LOG COM1 BESTPOS ONTIME 7 0.5 HOLD
The above example shows BESTPOS logging to COM port 1 at 7 second intervals and offset by 0.5 seconds
(output at 0.5, 7.5, 14.5 seconds and so on). The [hold] parameter is set so logging is not disrupted by the
unlogall
command.
To send a log only one time, the trigger option can be ignored.
Abbreviated ASCII Example 2:
LOG COM1 BESTPOS ONCE 0.000000 0.000000 NOHOLD
Refer to the
Command Formats
section of the
OEM6 Family Firmware Reference Manual
for additional
examples.
1. The OEM6 family of receivers can handle 64 logs at a time. If it is more than 64 logs at a
time, the receiver responds with an Insufficient Resources error.
2. Maximum flexibility for logging data is provided to the user by these logs. The user is
cautioned, however, to recognize that each log requested requires additional CPU time and
memory buffer space. Too many logs may result in lost data and degraded CPU
performance. Receiver overload can be monitored using the idle time field and buffer
overload bits of the Receiver Status in any log header.
3. Polled log types do not allow fractional offsets or ONTIME rates faster than 1 Hz.
4. Use the ONNEW trigger with the MARKTIME or MARKPOS logs.
5. Only the MARKPOS or MARKTIME logs and ‘polled’ log types are generated, on the fly, at
the exact time of the mark. Synchronous and asynchronous logs output the most recently
available data.
6. If the ONTIME trigger is used with asynchronous logs, the time stamp in the log does not
necessarily represent the time the data was generated but rather the time when the log is
transmitted.
1. In NovAtel Connect there are two ways to initiate data logging to the receiver's serial ports:
- the
LOG
command in the
Console
window or
- use the interface provided in the
Logging Control
window.
2. Only the ASCII/Abbreviated ASCII log table is included in this manual. Refer to the
LOG
OEM6 Family Firmware Reference Manual
for binary log details.