User manual

Toolbox 32 User Manual 1.47d www.cse-semaphore.com/mykingfisher
Page
20
RTU Type: The type of processor used by the RTU: CP-1, PC-1, CP-10/11, CP-21, SBX, ERS Micro, LP-
1/2/3, SB-1, Micro-4 or Other. This setting allows Toolbox to compile ladder logic in the correct format (for
each microprocessor type). Note a CP-30 or G30 is configured using Toolbox PLUS+ software.
I/O Scan Interval: The period (in milliseconds) at which the RTU scans all its IO modules and processes
ladder logic (default = 100 ms). By increasing the I/O Scan Interval, more time is left over for the RTU to
respond to incoming messages on communication ports. Set I/O Scan Interval to 10 ms or less if wanting to
use Timer blocks and count in 100ths of a second (provided that the RTU is capable of scanning that fast).
Note: a zero I/O Scan Interval will cause the RTU to scan as fast as possible and cause a Scan Overrun
system flag to appear in the RTU Status. Scan Overrun means that the RTU cannot process all the IO and
ladder at the configured interval.
System ID: (Default = AE Hex) The communications sync character used to screen incoming Kingfisher
messages. An RTU will only respond to Kingfisher messages that have the same sync character as this
System ID or that begin with AE (Hexadecimal). It is recommended that a system ID of AE is used except
when configuring a store-and-forward RTU as detailed in the topic Configuration - Network List, System ID.
System ID is not used by other protocols.
RTU Status Register: Blank or a local register (#R). If a local register is entered, the RTU system status
register (#YSTAT) will be continuously copied into this register even if ladder logic is disabled. This option
makes it possible to monitor the RTU status and alarm if the IO Processing and/or Logic Processing is
disabled or corrupted.
DNP Base Register: (#R) A local register defining the beginning of a block of 64 registers (Semaphore uses
#R129 by default). All the DNP3 parameters are defined in these registers by using ladder logic. The
definition of each register in the 32-register block is available from Semaphore by request.
Comms Priority: (0, 1 or 2) Comms Priority defines how often the RTU tries sending messages after a
communications failure. A Comms Priority of 0 is used by default. The Message Retries parameter
mentioned below is configured for each RTU in Configuration - Network List.
• Priority 0: Each message will have up to Message Retries or until it is successful. The Global Retries
field is ignored.
• Priority 1: Each Message will have up to Message Retries or the amount specified in the Global Retries
field (whichever is less). Once communications to an RTU have failed more than the Global Retries
setting, the next messages will only be sent once until a successful message is received from that RTU.
• Priority 2: Each Message will have up to Message Retries or the amount specified in the Global Retries
field (whichever is less). Once communications to an RTU have failed more than the Global Retries
setting, no more messages will be sent to that RTU until a successful message is received from that
RTU.
Global Retries: The total number of consecutive communication attempt failures for any RTU site before
action is taken. This field is only used when a Comms Priority of 1 or 2 is configured (please see above).
Eg. After 10 communication fails in a row to RTU2, RTU1 will then only have one attempt at each new
message to RTU2. RTU2 will continue to have up to 3 retries at each new message to RTU1. The
global retries setting for each RTU will be:
Master RTU1 Remote RTU2
Priority=1
Global Retries=10
Network List
RTU2 Message Retries=3
Priority=0
Global Retries=0
Network List
RTU1 Message Retries=3