
Doc
#
E166703
E-32
E: Retrieving Logs
Electro
Industries/GaugeTech
The Leader In Power Monitoring and Smart Grid Solutions
Electro
Industries/GaugeTech
The Leader In Power Monitoring and Smart Grid Solutions
• The clock changed event shows the clock value just before the change in the Mod
and Parm bytes. Parms are bit-mapped:
• b31 - b28
month
• b27 - b23
day
• b22
daylight savings time flag
• b20 - b16
hour
• b13 - b8
minute
• b5 - b0
second
• unused bits are always 0
• Stimulus for a flash sector error indicates what the flash was doing when the error
occurred: 1 = acquire sector, 2 = startup, 3 = empty sector, 4 = release sector, 5 =
write data.
• Flash error counters are reset to zero in the unlikely event that both copies in
EEPROM are corrupted.
• The flash job queue is flushed (and log records are lost) in the unlikely event that
the queue runs out of space.
• A "babbling log" is one that is saving records faster than the MP200 unit can handle
long term. When babbling is detected, the log is frozen and no records are
appended until babbling ceases. For as long as babbling persists, a summary of
records discarded is logged every 60 minutes. Normal logging resumes when there
have been no new append attempts for 30 seconds. Onset of babbling occurs when
a log fills a flash sector in less than an hour (applies only to Alarm, I/O Change, and
Historical logs), when the log fills, or when a log grows so far beyond its normal
bounds that it is in danger of crashing the system. This applies to all logs except
the System log, which does not babble. It is possible for the other logs during an
extended log retrieval session.
• Logging of diagnostic records may be suppressed via a bit in programmable
settings.
Содержание MP200
Страница 1: ...V 1 07 November 5 2018 ...
Страница 2: ...This page intentionally left blank ...