Device diagnostics – SATEC PM180 Operation Manual User Manual

Page 26

Advertising
background image

‎Chapter 2 Device Description

Device Diagnostics

24

PM180 Substation Automation Unit

aligned time synchronization pulses through relay contacts connected to DI1-DI48
PM180 digital input, or from the Ethernet network using SNTP protocol.
The PM180 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

Time Synchronization Source

in section Local Settings, Chapter 7.

Device Diagnostics

Device diagnostic messages may appear as a result of the PM180 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

Viewing the Event Log

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 PM180
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

Viewing and Clearing Device Diagnostics

in Chapter 11,

Viewing and Clearing

Device Diagnostics

in Chapter 4, and

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.

Device Fault Alarm

The PM180 provides a global "DEVICE FAULT" event flag that is asserted all the
time while one of the non-critical diagnostics events exists. It can be checked from a
setpoint (see Using Control Setpoints in Chapter 7) to give a fault indication via a
relay output. If the alarm relay is programmed for failsafe mode using inverting
polarity, then its normally closed contacts will be open if either the device looses
power or a non-critical device fault occurs. Note that in the event of a critical system
failure, all relay outputs are automatically released.

Advertising