Peer Redundancy Parameters

UNINTENDED EQUIPMENT OPERATION

Do not change these protocol parameters, except on the advice of Technical Support for this product.

Failure to follow these instructions can result in death, serious injury, or equipment damage.

Parameter

Allowable values

Default value

Description

[DNPR]
ActivateIfPeerIsActiveOffline

[<unit>]
ActivateIfPeerIsActiveOffline

0 – Disable

1 – Enable

1

This parameter is used in a scenario where one of the redundant I/O devices is active and can open the TCPIP connection to the RTU, but stays offline as the driver does not get any response for the DNP3 messages it sends to the RTU.

If this is the case and the parameter is set to 1, the driver performs the switchover to the redundant I/O device peer and makes it active giving that I/O device a chance to communicate to the RTU.

If this behavior is not required, this parameter should be set to 0.

[DNPR]
EnablePeerRedundancy

0 – Disable peer driver redundancy.

1 – Enable peer driver redundancy.

0

Enable the peer redundancy process. Only 1 peer driver is supported.

[DNPR]LocalAddress

Valid IP address.

127.0.0.1

The IP address of yourself for listening on.

[DNPR]LocalPort

Port.

5000

Valid Port you want to listen on.

[DNPR]MaxPeerOutQueueSize

1 to 100,000

10,000

If DNPR redundancy is configured, the driver replicates the value updates received from the device to the redundant peer. This provides the peer driver with the latest values in case a switchover occurs.

This parameter controls the maximum number of value updates which the driver stores in the queue before sending them to the peer. Limiting the queue size may be required if the driver receives more values updates than it can replicate.

Note: If the parameter value is greater than 100,000, it will be reset to 100,000.

[DNPR]PeerAddress

Valid IP address.

None

The IP address of your peer driver.

[DNPR]PeerPort

Port

5200

Any Valid Peer Destination Port.

[IOSERVER]
WatchdogPrimary

0 – Disable

1 – Enable

0

Should be set when peer redundancy is in use. This helps ensure that the check that your unit is still online occurs for every unit.

Not only does this enable the unit’s offline to be noticed if NO reads are happening to that unit, but enables the driver to minimize #COMs on changeover by reporting offline in this check, and not on actual read requests.

[DNPR]
MaxMsgPerPollTime

1 to 4294967295

500

The maximum number of peer cache updates to be processed per call to Cpu() which is controlled by the "PollTime" parameter.

[DNPR]
PeerCommRetryCount

1 to 10

3

Retries allowed on peer messages before the peer communications are considered down.

[DNPR]
PeerKeepAliveTime

1 to 65535

30000

Ping time between pairs to check "they are there".

[DNPR]PeerTimeout

1 to 65535 ms

4000 ms

Timeout time in getting a response back from your peer.

[DNPR]
UnitUsurpModeDefault

[<unit>]UnitUsurpMode

0 means that an integrity poll will be issued

1 means that an RTU time read will be issued.

2 means nothing will be done.

3 means that a static (Class0) Poll will be issued.

3

Defines the default behavior on usurp of a unit.

The online status of the RTU is replicated between servers. So regardless of what the value is set to, the unit will initially have the same status as it had on the other server.

The polling sequence is also replicated, so the next periodic poll on the unit will occur at the same time it would have if the usurp had not occurred (unless a value of 0 is used, which results in the poll period being reset).

Note: No event will be generated if the usurp mode is 3 (Static Poll) and the value in the device is different than the value in the driver cache.