intek hybrid opc server v3.1.0 hybrid opc... · 2007-03-20 · p age 1 of 84 intek hybrid opc...

P age 1 of 84

InTek Hybrid OPC Server – User’s Guide

InTek Hybrid OPC Server User’s Guide Version 3.1.0.1

September, 2004

InTekTM

P age 2 of 84


Integra Teknik Asia, PT

Kawasan KaliMas C.3 Bekasi Timur 17113 Indonesia Phone : (62-21) 8835-3922 Fax : (62-21) 8835-3933

http://www.integrateknik.com CONFIDENTIAL

The information contained herein is confidential and proprietary to Integra Teknik Asia PT. It may not be disclosed or transferred, directly or indirectly, to any third party without the explicit written permission of Integra Teknik Asia PT.

All rights reserved. No part of this document may be reproduced, stored in a retrieval system, translated, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without prior written permission of Integra Teknik Asia PT.

© Copyright 2003 Integra Teknik Asia PT


P age 3 of 84


Integra Teknik Asia, PT.............................................................................................................. 2

I. INTRODUCTION................................................................................................................... 6

I.1. Special InTek™ Hybrid OPC Server Features............................................................. 7

I.2. System Requirements ................................................................................................... 9

I.3. About this Manual ...................................................................................................... 10

I.4. Your InTek Hybrid OPC Server License ................................................................... 10

I.5. Technical Support....................................................................................................... 11

II. OVERVIEW...................................................................................................................... 12

II.1. Menu Bar .................................................................................................................... 13

II.1.1. File .................................................................................................................. 13

II.1.2. Edit.................................................................................................................. 16

II.1.3. View................................................................................................................ 16

II.1.4. Server............................................................................................................ 17

II.1.4. Help .............................................................................................................. 18

II.2. Toolbar ...................................................................................................................... 18

II.3. Poll Window.............................................................................................................. 19

CONFIGURATION ................................................................................................................. 21

III.1. Create a New Polling Database File ......................................................................... 21

III.1.1. Define a Channel ............................................................................................ 21

III.1.2. Configure the Com Port.................................................................................. 23

III.1.3. Define a Device .............................................................................................. 25

III.1.4. Copy Device ................................................................................................... 26

III.1.5. Define a Tag ................................................................................................... 26

III.1.6. Configure the User Admin ............................................................................. 26

III.1.7. Saving the File ................................................................................................ 28

TABLE OF CONTENTS

P age 4 of 84


III.2. Hot Standby Redundancy ......................................................................................... 29

III.2.1. Add new UDP Port ......................................................................................... 31

III.2.2. Primary OPC Server ....................................................................................... 32

III.2.2. Standby OPC Server ....................................................................................... 33

III.3. Start the OPC Server................................................................................................. 34

Appendix A Internal Tag.......................................................................................................... 35

Appendix B Modbus Protocol .................................................................................................. 37

B.1. Define a Device ......................................................................................................... 38

B.2. Define a Tag............................................................................................................... 41

Appendix C IEC 60870-5-101 Protocol ................................................................................... 43

C.1. Define a Device ......................................................................................................... 44

C.2. Define a Tag............................................................................................................... 46

C.3. Interoperability IEC 60870-5-101 Document............................................................ 48

Appendix D IEC60870-5-103 Protocol .................................................................................... 52

D.1. Define a Device ......................................................................................................... 53

D.2. Define a Tag .............................................................................................................. 56

D.3. Dump Disturbance Log.............................................................................................. 57

D.4. Interoperability IEC 60870-5-103 Document............................................................ 60

Appendix E IEC 60870-5-104 Protocol ................................................................................... 65

E.1. Define a Device.......................................................................................................... 65

E.2. Define a Tag............................................................................................................... 66

Appendix F DNP 3.0 Protocol.................................................................................................. 67

F.1. Define a Device .......................................................................................................... 67

F.2. Define a Tag ............................................................................................................... 69

F.3. Interoperability DNP 3.0 Document .......................................................................... 71

P age 5 of 84


Appendix G SPABus ................................................................................................................ 75

G.1. Define a Device ......................................................................................................... 75

G.2. Define a Tag .............................................................................................................. 79

Appendix H Modbus Slave....................................................................................................... 79

H.1. Define a Slave Device and Device Mirroring............................................................ 79

H.2. Define a Tag .............................................................................................................. 81

Index ......................................................................................................................................... 83

P age 6 of 84


I. INTRODUCTION

OLE for Process Control (OPC™) is a new technology designed to bridge Windows based

applications and process control hardware. It is an open standard that permits a consistent

method of accessing field data from plant floor devices. This method remains the same

regardless of the type and source of data.

OPC servers provide a method for many different software packages to access data from a

process control device. Traditionally, any time a package needed access to a device’s data, a

custom interface, or driver, needed to be written. The purpose of OPC is to define a common

interface that is written once, and then reused by any business, SCADA, MMI, or customs

software packages.

The InTek Hybrid OPC Server follows the requirements of the OPC specification to provide

access to Intelligent Electronic Device (IED) data to any OPC client. This server implements

version 1.0 of the OPC custom interface.

InTek Hybrid OPC Server is a new technology OPC product which designed to run multi-

protocol over single serial communication port/channel. This technology is the first OPC

Server product in the world as far as we know until the releasing of this product.

There are many serial protocols that currently supported by InTek™ Hybrid OPC Server and

all of them (or combination of several protocols) could be set to run on single serial port, such

as single Radio channel, one Power Line Carrier channel, etc. The list of serial protocols is

defined in section I.1.

Beside the above technology InTek Hybrid OPC Server also have feature which the other

OPC server don’t have, that is pre-define devices template. These facilities for devices

template (pre-define devices with all of its tags) allow the user to just select that Device

without any requirement to define any tags further.

Unlike many other OPC servers in the world, the InTek Hybrid OPC Server requires very

easy configuration to make communication to all of kind protocol which supported by this

server. There are many more features of InTek Hybrid OPC Server, all of that features will

describe in section I.1.

I. INTRODUCTION

P age 7 of 84


Contents:

Special InTek Hybrid OPC Server Features

System Requirements

About this manual

Your InTek Hybrid OPC Server License

Technical Support

I.1. Special InTek™ Hybrid OPC Server Features

InTek Hybrid OPC Server includes the following special features:

Multi-protocol over single serial communication port/channel

The serial protocols that currently supported by InTek Hybrid OPC Server are:

IEC 60870-5-101

IEC 60870-5-103

IEC 60870-5-104

DNP 3.0

Modbus RTU / Jbus

Modbus TCP

Modbus ASCII

ABB SPAbus

EDF HNZ (multi versions)

KIM-LIPI Micromint

(Please contact us to find the latest protocols list that we have supported)

Pre-defined device/register template

Facilities for devices template (pre-define devices with all of its tags) allow the

user to just select that Device without any requirement to define any tags further.

Also, the template will include direct collection of the historical log within the

device, and the collection could be triggered by a point change and/or periodic

P age 8 of 84


regular base. The acquired history log will be directly presented as interpreted

data on CSV/text file, or any other required file format.

With this template capability, build-up OPC Server database could be done less

than one hour to define hundreds of Devices (that already has a template

database).

Currently, InTek Hybrid OPC Server already has a built-in Database/Tags

Template and Historical collection for the following IED (Intelligent Electronic

Device):

Keltronics ESP (Electrical Submersible Pump) Controller

Vortex ESP (Electrical Submersible Pump) Controller

CTI ESP (Electrical Submersible Pump) Controller

PML ION-7700 and ION-6200 series Power Monitor

HC 6xxx series Power Monitor

Schneider MG Sepam 2000

Siemens Siprotec series Protection Relay

ABB SPA series Protection Relay

(Please contact us to find the latest IED devices list that we have supported)

For non-RBE (report-by-exception) protocol, such as Modbus, InTek Hybrid

OPC Server has a special feature such as :

Real-Time Poll

Periodic Poll

On-Demand Poll - drive by OPC Client

With the facilities to arrange the polling group, user could select and achieve the

most efficient polling cycle rate as per their system requirement, for example :

just select the most important data to be poll as real-time

assign the regular data to be polled periodically (e.g. 5 minutes, 15 minutes,

hourly, three times a day, daily, etc.)

perform on-demand poll whenever they required for any data/tag

P age 9 of 84


The InTek Hybrid OPC Server also featured with communication analyst, such

as :

1. Real-time protocol raw-data display and interpretation

2. Data communication log

3. Communication statistic

4. Latest raw protocol messages stored as ten (10) roll-over file per channel

5. Event / COS log automatically within plain text file.

Support time synchronization and timestamp from controller for the following

protocols.

- DNP 3.0 - IEC 103

- IEC 101 - IEC 104

With this feature OPC Client will get real values and timestamp from RTU/IED.

Our InTek Hybrid OPC Server has been tested to interface with the following

OPC Clients :

Wonderware InTouch 7.x via Wonderware OPClink

Citect 5.x via Citect OPC Client I/O Driver

DeltaV 5.x via DeltaV OPC Mirror and Matrikon Data Manager

Matrikon OPC Explore

Siemens OPC Scout

Siemens Spectrum PowerCC v3.1

I.2. System Requirements

To run InTek Hybrid OPC Server, we recommend the following hardware and

software:

1. PC with a Pentium II – 450 MHz processor or higher.

2. At least 100MB of free hard disk space.

3. At least 64 MB of Random Access Memory (RAM).

4. Microsoft Windows 2000 Server or Microsoft Windows 2000 Professional

operating systems.

P age 10 of 84


I.3. About this Manual

This manual is divided into a series of logical building block chapters that describe

the various aspects of configure InTek Hybrid OPC Server. It is written in a

"procedural" format that tells you in numbered steps how to perform most functions

or tasks.

For details on the runtime environment, see your InTek Hybrid OPC Server User’s

Guide.

For details how to configuration device and tag for the specific protocol, see

Appendix in this book.

I.4. Your InTek Hybrid OPC Server License

InTek Hybrid OPC Server needs one file license before the system application

running. The name of this file “ITAOPCMaster.key”, this file is saving under

directory which InTek Hybrid OPC Server is installed.

This file can not use by another computer; this file is made only for specific

computer. If you want change the place your InTek Hybrid OPC Server or you want

use several computer, you must contact us to get your new license file.

P age 11 of 84


I.5. Technical Support

InTek Technical Support offers a variety of support options to answer any questions

on InTek products and their implementation.

Prior to contacting technical support, please refer to the relevant chapter(s) in your

InTek Hybrid OPC Server User’s Guide for a possible solution to any problem you

may have with your InTek Hybrid OPC Server program. If you find it necessary to

contact technical support for assistance, please have the following information

available:

1. The version of InTek OPC Server you are running.

2. The type and version of the operating system you are using. For Example,

Microsoft Windows 2000 Professional Service Pack 1.

3. The exact wording of system error messages encountered.

4. Details of the attempts you made to solve the problem(s) and your results.

5. Details of how to recreate the problem.

You can send to us via email all of your question or problem include the above

information at [email protected].

P age 12 of 84


II. OVERVIEW

These sections describe all of functionality in InTek Hybrid OPC Server like Menu, Toolbar,

Windows, etc. The main window of InTek Hybrid OPC Server appear in below picture, as

you can see this program is so simple and everyone can operate it without have any special

knowledge. All of communications activities between OPC Server and the Devices are appear

in this window.

II. OVERVIEW

1

3

67

2 5

8

4

P age 13 of 84


Menu Bar

Toolbar

List of Channel and Device

Devices

Poll Window

Poll Status Devices

Polling Cycle

Status Bar

II.1. Menu Bar

A menu displays a list of commands to operate the OPC Server. There are 4 sub menus in

this program. Following will be describing functionality the commands in that entire sub

menu.

II.1.1. File

1. New

This command is used to make a new polling device database.

2. Open

This command is used to open polling device database file this file have

extension .itk.

3. Save

After you made a new file or you make a change in any file polling

database you must save it using this command.

4. Save As

If you want saving your file polling database into other file you can use

this command. The polling database file has extension .itk

1

2

3

4

5

7

6

8

P age 14 of 84


5. Login

You must Login for the first matter you must to do to operate this OPC

Server. When you click the Login command, the following panel will

appear you must fill up the text box appropriate you’re Username and the

password.

You must Login As ‘Administrator’ with password ‘administrator’ when

you use the OPC Server for the first time. The OPC Server will be

recording your entire configuration changed in polling database file. This

recorded will be store in ACTIVITYLOG.log file which saved in the

InTek Hybrid OPC Server Log directory.

6. Logout

This command is used if you want logout.

7. Change Password

This command is used to change your password. When you click this

command, the following panel will appear, fill up your new password

twice.

P age 15 of 84


8. User Admin

This command is used to add a new user or edit any user except

Administrator and Dispatcher. Only the Administrator can use this

command. The following panel will appear when you want add new user

or edit any user in security database program.

Auto Logout time have function to none activate the active user

appropriate the time you fill up in text box. The configuration for this

panel and the others panel will be described in Configuration section.

9. Com Ports

This command is used to add new com port or change the com port

configuration in your computer. How to configure this panel will be

describe in Configuration section.

10. Dump Stats

This command is used to extract communication statistic between listed

devices and OPC Server. This command make a new file with name

Stats.txt where saved in the same directory with InTek Hybrid OPC

Server. This command is not available on this version.

P age 16 of 84


11. Exit

This command is used to close the application, before you close the

application you must stop the scanner (How to start and stop the scanner will

be describe in Configuration section).

II.1.2. Edit

The commands in this sub menu have main function to configured the polling

database file, the following will be described that command one by one. In

Configuration section will be described how to use each that command.

1. Delete, is used to delete the channel, device, group and tag.

2. New Channel is used to make a new channel.

3. New Device is used to make a new device.

4. New Group is used to make a new group.

5. New Tag, is used to make a new tag

6. Properties, is used to see property of channel, device, group and tag.

II.1.3. View

The commands in this sub menu are used only for enable or disable viewing

Toolbar and Status bar.

P age 17 of 84


II.1.4. Server

The commands in this sub menu have main functionality to operate the Server, all of that

are described below:

1. Properties, when you click this command the following panel will appear

The following table described the setting found in this panel:

Setting Description

Log Directory Enter the path directory for your Communication Log Directory

Log Auto-Stop Fill for the maximum time to Log Communication

Auto Start Scanner Check this option if you want the OPC Server automatic start polling when running

Program To Execute InTek OPC Server giving you amenity to run automatically five program

Delay Fill the delay time to execute the current program

2. Disable All Logging

This command is used to discontinuing all log communication.

P age 18 of 84


II.1.5. Help

The commands in this sub menu will explained below:

1. About, is used to show the splash screen InTek Hybrid OPC Server.

2. User Guide is used to show the InTek Hybrid OPC Server User Guide in CHM

format.

II.2. Toolbar

The following picture show the Toolbar in InTek Hybrid OPC Server, as you can see there

are eight buttons.

All of the button will described below.

New File

Open File

Save File

Delete (Channel, Device, Group, Tag)

Start Poll (Selected Channel)

Stop Poll (Selected Channel)

Start Poll All Channel

Stop Poll All Channel

1 8

2

3

4

5

6

7

3

4

5

6

1

2

7

8

P age 19 of 84


II.3. Poll Window

In Poll Window you can see the listed of devices, live poll communication status and the

last poll cycle in each device in one selected channel.

Channel Name

Each channel represents one com port.

List of device in selected channel

Each device in one channel can be copy to other channel or same channel.

Poll status device symbol (multi state condition)

Each device has this symbol with multi state condition. There are four condition

statuses, each condition represent the communication status in selected channel.

Below the four conditions mentioned:

Device Disable (not include in the polling device)

Device Timeout (Polling/Communication Fail)

Device in Polling

Device finished Polling

3

1

2

2

3

1

P age 20 of 84


The list of tag each device is appearing to in this window if one device is selected as you can

see in below picture.

P age 21 of 84


CONFIGURATION

InTek Hybrid OPC Server requires very little configuration to operate correctly. The

following sections will guide you through the configuration procedure.

III.1. Create a New Polling Database File

Click ‘New’ on the ‘File’ menu or new button to create a new file then follow up the steps

below:

1. Define a Channel

2. Configure the Com Port

3. Define a Device

4. Define a Tag

5. Configure the User Admin

6. Saving the File

III.1.1. Define a Channel

When defining a channel, the following panel will appear:

III. CONFIGURATION

P age 22 of 84



Setting Description

Name Enter the Channel Name

Description Enter the channel description

Com Port Select the com port for this channel

Sec. Com Port Select the secondary com port, this is make the channel redundant

Disable Checked this to make the selected device not polled

Address Enter the Channel Address (Only for specific protocol). The default value is 1.

Device Skipping Enter the time, in milliseconds, that the server should wait if the server sense one device is down or skip.

Device Empty Enter the time, in milliseconds, that the server should wait to process the polling process if device is empty in database.

Start Start the polling process in selected channel

Stop Stop the polling process in selected channel

After clicking OK, the new Channel will appear in the poll window. Special Function

InTek Hybrid OPC Server will automatically storing last sent/received raw message in ten (10) roll-over text file. This function necessary for tracing problem or troubleshooting purpose.

Dump file will be saved in LOG directory with format of file name as follow: Filename : COM-COMX-DUMPYY.TXT X = Communication port number YY = Dump file order number

P age 23 of 84


III.1.2. Configure the Com Port

Click ‘Com Ports’ on the ‘File’ menu, then following panel will appear:

P age 24 of 84


The following table described the setting found in that panel:

Setting Description

Com Port Select the Com Port where want to configure

Disable Checked this to make the selected com port disable

Add Serial Port Add new com port

Baud Rate Select the Baud Rate, there are from 4800 – 115200

Flow Select the flow control where want to use in com port, there are three options: Hardware (RTS + CTS), Modem (RTS + Timeout), None.

Parity Select the parity where want to use in com port, there are three options: even, odd, and none

Data Bits Select the number of Data Bits there are two options: 8 (RTU) and 7 (ASCII)

Stop Bits Select the number of Stop Bits there are two options: 1 and 2

RTS Prekey Enter the time of RTS prekey in msec

CTS Prekey Enter the time of CTS prekey in msec

Add Server Port is used only for specific protocol

Add Client Port Add new TCP/IP com port

My IP Address Enter the IP address of computer

My Port Enter the Port number of computer (Default number 2404 for IEC60870-104 and 502 for Modbus TCP)

Peer Address Enter the IP address of slave device

Peer Port Enter the Port number of slave device (Default number 2404 for IEC60870-104 and 502 for Modbus TCP)

P age 25 of 84


III.1.3. Define a Device

Click ‘Device’ on the ‘Edit’ menu, then following panel will appear:


Setting Description

Name Enter the Name of device

Description Enter the description of device

Type Protocol Select the type of protocol where want to use in this device (see Appendix)

Next Go to the next panel on device configuration

The configuration for the next panel appropriate with type of protocol you have selected

when define new device. See Appendix for the next configuration on define new device.

Special Function

Every devices using Report By Exception (RBE) protocol type will be fully featured with Event or Changes Of State log. Event log file will created when change of state occurred for the first time on any devices. Content of event log file are every changes of state values send by RTU/IED including actual RTU/IED timestamp if supported by those devices.

Filename : EVENTCOE-HHMMSS-YYYYMMDD.LOG HHMMSS = Hour, Minute, Second YYYYMMDD = Year, Month, Day

P age 26 of 84


III.1.4. Copy Device

Each device in one channel can be copy to other channel or same channel. All of exist tag

in device will be copied also if device copied. The instruction command to copy device is

“Ctrl + Insert” and to paste copied device “Shift + Insert”. Select the device which want

to copy by moving the cursor to device and press “Ctrl” hold it then press “Insert” key, if

Copy command succeeds the message panel “Device Copied” will appear. To paste the

copied device, choose the Channel where that device copied will reside in then press

“Shift” hold it then press “Insert”. If the Paste command succeeds the new device will

appear at the listed device in that Channel.

III.1.5. Define a Tag

For define a tag is appropriate to protocol type which have selected when define new

device. In Appendix will be explain how to define a tag appropriate with type of protocol

which used by device.

III.1.6. Configure the User Admin

Click ‘User Admin’ on the ‘File’ menu to configure User Admin.


P age 27 of 84


Setting Description

User List Show the list of user in OPC Server

Edit Edit user setting for the selected user

Add Add new user

Delete Delete the selected user

Auto Logout Time Enter the Auto Logout Time, in minute, that the OPC Server should wait to automatic Logoff the current active user

When editing or adding user, the following panel will appear:


Setting Description

Login Name Enter the Login Name

User Name Enter the User Name

Privileged Select the privileged of user, Administrator or Dispatcher

Password Enter the Password of user

Confirm Enter again the current password of user

P age 28 of 84


III.1.7. Saving the File

Select ‘Save’ from the ‘File’ menu, the following panel will appear:

Enter the name of file with extension .itk then click the Save button. The OPC Server

wills automatic open the last Polling Database File. The OPC Server is ready to process

the polling process now. In the next section will explain how to start the OPC Server.

P age 29 of 84


III.2. Hot Standby Redundancy

InTek Hybrid OPC Server provides robust redundancy system that support Hot-Standby

redundant mechanism. Both side of OPC Server will always communicate through local

area network using a redundant UDP port for internal OPC Server communication.

This communication is guarantee that Master and Standby OPC Server knows if the other

OPC Server still alive or not and when OPC Server must doing switchover.

The following picture show the sample of InTek OPC Server network with several OPC Clients are connected to OPC Server through local or remote clients.

OPC Client #3

via DCOMOPC Client #5

via DCOMOPC Client #4

via DCOM

Primary OPC Server+

OPC Client #1

Standby OPC Server+

OPC Client #2

Internal OPC ServerCommunication

via UDP message

P age 30 of 84


How InTek OPC Server redundancy work? Both OPC Sever on Primary and Standby server waiting initiate from connected OPC Client .

Initiate from client is writing to OPC Server internal tag that is ClientActiveCounter, OPC

Server will consider active OPC Client is the one that keep writing to this internal tag.

If there are condition where both of OPC client write value to ClientActiveCounter tag at the

same time then Primary OPC Server is OPC Server that have more higher priority will keep

polling data to RTU/IED and standby OPC Server will remain standby.

Switchover only occurred if there are some circumstances occured as following:

- Last connected opc client stop writing and opc client connected to other opc server

start writing to internal ClientActiveCounter tag.

- Running OPC Server crash or shutdown

- Fatal error found within running opc server, for example all communication port fail

or missing.

P age 31 of 84


III.2. 1.Add New UDP Port

You can add one or more UDP port for redundancy purpose and the procedures to add a

new UDP port are describes as following:

1. Select menu File | COM Port…

2. Click on Add UDP Port button to add new UDP port

3. Enter My IP Address, Peer Address and Peer port

Setting Description

My IP Address Local computer IP Address

Peer Address Remote computer or RTU/IED IP Address

My Port Local computer port, automatically adjusted following of Peer port

Peer Port Port communication number

P age 32 of 84


III.2. 2.Primary OPC Server

To configure your OPC Server as Primary OPC Server is shown as following

1. Select on menu Server | Redundancy

2. Check on Master

3. Select UDP port name at Port 1

4. If the network support dual Ethernet Address than for UDP port redundancy you

could using Port 2 as shown on below picture.

Single UDP Port

Redundant UDP Port In redundant UDP system OPC Server act as Master always trying to communicate with

standby using Port 1 instead of Port 2 and if initialization on Port 1 fail then Port 2 will be

used to communicate. The advantage of this option is to eliminate loss of communication in

both OPC Server if there is one Ethernet, HUB or wiring problem occurred on one local area

network.

P age 33 of 84


III.2. 3.Standby OPC Server

To configure your OPC Server as Standby OPC Server is shown as following

5. Select on menu Server | Redundancy

6. Check on Force to Standby

7. Select UDP port name at Port 1

8. If the network support dual Ethernet Address than for UDP port redundancy you

could using Port 2 as shown on below picture.

Single UDP Port

Redundant UDP Port

P age 34 of 84


III.3. Start the OPC Server

Follow the steps below to start the Polling Process OPC Server :

1. Start the InTek Hybrid OPC Server by click the shortcut in InTek Software folder in

Start Menu.

2. Click ‘Open’ on the ‘File’ menu or open button on toolbar to open the polling database

file where you want to process it.

3. Login with your user name.

4. Determine the path directory for OPC Server Log Directory.

5. Click ‘Start’ button on toolbar to start the polling process in selected channel, if you

want to start the polling process in all channel click ‘Start All’ button on toolbar.

6. See the poll status device symbol to make sure the polling process OPC Server

working.

7. Stop the polling process OPC Server by click ‘Stop All’ button on toolbar before exit

the application.

P age 35 of 84


Appendix A Internal Tag

InTek Hybrid OPC Server has internal tag in each device where divided in 3 groups, which

are:

2. DevStats

3. ProcStats

4. CommStats

DevStats have 7 internal tags, will described below:

Tag Name Data Type Description

DeviceType Integer

Type of current device, this tag is used to identify the kind of current device, it’s usually use in template device or you can fill the type of device when you create a new device (See Appendix – Define Device)

DeviceAddressID Integer Communication Address of current device

RtuOutOfOrder Boolean It’s used to determining Communication Status of Device. The value 0 showing the communication is Good on the contrary mean Bad

RtuOutOfService Boolean This tag is used to determining the Service Status of Device. The value 0 showing the Device status is Enable on the contrary mean Disable

DevFirmwareRev Integer This tag is used to get “Device Firmware Revision” information, this tag is belong to specific protocol / device

FirmwareRev Integer This tag is used to get “Firmware Revision” from specific protocol / device

HWStatusFlags Integer This tag is used to determining the Flag Status of Hardware of specific protocol

Appendix A Internal Tag

P age 36 of 84


ProcStats have 5 internal tags, will described below:


DevControlResult Integer This tag show the result of device control

ControlResult Integer This tag shows the result of control Tag.

InitStatus Integer This tag represent the Initial Status for specific protocol

ControlInprogress Boolean This tag show the progress status of control Tag

CommandRequest Integer This tag is used to request specific command such as General Interrogation

There are four values to represent the return value in controllable Tag and In Tag Named

“ControlResult” , that are:

Value Meanings

1100 STARTING

1200 SUCCESS

1300 FAILED

1400 TIMEDOUT CommStats have 10 internal tags, will described below:


LastPollPeriode Integer Show the last poll period current device in msec

ResetStatsCounter Integer Command to reset all counter tags in CommStats group

UnrecognizedRespCounter Integer Number of unrecognized response from device

NoResponseCounter Integer Number of no response from device

InvalidResponseCounter Integer Number of invalid response from device

ValidResponseCounter Integer Number of valid response from device

PollCounter Integer Number of poll of device

PollStatus Integer Show the Poll Status of device

LastReplyTime Date Show the Date and Time for the Last Reply of device

LastPollTime Date Show the Date and Time for the Last Poll of device

P age 37 of 84


Appendix B Modbus Protocol

This protocol defines a message structure that controllers will recognize and use, regardless of

the type of networks over which they communicate. It describes the process a controller uses

to request access to another device, how it will respond to requests from the other devices,

and how errors will be detected and reported. It establishes a common format for the layout

and contents of message fields.

The Modbus protocol provides the internal standard that the Modicon controllers use for

parsing messages. During communications on a Modbus network, the protocol determines

how each controller will know its device address, recognize a message addressed to it,

determine the kind of action to be taken, and extract any data or other information contained

in the message. If a reply is required, the controller will construct the reply message and send

it using Modbus protocol.

InTek Hybrid OPC Server has implemented this protocol in its protocol library. The devices

which used Modbus protocol has implemented to in device template InTek Hybrid OPC

Server.

The available Modbus devices in device template are listed below:

Keltronics ESP (Electrical Submersible Pump) Controller

Vortex ESP (Electrical Submersible Pump) Controller

Schneider MG Sepam 2000

HC6030 Power Meter

HC6000 Power Meter

ION 7700

ION 6200

(Please contact us to find the latest Modbus devices list that we have supported)

Appendix B Modbus Protocol

P age 38 of 84


The following sections will guide you through the configuration procedure to define new

Modbus device.

B.1. Define a Device

Click ‘New Device’ on ‘Edit’ menu, or press Ctrl+D, then following panel will appear:

Select the kind of Modbus device you want add to database, then click ‘Next’ for the next

configuration panel.

The settings for the next panel (see the next page) are described in following table.

Setting Description

Name Fill the name of device

Description Fill the description of device

Disable Check this option if the current device want disable in polling process.

Device Type writing down device type which you wish

Address Enter the communication device address

Inter Poll Delay Enter the maximum time, in milliseconds, that the OPC Server should wait to poll again this device

Recv Timeout Enter the maximum time, in milliseconds, that the OPC Server should wait for a response from device

P age 39 of 84


Send Timeout Enter the maximum time, in milliseconds, that the OPC Server should wait to send a message to device

Skip Count if Down Enter the number of polling cycle, that the server will skip the device if not responded

Data Refresh Count Enter the maximum count that the server will refresh the device data in one polling

Number of Coil Enter the maximum number of coil that the server will request in one message

Number of Register Enter the maximum number of register that the server will request in one message

Scan Group Command to configure the Scan Group

Logging Enable Check this to enable communication logging current device

The picture below shows the next panel and the table upstairs described the setting for this

panel.

P age 40 of 84


The picture below shows the Scan Group panel and the table described the setting for this

panel.

Setting Description

Real Time Tags Tags in this group will always update in real time

Periodic Tags Tags in this group will update appropriate Periodic Scan Time

Periodic Scan Time Enter the Periodic Scan Time in msec

P age 41 of 84


B.2. Define a Tag

You can only define a tag in Generic Modbus, click ‘New Tag’ on the ‘Edit’ menu to add a

new tag in device database, then the following panel will appear:

P age 42 of 84



Setting Description

Tag Name Enter the Name of tag

Tag Type Select the type of register

Simulate Check this to simulate tag value

Bi-polar Check this to enable sign value of tag

Description Enter the description of tag

Address Enter the point address of tag

Type Select the type of data

Enable Range Select this option to enable scaling in raw value

Raw Enter the raw range value device

Scale to Enter the raw range scaling

Engineering Unit Enter the engineering unit of tag

Value 1 Enter the message when digital data has value = 1

Value 0 Enter the message when digital data has value = 0

Status Class Choose the status class, none, alarm, or event

Enable Alarm Select this option to enable alarm in tag

LoLo Enter the Low Low Alarm Value

Lo Enter the Low Alarm Value

Hi Enter the High Alarm Value

HiHi Enter the High High Alarm Value

Alarm State Select the alarm state for digital tag

Level info Enter the alarm level of tag

Comment Enter the comment for alarm

Enable History Select this option to enable historical of this tag

% Dead Band Enter the dead band historical value of tag

P age 43 of 84


Appendix C IEC 60870-5-101 Protocol

The IEC 60870-5-101 protocol series run in a lot of system all over the world and a lot of

utilities plan to use one or more companion standards to support their processes. A lot of

suppliers already have implemented of will start to implement one or more of the Companion

Standard in their equipment. Even suppliers outside the utility industry have already started

using these protocol series for telecontrol and monitoring. It seems that users and suppliers

have met the advantages in the use of IEC standardized protocols.

InTek Hybrid OPC Server has implemented the IEC60870-5-101 series and the other series of

this IEC protocol in its protocol library. The other series of this protocol which have

implemented are listed below:

IEC 60870-5-103

IEC 60870-5-104


IEC60870-5-101 device.

Appendix C IEC60870-5-101 Protocol

P age 44 of 84


C.1. Define a Device


Select the IEC60870-5-101 then click ‘Next’ for the next configuration panel.

The picture below shows the next panel and the table described the setting for this panel.

P age 45 of 84


Setting Description



Address Enter the communication device address.

CAASDU Enter the Common Address of ASDU which used by Device

Time Sync Timer Enter the time, in milliseconds, that the server should set a device’s time. Default is 36minutes. Setting 0 disables time synchronization.

CAASDU Enter the number of byte Common Address of ASDU (default = 2)

COT Enter the number of byte Cause Of Transmission (default = 1)

Link Address Enter the number of byte Link Address of device (default = 1)

IOA Enter the number of byte Information Object Address (default = 2)

Logging Enable Check this to enable communication logging current device The others setting have been explained in Appendix B – Define a Device

P age 46 of 84


C.2. Define a Tag

You can only define a tag in Generic IEC60870, click ‘New Tag’ on the ‘Edit’ menu to add a

new tag in device database, then the following panel will appear:

The following table described the settings found in this panel:

Setting Description

Tag Name Enter the Name of Tag

Tag Type Select the type of tag

IO Address Enter the IO Address of tag

CAASDU Enter the Common Address of ASDU of tag The others settings have been explained in Appendix B – Define a Tag.

P age 47 of 84


The following table shows the available IEC 60870-5-101 Tag Type

Function Code Tag Type

1 Single point information

3 Double point information

9 Measured value, normalized value

11 Measured value, scaled value

13 Measured value, short floating point value

45 Single command

46 Double command

48 Set point command, normalized value

49 Set point command, scaled value

50 Set point command, floating point value

110 Parameter of measured value, normalized value

111 Parameter of measured value, scaled value

112 Parameter of measured value, floating point value The following table shows the Parameter for Control Command and Double Command

Value interpretation.

Parameter for Control Command Double Command Value Interpretation

Value Command Type Value Command Type

11 SELECT OPEN 0 INVALID

12 SELECT CLOSE 1 OPEN

31 EXECUTE_OPEN 2 CLOSE

32 EXECUTE_CLOSE 3 INVALID

41 DIRECT_EXECUTE_OPEN - -

42 DIRECT_EXECUTE_CLOSE - -

P age 48 of 84


C.3. Interoperability IEC 60870-5-101 Document

Network configuration Point-to-point

Multiple point-to-point

Multipoint-party line

Multipoint-star

Physical layer Transmission speed (control direction) Unbalanced interchange circuit V.24/V.28 Standard 100 bit/s

200 bit/s

300 bit/s

600 bit/s

1200 bit/s

Unbalanced interchange circuit V.24/V.28 Recommended if >1200 bit/s 2400 bit/s

4800 bit/s

9600 bit/s

19200 bit/s

38400 bit/s

56000 bit/s

Balanced interchange circuit X.24/X.27 2400 bit/s

4800 bit/s

9600 bit/s

19200 bit/s

38400 bit/s

56000 bit/s

64000 bit/s

Transmission speed (monitor direction) Unbalanced interchange circuit V.24/V.28 Standard 100 bit/s

200 bit/s

300 bit/s

600 bit/s

1200 bit/s

Unbalanced interchange circuit V.24/V.28 Recommended if >1200 bit/s 2400 bit/s

4800 bit/s

9600 bit/s

19200 bit/s

38400 bit/s

56000 bit/s

Balanced interchange circuit X.24/X.27 2400 bit/s

4800 bit/s

9600 bit/s

19200 bit/s

38400 bit/s

56000 bit/s

64000 bit/s

X

X

X

X X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

P age 49 of 84


Link layer Link transmission procedure Balanced transmission

Unbalanced transmission

Frame length Maximum length L (number of octets) Address field of the link

Not present (balanced transmission only)

One octet

Two octets

Structured

Unstructured

Application layer Transmission mode for application data Common address of ASDU (system-specific parameter) One octet Two octets

Information object address (system-specific parameter) One octet

Two octets

Three octets

structured

unstructured

Cause of transmission (system-specific parameter) One octet Two octets (with originator address)

255

X X

X

X X

X

X X

X X

P age 50 of 84


Selection of standard ASDUs Process information in monitor direction <1> := Single-point information M_SP_NA_1

<2> := Single-point information with time tag M_SP_TA_1

<3> := Double-point information M_DP_NA_1

<4> := Double-point information with time tag M_DP_TA_1

<5> := Step position information M_ST_NA_1

<6> := Step position information with time tag M_ST_TA_1

<7> := Bitstring of 32 bit M_BO_NA_1

<8> := Bitstring of 32 bit with time tag M_BO_TA_1

<9> := Measured value, normalized value M_ME_NA_1

<10> := Measured value, normalized value with time tag M_ME_TA_1

<11> := Measured value, scaled value M_ME_NB_1

<12> := Measured value, scaled value with time tag M_ME_TB_1

<13> := Measured value, short floating point value M_ME_NC_1

<14> := Measured value, short floating point value with time tag M_ME_TC_1

<15> := Integrated totals M_IT_NA_1

<16> := Integrated totals with time tag M_IT_TA_1

<17> := Event of protection equipment with time tag M_EP_TA_1

<18> := Packed start events of protection equipment with time tag M_EP_TB_1

<19> := Packed output circuit inf of protection equipment with time tag M_EP_TC_1

<20> := Packed single-point information with status change detection M_PS_NA_1

<21> := Measured value, normalized value without quality descriptor M_ME_ND_1

X

X

X

X

X

P age 51 of 84


Process information in control direction <45> := Single command C_SC_NA_1

<46> := Double command C_DC_NA_1

` <47> := Regulating step command C_RC_NA_1

<48> := Set point command, normalized value C_SE_NA_1

<49> := Set point command, scaled value C_SE_NB_1

<50> := Set point command, short floating point value C_SE_NC_1

<51> := Bitstring of 32 bit C_BO_NA_1

Parameter in control direction (station-specific parameter) <110> := Parameter of measured value, normalized value P_ME_NA_1

<111> := Parameter of measured value, scaled value P_ME_NB_1

<112> := Parameter of measured value, short floating point value P_ME_NC_1

<113> := Parameter activation P_AC_NA_1

Clock synchronization (station-specific parameter) Clock synchronization

General interrogation (system or station-specific parameter)

Global

X

X

X

X

X

X

X

X

X

X

P age 52 of 84


Appendix D IEC60870-5-103 Protocol

The IEC 60870-5-103 defines an open communication interface for the communication with

protection relays. The IEC 60870-5-103 has its main focus on protection equipment. The IEC

60870-5-103 describes methods of information exchange. It is based on explicitly specified

Application Service Data Units (ASDUs) and application procedures for transmission of

‘standardized’ messages. These ‘standardized’ messages (compatible part) do not include all

possible protection functions and all possible messages of these protection functions. For this

reason, relays may offer more information than explicitly defined in the standard. For these

cases the ‘private ranges’ are defined in the standard and have to be used for compatibility

reasons.

InTek Hybrid OPC Server has implemented this protocol in its protocol library. The device

which used this protocol like Siprotect from Siemens has implemented to in device template

InTek Hybrid OPC Server.

The available protection devices in device template are listed below:

7SJ531

7SJ60 - 7SJ 64

7UT51 – 7UT61

7UM61

(Please contact us to find the latest Protection devices list that we have supported)

Appendix D IEC60870-5-103 Protocol

P age 53 of 84



IEC60870-5-103 device.

D.1. Define a Device


Select IEC 60870-5-103 or the device template which using IEC 60870-5-103 such as

Siprotec, then click “Next” for the next configuration

P age 54 of 84



Setting Description


Function Select the Function Type of the protection equipment used (see the table below for details function)


The others settings have been explained in Appendix B – Define a Device.

The following table described the available function type:

Function Type Description

128 Distance the protection t[z]

160 Over current Protection I>>

176 Transformer differential protection Dlt

192 Line differential protection DII

254 Generic function type GEN

255 Global function type GLB

P age 55 of 84


The following table shows the Parameter for Control Command and Double Command

Value interpretation.

Parameter for Control Command Double Command Value Interpretation

Value Command Type Value Command Type

11 General Command 0 INVALID

12 General Command 1 OPEN

31 General Command 2 CLOSE

32 General Command 3 INVALID

41 General Command - -

42 General Command - -

P age 56 of 84


D.2. Define a Tag

You can only define a tag in Generic IEC60870-5-103, click ‘New Tag’ on the ‘Edit’ menu to

add a new tag in device database, then the following panel will appear:

Setting Description

Tag Name Enter the Name of tag

Tag Type Select the type of tag

INF Enter the Information Number of tag

FUN Enter the Function Type of tag The other settings have been explained in Appendix B – Define a Tag.

P age 57 of 84


D.3. Dump Disturbance Log File Name and Location The Disturbance Log file is a text file located in the “Running” Directory of the InTek OPC

Server. The file is named according to the following convention:

Disturbance-DevName-FaultNumber-YYYYMMDD.log Where DevName is the Device Name and FaultNumber is the given Fault Number. So if, for

example, Device “SJ62Dev01” is reporting a disturbance with Fault Number 2 on July 10

2003, the disturbance log file will name:

Disturbance-SJ62Dev01-003-20030710.log

Each file contains only the values related to a specific disturbance on the specific Device. Generation of Disturbance Log Following the IEC 60870-5-103 convention the log file is generated when the device sends an

ASDU 26 (List of disturbances) and from there

the status and the channel values are extracted

accordingly.

During the collection of the disturbance data the

data updates may be locked up because of the

disturbance information consist of many data

which take some time to be retrieved. Because

of this, the generation of Disturbance Log is

OFF by default.

To enable the log Disturbance click on the “Log

Disturbance” option on the Device Properties

dialog. (See the shown picture.)

P age 58 of 84


Content of Disturbance Log The Disturbance Log contains a partially interpreted data from the Device. The content of the

file is as follow:

Starts with a “Disturbance Header Block”: ******* Disturbance ### ******** TimeStamp: hh:mm:ss.uuuu YYYY-MM-DD Status: TP[#]TM[#]TEST[#]OTEV[#] Type: [1] -- Grid Fault#: # -- No. Of Channel: # -- Element per Channel: ### -- Interval: ### microseconds. Time of First Data: hh:mm:ss:uuuu Where # represents numbers, and hh:mm:ss.uuuu represents a time stamp, while YYYY-

MM-DD represents a date.

And following that header is the “Tag Status Block” **** Start of Tags Dump **** [0] TagName1 = ON [1] TagName2 = OFF [2] … … Where TagName is replaced with a known Tag Name, if the Tag Name is not registered it

will be named as Tag(FUN=##, INF=##) , the value is either “ON”, “OFF” or “??”. This Tag

Status Block may be repeated. The first one indicates the status of the tags BEFORE the

disturbance occur, the next block indicates the status DURING the disturbance

At the end of the block is the following marker: **** End of Tags Dump **** Which is then followed by the “Channel Waveform Capture Block” which started by: **** Start of Channel # Dump Raw Value x 32768 **** TOV: # -- Channel#: # -- RPV: ### -- RSV: ### -- RFA: ### Where ### indicates a number. RPV, RSV and RFA are defined in the IEC-60870-5-103 as follow: RPV: Rated Primary Value RSV: Rated Secondary Value

P age 59 of 84


RFA: Reference Factor Following this header is list of values of the snapshot of the waveform on the respected

channel; the snapshot is taken started at some given time (specified as “Time of first data” in

the “Disturbance Header Block”). This starting time is always earlier than the Disturbance

Time.

The snapshot is created by sampling the waveform at a given period (specified as “Interval” in

the “Disturbance Header Block”).

The Values listed in this block is formatted as follow: Index_1, value_1 Index_2, value_2 … Where index is and index and value is a Raw Value. The number is repeated as many as

specified in “Element per Channel” parameter of the “Disturbance Header Block”. This Raw

Value is already multiplied by 32768 to minimize rounding error. By Copying and Pasting

this values into an excel worksheet a Waveform graph can be generated, using index as the

X values and value as Y values.

This Block is ended by: **** End of Channel Data Dump **** This “Channel Waveform Capture Block” is repeated as many times as specified by the number of channel in the “Disturbance Header Block”. At the end of the file the following marker should be found. **** End of Disturbance Data Dump ****

P age 60 of 84


D.4. Interoperability IEC 60870-5-103 Document Physical layer (network-specific parameter) Electrical interface EIA RS -485

Number of loads ....................... for one protection equipment

NOTE – EIA RS-485 standard defines unit loads so that 32 of them can be operated on one line. For detailed information refer to clause 3 of EIA RS-485 standard. Optical interface Glass fiber

Plastic fiber

F-SMA type connector

BFOC/2,5 type connector

Transmission speed 9600 bit/s

19200 bit/s

Application layer Common Address of ASDU One COMMON ADDRESS OF ASDU (identical with station address)

More than one COMMON ADDRESS OF ASDU

X

X

X

X

X

X

P age 61 of 84


Selection of standard information numbers in monitor direction System functions in monitor direction INF Semantics

<0> End of general interrogation

<1> Time synchronization

<2> Reset FCB

<3> Reset CU

<4> Start/restart

<5> Power on

Status indications in monitor direction INF Semantics

<16> Auto-recloser active

<17> Teleprotection active

<18> Protection active

<19> LED reset

<20> Monitor direction blocked

<21> Test mode

<22> Local parameter setting

<23> Characteristic 1




<27> Auxiliary input 1




X

X

X

X

X

X

X

X

X

X X

X

X

X

X X

X

P age 62 of 84


Supervision indications in monitor direction INF Semantics

<32> Measurand supervision I

<33> Measurand supervision V

<35> Phase sequence supervision

<36> Trip circuit supervision

<37> I>> back-up operation

<38> VT fuse failure

<39> Teleprotection disturbed

<46> Group warning

<47> Group alarm

Earth fault indications in monitor direction INF Semantics

<48> Earth fault L1

<49> Earth fault L2

<50> Earth fault L3

<51> Earth fault forward, i.e. line

<52> Earth fault reverse, i.e. busbar

Auto -reclosure indications in monitor direction INF Semantics

<128> CB ‘on’ by AR

<129> CB ‘on’ by long-time AR

<130> AR blocked

X

X

X

X

X

X

X

X X

X X

X

X

X

X

X X

P age 63 of 84


Fault indications in monitor direction INF Semantics

<64> Start /pick-up L1



<67> Start /pick-up N

<68> General trip

<69> Trip L1 <70> Trip L2

<71> Trip L3

<72> Trip I>> (back-up operation)

<73> Fault location X in ohms

<74> Fault forward/line

<75> Fault reverse/busbar

<76> Teleprotection signal transmitted <77> Teleprotection signal received

<78> Zone 1

<79> Zone 2

<80> Zone 3

<81> Zone 4 <82> Zone 5

<83> Zone 6

<84> General start/pick-up

<85> Breaker failure

<86> Trip measuring system L1



<89> Trip measuring system E

<90> Trip I>

<91> Trip I>> <92> Trip IN>

<93> Trip IN>>

X

X

X

X

X

X X

X

X

X

X

X

X X

X

X

X

X X

X

X

X X

X

X

X

X X

X

X

P age 64 of 84


Measurands in monitor direction INF Semantics

<144> Measurand I

<145> Measurands I, V

<146> Measurands I, V, P, Q

<147> Measurands IN, VEN

<148> Measurands IL1,2,3, VL1,2,3, P, Q, f

Selection of standard information numbers in control direction System functions in control direction INF Semantics

<0> Initiation of general interrogation

<0> Time synchronization

General commands in control direction INF Semantics

<16> Auto-recloser on/off

<17> Teleprotection on/off

<18> Protection on/off

<19> LED reset

<23> Activate characteristic 1




Basic application functions Test mode

Blocking of monitor direction

Disturbance data

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

P age 65 of 84


Appendix E IEC 60870-5-104 Protocol

E.1. Define a Device


Select the Generic IEC870104, and then click ‘Next’ for the next configuration panel.

The picture below shows the next panel

Appendix E IEC 60870-5-104 Protocol

P age 66 of 84


The settings for that panel are described in following table.

Setting Description






GI Timer Enter the time, in milliseconds, that the server should perform General Interrogations

The others setting have been explained in Appendix B – Define a Device

E.2. Define a Tag

Define a tag in IEC60870-5-104 is same with in IEC60870-5-101 (Appendix C)

P age 67 of 84


Appendix F DNP 3.0 Protocol F.1. Define a Device


Select the DNP 3.0 Serial, and then click ‘Next’ for the next configuration panel.


Appendix F DNP 3.0 Protocol

P age 68 of 84


Setting Description






GI Timer Enter the time, in milliseconds, that the server should perform General Interrogations


P age 69 of 84


F.2. Define a Tag

The following configuration panel is to create a tag in DNP device.

P age 70 of 84


Setting Description

Tag Name Fill the name of tag

Tag Type Select the type of tag (see the table below for available tag type)

Address Enter the Address of tag

CAASDU Enter the Class Info of tag

Set (1) Select the type of Set for the Control Block Tag

Clear (0) Select the type of Clear for the Control Block Tag

Time ON Enter the Time ON value in msec

Time OFF Enter the Time OFF value in msec

Repeat Enter the repeat time The other settings have been explained in Appendix B – Define a Tag. The following table shows the available DNP 3.0 Tag Type in InTek OPC

Tag Type Parameter for Control Command

Obj Var Tag Type Value Command Type

1 2 Binary Input with Status 10 Control Block

10 0 Binary Output All Variations 31 Control Block

12 0 Control Block All Variations 32 Control Block

20,22 0 Binary Counter 41 Control Block

21,23 0 Frozen Counter 42 Control Block

30,32 0 Analog Input - -

31,33 0 Frozen Analog Input - -

40 0 Analog Output Status All Variations - -

41 1 32 Bit Analog Output Block - -

41 2 16 Bit Analog Output Block - -

50 0 Time and Date All Variations - -

P age 71 of 84


F.3. Interoperability DNP 3.0 Document

Vendor Name : PT. Integra Teknik Asia Device Name : InTek OPC Server Highest DNP Level Supported : Device Function: For Requests Level 3 Master Slave

For Responses Level 3

Notable objects, functions, and/or qualifiers supported in addition to the Highest DNP

Levels Supported (the complete list is described in the attached table):

Maximum Data Link Frame Size

(octets)

Transmitted

Received

Maximum Application Fragment Size

(octets)

Transmitted

Received

Maximum Data Link Re-tries:

None

Fixed at

Configurable, range to

Maximum Application Layer Re-tries:

None

Configurable, range to

X

X

X

292

292

255

2048

1 10

of 84


Requires Data Link Layer Confirmation: Never

Always

Sometimes

Configurable

Requires Application Layer Confirmation: Never

Always

When reporting Event Data

When sending multi-fragment responses

Sometimes

Configurable

Timeouts while waiting for: Data Link Confirm None Fixed at Variable Configurable

Complete Appl. Fragment None Fixed at Variable Configurable

Application Confirm None Fixed at Variable Configurable

Complete Appl. Response None Fixed at Variable Configurable

Others _________________________________________________________________

X

X

X

X

X

X

of 84


Sends/Executes Control Operations: WRITE Binary Outputs Never Always Sometimes Configurable

SELECT/OPERATE Never Always Sometimes Configurable

DIRECT OPERATE Never Always Sometimes Configurable

DIRECT OPERATE - NO ACK Never Always Sometimes Configurable

Count > 1 Never Always Sometimes Configurable

Pulse On Never Always Sometimes Configurable

Pulse Off Never Always Sometimes Configurable

Latch On Never Always Sometimes Configurable

Latch Off Never Always Sometimes Configurable

Queue Never Always Sometimes Configurable

Clear Queue Never Always Sometimes Configurable

Fill Out The Following Item For Master Devices Only: Expects Binary Input Change Events: Either time-tagged or non-time-tagged for a single event

Both time-tagged and non-time-tagged for a single event

Configurable (attach explanation)

X

X

X

X

X

X

X

X

X

X

X

X

of 84


IMPLEMENTATION OBJECT

This table describes the objects, function codes and qualifiers available in this Master

OBJECT REQUEST

(slave must parse) RESPONSE

(master must parse)

Obj

Var

Description

Func Codes (dec)

Qual Codes (hex)

Func Codes

Qual Codes (hex)

1 2 Binary Input with Status 129, 130 00, 01

10 0 Binary Output - All Variations 1 06

12 0 Control Block - All Variations

20 0 Binary Counter - All Variations 1, 7, 8, 9, 10 06

21 0 Frozen Counter - All Variations 1 06

22 0 Counter Change Event - All Variations 1 06,07,08

23 0 Frozen Counter Event - All Variations

30 0 Analog Input - All Variations 1 06

31 0 Frozen Analog Input - All Variations

32 0 Analog Change Event - All Variations 1 06,07,08

33 0 Frozen Analog Event - All Variations

40 0 Analog Output Status - All Variations 1 06

41 1 32-Bit Analog Output Block

41 2 16-Bit Analog Output Block 3, 4, 5, 6 17, 28 129 echo of request

50 0 Time and Date - All Variations

of 84


Appendix G SPABus G.1. Define a Device


Select the DNP 3.0 Serial, and then click ‘Next’ for the next configuration panel.


Appendix G SPABus Protocol

of 84


Setting Description





of 84


G.2. Define a Tag

The following configuration panel is to create a tag in SPABus Device.

of 84


Setting Description

Tag Name Fill the name of tag

Tag Type Select the type of tag (see the table below for available tag type)

Channel Number Enter the Channel Number of tag

Data Number Enter the Data Number of tag

Readable Check this to make the current tag access readable

Writeable Check this to make the current tag access writeable The other settings have been explained in Appendix B – Define a Tag. The following table shows the available SPABus Tag Type

SPABus Code Tag Type

I Analog Input Values and Digital Input States

O Analog Output Values and Digital Output States

S Setting Values

V Variables (internal)

of 84


Appendix H Modbus Slave Modbus Slave protocol could be utilized as a protocol converter to convert any protocol such

as DNP 3.0, IEC 60870-5-101/103, ABB SPAbus to Modbus RTU. Modbus slave can be use

to as device mirroring to any Modbus device in polling database InTek OPC.

H.1. Define a Slave Device and Device Mirroring

Click ‘New Device’ on ‘Edit’ menu, or press Ctrl+D, then select the kind of Modbus Slave

there are three optional: RTU, ASCII, and TCP.

The picture below shows the next configuration panel

Click “Link To a Device” to make this slave as device mirroring to any Modbus device.

Appendix H Modbus Slave Protocol

of 84


The Tag Picker panel will show as picture below after clicked that button, then select any

device to be mirrored to Slave device (note : that device must be use Modbus protocol). The

Slave device will have a same tag with device where mirrored and will be made automatically.

Leave the “Link to a Device” blank to make a Modbus Slave device as protocol converter.

The others setting for configuration panel have been explained in Appendix A – Define New

Device.

of 84


H.2. Define a Tag

The following picture shows the configuration panel to create a tag in Slave device which

used as protocol converter

of 84


Setting Description

Address Enter the full Modbus Address (i.e. Input Register = 3xxxx ; Output Register = 4xxxx ; Input Status = 1xxxx ; Coil Status = xxxx)

Linked To Fill the name of tag where the current tag linked. Click the “Lookup” button to find that tag in Tag Picker panel (note: the data type of both of tag must be same)

Use Raw Value Checked this to enable raw value of Linked tag The other settings have been explained in Appendix B – Define a Tag.

of 84


Index

.itk, 13, 28 About, 7, 10, 18 button, 18, 21, 28 CAASDU, 40, 41, 60, 62, 63 Channel, 13, 16, 18, 19, 21, 22

New Channel, 16 Com Ports, 15 command, 13, 14, 15, 16, 17 CommStats, 30, 31 communication logging, 34, 40 control, 6, 23 copy, 19, 25 COT, 40 data, 6, 8, 9 Delete, 18, 26 Device, 6, 7, 8, 13, 18, 19, 21, 22, 25

Copy Device, 3, 25 New Device, 16 Slave, 65, 73, 74 Slave device, 74, 75 device mirroring, 73

DevStats, 30 Disable, 19, 22, 23 Disturbance, 51, 52, 53, 58 Dump Stats, 15 Edit, 16

Delete, 16 Exit, 16 File, 13, 18, 21, 23, 26, 28 IED, 6, 8, 32, 47 internal tags, 30, 31 License, 7, 10 Log, 7, 9, 14, 17, 29, 51, 52

Disturbance Log, 51 Login, 14, 27

Logout, 14, 15, 26 Menu, 12, 13 MMI, 6 New, 13, 16, 18 OPC, 1, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15,

17, 18, 21, 26, 28, 29

OPC client, 6 OPC Server, 6, 10, 11, 12, 14, 15, 28

Open, 13, 18 password, 14, 27

Change Password, 14 Poll, 8, 13, 18, 19

Poll Window, 13 Polling Cycle, 13

Port Baud Rate, 23 Com Ports, 15, 19, 22, 23 serial port, 6

ProcStats, 30 Properties, 16, 17 protection, 8, 49, 55, 58 protocol, 6, 7, 8, 9, 10, 25, 26

ABB SPAbus, 7 DNP 3.0, 7 EDF HNZ, 7 IEC 60870-5-101, 7 KIM-LIPI, 7 Modbus RTU / Jbus, 7 protocol converter, 73, 74, 75

protocol Modbus ASCII, 7 Generic Modbus, 16

Raw, 37, 52, 53, 76 redundant, 22 Save, 13, 18, 28

Save As, 13 SCADA, 6 Scan Group, 34, 35 Server, 1, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15,

17, 18, 21, 26, 28, 29 Setting, 17, 22, 23, 25, 26, 27, 33, 35, 37,

49, 50, 60, 62, 63, 64, 70, 71, 76 Start, 17, 18, 22, 28, 29 Stop, 18, 22, 24 symbol, 19 tag, 8, 10, 16, 20, 21, 26, 30, 36, 37, 41, 45,

50, 60, 63, 71, 72, 75, 76 New Tag, 16

of 84


Tag Picker, 74, 76 template, 6, 7, 8 Time, 6, 8, 9, 14, 15, 22

Periodic, 8, 35 Real Time, 35 Time Sync, 40, 49, 60, 62

Timeout, 19, 23 Toolbar, 12, 13, 16, 18 User, 1, 10, 11, 18, 21, 26, 27

Administrator, 14, 15, 27 Dispatcher, 15, 27 User Admin, 15, 26

View, 16

intek hybrid opc server v3.1.0 hybrid opc... · 2007-03-20 · p age 1 of 84 intek hybrid opc...

Documents