User Manual

SGD-SB2025NT-TUM, Part 2
Jan 12 Page 92 TM LOGGING
13 TM LOGGING
13.1 O VERVIEW
This section describes the TM Logging facility that is an inherent feature of the TM and
independent of all other options.
Information is automatically gathered by the TM; the only setup required is that of setting system
time. The data is stored in four log files, one covering each event subject. These are generated
on a daily basis and are retained for 28 days. Through the TM ET, the information held in any log
file (current or historic) may be viewed by selecting the date and the log subject. The log file view
on the ET also allows the results to be filtered to focus on the specific subjects such as channel,
equipment and type if a specific issue is being analysed.
The SB2025NT has the option to use a compact flash card instead of the usual hard disk drive and
to reduce wear and prevent premature failure the amount of logging is reduced when the CF is
fitted.
Once a log file is transferred to the ET (opened) it may then be saved to a file in “comma separated
values” (csv) format for archiving. This format makes it ideal for transfer to a spreadsheet if a more
detailed examination outside of the ET application is required. The original log files are not
accessible to the user.
13.2 E VENT S UBJECTS
The log files are separated into the four event subjects: Alarms; System; Voter; and ET. A new log
file is created when the first event for that log occurs for that day. If the first event is the TM being
switched on, every log file will start with that entry showing the time the log file was created and the
fact that the TM was started. Subsequent TM restarts or reboots are logged in each file but the full
start-up information is only in the system log.
13.2.1 Alarms Log
For an event to be logged in the Alarm log, that event must be configured to alarm status. Full
information on configuring alarms and their action can be found in Section 12 – Alarms . The
occurrence of every alarm event is logged with the information that uniquely identifies the source
and nature of the alarm. The action of acknowledging an alarm is also logged and this action may
or may not have occurred before the status of the alarm item in question has returned to normal.
If the item had returned to normal status before the alarm is acknowledged, the alarm log will show
the alarm cleared immediately after the alarm was acknowledged. If the acknowledge occurs while
the item is still at alarm status, the alarm cleared message will be logged at the point at which the
status returned to normal, i.e. in real time.
13.2.2 System Log
The system log is focussed on recording events and conditions that might impact upon the
operation of the wider Solar network. Events that directly or indirectly involve the TM are logged
even though these might have occurred at a remote Station NI. For example, a record will be kept
of the ‘PPS’ and ‘PLL’ status for every NI, as problems with either item will result in inaccurate
measurement of the PATs, which impact upon the TM. The log will also record the error counts of
frequency and phase for a NI PLL. These are displayed in the style of ‘0Xnn’ for each value,
where “nn” is the error value in hexadecimal notation.
The event field of a system log will have many entries immediately after a TM is restarted. There
will be more than 20 log entries for the TM itself and also one per NI as each unit is enabled and
brought online.