Communication Card Part Number Options - ABB TPU2000 Technical Manual

TPU2000/2000R Modbus/Modbus Plus Automation Guide
CAUTION: Sensitive electronic components are contained within the TPU2000 and TPU2000R units. The
individual removing the component boards from the fixed chassis must be grounded to the same
potential as the unit. IF THE OPERATOR AND THE CASE ARE NOT CONNECTED TO THE SAME GROUND
POTENTIAL, STATIC ELECTRICITY MAY BE CONDUCTED FROM THE OPERATOR TO THE INTERNAL
COMPONENTS RESULTING IN DAMAGE TO THE UNIT.

Communication Card Part Number Options

The TPU2000 and TPU2000R may be ordered with a variety of communication options as listed in Table 2-1.
The communication option card installed in the unit is identified by the part number located on the unit or identified
through the ECP, WinECP or Front Panel (LCD) interfaces.
The protocols available are:
STANDARD TEN BYTE – This is an ABB specific ASCII encoded (asynchronous) 10 byte
communication protocol. It allows attainment of all relay parameters. It is the base unit protocol in which
configuration programs such as ECP, and WinECP communicate to the TPU2000 or TPU2000R. It is
the protocol standard for the COM 0 communication port of the TPU2000 and TPU2000R. Standard 10
Byte does not utilize a proprietary hardware physical interface. Appendix A includes the TPU2000 and
TPU2000R Standard 10 Byte Protocol Document.
INCOM – This is an ABB Specific bit oriented (synchronous) protocol. INCOM uses the same
commands as Standard Ten Byte, but its inherent bandwidth utilization is far greater than Standard Ten
Byte is in that no data encoding is required. INCOM only defined two baud rates 9600 and 1200.
INCOM is a proprietary interface in that its physical presentation to the communication medium is
dependent upon the baud rate selected. 1200 Baud uses current injection baseband signal
presentation, whereas 9600-Baud implements a phase shift frequency in its representation of digital 1
and 0 values. Appendix A includes the TPU2000 and TPU2000R Standard Ten Byte Protocol
document which describes INCOM in further detail.
DNP 3.0 – This is a Utility industry standard protocol allowing communication between a host and
slave devices. DNP 3.0 is a byte oriented (asynchronous) protocol which is physical interface device
independent. The protocol allows for time synchronization, and unsolicited event reporting. It is a very
popular protocol in utility installations. The discussion of DNP 3.0 protocol is included in this document.
SPACOM – This is an ABB Specific byte oriented (asynchronous) protocol common in Europe. It is a
Master-Slave protocol which is implemented on a variety of physical interfaces. SPACOM protocol is
not covered within this document.
SERIAL MODBUS – This is an Industrial standard. The protocol allows a single master device to
communicate with several slave devices. It has gained wide acceptance in that a great majority of utility
devices incorporate Modbus protocol. Modbus Protocol is physical interface independent. Modbus
Protocol has two emulation's RTU (a synchronous bit oriented emulation) and ASCII (an asynchronous
byte oriented emulation). The TPU2000 and TPU2000R may be configured for both emulations. The
discussion of Modbus protocol is included in this document. Please reference the TPU2000 and
TPU2000R Modbus/Modbus Plus Automation Technical Guide TG 7.11.1.7-51 for a discussion of this
protocol.
TCP/IP MODBUS is an evolution of Serial Modbus in that it uses Ethernet as the mechanism to
transfer the Modbus Serial packets across an Ethernet LAN. It is gaining in popularity in that several
protocols and network transmissions may peaceably coexist on a single network cable. Network
Modbus (or TCP/IP Modbus) has its own protocol conventions and is not merely initiation of an
Ethernet TELNET session over the Local Area Network (LAN) (AVAILABLE ON THE TPU2000R
ONLY 2 Winding Unit ).
MODBUS PLUS – This protocol is also and industrial standard. Modbus Plus allows up to 64 devices
to communicate on a single network using token passing techniques. 5 networks may be bridged
(interconnected) to form a larger Modbus Plus network. The Modbus Plus protocol is fast (1 megabaud)
and uses several advanced techniques to maximize bandwidth. The physical interface to Modbus Plus
is proprietary and regulated by Groupe Schneider. Modbus Plus is the incorporation of Modbus
6