Time synchronization, Device diagnostics – SATEC SA300 ezPAC Operation Manual User Manual
Page 25
Chapter 2 Device Description
Time Synchronization
SA300 Substation Automation Unit
25
Time Synchronization
Time synchronization can provide a common time basis for the fault recorders in a
protection or control system so that events and disturbances within the entire station
can be compared to one another.
The SA300 can receive time synchronization signal either from a GPS satellite clock
that has an IRIG-B time code output, or from another device that can provide minute-
aligned time synchronization pulses through relay contacts.
The SA300 IRIG-B port uses unmodulated (pulse-width coded) time code signal
(unbalanced 5V level).
For more information on time synchronization in your device and IRIG-B operation,
see
in section Local Settings, Chapter 7.
Device Diagnostics
Device diagnostic messages may appear as a result of the SA300 built-in diagnostic
tests performed during start-up and device operation.
All diagnostic events are recorded in the device Event log and can be inspected via
PAS (see
in Chapter 14). The diagnostics status is also stored
in a non-volatile register, which is not affected by loss of power and may be read and
cleared via PAS, from the RDM, or from a user application. Refer to the SA300
communication guides for the diagnostic register address and layout. See
Device
Diagnostic Codes
in Appendix F for the list of diagnostic codes and their meanings.
Device failures are divided into three categories:
1. Non-critical intermittent faults with auto-reset. They do not cause
the device to restart but may cause temporary degradation of
device functionality, like IRIG-B time code signal faults. These
faults are cleared automatically as the condition that caused the
fault disappears.
2. Non-critical recoverable hardware or configuration faults with
manual reset. These faults normally cause the device to restart
followed by repairing of the configuration data. These faults must
be cleared manually via PAS, from the RDM, or from a user
application.
3. A critical unrecoverable hardware or configuration failure. The
reason may be an unrecoverable sampling failure, or corruption of
the time, the factory device configuration or the calibration setup
data. A critical error causes the device to release all its outputs and
to stop normal operation until the faults that caused the critical
error are cleared.
Hardware failures are normally non-critical recoverable faults that do not cause a
system failure but may cause data loss. Hardware failures are often caused by
excessive electrical noise in the region of the device.
A configuration reset may also be a result of the legal changes in the device
configuration whenever other configuration data is affected by the changes made.
In the event of a device fault, check the fault reason and clear the device diagnostics.
If the reason is a time fault, update the device clock. In the event of a configuration
reset, determine the device setup affected by the fault via the event log, and then
verify the setup data.
See
271H
272H
Viewing and Clearing Device Diagnostics
in Chapter 11,
273H
Viewing and Clearing
Device Diagnostics
in Chapter 4, and
274H
Status Information Display
in Chapter 3 on how
to inspect and clear the device diagnostics status.
If the device continuously resets itself or an unrecoverable critical error occurs,
contact your local distributor.