Physical Layer; C: Dnp Mapping - Electro Industries Shark 200 Installation & Operation Manual

C: DNP Mapping

C.1: Overview
This Appendix describes the functionality of the Shark® 200 meter's version of the
DNP protocol. A DNP programmer needs this information in order to retrieve data
from the Shark® 200 meter using this protocol. The Shark® 200 meter's version of
DNP is a reduced set of the Distributed Network Protocol Version 3.0 subset 2, with
enough functionality to get critical measurements from the Shark® 200 meter.
The Shark® 200 meter's DNP version supports Class 0 object/qualifiers 0,1,2,6, only.
No event generation is supported. The Shark® 200 meter always acts as a secondary
device (slave) in DNP communication.
An important feature allows DNP readings in primary units with user-set scaling for
current, Voltage, and power (see Chapter 8 in the Communicator EXT
MeterManager EXT Software User Manual for instructions).
C.2: Physical Layer
DNP uses both Network (TCP/IP) and serial communication. DNP3 serial communica-
tion can be assigned to Port 2 (RS485 compliant port) or any communication capable
option board. Serial Speed and data format are transparent for DNP: they can be set
to any supported value. The IrDA port cannot use DNP. DNP3 over Ethernet is sup-
ported along with Modbus via a DNP3-enabled Network card. DNP packets should be
directed to the port assigned for DNP during the meter's Device Profile configuration
(see Chapter 8 in the Communicator EXT
Manual for instructions). The DNP implementation is identical, regardless of the phys-
ical layer being used.
Electro Industries/GaugeTech
Electro Industries/GaugeTech
The Leader In Power Monitoring and Smart Grid Solutions
The Leader In Power Monitoring and Smart Grid Solutions
C: DNP Mapping
TM
4.0 and MeterManager EXT Software User
#
Doc E149701
TM
4.0 and
C-1