User manual

Toolbox 32 User Manual 1.47d www.cse-semaphore.com/mykingfisher
Page
42
System ID: This is the communications sync character used at the start of outgoing Kingfisher messages.
An RTU will only respond to Kingfisher messages that begin with the same System ID as the RTU's own
system ID (as configured in Configuration, System Parameters) or that begin with AE (Hexadecimal). System
ID is not used by other protocols.
Default system IDs for Kingfisher messages are as follows:
• AE - Default for Series 2 RTUs. It is recommended that AE be used for all Series 2 RTUs except Store
and Forward RTUs as illustrated below.
• AC - Series 1 CPU3 or Series 1 CPU1 with version 3 EPROM
• A5 - Series 1 CPU1 with version 2 or prior EPROM
A Series 2 RTU knows it is communicating with a Series 1 RTU whenever a system ID of AC or A5 is used.
When a Series 2 RTU receives a Modbus output command for a Series 1 outstation, it will convert the
message into Series 1 format. Note: A Series 2 RTU will not convert Citect Kingfisher driver outputs into
Series 1 format for Series 1 outstation RTUs.
To prevent both RTU2 and RTU3 responding at the same time, RTU2 and RTU3 are configured with unique
system IDs as shown below. RTU1 sends the indirect message to RTU2 with a System ID of A1. RTU3 will
only respond to messages with a system ID of A2 and so ignores the message. When RTU2 forwards the
message to RTU3, the message is sent with a System ID of A2. RTU3 then responds to the message.
Note: System IDs 00 and FF are reserved and should not be used.
Target RTU System ID Route
RTU1
RTU3
RTU2
System ID=A1
System ID=A
2
System ID=AE
Target RTU System ID Route
Port 4
Target RTU System ID Route
1
AE
Indirect via RTU 2
Port 5
Port 6
Weak radio signal
Strong radio signal
Strong radio signal
2
A
1
Direct via Port 6
2 A1 Direct via Port 4
3 A2 Indirect via RTU 2
1 AE Direct via Port 5
3
A
2
Direct via Port 5
Direct/Indirect: Direct means the RTU is directly connected to the target RTU (eg. via a private line or radio
link). Indirect means the RTU must communicate via one or more other RTUs (called store-and-forward
RTUs) to access the target RTU. When an RTU hears a message that is not for itself, it will store and
forward (or relay) the message to the destination RTU if it has a network link to that destination RTU.
Port # / Via RTU #: For a Direct connection, this is the local port number (as configured in the Port List) to be
used to communicate with the target RTU. For an Indirect connection, this is the directly-connected RTU
address via which the message must be sent to reach the target RTU.
Message Retries: The number of times the RTU will retry sending a message to the target RTU if the
previous attempts have failed. The maximum number of attempts is one more than the Message Retries
setting.