User manual

Toolbox 32 User Manual 1.47d www.cse-semaphore.com/mykingfisher
Page
30
with its own network data corresponding to that RTU. The local RTU will also relay Modbus output
messages in either Series 1, Series 2 or Modbus format. Modbus messages are relayed in Series 1
format to outstations that have a system ID of AC or in Series 2 format to outstations that have a system
ID of AE. Modbus messages are relayed in Modbus format if the port that the RTU relays the message
out of is configured as a Modbus initiating port. Note: after successfully relaying an output message, the
network register corresponding to the output will also be updated in the local RTU.
• Mbus slave, S2
#
: Modbus and Series 2 protocols. The RTU will respond to Modbus messages that are
for itself only.
• Mbus init&parity
#
: Identical to Mbus init, S2 but uses an even parity port setting and will not respond to
Series 2 messages.
• Mbus init&resp&par
#
: For CPU ports only. Identical to Mbus init&resp, S2 but uses an even parity port
setting and will not respond to Series 2 messages.
• Mbus SCADA&parity
#
: Identical to Mbus SCADA, S2 but uses an even parity port setting and will not
respond to Series 2 messages.
• Mbus slave&parity
#
: Identical to Mbus slave, S2 but uses an even parity port setting and will not
respond to Series 2 messages.
• Modem Sw Unit: Email Modem Switch Unit.
• Monitor WeatherStn: GLX data logger.
• Multitrode 2PC: Multitrode pump controller.
• NEC DCU: NEC PLC.
• OMRON: Omron PLC.
• PEEK: PEEK traffic light controller.
• Remote Data Logger: Protocol for Sagasco.
• S1 Ctrl, Mbus, S2
#
: Series 1 Controller, Modbus and Series 2 protocols. Identical to Mbus SCADA, S2
but will also respond as a Series 1 master RTU. Will also relay series 1 messages to RTUs that are in
the Network List.
• S1 Outstn, S2: Series 1 Outstation and Series 2 protocols. Will not relay series 1 messages for other
RTUs.
• S1 Ctrl, no CRC, S2: Original Series 1 Controller (for use with CPU1 modules) and Series 2 protocols.
Will relay series 1 messages to RTUs that are in the Network List.
• S1 Out, no CRC, S2: Original Series 1 Outstation (for use with CPU1 modules) and Series 2 protocols.
Will not relay series 1 messages for other RTUs.
• SER_SSPA: Device protocol.
• Shaft Encoder: Hohner Shaft Encoder.
• Simatic TI: Siemens Simatic 500 series PLCs..
• SM6615: Device protocol.
• STIC Gauge: Enraf STIC receiver.
• Tandberg: Digital receiver and decoder.
• Traffic Light Controller: Device protocol.
• TRIO Eseries: Trio E series radio interface.
• TS5000: TS5000 RTU.
• User-Defined: User defined protocol configured in ladder logic. When User-Defined is selected, another
configuration box will appear. The number of data bits (7 or 8), the parity (none, even or odd) and the
number of stop bits (1 or 2) can then be specified.
• YSI Logger: Device protocol.
Port Security: (Level 0 to 5) The security access level of each port. Port security is enabled by loading the
Security driver and configuring the port with a non-zero security level. Please see the appendix - RTU
Security for more information.
* All protocols except Series 2 require a special version of firmware or a firmware driver. Special versions of
firmware and firmware drivers are available from Semaphore. Standard firmware drivers are available from
www.cse-semaphore.com/mykingfisher. Some protocols will operate on both PC-1/CP-xx and MC ports
while other protocols operate on PC-1/CP-xx ports only or MC ports only as detailed in Protocols.pdf
available from www.cse-semaphore.com/mykingfisher.