User manual

Toolbox 32 User Manual 1.47d www.cse-semaphore.com/mykingfisher
Page
112
Example - Polling Data
Polling is usually performed by the master RTU in order to get a regular update of remote RTU data and to
determine if communications to the remote RTUs have failed.
The Series 2 protocol allows for full-duplex communications which means that the RTU can simultaneously
transmit and receive. However, since most radios are half-duplex, which means that the RTU cannot transmit
and receive simultaneously, it is necessary to force the RTU to wait for a reply to each transmit message.
Unless the RTU is forced to wait, it will transmit all the polling messages one after the other - which can take
a few seconds. Because of the delay, the first polling message will have timed out before the RTU is able to
receive a reply as the RTU is still busy transmitting. The following examples show how to force the RTU to
wait for a reply to each message when polling.
Basic polling
The example below polls RTUs 2, 3 and 4 every 15 minutes. The example checks that port 3 is free (ie. not
waiting for a reply to a message - #YPST3.2 ) before polling the next RTU. Note: the port number to check is
the port configured to communicate with each remote RTU as defined in the Port List.
Poll remote RTUs every 15 minutes
DoEvery15min Poll Flag 2
#T1 #R1.2
├──[PERIOD]─────────────────────────────────────────────────────┬─────(S)─────┤
15 Minutes
Poll Flag 3
#R1.3
├─────(S)─────┤
Poll Flag 4
#R1.4
└─────(S)─────┤
Poll Flag 2 P3 Waiting Poll RTU2
#R1.2 #YPST3.2 RTU 2
├─────┤ ├─────────────────────────────────────────────────┤/├────┬──(RX_DATA)──┤
#R1
Poll Flag 2
#R1.2
└─────(R)─────┤
Poll Flag 3 P3 Waiting Poll RTU3
#R1.3 #YPST3.2 RTU 3
├─────┤ ├─────────────────────────────────────────────────┤/├────┬──(RX_DATA)──┤
#R1
Poll Flag 3
#R1.3
└─────(R)─────┤
Poll Flag 4 P3 Waiting Poll RTU4
#R1.4 #YPST3.2 RTU 4
├─────┤ ├─────────────────────────────────────────────────┤/├────┬──(RX_DATA)──┤
#R1
Poll Flag 4
#R1.4
└─────(R)─────┤