Comparison of DNP 3.

0, IEC 870-5-101 and Modbus

The following tables list the detail of the analysis.

Table - 1 provides comparison depending on the various features of the protocols.

Table - 2 presents information on functions and/or messages, which are applicable to the
IED/RTU communication functions for DNP 3.0 and IEC 870-5-101, using a common name to
relate similar operations in each of the implementations.

Table - 3 gives information on function as available in Modbus protocol.

Table 1 - Comparison of DNP 3.0, IEC 870-5-101 and Modbus [ref. 1, 9 & 11]

Feature IEC 870-5-101 DNP 3.0 Modbus

Standardization IEC Standard (1995) Open industry Not Applicable

Amendments 2000,2001 specification (1993)

Standardization IEC TC 57 WG 03 DNP user s group Modicon Inc.

Organization

Architecture 3-layer EPA architecture 4-layer architecture Application layer

Also supports 7 layer messaging protocol
TCP/IP or UDP/IP

Physical layer Balanced Mode Balanced mode Balanced mode of

Point to Point transmission transmission
Multipoint to point
Implementation by X.24 It supports multiple RS 232 serial interface
/ X.27 standard masters, multiple slave implementation
and peer-to-peer
Unbalanced Mode communication Peer to peer
Point to Point communication
Point to Multipoint RS 232 or RS 485
Implementation by V.24 implementation TCP/IP over Ethernet
/ V.28 standard
TCP/IP over Ethernet,
802.3 or X.21

Data link layer Frame format FT 1.2 Frame format FT3 Two types of message
Hamming distance 4 Hamming distance-6 frames are used:

1
 Feature IEC 870-5-101 DNP 3.0 Modbus
ASCII mode and
RTU mode

Application layer Both IEC 870-5-101 and Remote starting / Does not give time
DNP 3.0 provides stopping of software stamped events. We
Time applications have sequence of
synchronization events (without time but
Time stamped Polling by data priority not event list with time.
events level
Select before Does not provide polled
operate Broadcast addressing report by exception
Polled report by
exception Multiple data types per Checksum ensures
Unsolicited message are allowed proper end-to-end
responses communication
Data Internal Indication field
group/classes IID present in response
header
Limited to single data
type per message Application layer
confirms events; use of
Can control one point CON bit is made
per message only

No internal indication
bits

No application layer
confirms for events

Device Addressing Link address could be 0, Link contains both Addresses field contains
1, 2 bytes source and destination two characters (ASCII
address (both always 16 mode) or 8 bits (RTU
Unbalanced link bits) mode)
contains slave address
Application layer does Valid address in range
Balanced link is point to not contains address 1-247
point so link address is
optional (may be 32 b point addresses of
included for security) each data type per Address 0 used for
device broadcast

Configuration Baud rate Baud rate Baud rate

Parameters
required Device addresses Device addresses Mode ASCII or RTU

Balanced / unbalanced Fragment size Parity mode

Frame length

Size of link address

Size of ASDU address

Size/structure of point
number

2
 Feature IEC 870-5-101 DNP 3.0 Modbus

Configuration Size of cause of

Parameters transmission
required contd...

Application A few application Permits vendors to Allows user to create

Specific specific data types create application application specific
information model available specific extensions model

Data objects and Data objects and

messages are not messages independent
independent to each to each other
other

Cyclic Eliminates static data Available but interval Not Applicable

transmission poll message from cannot be remotely
master adjusted

Interrupted by event
triggered communication
request

Dominant market Europe (South America, North America Used worldwide for
Australia and china) (Australia and china) application with low
volume data

Online Enable/ disable Define group of data Efficient online

configurations communication control configuration could be
objects Selecting data for made by Modbus
responding TCP/IP
Loading configuration
Enable/ disable
Change report / logging communication control
behavior objects

Loading configuration

Change report / logging

behavior

Open for other Not Available Yes open for other Yes. One could write
encoding solutions encoding solutions like source code in
XML programming languages
like C, VC++ & JAVA
etc.

3
S.o.E:

The RTU shall support Sequence of Events (SoE) inputs. A single point may be both status and SoE.
SoE shall be time-stamped to a resolution of 20 millisecond within the RTU. The RTU shall allow SoE to
be activated and deactivated on an RTU basis or on a point basis using a command message. The
RTU shall set a flag in the return message of any communication from the Control Centre indicating
there is SoE data. A flag shall also be set to indicate to the Control Centre that the buffer is 80 %
full. The buffer size shall be no less than three (3) times the buffer required for total
SoE in the RTU.

The Control Centre shall request SoE data. SoE data shall not be deleted unless directed to do so by
the Control Centre. SoE data, if not specifically deleted, shall be overwritten when the buffer is full with
the oldest data being overwritten. The RTU shall have a retransmit capability of all SoE data currently in
memory if it is commanded. The event shall contain the point ID, the point current state and the
time of the state change. SoE shall have electronic filtering on each point to discriminate false
indications. The time tag shall be the time of the first valid detected
closure.

Note:
THE VENDOR SHOULD SUBMIT PROOF OF RTU CERTIFICATION (AS CONFORMING TO 104
PROTOCOL) BY KEMA
.