Rockwell Automation T8xxx Trusted Communications Interface - Manual (Page 16)

Trusted
TM
Communication Interface T8151B
Issue 21 Apr 10 PD-T8151B 16
3. Application
3.1. Supported Protocols
3.1.1. Front Panel Serial Port
This port operates at 19200 baud on RS232. A command-line diagnostic protocol is available via this
port, accessed using a TC-304-01 maintenance cable and a terminal program. This protocol is not
affected by the Processor front panel keyswitch.
3.1.2. Rear Serial Ports
These ports may be configured between 1200 and 115200 baud. All four ports support RS485, port 1
supports RS232 with full handshaking and port 2 supports RS232 without handshaking. These ports
can be allocated as a Modbus RTU slave or master (Modbus Master requires a T8122 or T8123
Processor Interface Adaptor).
3.1.3. Ethernet Ports
These ports can each support multiple protocols simultaneously.
 Modbus RTU slave, packaged as a serial stream on Ethernet. This is appropriate for
conversion to serial Modbus at terminal servers or for the Trusted
TM OPC servers and
SOE/Process Historian collector. Up to ten connections can be made to Ethernet slaves, and
the port only needs to be allocated once. Port 2000 is used by default. The slave can either
actively make a connection (appropriate for some terminal servers) or wait for a connection.
 Open Modbus TCP, an Ethernet Modbus protocol designed by Modicon. This will automatically
operate if port 502 is selected. Only Modbus slave is available on this protocol.
 Modbus RTU Master, packaged as a serial stream on Ethernet. This is enabled by fitting a
T8122 or T8123 Processor Interface Adaptor. The Master only makes one connection, so it
may connect to one Ethernet-based slave or to one chain of slaves on a serial link via a
terminal server. Each communications interface can control up to 16 Modbus Masters,
communicating with up to 64 slaves total, with up to 400 messages total. Each master, slave
and message can be individually controlled and monitored, including statistical data. A Modbus
Master can also broadcast messages to some or all slaves simultaneously.
 SOE over Modbus protocol. A section of the Modbus address map is used as an event buffer
for SOE events (not Process Historian). This requires programming in the remote end to poll
the data block (with a Modbus Master) and interpret the events. This can provide a faster event
transfer than the protocol used by the OPC server and SOE collector.
 Toolset communications over Ethernet. A total of two Toolset connections may be made to the
system over Ethernet, one per communication interface (however it is advised to only connect
one Toolset, see TN20011). This uses port 6000 and uses proprietary protocols. There is no
need to configure this connection; it is available by default.
 Command line diagnostics protocol, as for the front panel serial port above. This uses port 23
and communicates with a Telnet program (e.g. Hyperterminal or Teraterm). This port is not
available by default (for security), and must be enabled via a diagnostic command. Two Telnet
connections may be made to the system for command line diagnostics.
 ‘Simplex’ peer to peer communications between Trusted
TM
systems, using sxp2p definitions.
This protocol uses port 4000 and is configured in the application. Refer to PD-8017 issue 6 for