Ovation

Data Link Server Interface to

DNP 3.0
Data Sheet




Emerson Process Management Power & Water Solutions. All rights reserved. Page - 1
OV-SYS-XX-136 [1] Proprietary



Features
Installed on a Windows

-based Ovation station

to support communication with remote devices
and stations.
Backwards compatible with all versions of
Ovation to provide interface capabilities with
existing Ovation installations.
Supports a variety of communication protocols
including both DNP Client and DNP Server.



DNP 3.0 provides open, standards-based
interconnectivity between substation computers,
remote terminal units, intelligent devices, and
master stations. Through our Data Link Server
software package, the Ovation

expert control
system offers seamless communicate between
the plant DCS and your DNP 3.0 client or server.

The Data Link Server software package consists
of a configuration tool graphical user interface
(GUI), the DLS Manager service, and the
standalone license manager. The installation
utility gives the user the option of installing the
configuration tool, the DLS Manager service, or
both. The DLS Manager runs the communication
drivers. The configuration tool provides
debugging and monitoring capabilities. The DLS
Manager requires a license but the configuration
tool does not.

The DLS package can be installed on any type
of Ovation station. It can be installed on an
existing operator station to provide
communication capabilities without the addition
of hardware. It can also be installed on a pair of
redundant base stations in an enclosure to
provide more secure communication.

The Data Link Server supports both
asynchronous serial communication and
Ethernet TCP/IP socket communication. A
terminal server is used to provide additional
serial ports for the Ovation station.

The data link configuration consists of a
hierarchy of objects. These objects include:
server drop, communication line, remote device,
scan block, and process point. The server drop
is the Ovation station running the Data Link
Server. The communication line defines the
communication protocol and the ports. The
remote device configuration objects contain the
address and type of each device. The scan
block defines the operation (read or write) and
the frequency of communication. The process
point object maps a remote register with an
Ovation process point. A DNP client line is used
to communicate with DNP servers. A DNP RTU
Simulator line is used to make the Ovation
station appear as a DNP Server to a remote
DNP client.
Client Line
The DNP line supports the DNP 3.0 Level 2
protocol. The client can accept most qualifiers
and variation in the server responses. It
supports the functions: read, write, read class 0
(static), read class 1 (event), read date and time.
Supported object types are: 1, 2, 10, 20, 22, 30,
32, 40 and 50.
Ovation

Data Link Server Interface to DNP 3.0
Data Sheet




Emerson Process Management Power & Water Solutions. All rights reserved. Page - 2
OV-SYS-XX-136 [1] Proprietary
RTU Simulation Line
The DNP RTU Simulation Line supports the
DNP 3.0 Server Level 2 protocol. This DNP
V3.00 server driver is based on the Protocol
Translator software package.

An Ovation process point is assigned a DNP
data object type (analog input =30) and an
index number by the configuration tool. The
driver fills any gaps in the list of indices for an
object in with dummy objects. This allows points
to be added and deleted without changing index
numbers. The server responds to a Class 0 poll
by returning the current value and status of all
objects. The server responds to a Class 1 poll
by returning the event queue for objects 2, 22,
and 32. The event queue data includes a
timestamp for each value. A point's value is
stored in the event queue if its value exceeds
the configured deadband. A deadband of -1
disables the event check.

The server does not make a distinction between
object types 1 and 2, 20 and 22, and 30 and 32
in Class 0 polls. Index numbers cannot be
shared between these types. For example, if
data object 22:5 is defined the server will return
its current value in a Class 0 poll but it will be
labeled 20:5.
Time Stamping
Some requests, such as the DNP Class 1 poll,
return timestamped data. The returned
timestamps can be stored to the eDB enterprise
historian through the use of deluxe points.
Deluxe points are broadcast to the Ovation
highway with a timestamp along with a value
and status.

If the returned value is mapped to a deluxe
point, and if the timestamped configuration flag
is set, then the DLS will write the returned value,
status and timestamp to the mapped point.

The eDB scanner must be configured to so that
it reads the deluxe point's timestamp rather than
the highway timestamp.

It takes the Data Link Server about two seconds
to store a value for a deluxe point. It must give
the OPP time to broadcast the point and it must
give the eDB scanner time to see the change.
This means that the event data cannot change
rapidly for a long period of time.
Point Status
Some remote devices such as DNP Servers
return a status along with a data object value.
This status is used to set the quality of the
mapped process point. Only point quality (good
or bad) is set by the Data Link Server. Other
status bits, such as high alarm and timed out,
are set by the originating Ovation station.

Specifications
Object ID Function Variation Qualifier
1 binary input Read 0, 1, 2 0, 1
2 binary input change Class 1 poll
10 binary output Read 0, 1, 2 0, 1
10 binary output Write 1, 2 0, 1
20 binary counter Read 0, 1, 2, 5, 6 0, 1
22 counter change event Class 1 poll
30 analog input Read 0, 1, 2, 3, 4 0, 1
32 analog input change Class 1 poll
40 analog output Read 0, 1, 2 0, 1
40 analog output Write 1, 2 0, 1