The settings are located under .
| Setting | Description |
|---|---|
| Mapping select | Selects one of the protocol data point mappings, 1 or 2, to be used by this instance. The data point mappings can be created using Communication Management in PCM600. Several IEC 60870-5-104 protocol instances can use the same mappings. |
| Show bad time | Enabled by default. The relay has an internal, fixed criterion for tagging change event’s time stamps as “bad”. It means that the relay has not been time-synchronized for a specific time period. The “bad” time stamp criterion is based on the accuracy demands stated for the native IEC 61850 standard change events. The IEC 60870-5-104 change events are derived from these native events. It is possible to discard the “bad time” tag for IEC 60870-5-104 events. |
| Time zone | The change event time stamps can be reported in either UTC or local time. The default setting is UTC time. This setting is also relevant when using IEC 60870-5-104 control commands with time tags. The client-provided time stamp must be given in this defined time format. The setup of the local time, meaning the relative time adjustment to be made between UTC (GMT) time and local time, is done elsewhere in the relay. |
| Overflow mode | In case of internal indication event buffer overflow, it is possible to define whether to keep the oldest or the newest events in the buffer. The default setting keeps the oldest events and also adds an overflow event as the last event. It is possible to omit overflow handling by setting this parameter to "Keep newest" and defining OvInd IOA to value "0". |
| OvInd IOA | Single-point object address for the overflow indication. The default value is address "60000". Value "0" means that no overflow indication object exists. When an overflow indication occurs, the client can trigger a GI request. |
| OvInd NoGI IOA | Single-point object address for overflow indications occurring in objects which are not subject to GI. If overflow from these objects occurs, a GI request from the client does not reveal any lost data and thus GI request is unnecessary. It is possible to make this address equal to the OvInd IOA address, and thus generate overflow indication for all data object types. |
| Selection timeout | Protocol-dependent timeout between select and execute control commands. The controllable object also has a timeout setting configured, mainly intended for local control operation. When the control command is performed remotely from this protocol, the configured timeout is temporarily overridden by this setting. The default timeout value is 30 seconds. |
| Counter reporting | Counter objects, that is, integrated totals, can be reported spontaneously or be read on demand by the client using a counter interrogation request. This setting enables or disables the spontaneous counter reporting based on freeze operation. The freeze operation can be given from the client as a request or also be triggered externally through the protocol function block’s physical EC_FRZ control input. |
| Freeze Mode | Defines if the counter freeze operation should only freeze (latch) the current counter values or also reset the counters. The default setting is "Not in use", meaning that the client should read (interrogate) the counters on demand. |
| IT_FRZ | Control point for counter freeze operation. This control is logically connected to the function block’s EC_FRZ input. For test purposes, it is possible to manually trigger a counter freeze operation and spontaneous transmission with this setting. |
| Cyclical Period | Event-generating data objects can alternatively be configured for cyclical transmission. This data point specific configuration can be done by Communication Management in PCM600. The Cyclical Period setting defines the periodical reporting time of these cyclical data objects. |
| Command delay | Defines the maximum delta time (internal delay) allowed for client control commands with time stamps. |
| Prtl Customization | Customization parameter. Configuration of advanced protocol customization features. See Advanced protocol customization for details. |