User manual

Toolbox 32 User Manual 1.47d www.cse-semaphore.com/mykingfisher
Page
117
Example - Comms Fails Today And Yesterday
Communication fails give a good indication of the state and reliability of the RTU communications network.
Communication statistics are automatically recorded by the RTU in Network Link Registers. These network
link registers can be accessed by SCADA software by copying them to local registers. At midnight, the fails
today values can be copied to fails yesterday registers and then the network link registers reset to zero.
Communication status is updated after each poll or when an exception report is received (which clears the
comms fail).
Manage Comms Attempt Fail Counters For RTU2
DoEvery1Sec CopyFailsTdy
#YTICK.SEC #R22
├─────┤ ├────────────────────────────────────────────────────────────(Copy)────┤
#YLFAIL2
Rollover Comms Attempt Fails At Midnight
12AMRollover RollovrFails
#R100.4 #R32
├─────┤ ├────────────────────────────────────────────────────────┬───(Copy)────┤
#R22
ClrFailsTdy
#YLFAIL2
└───(Copy)────┤
0
Flag a comms fail after a failed poll
R2 PollFail R2 CommsFail
#YLST2.1 #R2.2
├─────┤ ├──────────────────────────────────────────────────────────────( )─────┤
Figure: Managing Comms Attempt Fails For Today And Yesterday
It is usually more accurate to record the number of message fails instead of the number of attempt fails. A
message fail occurs when all of the configured attempts fail (eg. 3 attempts at each poll message). The
example below shows how to count message fails and how to flag a communications fail after 10
consecutive attempt fails for RTU2.
Count a new fail for each poll fail (3 attempts per poll)
R2 MsgFail R2 PFailsTdy
#YLST2.1 #R202
├─────┤ ├────────────────────────────────────────────────────────┬────(Inc)────┤
R2 MsgFail
#YLST2.1
└─────(R)─────┤
Rollover Poll Fails At Midnight
12AMRollover Roll PFails
#R100.4 #R202
├─────┤ ├────────────────────────────────────────────────────────┬───(Copy)────┤
#R222
R2 PFailsTdy
#R202
└───(Copy)────┤
0
Flag a comms fail after 10 consecutive failed attempts
R2 Fails R2 CommsFail
#YLFC2 #R2.2
├─────[>]──────────────────────────────────────────────────────────────( )─────┤
9
Figure : Managing RTU2 Poll Fails For Today And Yesterday