158
SPAN-SE User Manual Rev 1
Appendix C
Data Logs
three types: Synchronous, asynchronous, and polled. The data for synchronous logs is generated on a
regular schedule. Asynchronous data is generated at irregular intervals. If asynchronous logs were
collected on a regular schedule, they would not output the most current data as soon as it was
available. The data in polled logs is generated on demand. An example would be RXCONFIG. It
would be polled because it changes only when commanded to do so. Therefore, it would not make
sense to log this kind of data ONCHANGED, or ONNEW. The following table outlines the log types
and the valid triggers to use:
Table 32: Log Type Triggers
Section C.1.4, Message Time Stamps
for information on how the message time stamp
is set for each type of log.
1. A SPAN-SE user can request up to 25 logs from the OEMV-3, in addition to 30 SPAN-
specific logs. If you attempt to log more than 30 logs at a time, the receiver responds with an
Insufficient Resources error.
2. Asynchronous logs, such as BESTLEVERARM, should only be logged ONNEW. Otherwise,
the most current data is not output when it is available. This is especially true of the ONTIME
trigger, which may cause inaccurate time tags to result.
3. Use the ONNEW trigger with the MARK
x
TIME or MARK
x
PVA logs.
Before the output of fields for ASCII and Binary logs, there is an ASCII or binary header respectively.
See the ASCII and Binary Sections that follow. There is no header information before Abbreviated
ASCII output.
Type
Recommended Trigger
Illegal Trigger
Synch
ONTIME
ONNEW, ONCHANGED
Asynch
ONCHANGED
-
Polled
ONCE or ONTIME
1
1. Polled log types do not allow fractional offsets and cannot do
ontime rates faster than 1Hz.
ONNEW, ONCHANGED
