User manual

Toolbox 32 User Manual 1.47d www.cse-semaphore.com/mykingfisher
Page
29
Protocol: The protocol that the RTU is able to use on the port. Protocols require a firmware driver* to be
loaded in the RTU and cannot be used with other protocols on the same port (with the exception of Modbus
and Kingfisher). The available protocols are:
• Series 2: Kingfisher Series 2 protocol. This is the default Protocol setting.
• ADS Data Logger: Device protocol.
• Allen Bradley: Allen Bradley PLC.
• ALERT: Radio reporting gauge.
• Alstrom Relay: Device protocol.
• ASCII No Parity: Device protocol.
• ASCII Even Parity: Device protocol. Same as above but with even parity.
• BCL ARC Device: Device protocol.
• Conitel: Device Protocol
• Cooper: Device protocol.
• DATAC: DATAC RTU.
• Datataker: Device protocol.
• Datran DT300: Device protocol.
• DNP-3: Please see the driver documentation from Semaphore.
• DV1000: Device protocol.
• Form 4C: Form 4C Reclosure.
• FUJI Micrex-F: Fuji Micrex-F PLC.
• FUJI NJ Series: Device protocol.
• GE CCM: Device protocol.
• GE SNP-X: Device protocol.
• GE T60 Relay: Device protocol.
• Genisys: Genisys train controller (slave).
• Genisys Master: Genisys master train controller.
• GPS: CP-21 GPS option board (superseded).
• GPS NMEA: NMEA 0183 ASCII protocol. For GPS devices connected to an RTU serial port. Eg. GM-66-
232 Mini GPS Locator.
• Hart: Device protocol.
• IDEC PLC: Device protocol.
• INLINE, INLINE2: Inline flow computer.
• INTRAC: Motorola INTRAC RTU.
• JZA Train Control: Device protocol.
• MAC-800: MAC 800 RTU.
• Mercury: Mercury flow computer.
• Microtran: Email Microtran RTU.
• Mier Transposer: Device protocol.
• Minitran: Email Minitran RTU.
• G&F Minitran: Gas and Fuel Minitran RTU.
• MTran Host: Minitran Host, South East Water.
• Mbus ASCII Init
#
: Modbus protocol for an MC-xx port only. Identical to Mbus init, S2 but uses ASCII
data format instead of Modbus RTU format.
• Mbus init, S2
#
: Modbus and Series 2 protocols. Allows the RTU to initiate Modbus messages using
ladder logic and to relay output messages in Modbus format.
• Mbus init&resp, S2
#
: For CPU ports only. Modbus and Series 2 protocols. Allows the RTU to initiate its
own Modbus messages using ladder logic and respond to Modbus messages from other devices. This
option should only be selected if two devices are connected using the Modbus protocol and both sides
will initiate messages.
• Mbus SCADA, S2
#
: Modbus master and Series 2 protocols. The RTU will respond to Modbus
messages that are for itself and for any other RTU. This option is used for the master RTU which stores
copies of the outstation RTU data. If data is requested from an outstation RTU, the RTU will respond