![Funk-Electronic Piciorgros RTU-81 User Manual Download Page 74](http://html1.mh-extra.com/html/funk-electronic-piciorgros/rtu-81/rtu-81_user-manual_2346370074.webp)
Funk-Electronic Piciorgros GmbH
RTU-810
V2.30 - Page 74 of 126
3.5.1.5
Timeout values
There are two different timeout types which can force the outputs into the secure state
when the radio communication to the master breaks or if the RTU-810 is not being
polled anymore:
X-Timeout:
This applies only to data which is received on the radio frequency.
If this timeout is enabled, every radio telegram which belongs to the same radio
layer address and which can be decoded by the RTU-810 decrements the given
X-Timeout value by 1.
Every received radio telegram which is addressed to the RTU-810 itself will
reset the X-Timeout counter to the configured value.
The X-timeout will run off to 0 after the configured number of radio telegrams
from a master addressed to other devices were seen by the RTU-810 on the radio
channel without the RTU-810 itself being polled.
T-Timeout:
The T-Timeout is set to the configured value at the RTU-810's start
and each time the RTU-810 is accessed by a master, regardless which protocol
the access is using (DNP3, IEC-60870, MODBUS) and regardless of the
interface which was used (radio, GSM, Ethernet, serial interface).
Otherwise it's decremented by 1 each second.
The T-Timeout will run off to 0 when the RTU-810 was not polled in any way
within the given number of seconds.
X-Timeout
The On/Off switch enables or disables the use of this timeout.
The number of telegram receive cycles from which it's counting down is
given in the number field.
T-Timeout
The On/Off switch enables or disables the use of this timeout.
The number of seconds from which it's counting down is given in the
number field.
Notes:
A running PicoLogo application which accesses the I/O of the RTU-810 will
periodically reload the X- and T-Timeout values! They will not run off in this
case
A MDP-310.200 or RTU-810 polling the device in RTU master mode will
configure the X-Timeout and T-Timeout centrally. The locally configured values
will be overwritten.
When any of these timeouts is enabled and runs off, all outputs are forced to the
secure OFF state.