Introduction; Functional Overview; Dnp Lan Slave Opc Client Features - ABB COM600 User Manual

1MRS755496
2.
2.1.
2.2.
Station Automation COM600 3.4
DNP 3.0 LAN/WAN Slave (OPC) User's Manual

Introduction

Functional overview

The DNP protocol slave interface of COM600 enables master systems communicating
with DNP protocol to receive data from and deliver commands to P&C devices connected
to the GW. The DNP slave is implemented as an OPC client, which transfers and converts
data between the DNP slave protocol interface and the OPC servers of COM600. See
COM600 User's Manual for more details.
The DNP LAN Slave OPC Client is configured using SAB600. SAB600 can also be
used for diagnosing and controlling the operation of the DNP LAN Slave OPC Client.
COM600 has a web server that can be used for remote diagnostic of the Gateway
including the DNP LAN Slave OPC Client.
The DNP LAN Slave OPC Client uses TCP/IP communication over the LAN interface.
Before you can start using the DNP LAN Slave OPC Client, configure at least one OPC
server to provide access to the process devices. In this user's manual, the term "DNP
LAN IED" is used for a virtual station in COM600 representing the slave stations visible
to the DNP master system.

DNP LAN Slave OPC Client features

The DNP LAN Slave OPC Client supports the following features:
• OPC Data Access Client v. 1.0/2.0 for accessing data from the OPC servers
•
OPC Alarms and Events specifications v. 1.10 for diagnostic and control purposes
•
IEC 61850 data modeling
•
System supervision:
• NCC connection supervision
• DNP 3.0 subset level 2 and level 3 support.
13