User manual

Toolbox 32 User Manual 1.47d www.cse-semaphore.com/mykingfisher
Page
111
Example - Sending The Exception Report
An RTU usually has a number of inputs and conditions that can trigger an exception report. Rather than
exception report every change separately, it is better if all these conditions set a common flag that causes a
single exception report to be sent containing all the RTU data. As shown in the previous sections for
exception reporting analogs and digitals, the Update RTU1 flag was set when an exception report was
required. An example of ladder logic used to send the exception report is shown below (for all types of
comms except Ethernet).
│ │
├Exception Report To RTU1 If Port 3 Is Not Waiting For a Reply ┤
│ │
│Update RTU1 P3 Waiting ExRepToRTU1 │
│ #R100.2 #YPST3.2 RTU 1 │
├─────┤ ├─────────────────────────────────────────────────┤/├────┬──(TX_DATA)──┤
│ │ #AI14.2 │
│ │Update RTU1 │
│ │ #R100.2 │
├ ┼ ┼ ┼ ┼ └─────(R)─────┤
│ │
Exception Reporting Using Ethernet
It is possible to communicate with multiple RTUs at the same time using one Ethernet port. Therefore,
instead of checking if the port is busy (waiting for a reply from any RTU), it is better to check if the target RTU
is busy as shown below.
│ │
├Exception Report To RTU1 If RTU1 Not Busy ┤
│ │
│Update RTU1 RTU1 Busy ExRepToRTU1 │
│ #R100.2 #YLST1.2 RTU 1 │
├─────┤ ├─────────────────────────────────────────────────┤/├────┬──(TX_DATA)──┤
│ │ #AI14.2 │
│ │Update RTU1 │
│ │ #R100.2 │
├ ┼ ┼ ┼ ┼ └─────(R)─────┤
│ │