user´s manual opc s e - resolucom · the information in these documents is not binding. ... opc...

OPC S E R V E R E T H E R N E T

OPC Server EthernetManual Version 1006-001

User´s Manual

OPC Server Ethernet

OPC Server EthernetIntro

[ OPC Server Ethernet Manual / Intro ]

C O P Y R I G H TThe contents of this manual and the related software are the property of INAT GmbH. This information is subject to the conditions of a general or special license agreement (i.e., one-time license) and may only be used or copied in accordance with the specifications of this agreement.The information in these documents is not binding.Changes to the contents can occur at any time without prior notification. Subject to change due to technolo-gical advances.

© Copyright INAT GmbH 1996-2006

Industrial Networks for Automation TechnologyOstendstrasse 50AD-90482 NurembergTel: + 49 911 / 5 44 27-0Fax: + 49 911 / 5 44 27-27Web: www.inat.deEmail: [email protected]

All rights reserved.______________________________________________________Step®, Simatic® und Sinec® sind eingetragene Warenzeichen der Siemens AG.

OPC

Serv

er E

ther

net

Intro


CONTENT

1 Introduction ....................................................................................................................... 8

1.1 General .................................................................................................................................................. 81.2 Scope of Supply .................................................................................................................................... 91.3 System Requirements .......................................................................................................................... 91.4 OPC Overview ....................................................................................................................................... 9

1.4.1 What is OPC? .................................................................................................................................. 91.4.2 OPC DA Specification .................................................................................................................. 10

2 Getting Started ........................................................................................................... 14

2.1 Installation of the OPC Server ............................................................................................................ 142.2 Installation of the H1 driver ................................................................................................................ 19

2.2.1 Change number of H1 connections .............................................................................................. 202.2.2 Allow overwriting the MAC Address .............................................................................................. 202.2.3 Do not allow overwriting the MAC Address ................................................................................... 20

2.3 Installing the Server as Service ......................................................................................................... 212.4 Changing Server Type ......................................................................................................................... 212.5 Licensing ............................................................................................................................................. 22

2.5.1 Licensing with dongle .................................................................................................................... 222.5.2 Licensing with license request code .............................................................................................. 22

2.6 Updating and Upgrading ..................................................................................................................... 242.6.1 Update ........................................................................................................................................... 242.4.2 Upgrade ......................................................................................................................................... 24

3 Communication Basics ............................................................................... 26

3.1 Job types ............................................................................................................................................. 263.1.1 SEND / RECEIVE .......................................................................................................................... 263.1.2 WRITE active / WRITE passive ..................................................................................................... 263.1.3 FETCH active / FETCH passive .................................................................................................... 263.1.4 FETCH on EVENT ........................................................................................................................ 27

3.2 Connections ......................................................................................................................................... 273.2.1 TCP/IP Connections ...................................................................................................................... 283.2.2 H1 Connections ............................................................................................................................ 293.2.3 RFC1006 Connections .................................................................................................................. 31

3.3 S5 Connections .................................................................................................................................. 323.4 S7 Connections .................................................................................................................................. 33

3.4.1 Not parameterizable connections (Standard connections) ............................................................ 34



3.4.2 Parameterizable connections ....................................................................................................... 343.5 Modbus Connection ........................................................................................................................... 343.6 NetLink Connection ............................................................................................................................ 353.7 PLC-5 Connection .............................................................................................................................. 353.8 MELSEC-Q Connection ...................................................................................................................... 36

4 Configuration .............................................................................................................. 38

4.1 Required steps for OPC Communication ......................................................................................... 384.2 Setting up a new connection .............................................................................................................. 39

4.2.1 Edit TCP/IP Parameters ................................................................................................................ 414.2.2 Edit H1 Parameters ...................................................................................................................... 48

4.3 Shutting down the OPC Server .......................................................................................................... 524.4 Alias Configuration ............................................................................................................................ 53

4.4.1 Import Step 7 Symbols ................................................................................................................. 544.5 Server Settings ................................................................................................................................... 55

4.5.1 Protocol Timer Tick ........................................................................................................................ 554.5.2 Configuration file ........................................................................................................................... 554.5.3 Data types .................................................................................................................................... 564.5.4 Echo Written Data back to Client .................................................................................................. 564.5.5 Show Server Icon in the task bar .................................................................................................. 56

4.6 Server Optimisation ............................................................................................................................ 574.6.1 Combine coherent blocks always (max) ........................................................................................ 574.6.2 Chronological Order is preserved .................................................................................................. 574.6.3 Write every item separately (off) ................................................................................................... 574.6.4 Write with Priority, Chronological Order is Preserved .................................................................... 574.6.5 Writes with immediate positive Confirm (default: No) .................................................................... 574.6.6 Read between Write (default: No) ................................................................................................. 57

4.7 Server Options .................................................................................................................................... 584.7.1 String Format ................................................................................................................................. 584.7.2 Timeouts ........................................................................................................................................ 58

4.8 H1 Station Address ............................................................................................................................. 594.9 DCOM Configuration .......................................................................................................................... 60

4.9.1 User ............................................................................................................................................... 604.9.2 Computer properties for client and server machine ...................................................................... 604.9.3 OPC Server Settings for Server PC .............................................................................................. 62

4.10 Main window ...................................................................................................................................... 654.11 Logging ............................................................................................................................................... 674.12 Suspend and resume the OPC Server ............................................................................................. 69

OPC

Serv

er E

ther

net

Intro


5 Item ID Syntax ............................................................................................................. 72

5.1 S7 Item ID Syntax ................................................................................................................................ 725.2 S5 Item ID Syntax ................................................................................................................................ 755.3 Modbus Item ID Syntax ....................................................................................................................... 795.4 Send / Receive Item ID Syntax ........................................................................................................... 815.5 PLC-5 Item ID Syntax .......................................................................................................................... 835.6 Mitsubishi Item ID Syntax ................................................................................................................... 855.7 Arrays ................................................................................................................................................... 875.8 Suffixe ................................................................................................................................................... 88

5.8.1 Suffix BA ........................................................................................................................................ 885.8.2 Suffix BCD ..................................................................................................................................... 885.8.3 Suffix D .......................................................................................................................................... 895.8.4 Suffix DT ........................................................................................................................................ 895.8.5 Suffix DU ....................................................................................................................................... 905.8.6 Suffix KA ........................................................................................................................................ 905.8.7 Suffix KF ........................................................................................................................................ 905.8.8 Suffix KG ....................................................................................................................................... 905.8.9 Suffix KT ........................................................................................................................................ 915.8.10 Suffix RI ....................................................................................................................................... 915.8.11 Suffix RU ..................................................................................................................................... 915.8.12 Suffix S5T .................................................................................................................................... 915.8.13 Suffix SWAB ................................................................................................................................ 915.8.14 Suffix T ........................................................................................................................................ 925.8.15 Suffix TOD ................................................................................................................................... 925.8.16 Suffix TR ...................................................................................................................................... 92

5.9 Bit Masking .......................................................................................................................................... 925.10 Special Items ...................................................................................................................................... 93

5.10.1 Pollinterval ................................................................................................................................... 935.10.2 Storesettings ............................................................................................................................... 945.10.3 Maxinterval .................................................................................................................................. 945.10.4 Itemcount ..................................................................................................................................... 945.10.5 Errorcount ................................................................................................................................... 945.10.6 Writecomplete ............................................................................................................................. 955.10.7 Status .......................................................................................................................................... 955.10.8 WriteItemCount ........................................................................................................................... 955.10.9 WriteStatusMsg ........................................................................................................................... 955.10.10 Servercycle ................................................................................................................................ 98

6 OPC Client ....................................................................................................................... 100

6.1 Connect Client and Server ................................................................................................................ 1006.3 Add OPC Items ................................................................................................................................. 1026.4 Browse the Server Address Space .................................................................................................. 1036.5 Read real-time values ....................................................................................................................... 103



6.6 Write control values ......................................................................................................................... 104

7 Appendix ............................................................................................................................ 108

7.1 Win.ini ................................................................................................................................................. 108

C H A P T E R 1 :I N T R O D U C T I O N

OPC Server EthernetChapter 1: Introduction

[ OPC Server Ethernet Manual / Chapter 1: Introduction ]

1 INTRODUCTION

1.1 General Six Ethernet OPC server types are available, each with a different range of supported protocols. Depending on the supported transport protcols and application protocols, the OPC server enables the transfer of real-time data between Siemens S5/S7 PLCs, Allen-Bradley PLCs, Mitsubishi PLCs, devices with Modbus on TCP interface and OPC clients via Ethernet. The following OPC servers are available:

OPC Server Type Transport Protocols Application ProtocolsOPC Server TCPIPH1(Order No.: 100-3100-01)

● TCP/IP● RFC1006● PLC Header● ISO (H1)

● S7 Protocol● S5-AP● Modbus on TCP● AB PLC-5● Melsec-Q● Send / Receive● NetLink

OPC Server H1(Order No.: 100-3110-01)

● ISO (H1) ● S7-Protokoll● S5-AP● Send / Receive

OPC Server TCPIP-S(Order No.: 100-3120-01)

● TCP/IP● RFC1006● PLC Header

● S7-Protokoll● S5-AP● Modbus on TCP● AB PLC-5● Melsec-Q● Send / Receive● NetLink

OPC Server TCPIP-I(Order No.: 100-3150-01)

● TCP/IP● PLC Header

● S7 Protocol● S5-AP● Modbus on TCP● Send / Receive● NetLink

OPC Server TCPIP-M(Order No.: 100-3160-01)


● Melsec-Q● Send / Receive

OPC Server Modbus(Order No.: 100-3140-01)


● Modbus on TCP● Send / Receive● NetLink

OPC

Serv

er E

ther

net

Chap

ter 1

: Int

rodu

ctio

n


1.2 Scope of SupplyBefore setting up the OPC server, please make sure, that the following components are included in the scope of supply.

CDROM with OPC Server INAT Demo software INAT ManualsOptional: Dongle

Optional: Certificate

1.3 System Requirements The INAT OPC servers have the following minimum system requirements:

System Requirements● Intel Pentium II 200 MHz Processor● 64 MB RAM● 25 MB hard drive space● Windows 98 / ME / NT / 2000 / XP / 2003

1.4 OPC Overview

1.4.1 What is OPC?OPC (OLE for Process Control) was designed to bridge Windows based applications and process control hardware and software applications. 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 con-trol device, such as a PLC or DCS. Traditionally, any time a package needed access data from a device, a custom interface, or driver, had to be written. The purpose of OPC is to define a common interface that is written once and then reused by any business, SCADA, HMI, or custom software packages.



Once an OPC server is written for a particular device, it can be reused by any application that is able to act as an OPC client. OPC servers use Microsoft’s OLE technology (also known as the Component Object Model, or COM) to communicate with clients. COM technology permits a standard for real-time information exchange between software applications and process hardware to be defined.

1.4.2 OPC DA Specification The OPC DA Specification was the first specification published by the OPC Foundation. It is used to move real-time data from PLCs and other control devices to HMIs and other display clients. It defines an interface between client applications and server applications for data transfer.

1.4.2.1 Class modelThe OPC Specification defines three hierarchical classes for data access: OPCServer, OPCGroup und OPCItem

Class: OPCServerAn OPCServer object represents a vendor specific OPC server. OPC servers implement the access to the hardware. The OPC server receives a unique name by its vendor, so that it can be identified. In COM stan-dard, this name is called ProgID.

OPC

Serv

er E

ther

net

Chap

ter 1

: Int

rodu

ctio

n


All INAT Ethernet OPC Servers have the following ProgID:

INAT TCPIPH1 OPC Server

Class: OPCGroupAn OPCGroup object structures the variables used by the server. The OPCGroup manages the single process variables, the OPC items.

Class: OPCItemAn OPCItem object represents the ultimate process variable. In the address space of the OPC server, the item is identified by its Item ID (Item Syntax). An item is NOT the data source, but the connection to the data source. The Item ID is defined by the server vendor. Each item has the following properties:

Value the latest value read from the serverQuality the latest quality read from the serverTime Stamp time when the latest value was read

C H A P T E R 2 :G E T T I N G S TA R T E D

OPC Server EthernetChapter 2: Getting Started

[ OPC Server Ethernet / Chapter 2: Gettings Started ]

2 GETTING STARTED

2.1 Installation of the OPC ServerThe INAT OPC Server may be installed as application or as service. For both variants the following steps are required. 1. If you received your OPC Server from the INAT website (Download Area), please refer to point 5. If you received the OPC Server on a CDROM, insert the CDROM „OPC Server“. 2. If autostart is not activated in your PC, use start.exe or index.html. If autostart is activated, the following dialog appears:

3. Select „Installation“. „Installation“: files to install INAT OPC Server. „Software Overview“: a downloadable overview with INAT software and manuals. „Informative Literature“: a downloadable overview with INAT informative literature (press releases, manuals etc).

4. Click OPC Server Ethernet.5. Save the file opceth.exe in a directory of your choice.6. Run the .exe file. Be sure that there are no Windows programs running.

OPC

Serv

er E

ther

net

Chap

ter 2

: Get

ting

Star

ted


7. Select the installation language and click „OK“.

8. Select „Next“.

9. Accept the license agreement with „Yes“.


11. Select the directory, where the server shall be installed (Default: C:\Programme\INAT\OPC Server Ethernet\) and confirm with „Next“.



12. Enter the folder for the OPC server (Default: INAT\OPC Server Ethernet) and select „Next“.

13. Select the desired installation:

Complete OPC server, H1 protocol driver, hardlock dongle drivers, manuals and OPC components of the OPC Foundation are installed.

Minimum OPC server, H1 protocol driver and OPC components of the OPC Foundation are installed.

User-defined You decide, which components are installed. It´s possible to select or deselect some components.

14. Please wait while setup installs the required data.

OPC

Serv

er E

ther

net

Chap

ter 2

: Get

ting

Star

ted


15. After the OPC server installation, the hardlock device criver and the OPC core components are installed - if selected!

16. The installation of the „hardlock device drivers“ is required to license the OPC server via dongle. Select „Next“.

17. Select „Finish“.

18. To install the OPC components of the OPC Foundation, you must accept the license agreement. Select „Next“.




20. Select „Close“.

21. You are asked to select the desired server. Select a server and you will see the protocols provided. The server type may be changed at any time (see chapter 2.4). This provides the opportunity to test the functio-nal range of the diverse server types without installing another software.

NOTE

If you have already installed and licensed a server and change the server type your license expires. You need a new license confirm code or a new dongle!

If using a OPC server, that supports the ISO (H1) protocol, the H1 protocol driver must be installed (see chapter 2.2)Installation is complete. If you do not license the OPC server, it runs for 72 hours after every start or restart.

OPC

Serv

er E

ther

net

Chap

ter 2

: Get

ting

Star

ted


2.2 Installation of the H1 driverIf you have choosen a server that supports the ISO (H1) protocol and the H1 protocol driver has not yet been installed, the network window in the system control appears

During the installation of the OPC server the H1 driver will automatically be copied to the hard disc. A PC-H1 subdirectory will be created in the installation directory of the server. Default: C:\Programs\INAT\OPC Server Ethernet\pch1\

To install the H1 driver follow these steps: ● After the installation of the OPC server the window „network“ in the system control opens● Select at least one LAN● Open the „Properties“ dialog of the LAN connection● Select „Install“ ● Add a new protocol● Select „Have Disc“. Select the path of the H1 driver

(default: C:\Programs\INAT\OPC Server Ethernet\pch1\driver)● Select the *.inf file, confirm with „Open“ and „OK“● Select „INAT H1 Iso Protocol“ and confirm with „OK“ ● The PC-H1 protocol driver is now linked to your network card(s)● Close all network windows

NOTE

The installation of the PC-H1 protocol driver requires a system reboot



2.2.1 Change number of H1 connections The registry entry „200H1Connections.reg“ increases the maximum number of H1 connections from 64 (default) to 200. Select Start > Programs > INAT > OPC Server Ethernet >pch1 > H1 registry scripts > 200H1Connections.reg. A warning will appear. Confirm with „Yes“. A confirmation message will verify that the new registry entry has been made.

NOTE

The change to the registry requires a system reboot

2.2.2 Allow overwriting the MAC Address In the default setting, the MAC address of the Ethernet adapter linked with the H1 protocol may not be changed during runtime. With the registry entry „H1ChangeAddress.reg“ this restriction is lifted. Select Start > Programs > INAT > OPC Server Ethernet >pch1 > H1 registry scripts > H1ChangeAddress.reg.A warning will appear. Confirm with „Yes“. A confirmation message will verify that the new registry entry has been made. Now it is possible to change (overwrite) the Ethernet address during runtime (see chapter 4.8 „H1 Station Address“). Please note that this setting may slow down your system.

NOTE


2.2.3 Do not allow overwriting the MAC AddressWith the registry entry „H1DoNotChangeAddress.reg“ the registry entry „H1ChangeAddress.reg“ can be canceled. Select Start > Programs > INAT > OPC Server Ethernet > pch1 > H1 Registry Scripts > H1DoNotChangeAddress.reg. A warning will appear. Confirm with „Yes“. A confirmation message will verify that the new registry entry has been made. Now it is no longer possible to change (overwrite) the Ethernet address during runtime.

NOTE


OPC

Serv

er E

ther

net

Chap

ter 2

: Get

ting

Star

ted


2.3 Installing the Server as ServiceIn the default setting the installation program registers the INAT OPC Server to run as a local executable. If you want to run the server as an service (only possible with Windows NT/2000/XP), select Start > Programs > INAT > OPC Server Ethernet > Installing server as service. The server will be registered in the registry as service, that starts „manually“. With the next start of the server, it runs as service. In order to run the service automatically, change the start type in the system control.

2.4 Changing Server TypeThe server type may be changed at any time. This provides the opportunity to test the functional range of the diverse server types without installing another software. You can also change the server type in order to upgrade your server to a server type that supports more protocols.

NOTE

If you have already installed and licensed a server and change the server type your license expires. You need a new license confirm code or a new dongle! When selecting again the licensed server type, the license is valid again.

Select Start > Programs > INAT > OPC Server Ethernet > Tools > Change Type of server

Mark the desired server and confirm with „OK“. With the next start of the server, it runs with the selected protocol range.



2.5 Licensing

NOTE

In conjunction with RAID systems and Cluster stations, Dongle licensing is required!

2.5.1 Licensing with dongleThe OPC server supports hardware key licensing. A HASP hardware key coded to the particular OPC server can be purchased. This key must be securely fastened to the USB port/parallel port of the computer on which the server is installed. It does not interfere with hardware keys from other vendors, nor does it affect other normal port applications.

2.5.2 Licensing with license request code

NOTE

You should license your server when all tests are done. The desired server type must be installed on the target device. A later portation of the license confirm code to another hardware is NOT possible!

Follow these steps to license the server:● Install the server at the final hardware location. Start the server and choose „License“ from the help

menu.

● The license dialog appears.

● Compare the entries under Product and Order No. with your ordering data! ● Enter your company name and the user name in order to get a unique license. ● Press the button ->Clipboard. The data needed for the license request are now available. You only have

to paste them in your email program.

OPC

Serv

er E

ther

net

Chap

ter 2

: Get

ting

Star

ted


Example:-----------------------------------------Product : OPC-Server TCPIPH1Order No : 100-3100-01Customer : Company ABCUser : User XYZRequest : 0DQR70H0CH3CMXLConfirm : =========================================

● Send the data: - by fax to +49 911/54427-27 or - by email to [email protected].● Due to the contract with INAT you will get an unlimited license confirm code or a limited license confirm

code for test purposes.● Enter the code in the license confirm code field. Under License the following messages are possible:

OK your license is validChecksum is wrong Please check the codesNo valid license If the test runtime is over (by default 72h) the server ends



2.6 Updating and UpgradingINAT OPC Servers are improved and extended with helpful features on a regular basis. At the download area of the INAT website, the current version of the OPC servers is available. If you are already licensee of a OPC server license and want to use the latest version by replacing it with your earlier version, please determine, if it is an update or an upgrade.

2.6.1 UpdateUpdates are free. If the version number of your OPC server begins with the same number as the version number of the current version on the INAT Web Site, it is an update. Example:

Your server: 3.01.06Current server: 3.03.25

To update, install the OPC server (proceed as normal) and use the existing dongle or your existing license confirm code for licensing your server.

2.4.2 UpgradeUpgrades are not free. If the version number of your OPC server begins with another number than the ver-sion number of the current version in the Internet, it is an upgrade. Example:

Your server: 2.05.06Current server: 3.03.25

To upgrade, install the OPC server (proceed as normal). You will then receive the new license confirm code or a new dongle from us.

NOTE

Choose „About“ from the help menu to find out the version number of your OPC server

C H A P T E R 3 :C O M M U N I C AT I O N B A S I C S

OPC Server EthernetChapter 3: Com

munication Basics

[ OPC Server Ethernet Manual / Chapter 3: Communication Basics ]

3 COMMUNICATION BASICS

3.1 Job types Communication between the PC with OPC server and the PLC can be handled in several ways. The OPC server supports the following job types:

Job TypesSend DirectReceive DirectFetch Active (Read Active)Write ActiveFetch on Event Active

3.1.1 SEND / RECEIVESEND / RECEIVE means sending and receiving frames. The SEND station sends data, the RECEIVE station receives that data. The user program of the sending station supplies the source address of the data. The program of the receiving station specifies where the data will be saved. In the ISO/OSI reference model SEND / RECEIVE communication is Layer 4 based. The services of the upper layers are not required. SEND / RECEIVE communication can be handled via H1, TCP, UDP or RFC1006.

3.1.2 WRITE active / WRITE passiveThe WRITE function allows a data record to be transferred from one station (Write active) to a remote device (Write passive). In contrast to SEND / RECEIVE, the user program of the sending station supplies the source address of the data AND the data destination in the remote device. The passive end does firstly not know, how to interpret the data and what to do with it. These information must be transferred together with the raw data. Write function requires parameter transfer. The active end of the WRITE can force data on to the passive end

In the ISO/OSI reference model WRITE communication is Layer 7 based. The services of the upper layers are required. WRITE communication can be handled via H1, TCP, UDP or RFC1006. In addition to the trans-port protocols, application protocols are required.

3.1.3 FETCH active / FETCH passiveThe FETCH function allows a station (Fetch active) to read a data record from a remote station (Fetch passive). The receiving station is the active end while the sending station is the passive end, that allows data to be read. The user program of the receiving station supplies the source address of the data in the remote station AND the data destination in the own station.In contrast to a SEND job, the sending station does firstly not know what data shall be send. These informa-tion must be transferred. Fetch function requires parameter transfer. The active end of the FETCH can read a data record from the passive end

OPC

Serv

er E

ther

net

Chap

ter 3

: Com

mun

icatio

n Ba

sics


In the ISO/OSI reference model FETCH communication is Layer 7 based. The services of the upper layers are required. FETCH communication can be handled via H1, TCP, UDP or RFC1006. In addition to the trans-port protocols, application protocols are required.

3.1.4 FETCH on EVENTFETCH on EVENT function allows as the FETCH function a station to read a data record from a remote station. The receiving station is the active end while the sending station is the passive end, that allows data to be read. The user program of the receiving station supplies the source address of the data in the remote station AND the data destination in the own station.In contrast to a „normal“ FETCH job, with FETCH on EVENT, data are only transferred in the case of an event i.e. in case of changed data values. The comparison of the data is handled by the communication processor. Only in case of a value change, data is transferred via network. With „normal“ FETCH communi-cation, the requested data is transferred always, independent from the value.

3.2 ConnectionsTo exchange data between stations via Ethernet, a connection is required. A transport connection is a logi-cal connection between two access points. Typically connections must be configured on both ends of the communication. With Point-to-Point connec-tions the communication partners must agree, who establishes the connection active and passive.

Communication partner 1 Communication partner 2

OPC

Active Passive

Connection

The transport connection is based on address information that uniquely identify the transport route between the two access points. Address informations depend on used protocol. The used protocols must be under-stood by both stations.Data is transferred via Ethernet in data packets. These packets are supplemented with the addition of extra fields at the beginning and/or end of the packet (headers and trailers). These fields may include the source and destination addresses, the packet length, acknowledgement numbers and so on. For example data transferred via TCP/IP, are supplemented with a TCP header and an IP header.


munication Basics


Communication partner 1 Communication partner 2

OPC

Active Passive

H1 ConnectionMAC Address 1local TSAPremote TSAP

MAC Address 2local TSAP

remote TSAP

TCP ConnectionIP Address 1Port

IP Address 2Port

RFC1006 ConnectionMAC Address 1Port 102local TSAPremote TSAP

MAC Address 2Port 102

local TSAPremote TSAP

3.2.1 TCP/IP ConnectionsTCP/IP is not only one protocol, but a family of protocols. IP, TCP, UDP, ARP and others are part of the TCP/IP protocol family.

IP The Internet Protocol is a layer 3 protocol and is the building block of the Internet. Its functions include defining the datagram (the basic unit of transmission in the Internet), defining the Inter-net addressing scheme, routing datagrams to remote hosts and performing fragmentation and re-assembly of a datagram. To move data between hosts, IP uses IP addresses. It contains sufficient information to uniquely identify a network and a specific host on that network.IP is a connectionless protocol. This means that IP does not exchange control information (called a „handshake“) to establish an end-to-end connection before transmitting data.

TCP TCP is a layer 4 protocol. It is a connection-oriented protocol. This means that control information is exchanged with the remote system to verify that it is ready to receive data before sending it. After IP passes incoming data to the transport protocol, the trans-port protocol passes the data to the correct application process. Application processes are identified by port numbers.

UDP UDP is a layer 4 protocol. UDP is unreliable, connectionless datagram protocol. There are no techniques in the protocol for verifying that the data reached the other end of the network correctly. UDP uses port numbers to deliver data to the correct applications process.

OPC

Serv

er E

ther

net

Chap

ter 3

: Com

mun

icatio

n Ba

sics


3.2.1.1 Required Parameters for TCP connectionsTCP/IP connections use address information of IP addresses and ports.

IP Address Access to station

Port Access to application

IP Address In IP based networks, each station has an unambiguous IP address. Own IP address and destination IP address are part of the Source Address Field (resp. the Destination Address Field) of the IP header. With this additional address information stations outside the own LAN can be addressed - IP uses the network portion of the address to route the datagram between networks. The MAC header with MAC address is insufficient for it (example for an IP address: 192.0.9.4).

Port numberTCP/IP uses port numbers to pass the data to the correct application process. Port numbers are 16-bit values. The Source Port Number which identifies the process that sent the data and the Destination Port Number which identifies the process that is to receive the data are contained in the first header word of each TCP segment and UDP packet. Port numbers below 256 are reserved for „well-known-services“ (like FTP and TELNET) and are defined in the RFCs. Ports numbered from 256 to 1023 are used for other specific services. It is the combination of IP address and port number that uniquely identifies the TCP/IP connection. The combination of an IP address and a port number is called socket.

IP Address + Port number = SOCKET197.12.18.13 80 197.12.18.13, 80

STATION A

Port

IP Address A

STATION B

Port

IP Address B

3.2.2 H1 Connections The SINEC H1 is based on the specifications of the IEEE 802.3 extended with details for industrial com-munications and was developed by the Siemens AG in 1985. The term „SINEC H1“ has been replaced by the term „SIMATIC NET“. ISO 8073 is a ISO norm, that describes connection-oriented transport protocols. There are 5 protocol classes with different characteristics. H1 is a class 4 protocol.Like TCP, H1 works connection-oriented. H1 exchanges control information with the remote system to verify that it is ready to receive data before sending it. Like TCP, H1 provides data transfer between two application programs. The H1 transport protocol passes the data to the correct application process. Application proces-


munication Basics


ses are identified by TSAPs (corresponding to the port numbers with TCP). The ISO transport service does not use IP. It enables communication between stations at the same Industrial Ethernet Subnet.

3.2.2.1 Required parameters for H1 connectionsH1 connections use the address information of TSAPs and MAC addresses

MAC Address Access to station

TSAPs Access to application

MAC AddressEthernet components, that shall be targeted by messages need an unambiguous physical address, the MAC address. Own MAC address and destination MAC address are part of the Source Field (resp. the Destina-tion Field) of the MAC header of a Ethernet frame. With the MAC address a machine is unambiguously iden-tified on the network. In ISO (H1) networks the MAC addresses uniquely identify the access to the stations (example for a MAC address: 00 E0 4B 19 03 95).Station addressing is handled exclusively via MAC addresses. Therefore H1 is not routing-capable. Stations outside the own network can not be accessed.

TSAPsH1 uses TSAPs (Transport Service Access Points) to pass the data to the correct application process. For each connection a different pair of TSAPs is being used.

local TSAP identifies the transport service access point in the own system

remote TSAP identifies the transport service access point in the other system

To establish the connection, TSAPs have to correspond crosswise i.e.: local TSAP“ of station A must cor-respond with the „remote TSAP“ of Station B and „local TSAP“ of station B must correspond with „remote TSAP“ of station A.

Localer TSAP (Station A) = Remote TSAP (Station B)Remote TSAP (Station A) = Local TSAP (Station B)

TSAPs have a minimum length of 2 bytes and a maximum length of 16 bytes. It is the combination of MAC address and TSAPs that uniquely identifies the H1 connection.

STATION A

Local TSAP

Remote TSAP

MAC Adr. A

STATION B

Local TSAP

Remote TSAP

MAC Adr. B

OPC

Serv

er E

ther

net

Chap

ter 3

: Com

mun

icatio

n Ba

sics


3.2.3 RFC1006 ConnectionsTCP is a stream-oriented protocol. It is permitted to send almost any length IP packet it chooses. If two mes-sages were passed to a TCP/IP stack, the TCP/IP stack may choose to put both messages in one Ethernet frame. Alternatively it may choose to place half of the first message in the first Ethernet frame and all the rest in the next Ethernet frame. There is no EOM recognition.H1 (ISO) is a message-oriented protocol. There is EOM recognition. Messages arrive at the destination exactly in the same form they have been sent from the sender. Input block and Output block are identical.

Message-oriented H1 Stream-oriented TCP/IP

To recognize the end of a message, a blocking mechanism is required. The RFC1006 gives TCP/IP a mes-sage structure.RFC1006 (ISO Transport Service on the top of the TCP) specifies how to carry an ISO transport protocol on the top of the TCP/IP protocol. The port 102 is used for RFC1006 connections. To address stations IP addresses are used. To address applications TSAPs are used. For each connection a different pair of TSAPs is being used.

STATION A

Local TSAP

Remote TSAP

IP Address A

STATION B

Local TSAP

Remote TSAP

IP Address B


munication Basics


3.3 S5 Connections If data shall not only be read from a S5 PLC but also be written to the S5 PLC, a write connection is required besides the read connection. With the INAT OPC server only ONE connection has to be set up. Via the port number or the TSAP the read connection and the write connection are defined.

TCP/IP ConnectionStation A Station B

OPC

OPC connection- Port for Read- Port for Write

Read connection (passive)- PortWrite connection (passive)- Port

WRITE

READ

RFC1006 and H1 Connection

WRITE

Station A Station B

OPCREAD

OPC connection- Local TSAP- TSAP for Read- TSAP for Write

Read connection (passive)- Local TSAP- Remote TSAPWrite connection (passive)- Local TSAP- Remote TSAP

The connections must be parameterized on both sides of the connection (one connection for read and write in the OPC Server and two connections in the S5: one read connection and one write connection). When communicating via TCP/IP, the port for read must be the same on both sides of the connection. The same ist with the port for write: it must be the same on both sides of the connection, too. When communicating via RFC1006 or via H1, the local TSAP on the local side and the remote TSAP on the remote side must be the same. The remote TSAP on the local side and the local TSAP on the remote side must be the same.

OPC

Serv

er E

ther

net

Chap

ter 3

: Com

mun

icatio

n Ba

sics


3.4 S7 Connections When communicating with a S7 PLC, read and write jobs can be handled via one connection.

TCP/IP Connection

WRITE

Station A Station B

OPC

READ

OPC connection- Port for Read & Write

Read and Writeconnection (passive)- Port

RFC1006 or H1 Connection

WRITE

Station A Station B

OPC

READ

OPC connection- Local TSAP- TSAP for Read & Write

Read and Writeconnection (passive)- Local TSAP- Remote TSAP

When communicating via TCP/IP, the port for read and write must be the same on both sides of the connec-tion. When communicating via RFC1006 or via H1, the local TSAP (for read and write) on the local side and the remote TSAP on the remote side must be the same. The remote TSAP (for read and write) on the local side and the local TSAP on the remote side must be the same.

Reading of data from a S7 PLC and writing of data into a S7 PLC (Layer 7 communication) is handled via:

NOT PARAMETERIZABLE CONNECTIONS (Standard connections)PARAMETERIZABLE CONNECTIONS


munication Basics


3.4.1 Not parameterizable connections (Standard connections)Standard connections are connections, that are pre-parameterized on PLC side. For that reason, the con-nection must only be set up on OPC side and NOT on PLC side. Standard connections use standard TSAPs or standard ports. The number of standard connections is limited. If there are not enough standard connec-tions available, parameterizable connections must be used. Siemens communication processors handle standard connections via RFC1006 or H1. Normally the standard connections are sufficient.

3.4.2 Parameterizable connections The connection must be parameterized on both sides of the connection (one connection for read and write in the OPC Server and one connection in the S7).

3.5 Modbus Connection A Modbus connection is used to communicate with PLCs, that support the Modbus on TCP protocol (Groupe Schneider, Phoenix, Wago, Beckhoff etc.). The Modbus protocol can only be used with TCP/IP. Read and write jobs can be handled via one connection.

TCP/IP Connection

WRITE

Station A Station B

OPC

READ

OPC connection- Port for Read and Write

Read and Writeconnection (passive)- Port for Read and Write

The port for read and write must be the same on both sides of the connection. When using the port 502, the connection must only be set up on OPC side and NOT on PLC side. Besides the IP address and the port number, the Unid ID of the target device is required.

OPC

Serv

er E

ther

net

Chap

ter 3

: Com

mun

icatio

n Ba

sics


3.6 NetLink Connection A NetLink Connection is used to communciate with a S7 PLC that is connected to Ethernet via NetLink or IBHLink adapter. The NetLink protocol can only be used with TCP/IP. Read and write jobs are handled via one connection.

TCP/IP Connection

WRITE

Station A Station B withNetLink adapter

OPC

READ



The port for read and write must be the same on both sides of the connection. When using the standard port 1099, the connection must only be set up on OPC side and NOT on PLC side. Besides the IP address and the port number, the MPI address of the target device is required.

3.7 PLC-5 Connection When communicating with a PLC-5, read and write jobs can be handled via one connection. PLC-5 connec-tions use TCP/IP as transport protocol.

TCP/IP Connection

WRITE

Station A Station B

OPC

READ



The port for read and write must be the same on both sides of the connection. When using the port 2222, the connection must only be set up on OPC side and NOT on PLC side.


munication Basics


3.8 MELSEC-Q Connection A Melsec-Q connection is used to communicate with a Mitsubishi PLC of the Melsec-Q series. The Melsec-Q protocol can only be used with TCP/IP. Read and write jobs can be handled via one connection. The connection must be parameterized on both sides of the connection. In the OPC server one conenction for read and write is required. In the Melsec-Q PLC one passive receive connection and one passive send connection must be set up. The port for read and write must be the same on both sides of the connection.

TCP/IP Connection

WRITE

Station A Station B

OPC

READ



Standard connections may be used too. The connection must only be set up on OPC side and NOT on PLC side. Refer to the manual of your PLC to find out which port number is used as standard port. This port must be used as port for read and write with the OPC connection.

C H A P T E R 4 :C O N F I G U R AT I O N

OPC Server EthernetChapter 4: Configuration

[ OPC Server Ethernet Manual / Chapter 4: Configuration ]

4 CONFIGURATION The INAT OPC server requires very small amount of configuration to function properly.

4.1 Required steps for OPC Communication

Set up connection(Define Access Path)

OPC Server Configuration

Server Settingsoptional

optional Server Optimisation

Server Optionsoptional

Connect OPC Serverand OPC Client

1

2

Define / Import symbolsoptional

OPC Client Configuration

Add OPC Group

3

Add OPC Item

Read / Write

DCOM Configurationoptional

1. OPC Server Configuration For each hardware that shall be accessed for read and/or write, a connection must be set up in the OPC server. The connection defines the access path to the hardware.Users can change certain aspects of the server´s behaviour. All these options and settings are descri-bed in this chapter.

2. Connect OPC Server and OPC Client Server and Client must be connected to communi-cate with each other. This is described in chapter 6.

3. OPC Client ConfigurationIn the OPC client you add OPC groups and items. The handling of an OPC client is described in chapter 6.

OPC

Serv

er E

ther

net

Chap

ter 4

: Con

figur

atio

n


4.2 Setting up a new connectionFor each hardware that shall be accessed for read and/or write, at least one connection must be set up in the OPC server. The connection defines the access path to the hardware.The number of TCP/IP connections ist NOT limited. The maximum number of H1 connections is set to 64 in the default setting. With a registry entry, this number can be increased (see chapter 2.2.1 „Change number of H1 connections“).

To set up a new connection, follow these steps: ● Start the OPC server ● If the server runs as local executable, the main window of the server appears together with the about

box. The about box is closed after a few seconds automatically. ● If the server is installed as service and you start it for the first time, you hear a signal and the server icon

is indicated in the task bar. To configure the server, select Start > Programs > INAT > OPC Server Ether-net > OPC Server Ethernet or double-click the icon. The main window of the server appears.

● Choose „Access Path Definitions“ from the Configuration menu.

● The Access Path Definitions are used to create a new access path, to modify an existing access path or to delete an existing access path. To create a new one choose „New“ from the Configuration menu.

● The following entries are required:



NameEnter a name for the connection. This access path name will be used in the OPC client later, too. Type of ConnectionSelect the used transport protocol H1 (ISO) or TCP/IP. When com-municating via RFC1006 select TCP/IP.Type of ProtocolSelect the used application protocol S5, S7, Modbus, NetLink, PLC-5 or Melsec-Q. If NO high-level protocol shall be used, select Send / Receive. In this case raw data is transferred.

● Confirm with „OK“.● The TCP/IP Parameter window or the H1 Parameter window appears

TCP/IP Parameter Settings H1 Parameter Settings

OPC

Serv

er E

ther

net

Chap

ter 4

: Con

figur

atio

n


4.2.1 Edit TCP/IP Parameters

4.2.1.1 Allow Cyclic Poll / Poll intervalIf this selection is checked, data are updated cyclically. The frequency for updates is configured as poll interval. If this selection is unchecked, data are no longer updated cyclically. In this case the client must ask for the update. The poll interval (read interval) function specifies in milliseconds the intervals at which user data is updated. To keep the network load as low as possible, the intervals should be based on the importance of the particu-lar user data. The value „0“ indicates that the server reads as fast as possible.

4.2.1.2 Write access to PLC permittedSpecifies whether a write connection to the PLC is to be established. Write accesses can be disabled in general here.

4.2.1.3 Read and Write through one connectionRead and write thorugh one connection is possible with all protocols except to the S5 protocol. With TCP/IP only one port is required for read and write. With RFC1006 only one TSAP for read and write is required.

S5 ProtocolSiemens S5-CPs, INAT S5-TCP/IP:

It is NOT possible to read and write through one con-nection. One connection is required for the read job and another connection is required for the write job. One port number (or TSAP) for read and one port number (or TSAP) for write is required.

echolink It is possible to read and write through one connection.

4.2.1.4 Unsolicited Data from PLCThe server supports unsolicited data from the PLC with S5 connections and Send/Receive connections. Therefore a separate channel is assigned. A separate „Port for Unsolicited“ („TSAP for Unsolicited“ with RFC1006) is required for this channel.

4.2.1.5 Fetch on EventFetch on Event is possible with S5 connections and S7 connections, when using INAT communication pro-cessors S5-TCP/IP, S5-TCP/IP-100 and S7-TCP/IP. If Fetch on Event is activated, data from the PLC will no longer be polled cyclically, but transferred if a event occurs. Fetch on Event is handled via the read connection. With cyclic polling, the OPC server compares the received data with the previously received data. If there is a change, data is sent to the client. In opposite to this comparison by the server, with Fetch on Event, the comparison is handled by the CP. Only in case of a data change, data is transferred via network to the Server.



Advantages: - Data are only sent in case of an event- Cyclic poll is no longer required- Network traffic is reduced

4.2.1.6 Write Single Coil / Write Single Register (only with Modbus)If your Modbus device does not provide opcode „Write Multiple Coils (15)“ activate „Write Single Coil (05)“. If your Modbus device does not support opcode „Write Multiple Registers (16)“ actiavte „Write single register (06)“.

4.2.1.7 Start Address 1 / Start Address 0 (only with Modbus)Address spaces of Modbus devices are 0-based or 1-based - depending on manufacturer. Select 1 if your device interprets the base address with a starting offset of 1. Select 0 if your device interprets the base address starting at zero.

4.2.1.8 Destination: IP Address or nameEnter the IP address of the destination device (PLC, CP) here. A symbolic name can also be entered in this field if the computer is configured for DNS and a DNS server is available in the network to convert this symbolic name to an IP address.

4.2.1.9 Unit ID (only with Modbus)The Unit ID is the slave address of the target device.

4.2.1.10 MPI/PPI address (only with NetLink)Enter the MPI address of the target S7-400/300 or the PPI address of the target S7-200.

4.2.1.11 No HeaderWhen communicating with stations, that support „only“ the pure TCP/IP protocol „no header“ should be used. The application program on both sides is responsible for monitoring.

OPC

Serv

er E

ther

net

Chap

ter 4

: Con

figur

atio

n


4.2.1.12 Use PLC Header Select the PLC Header when communicating with INAT devices (S7-TCP/IP, S5-TCP/IP, echolink).

4.2.1.13 Use RFC1006With the activation of RFC1006 H1 frames are implemented in a TCP/IP frame. With that sepcial TCP/IP channel you communicate with the Siemens CPs of the S5 and S7 series. To configure the TSAPs click the button „ISO on TCP (RFC1006)“.

4.2.1.14 Local TSAP / remote TSAPThe local TSAP (Transport Service Access Point) is the address of the local application. The remote TSAP is the address of the remote application. To establish the connection the TSAPs must be the same crosswise. The local TSAP of station A and the remote TSAP of station B must be identical. The remote TSAP of station A and the local TSAP of station B must be identical.

OPC Server

PLC

Local TSAP Remote TSAP

Remote TSAPLocal TSAP

The remote TSAPs are: • TSAP for Read • TSAP for Write• TSAP for UnsolicitedThese three TSAPs should not be the same. TSAPs have a length of at least 2 bytes and a maximum length of 16 bytes. When communicating with S7 PLCs, typically standard TSAPs are used.

Standard TSAPs for S7 Connections With „not parameterizable connections“(= standard connections), standard TSAPs are used:



First Groupcontains device codes, for which ressources are provided in the S701: PG or PC02: OS (MMI device)03: e.g. Simatic S7 PLCSecond Groupcontains the addresses of these componentsLeft Character (Bit 7....4): Rack number multiplied by 2Right Characteren (Bit 3...0): Slot (< 16) of the CPU. For S7-300 always slot 2 is used

Standard TSAPs must be used on PLC side (remote TSAP of the OPC server station). Local TSAP (own TSAP of the OPC server station) ist arbitrary. It should contain the same format (e.g. 01 00)

Examples:01 00 PC with OPC server; direct addressing 03 43 OPC communication with S7 CPU in rack 2, slot 3 03 02 OPC communication with S7 CPU in rack 0, slot 203 2E OPC communication with S7 CPU in rack 1, slot 14

NOTE: Enter the standard TSAPs in the HEX field! The remote TSAP of S7 connec-tions is always 03 XY. X is the rack number multiplied by 2 and Y is the slot of the CPU.

Routing TSAPsWith the OPC Server Routing is possible. Routing ensures OPC communication transcending networks. OPC communication is possible with alle S7 stations, that can be reached via route stations. It is irrelevant how many route stations and networks are situated between the start device (OPC Server) and the target device. For Fetch / Write communication only on OPC side a connection must be configured. Information about the target network and the target device are required.

OPC

Serv

er E

ther

net

Chap

ter 4

: Con

figur

atio

n


Destination PLCParameters of the target device must be entered here.

S7 Subnet IDSpecify the S7 Subnet ID of the target network. You will find the subnet ID in the object properties of the subnet in the Step 7 project. The subnet ID consist of 2 numbers separated by a dash (one number of the project and one number of the subnet).

MPI/Profibus AddressIn case of a MPI subnet, enter the MPI address of the PLC. In case of a Profibus subnet enter the Profibus addresse.

Slot AddressEnter the slot number, where the CPU is located. With S7-300 systems, the CPU is always located on slot 2.

Service Service „3“ should be used for OPC communication.

First transition from Ethernet to MPI is echolinkIf you are using echolink that connects Industrial Ethernet with the subnet, check this button. Parameters of the Routing PLC must be entered here.

echolink

ETHERNET

OPC

Routing PLC

Target PLC

MPI (CPU) = 2MPI (CP ) = 3

PROFIBUS

Profibus = 6

Profibus = 2



COM PortEnter the Com Port of the echolink that is connected with the MPI interface of the S7 PLC.

Routing PLCThe Routing PLC is the S7 PLC, that is connected with the echolink via MPI. This PLC is the first transition from Induastrial Ethernet to MPI. Enter the MPI address of the routing device here (MPI address of the CPU or the CP).

NOTE: Some communication processors have a MPI address for backplane connec-tion. This address is assigned by the CPU. If such a CP is used, make sure to use the MPI address of the CP and not the MI address of the CPU.

MPI Address of the Routing PLCYou will find the MPI address of the Routing PLC in the object properties of the station in the Step 7 project. Is there is a MPI address (CPU) and a MPI address (CP), use the MPI address of the CP.

In the hardware configuration the address is available under „Backplane Connection“.

Generate TSAPsPress the button „Generate TSAPs“ when all settings are made. The TSAPs are generated and indicated.

4.2.1.15 MPI/PPI Parameters (only with NetLink and activated High Performance Protocol)In case of a MPI subnet enter the slot of the CPU and the service (service „3“ should be used for OPC com-munication). In case of a PPI subnet select the baudrate of the PPI interface.

OPC

Serv

er E

ther

net

Chap

ter 4

: Con

figur

atio

n


4.2.1.16 Port for Read, Port for Write, Port for Unsolicited The port number is a 16 bit number between 1 and 65535. The port number is the channel number via which a connection is identified. Port numbers between 1 and 1023 should not be used. The „Port for Read“ specifies the channel number via which the read-access is established. The „Port for Write“ specifies the channel number via which the write-access is established. Finally the „Port for Unsoli-cited“ specifies the channel number via which unsolicited data from the PLC are transferred. Port for Read, Port for Write and Port for Unsolicited should not be the same.

NOTE

To be able to establish the connection, the Port number must be the same on both sides of the connection.

4.2.1.17 Life ACKs, Life Data ACKsThis item activates the connection monitoring function which is restricted in many socket libraries. These frames are used to transfer the connection status to process visualization. If you are using the OPC server in a LAN with networked controllers, we recommend activating both functions. If the connection is being handled by a WAN, we recommend deactivating these functions. The default setting of the life acks and data life acks is ”activated”.

4.2.1.18 Connection Establishment active / passiveConnection Establishment specifies whether the own station actively initiates connection establishment or passively waits for the connection to be established by the other station. The same value may not be ente-red for both sides of the connection. The PC is usually parameterized active. This is also the default value.

4.2.1.19 Protocol TCP/UDPTCP (Transmission Control Protocol) is a secure protocol with checksum and confirmation. UDP (User Datagram Protocol) is not a secure protocol. It is handled by datagram services. The TCP protocol should be selected for normal data transmission.

4.2.1.20 Read Optimisation Here you may optimise read accesses to the hardware. If several variables which are not in the same operand area (e.g. in one data block, flag area, register area) shall be accessed, without read optimisation the complete area is read - from the first variable to the last variable. Even gaps within this area are read, no matter how long they are. Edit here which maximum length (in bytes) the gap may have between the desired items, without creating a new block. If the gap is longer, a new block is created.

4.2.1.21 High Performance Protocol(only with S7, NetLink, Modbus, PLC-5 and MELSEC-Q)With activation of the High Performance Protocol, acceses to variables, that are NOT part of the same ope-rand area, are combined (e.g. DB5.W3 + MW1 + T2 etc.) internally to one access. The number of data pak-kets transferred via the network is reduced. Therefore the best performance can be achieved in this mode.

NOTE:With INAT S7-TCP/IP the High Performance Protocol may not be used.



4.2.2 Edit H1 Parameters

4.2.2.1 Allow Cyclic Poll / Poll intervalIf this selection is checked, data are updated cyclically. The frequency for updates is configured as poll interval. If this selection is unchecked, data are no longer updated cyclically. In this case the client must ask for the update. The poll interval (read interval) function specifies in milliseconds the intervals at which user data is updated. To keep the network load as low as possible, the intervals should be based on the importance of the particu-lar user data. The value „0“ indicates that the server reads as fast as possible.

4.2.2.2 Write access to PLC permittedSpecifies whether a write connection to the PLC is to be established. Write accesses can be disabled in general here.

4.2.2.3 Read and Write through one connectionRead and write thorugh one connection is possible with all protocols except to the S5 protocol. With TCP/IP only one port is required for read and write. With H1 only one TSAP for read and write is required.

S5 ProtocolSiemens S5-CPs, INAT S5-TCP/IP:

It is NOT possible to read and write through one con-nection. One connection is required for the read job and another connection is required for the write job. One port number (or TSAP) for read and one port number (or TSAP) for write is required.

echolink It is possible to read and write through one connection.

4.2.2.4 Unsolicited Data from PLCThe server supports unsolicited data from the PLC with S5 connections and Send/Receive connections. Therefore a separate channel is assigned. A separate „Port for Unsolicited“ („TSAP for Unsolicited“ with H1) is required for this channel.

4.2.2.5 Fetch on EventFetch on Event is possible with S5 connections and S7 connections, when using INAT communication pro-cessors S5-TCP/IP, S5-TCP/IP-100 and S7-TCP/IP. If Fetch on Event is activated, data from the PLC will no longer be polled cyclically, but transferred if a event occurs. Fetch on Event is handled via the read connection. With cyclic polling, the OPC server compares the received data with the previously received data. If there is a change, data is sent to the client. In opposite to this comparison by the server, with Fetch on Event, the comparison is handled by the CP. Only in case of a data change, data is transferred via network to the Server.

OPC

Serv

er E

ther

net

Chap

ter 4

: Con

figur

atio

n


Advantages: Data are only sent in case of an eventCyclic poll is no longer requiredNetwork traffic is reduced

4.2.2.6 Destination: Ethernet AddressEnter the Ethernet address (MAC address) of the destination device (PLC, CP) here. Enter the number of the ethernet adapter, that is connected to the ISO (H1) network.

4.2.2.7 Local TSAP / remote TSAPThe local TSAP (Transport Service Access Point) is the address of the local application. The remote TSAP is the address of the remote application. To establish the connection the TSAPs must be the same crosswise. The local TSAP of station A and the remote TSAP of station B must be identical. The remote TSAP of station A and the local TSAP of station B must be identical.

OPC Server

PLC

Local TSAP Remote TSAP

Remote TSAPLocal TSAP

The remote TSAPs are: • TSAP for Read • TSAP for Write• TSAP for Unsolicited



These three TSAPs should not be the same. TSAPs have a length of at least 2 bytes and a maximum length of 16 bytes. When communicating with S7 PLCs, typically standard TSAPs are used.

Standard TSAPs for S7 Connections With „not parameterizable connections“(= standard connections), standard TSAPs are used:

First Groupcontains device codes, for which ressources are provided in the S701: PG or PC02: OS (MMI device)03: e.g. Simatic S7 PLCSecond Groupcontains the addresses of these componentsLeft Character (Bit 7....4): Rack number multiplied by 2Right Characteren (Bit 3...0): Slot (< 16) of the CPU. For S7-300 always slot 2 is used

Standard TSAPs must be used on PLC side (remote TSAP of the OPC server station). Local TSAP (own TSAP of the OPC server station) ist arbitrary. It should contain the same format (e.g. 01 00)

Examples:01 00 PC with OPC server; direct addressing 03 43 OPC communication with S7 CPU in rack 2, slot 3 03 02 OPC communication with S7 CPU in rack 0, slot 203 2E OPC communication with S7 CPU in rack 1, slot 14

NOTE: Enter the standard TSAPs in the HEX field! The remote TSAP of S7 connec-tions is always 03 XY. X is the rack number multiplied by 2 and Y is the slot of the CPU.

OPC

Serv

er E

ther

net

Chap

ter 4

: Con

figur

atio

n


4.2.2.8 Active / Passive connection establishment for Unsolicited For the mode „Unsolicited Data from PLC“ the connection establishement active or passive can be chosen independently from the connection establishement of read and write connections. Background information: Several CPs can be parameterized only active for send jobs.

4.2.2.9 Line Type Specifies whether the frames of this connection will be sent to all stations (i.e., broadcast) or only to certain groups of stations (i.e., multicast), and whether a secure (i.e., normal) or non-secure connection is to be used to transfer the data (i.e., datagram). „Normal“ is usually set here.

4.2.2.10 Multicast NumberSpecifies that the device to be parameterized belongs to a certain group of stations which are to be reached when a Multicast connection is used. The multicast circle window only applies when Multicast has been selected as the type of line.

4.2.2.11 PriorityPriority is a value from 0 (i.e., highest priority) to 4 (i.e., lowest priority). 0 and 1 are the so-called express priorities while 2 and 3 are the normal priorities. Priority 4 is seldom used since the connection must be reestablished for each sending job. If not used often, this priority puts less strain on the network load than the other priorities since the line is not monitored (i.e., the connection is disconnected after each sending job). Remember that the express priorities do not increase the transmission speed any more than the normal priorities. For some controllers, the data are transferred to the RAM with an interrupt when priority 0 is used. This may increase the speed of the total data transmission. When priorities 0 and 1 are used, the data length may not exceed 16 bytes. Priority 3 is usually used here.

4.2.1.12 Read Optimisation Here you may optimise read accesses to the hardware. If several variables which are not in the same operand area (e.g. in one data block, flag area, register area) shall be accessed, without read optimisation the complete area is read - from the first variable to the last variable. Even gaps within this area are read, no matter how long they are. Edit here which maximum length (in bytes) the gap may have between the desired items, without creating a new block. If the gap is longer, a new block is created.



● If all entries are made, select the button „OK“. The new access path is indicated in the connection window.

● Set up a new connection. Otherwise close the window.

● Select „Yes“ to save the configuration in the configuration file tcpiph1.NET in the root directory of the server (see chapter 4.5.2 „Configuration file“).

NOTE

Reboot your system!

4.3 Shutting down the OPC ServerIf the server runs as local executable, click the „Exit“ Button in the main window or choose „Exit“ from the Configuration menu to shut down the server. If you choose „Exit“ from the Configuration menu while the server runs as service, the configuration over-view of the server is closed. The server continues running as service (the server icon is still indicated in the task bar). The service can be shut down by choosing „Stop service“ from the Configuration menu.

OPC

Serv

er E

ther

net

Chap

ter 4

: Con

figur

atio

n


4.4 Alias Configuration The INAT OPC Server provides the ability to create user-defined aliases that can be used in place of regular OPC items. This is particularly useful when the item path for a given server is very complex or difficult to remember. The aliases are stored in a symbol file, that is imported every time the server starts. To create an alias, choose „Edit symbols“ from the View menu.

The standard Windows editor is opened

Each parameterized connection ist indicated here in brackets with the appendix „ALIASES“ in parentheses.

Syntax: [Access Path Name(Aliases)]Example: [PLC1(Aliases)]

In this example the Access Path Name is „PLC1“.

Now for each access path the variables in the PLC can be assigned a symbol name.

Syntax: Alias Name=AddressExample: speed=db5,W2

In this example the alias „speed“ represents the OPC item db5,W2All aliases are stored in the file tcpiph1.txt (default: C:\Programs\INAT\OPC Server Ethernet). The aliases are now available in the symbol view of the OPC server as well as with the browsing function of your OPC client (provided that the OPC client supports alias browsing). It is usually better to create aliases in groups rather than directly under the root.

Syntax: GroupName.Alias Name=AddressExample: Group1.speed=db5,W2



Symbol file Symbol view

4.4.1 Import Step 7 Symbols It is possible to import symbolic names from Step 7 to the symbol file of the OPC server. ● Choose „Step7 Symbol Import“ from the View menu.

● Select the S7 project.

● In the S7 Project select one of the S7 programs and appoint this program to a configured access path.● After selection of a valid program and the corresponding access path the button „Import Symbols“ beco-

mes active.

Symbol Table All symbolic names are imported.

DBs: Symbolic names of the data blocks are imported.

Arrays: In addition arrays are resolved. Please note, that this enlarges the symbol file of the OPC server.

● You will find the imported items in the symbol file „tcpiph1.txt“.

OPC

Serv

er E

ther

net

Chap

ter 4

: Con

figur

atio

n


4.4.1.1 Import Step 7 symbol comments Symbol comments can be imported as well. Therefore the following entry is required in the Win.ini:

AllowS7CommentImport=1

The comments are imported to the symbol file like „normal“ items (in addition to the symbolic name of the item).

Syntax: [Connection name(ALIASES)] Alias=Address Alias-comment=comment

Example: [PLC1(ALIASES)] Motor1.ON=M1.1 Motor1.ON-comment=This flag starts the motor

4.5 Server Settings

4.5.1 Protocol Timer TickHere you change the frequency at which the server checks for work to do. At this frequency the server tries to send one request command to the device (PLC) and tries to receive one response.

4.5.2 Configuration fileAll parameterized connections are stored automatically in a configuration file. The default path of the configuration file is c:\Programs\INAT\OPC Server Ethernet and the file name is TcpIpH1.NET. This path is automatically stored in the WIN.INI file. The server will use this path to load the configuration file the next time it is started.

NOTE

Note: The name of the configuration file MAY NOT be changed. The name TcpIpH1.net must be used.

4.5.2.1 Changing the path of the configuration fileTo change the path of the configuration file, choose „Server Settings“ from the configuration menu. Enter the complete path of the directory, where the file shall be stored or select the desired directory with the browse button. Restart the Server.

4.5.2.2 Save several configuration filesThere is no limit to the number of configuration files created, although each must be in a separate directory. To start the server with another configuration file than the one selected under „Configuration File Directory“, enter in the command line:tcpiph1.exe /d:[Path] (Mind the space between .EXE and /d). Example: tcpiph1.exe /d:C:\Data\Project1 if the configuration file is stored in C:\Data\Project1 or shall be created here.



4.5.3 Data types The settings for the default data format of the OPC items can be changed here. In PLC programs data types like BYTE, WORD or S5TIME are used. In contrast OPC works with so-called variant types. The data type from the PLC program is mapped to variant tpyes. For example the OPC item DB5.W3 (S7 Syntax, data type WORD) is mapped to the variant type VT_I4. The item syntax tables show how S7 and S5 data types are mapped to variant types. When creating OPC items, client applications can specify a requested data type for each item. The OPC server will attempt to convert any data from the item to this format if possible.

Compatibly to versions V1.22:This mode does not support arrays. Select this mode if you want to use older applications with the recent version of the OPC server.

Also unsigned: Select this mode if your client supports unsigned data types VT_UI2 and VT_UI4.

Only Standard types:This is the default setting and should be used with most clients. It is used if your client does not support unsigned data types VT_UI2 and VT_UI4.

4.5.4 Echo Written Data back to ClientIf a constant value in the PLC is overwritten by a client, it depends on the client, which of the values is dis-played in the server.Button not checked: The last read value is indicated (default); The button should not be checked when using the client iFIX.Button checked: The last written value is indicated. The button should be checked when using the client WinCC or WIZCON.

4.5.5 Show Server Icon in the task barIf this selection is checked, the OPC server will be displayed as an icon in the task bar when the main window is minimized.

OPC

Serv

er E

ther

net

Chap

ter 4

: Con

figur

atio

n


4.6 Server Optimisation

4.6.1 Combine coherent blocks always (max)This optimisation mode is the maximum form of optimisation. It is very useful and is set active on default because:a) less PLC frames are transmitted, and thererforeb) the network traffic is reduced!If a counter increments very fast, only the last value (or the recent value) is written to the PLC

4.6.2 Chronological Order is preservedThe items are queued in chronological order and are written to the PLC after the read access to the cor-responding data block was successful. Coherent blocks are combined but overlapping items are written separately. Single bits of a word are also written separately. That performance provides a secure forwarding of data to the PLC even if a bit is resetted and deleted in very short time intervals. The correct data flow is provided.

4.6.3 Write every item separately (off)In this case the optimisation is off. The data handling corresponds with the process under „Chronological order is preserved“.

4.6.4 Write with Priority, Chronological Order is PreservedWrite jobs are handled with higher priority. If there is a read job, it is followed through. Then writing is initiated at once. If there are several Items in the data block to be written, they are written in chronological order.The data block is read again, to give the user an immediate acknowledgement. If there are Items of another data block to be written, the write job is initiated at once and is handled as described above.With this write optimisation, deceleration with writing does no longer apply. Inching operation via keyboard or mouse is possible.

4.6.5 Writes with immediate positive Confirm (default: No)Waiting for confirmation may block the client. In this case the optimisation „Writes with immediate positive confirm“ is recommende. The user does not the receive the effective result of the write job, but a positive confirmation.

4.6.6 Read between Write (default: No)Please note, that reading between writing affects the performance of the server.



4.7 Server Options

4.7.1 String FormatThere is a difference between S5 and S7 strings.

S7 string: contains in the first byte the maximum length and in the second byte the current length of the stringS5 string: contains no length information

The syntax for S5 strings and S7 strings is the same (DBxSy.z). You define, to interpret the string format as S5 string or as S7 string. As default with S5 connections a string is interpreted as S5 String and with S7 connections it is interpreted as S7 string. You can change this setting and interpret all strings as S5 string. The following syntax is possible

S7 syntax: db9.STRING0.10S5 syntax: db9s0.10S7 string: db9g0.10 (forces a S7 string always)

4.7.2 TimeoutsAppTimeout [ms]: Timout for disconnection, if the partner station does not respond (multiplied with the factor App Count 3).Connection Timeout [ms]: Timeout, until quality „BAD“ is sent to the client. The message is sent immediately to the client (therefore default value is 0).

OPC

Serv

er E

ther

net

Chap

ter 4

: Con

figur

atio

n


4.8 H1 Station AddressIn this dialog you are able to display the status of the network adapter and to change the current runtime address if necessary.

Hardware AddressThe hardware or Ethernet address of your network adapter is stored in a ROM Chip on your adapter card.Runtime AddressOn default the field runtime address shows the same value as the hardware address field.Software AddressIn order to link your PC to an existing network, it may be necessary to change the hardware address according to the current network address structure. Enter the new Ethernet address in the dialog field software address. With the registry entry „H1ChangeAddress.reg“ overwriting the MAC Address during runtime is possible (see chapter 2.1.1.2). Set at program startup / Set nowWith the button „Set now“ the new address is active immediately. Choose the option „Set at program startup“ to change the current address with the next program startup.

NOTE

Mind to use the selected Ethernet address in a network only once! Mind that there are no running connections.

Driver Installation The driver installation display shows you the status of the H1 driver. Three messages are possible: „The installed H1 driver is up and running.“„No H1 protocol installed.“„The installed H1 driver is not licensed.“



4.9 DCOM Configuration DCOM is an object protocol that enables COM components (such as OPC clients and servers) to communi-cate directly with each other across a network. A certain amount of configuration is required on the system where the OPC server is installed to allow remote clients to connect to it over the network.

NOTE

The following steps are suggestions only. Ask your Windows NT System Administrator for more information about the settings that you should use, especially between different domains.

Start the DCOM configuration utility either from the server configuration utility or from the command-line (DCOMCNFG).

The main window for DCOMCNFG allows the user to either configure default settings for all COM servers or else to configure settings for a specific server chosen from the list. The former will affect all servers configu-red to use the default settings. The latter will affect the selected server only.

4.9.1 UserWORKGROUP DOMAINIn a workgroup users that login on the client and the server computer must be known on the other computer.

In a domain, a group with all OPC users should be created.

4.9.2 Computer properties for client and server machineBrowse to Console Root > Component Services > Computers and right click on My Computer. Select Pro-perties.

With General“, „Options“ and „MSDTC“ the default settings are used.

OPC

Serv

er E

ther

net

Chap

ter 4

: Con

figur

atio

n


Default PropertiesSettings for Domain

WORKGROUP DOMAINEnable DCOM on this computer Enable EnableDefault Authentication Level None ConnectStandard Impersonation Level Anonym Identify

Default Protocols

On the Default Protocols Tab the Connection-oriented TCP/IP protocol should be moved to the top position.



Default Security

Click the Button „Edit Default“ Access should be allowed for ● System● Network● Interactive● User (OPC Group)

4.9.3 OPC Server Settings for Server PCBrowse to Console Root > Component Services > Computers > My Computer > DCOM Config to display all DCOM server applications. Select INAT TCPIPH1 OPC Server and right click on it.

OPC

Serv

er E

ther

net

Chap

ter 4

: Con

figur

atio

n


Allgemein

Authentication Level: Default

Location

On the server specific Location Tab select „Run application on this computer

Identity

The identity is set to „interactive user“



Security

Select „Customize“ and click „edit“ to define users and goups. The following users and groups should have Launch, Access and Configuration Permisson.

● System● Network● Interactive● The users (OPC Group)

OPC

Serv

er E

ther

net

Chap

ter 4

: Con

figur

atio

n


4.10 Main windowThe main window of the OPC server shows you the status of all access pathes during runtime.

ROW 1

Access Path

Name of the connectionThe state of the connection is indicated beside the connection name, separated by a hyphen. OK: The connection to the communication partner is established and works. The connection is indicated in black colour. ERR: The connection to the communication partner is faulty. No data is transferred. The connection is indicated in red colour. Read: / WriteEach Read connection (Fetch) as well as each Write connection has a runtime number. Referring to these values you identify the entries of the OPC server logger. 0: the connection is not used1 to 999: H1 connections> 1000: TCP/IP connectionsThe number after the hyphen shows the connection state. An overview of all pos-sible error codes is given in chapter 5.7.9 under WriteStatusMsg / connection errors.Example: 3: WAIT_CONNECT



ROW 2

SendNewValue:Number of items, which are written from the OPC client to the OPC server up to now. If the writing speed of the OPC client is very fast, the OPC server optimizes and writes only the last written value to the PLC. Due to this procedure a difference between the values written from the client to the server and the values written from the server to the hardware can occur. WriteItemCount:Numer of values, which are written from the OPC server to the hardware up to now. WriteItemCount corresponds with the logger entry ShowSend. RecNewValue:Number of items which were written from the OPC server to the OPC client up to now. Since the data are transferred from the server to the OPC client only in case of a value change, this value is an important clue for the OPC / OPC traffic. Internally, the OPC server tries to keep the data items at least as „fresh“ as indicated in the update rate. However, the server will send values to the client no faster than the update rate in order to avoid overwhelming it. RecNewValue corresponds with the logger entry Show Rec Values. RecMsg:Number of frames, which the server has read from the PLC up to now. How often the server reads is defined with the poll interval. RecMsg corresponds with the logger entry Show Receive. ServerCycle:Number of complete cycles of the OPC server for this connection.

Ex ROW 3IdentificationData area (e.g. DATA BLOCK, FLAG, INPUT, OUTPUT etc.) Green: the interval is being processedGrey: no data are being requested Red: the data area is not available or too shortLen: Specifies the number of elements to be readItems:Specifies how many items are contained in this read interval and how many of them are active and/or inac-tive

OPC

Serv

er E

ther

net

Chap

ter 4

: Con

figur

atio

n


4.11 LoggingWith the logger function of the server the entire data traffic of the current OPC communication can be moni-tored. This is helpful with troubleshooting. The logger starts automatically, as soon as OPC communication starts. The record is available with View > Logger. With Logger > Delete all logger entries are deleted.With Logger > Settings the following settings are available:

Date each event is presented with its date.Time each event is presented with its time.Cursor at the end the logger shows always the last message at the end of the list.

With the default setting, the logger includes only errors for recording. Which information is logged can be defined with a click on the right mouse button in the headline of the main window.

The following information can be logged:



ShowEventsDetailed information that helps with troubleshooting. ShowSendNumber of values, which were written from the server to the PLC up to now. Corre-sponds with „WriteItemCount“ in the main window.ShowReceiveNumber of frames, which the server has read from the PLC up to now. Corresponds with „RecMsg“ in the main window.Show Poll Send and ReceiveRecords the PLCs response times. If “Show Send” or “Show Receive” are selected and „Show Poll“ is not active, the logger entries are reduced drasticallyShow ErrorsCorresponds with the connection error for read and write in the main window. ShowCreate PointShows the sum of items, which were created for this connection in the OPC client and were registered in the server.ShowActivate PointSum of items, which are active for this access path at the moment. Show Access PathShows the connections, which are triggered by the OPC client.Show Rec ValuesNumber of items which were written from the OPC server to the OPC client up to now. Since the data are transferred from the server to the OPC client only in case of a value change, this value is an important clue for the OPC / OPC traffic. Internally, the OPC server tries to keep the data items at least as „fresh“ as indicated in the update rate. However, the server will send values to the client no faster than the update rate in order to avoid overwhelming it. Show Rec Values corresponds with RecNewValue in the main window. Show Send ValuesNumber of items, which were written from the OPC client to the OPC server up to now. If the writing speed of the OPC client is very fast, the OPC server optimizes and writes only the last written value to the PLC. Due to this procedure a difference between the values written from the client to the server and the values written from the server to the hardware can occur. Show Send Values corresponds with Send-NewValue in the main window. Show SymbolsSymbol file information is logged.VerboseActivates or deactivates all logger entries, respectively.

OPC

Serv

er E

ther

net

Chap

ter 4

: Con

figur

atio

n


4.11.1 Save the Logging Settings Your setting which events shall be logged can be saved with „Save Logging Menu to Win.ini“. With the next start of the server this setting is used. If you do not save your settings, the next time the server starts it logs only „ShowErrors“.

4.12 Suspend and resume the OPC ServerClick the icon in the headline of the main window.

Suspend ProtocolThis is the „emergency exit“ of the OPC server. With „Suspend“ the running OPC server communication is stopped and idled with the current settings. Resume Protocol„Resume Protocol“ restarts stopped communication. Click with your mouse on the icon in the OPC server header frame on the top left side of the main window.

C H A P T E R 5 :I T E M ID S Y N TA X

OPC Server EthernetChapter 5: Item

ID Syntax

[ OPC Server Ethernet Manual / Chapter 5: Item ID Syntax ]

5 ITEM ID SYNTAX

5.1 S7 Item ID SyntaxThe OPC Item IDs have the following valid format

[group.]<area><data type><start address>[.array][suffix]

If the data type is BOOL, the bit number is required:

[group.]<area><data type><start address><.bit no.>[.array][suffix]<> mandatory [ ] optional

[Group.]Items may be grouped. If there are gaps in the periphery, they can be skipped with using groups. The gap will then not be accessed. Therefore a group name is used in front of the item name, separated by a dot. (Group name.Item name) Example:Group1.A10.1 Group2.A10.3

<area>

Syntax Orientation1 Access Rights NoteData Block DBx. BYTE Read / Write With blocks a block number

x is required (x = 1 to 65535). There must be a dot or a comma between block number and data type

Instant Block DIx. BYTE Read / Write

Flag M or F BYTE Read / Write

Timer T WORD Read

Counter Z or C WORD Read / Write

Input E or I BYTE Read

Output A or O or Q BYTE Read / Write

Peripheral Input PE or PI BYTE Read

Peripheral Output PA or PO BYTE Read / Write1 BYTE oriented means, that per physical address a byte is addressed WORD oriented means, that per physical address a word (16 bit) is addressed

OPC

Serv

er E

ther

net

Chap

ter 5

: Ite

m ID

Syn

tax


<data type>

ExamplesSyntax DB / DI M E/A PE /PA C/T Array Auffix OPC Data Type

BIT VT_BOOL

X DB5.X4.3 MX1.3 ------- ------- ------- ------- -------

BIT VT_BOOL

DB5.4.3 M1.3 E4.3 I4.3 A4.3 O4.3

PE4.5 PI4.5 PA1.3 PO1.3

------- ------- -------

BYTE VT_UI1

B Byte

DB5.B2 DB5.Byte2

MB4 MByte4 FB4 FByte4

EB4 EByte4 IB4 IByte4 AB5 AByte5 OB5 OByte5

PEB4 PEByte4 PIB4 PIByte4 PAB5 PAByte5 POB5 POByte5

------- DB5.B2.4 DB5.Byte2.4 MB4.3 MByte4.3 FB4.4 FByte4.4 POB5.3 usw.

BA BCD RI RU

VT_BOOL | VT_ARRAY VT_UI1 VT_R4 VT_R4

WORD VT_I4 (VT_UI2*)

W Word

DB5.W3 DB5.Word3

MW4 MWord4 FW4 FWord4

EW4 EWord4 IW4 IWord4 AW5 AWord5 OW5 OWord5 QWord5

PEW4 PEWord4 PIW4 PIWord4 PAWord5 PAWord5 POW5 POWord5

C5 Z5 T5

DB5.W3.2 DB5.Word3.2 MW4.2 EWord4.2 PAWord5.3 C5.3 Z5.10 T5.2 usw.

BA BCD D DT DU KF KT RI RU S5T SWAB TR

VT_BOOL | VT_ARRAY VT_I2 VT_BSTR VT_BSTR VT_BSTR VT_I2 VT_BSTR VT_R4 VT_R4 VT_BSTR VT_I4 (VT_UI2*) VT_R4

INT VT_I2

I Int

DB5.I3 DB5.Int3

MI4 MInt4 FI4 FInt4

EI4 EInt4 II4 IInt4 AI5 AInt5 OI5 OInt5

PEI4 PEInt4 PII4 PIInt4 PAI5 PAInt5 POI5 POInt5

------- DB5.I3.2 DB5.Int3.2 MI4.4 FInt4.3 AInt5.3 OI5.2 OInt5.5 POInt5.4 usw.

BA BCD DT DU KT RI RU S5T SWAB TR

VT_BOOL | VT_ARRAY VT_I2 VT_BSTR VT_BSTR VT_BSTR VT_R4 VT_R4 VT_BSTR VT_I2 VT_R4

DOUBLE WORD VT_R8 (VT_UI4*)

DW Dword

DB5.DW3 DB5.Dword3

MDW4 MDWord4 FDW4 FDWord4

EDW4 EDWord4 IDW4 IDWord4 ADW5 ADWord5 ODW5 ODWord5 QDW5

PEDW4 PEDWord4 PIDW4 PIDWord4 PADW5 PADWord5 PODW5 PODWord5

------- DB5.DW3 MDW4.2 FDW4.2 EDW4.4 ADWord5.8 PEDW4.8 PADW5.4 PODW5.4 usw.

BA BCD KF KG RI RU S5T SWAB T TOD

VT_BOOL | VT_ARRAY VT_I4 VT_I4 VT_R4 VT_R4 VT_R4 VT_BSTR VT_R8 (VT_UI4*) VT_BSTR VT_BSTR

DOUBLE INT VT_I4

D DI DInt

DB5.DI3 DB5.DInt3

MDI4 MDInt4 FDI4 FDInt4

EDI4 EDInt4 IDI4 IDInt4 ADI5 ADInt5 ODI5 ODInt5 QDI5

PEDI4 PEDInt4 PIDI4 PIDInt4 PADI5 PADInt5 PODI5 PODInt5

------- DB5.D3.2 DB5.DI3.2 DB5.DInt3.4 MDI4.5 EDI4.5 ADI5.2 PEDI4.5 PADInt5.2 usw.

BA BCD KG RI RU SWAB T TOD

VT_BOOL | VT_ARRAY VT_I4 VT_R4 VT_R4 VT_R4 VT_I4 VT_BSTR VT_BSTR

Continuation next page...


ID Syntax


Note: Counter and TimerCounters and Timers are always addressed as words. No type specifier is accepted. Timer can only be read! Counters can be read and written.Timer values are indicated in seconds e.g. T = 0.7 => T = 0,7s = 700ms.Counter values are indciated decimal (0 to 999).

<start address>The start address is the index of the data item within the area or block. Example: DB5.DW6: Double word 6 of data block 5 is the start address for data to be read. Example: MB17: Flag byte 17 ist the start address for data to be read.If the start address is a special bit, the bit number is required.

<.bit number>Whenever the data type is BOOL, the bit number is required! Example: E4.3: Bit 3 of input byte 4: an input bit is addressed here Example: MX12.1: Bit 1 of flag byte 12: a flag bit is addressed here

[.array]An array defines a grouping of one data type. If you want to read several data words from one data block, then you define an array of words. You access the data stored in an array using the standard syntax tog-ether with the array length separated by a dot. Example: DB10.REAL2.5. Learn more about arrays in chapter 5.7

[suffix]With the help of a suffix a value can be described in another format. Learn more about suffixes in chapter 5.8

REAL VT_R4

R Real

DB5.R2 DB5.REAL2

MR4 MREAL4

ER4 EREAL4 IR4 IREAL4 AR4 AREAL4 OR4 OREAL4

PER4 PEREAL4 PIR4 PIREAL4 PAR4 PAREAL4 POR4 POREAL4

------- DB5.R2.2 DB5.REAL2.4 MR4.5 ER4.4 AREAL4.5 PER4.2 PAR4.7 POR4.3 usw.

------- -------

STRING VT_BSTR

S String

DB5.S1.2 DB5.String1.2

MS2.3 MString2.3

------- ------- ------- ------- KA VT_BSTR

S7-STRING VT_BSTR

G DB5.G2.2 MG2.3 ------- ------- ------- ------- KA VT_BSTR

* if „also unsigned“ is selected as data type (Server Settings)

OPC

Serv

er E

ther

net

Chap

ter 5

: Ite

m ID

Syn

tax


5.2 S5 Item ID SyntaxThe OPC Item IDs have the following valid format



[group.]<area><data type><start address><.bit no.>[.array][suffix]<> mandatory [ ] optional

[Group.]Items may be grouped. If there are gaps in the periphery, they can be skipped with using groups. The gap will then not be accessed. Therefore a group name is used in front of the item name, separated by a dot. (Group name.Item name) Example:Group1.A10.1 Group2.A10.3

<area>

Syntax Orientation1 Access Rights Note Data Block DBx WORD Read / Write With blocks a block number

x is required (x = 1 to 65535). Expanded Data

BlocksDXx WORD Read / Write

Flag M or F BYTE Read / Write

Timer T WORD Read

Counter Z or C WORD Read / Write

Input E or I BYTE Read

Output A or O or Q BYTE Read / Write

Periphery P BYTE Read / Write

Expanded Peripheral Bytes

OB BYTE Read / Write

System Data Area RS or BS WORD Read

Absolute Memory AS WORD Read1 BYTE oriented means, that per physical address a byte is addressed WORD oriented means, that per physical address a word (16 bit) is addressed


ID Syntax


<data type> for data blocks and expanded data blocks

Syntax Example Array Suffixe OPC Data Type

BIT VT_BOOL

D DB5D4.12 ------- ------- -------

BYTE VT_UI1

DB DB5DB3 DB5DB3.5 BA VT_BOOL | VT_ARRAY

LEFT BYTE VT_UI1

DL DB5DL4 DB5DL4.2 BA VT_BOOL | VT_ARRAY

RIGHT BYTE VT_UI1

DR DB5DR2 DB5DR2.5 BA VT_BOOL | VT_ARRAY


DW DB5DW4 DB5DW4.5 BA BCD D DT DU KF KT RI RU S5T SWAB TR

VT_BOOL | VT_ARRAY VT_I2 VT_BSTR VT_BSTR VT_BSTR VT_I2 VT_BSTR VT_R4 VT_R4 VT_BSTR VT_I4 (VT_UI2*) VT_R4


DD DB5DD3 DB5DD3.2 BA BCD IEEE KF KG RI RU SWAB T TOD

VT_BOOL | VT_ARRAY VT_I4 VT_R4 VT_I4 VT_R4 VT_R4 VT_R4 VT_R8 (VT_UI4*) VT_BSTR VT_BSTR

STRING VT_BSTR

S DB5S2.3 ------- ------- -------


OPC

Serv

er E

ther

net

Chap

ter 5

: Ite

m ID

Syn

tax


<data type> for all other areas

Note: Counter and TimerCounters and Timers are always addressed as words. No type specifier is accepted. Timer can only be read! Counters can be read and written.Timer values are indicated in seconds e.g. T = 0.7 => T = 0,7s = 700ms.Counter values are indciated decimal (0 to 999).

<start address>The start address is the index of the data item within the area or block. Example: DB5DD6: Double word 6 of data block 5 is the start address for data to be read Example: MB17: Flag byte 17 ist the start address for data to be read.If the start address is a special bit, the bit number is required.

Syntax M E/A P / OB C / T / RS / AS

mit Array sinnv. Suffixe

OPC Datentyp

BIT VT_BOOL

M4.3 F4.3

E4.3 I4.3 A4.3 Q4.3

------- ------- ------- ------- -------

BYTE VT_UI1

B MB4 FB4

EB4 IB4 AB5 QB5

PB4 OB4

------- MB4.3 FB4.4 EB4.4 IB4.5 AB5.2 QB5.5 PB4.2 OB4.3

------- -------

WORD VT_UI2 VT_I4

W MW4 FW4

EW4 IW4 AW5 QW5

PW2 OW2

C5 T5 RS4 BS4 AS5

MW4.2 FW4.4 EW4.5 IW4.2 AW5.5 QW5.2 PW2.10 OW2.3 C5.5 T5.3 RS4.2 BS4.7 AS5.2

BA BCD D DT DU KF KT RI RU S5T SWAB TR

VT_BOOL | VT_ARRAY VT_I4* / VT_UI2** VT_BSTR VT_BSTR VT_BSTR VT_I2 VT_BSTR VT_R4 VT_R4 VT_BSTR VT_I4* / VT_UI2** VT_R4

DOUBLE WORD VT_R4(*) VT_UI4**

D MD4 FD4

ED4 ID4 AD5 QD5

PD5 OD5

------- MD4.4 FD4.2 ED4.6 ID4.2 AD5.6 QD5.2 PD5.4 OD5.9

BA BCD IEEE KF KG RI RU SWAB T TOD

VT_BOOL | VT_ARRAY VT_I4 VT_R4 VT_I4 VT_R4 VT_R4 VT_R4 VT_I4 VT_BSTR VT_BSTR

STRING VT_BSTR

S MS4.5 FS4.5

------- ------- ------- ------- ------- -------


ID Syntax


<.bit number>Whenever the data type is BOOL, the bit number is required! Example: E4.3: Bit 3 of input byte 4: an input bit is addressed here Example: MX12.1: Bit 1 of flag byte 12: a flag bit is addressed here



OPC

Serv

er E

ther

net

Chap

ter 5

: Ite

m ID

Syn

tax


5.3 Modbus Item ID SyntaxThe OPC Item IDs have the following valid format



[group.]<area><data type><start address><.bit no>[.array][suffix]<> mandatory [ ] optional

[Group.]Items may be grouped. If there are gaps in the periphery, they can be skipped with using groups. The gap will then not be accessed. Therefore a group name is used in front of the item name, separated by a dot. (Group name.Item name) Example:G1.40001 G2.R2 G3.S20.30

<area>

Syntax Number Orientation1 Access RightsDiscrete Inputs I

E DI DE

1xxxxx BIT Read

Discrete Outputs A O Q DA DO DQ

0xxxxx BIT Read / Write

Input Register ER IR

3xxxxx WORD Read

Register (Holding Register)

R HR

4xxxxx WORD Read / Write

1 BIT oriented means, that per physical address one bit is addressed WORD oriented means, that per physical address a word (16 bit) is addressed

Discrete I/Os have 1 bit but for read and write it is assigned a 8 bit unit. Before writing one bit, one byte is read. The corresponding bit is switched and then one byte is written. Note: If another bit has changed in the PLC during this procedure, it is overwritten with an old value by the server.Ranges may be addressed by code or by number. For example a Discrete Input can be accessed via „E“ as well as via „1“


ID Syntax


<data type>

Syntax Syntax R

Syntax E/A

Syntax ER

with Array

Suffix OPC Data Type

BIT VT_BOOL

X RX5.2 HRX5.2 4X5.2

E255 I255 DE255 DI255 125543

------- ------- ------- -------

WORD VT_I2

ohne R50 HR50 400050

------- ER120 IR120 312034

R50.2 HR50.2 400050.2 ER120.2 IR120.2 312034.2

BA BCD D WDT* KT RI RU S5T SWAB

VT_BOOL | VT_ARRAY VT_I2 VT_BSTR VT_BSTR VT_BSTR VT_R4 VT_R4 VT_BSTR VT_I2

DOUBLE WORD VT_I4

D RD50 HRD50 4D50

------- ERD120 RD50.3 HRD50.3 4D50.3 ERD120.3

BA BCD SWAB KG IEEE TR RI RU T WDT***

VT_BOOL | VT_ARRAY VT_I4 VT_I4 VT_R4 VT_R4 VT_R4 VT_R4 VT_R4 VT_BSTR VT_BSTR

STRING VT_BSTR

S RS5.4 ------- ERS5.4 ------- KA SWAB

VT_BSTR VT_BSTR

* Suffix WDT (Wago Date and Time) uses 4 registers (8 bytes)

<start address>The start address is the index of the data item within the area or block. Example: ER120: Input Register 120 is the start address for data to be read If the start address is a special bit, the bit number is required.

<.bit number>Whenever the data type is BOOL, the bit number is required! HRX5.2: Bit 2 of Holding Register 5 is addressed here[.array]An array defines a grouping of one data type. If you want to read several data words from one data block, then you define an array of words. You access the data stored in an array using the standard syntax tog-ether with the array length separated by a dot. Example: DB10.REAL2.5. Learn more about arrays in chapter 5.7


OPC

Serv

er E

ther

net

Chap

ter 5

: Ite

m ID

Syn

tax


5.4 Send / Receive Item ID SyntaxThe OPC Item IDs have the following valid format

<job><data type><start address>[.array][suffix]


<job><data type><start address><.bit no.>[.array][suffix]<> mandatory [ ] optional

<job>

SyntaxSEND S

RECEIVE R

<data type>

Syntax Syntax Send

Syntax Receive

Array Suffix OPC Data Type

BIT VT_BOOL

X SX1.2 RX1.2 ------- ------- -------

BIT VT_BOOL

none S1.2 R1.2 ------- ------- -------

BYTE VT_UI1

B BYTE

SB4 SBYTE4

RB5 RBYTE5

SB4.4 SBYTE4.5 RB5.2 RBYTE5.2

BA BCD RI RU

VT_BOOL | VT_ARRAY VT_UI1 VT_R4 VT_R4

CHAR VT_BSTR

C CHAR

SC4 SCHAR4

RC5 RCHAR5

SC4.2 SCHAR4.2 RC5.4 RCHAR5.4

BA DT

VT_BOOL | VT_ARRAY VT_BSTR


W WORD

SW10 SWORD10

RW10 RWORD10

SW10.2 SWORD10.2 RW10.2 RWORD10.2

BA BCD D KF KT RI RU S5T SWAB TR

VT_BOOL | VT_ARRAY VT_I2 VT_BSTR VT_I2 VT_BSTR VT_R4 VT_R4 VT_BSTR VT_I4 (VT_UI2*) VT_R4

INT VT_I2

I INT

SI4 SINT4

RI5 RINT5

SI4.2 SINT4.2 RI5.5 RINT5.5

BA BCD KT RI RU S5T SWAB TR

VT_BOOL | VT_ARRAY VT_I2 VT_BSTR VT_R4 VT_R4 VT_BSTR VT_I2 VT_R4

Continuation next page...


ID Syntax



D DW DWORD

SD6 SDW6 SDWORD6

RD6 RDW6 RDWORD6

SD6 SDW6 SDWORD6 RD6 RDW6 RDWORD6

BA BCD KF KG RI RU SWAB T

VT_BOOL | VT_ARRAY VT_I4 VT_I4 VT_R4 VT_R4 VT_R4 VT_R8 (VT_UI4*) VT_BSTR

DOUBLE INT VT_I4

DI DINT

SDI6 SDINT6

RDI6 RDINT6

SDI6.2 SDINT6.2 RDI6.5 RDINT6.5

BA BCD KG RI RU SWAB T

VT_BOOL | VT_ARRAY VT_I4 VT_R4 VT_R4 VT_R4 VT_I4 VT_BSTR

REAL VT_R4

R REAL

SR2 SREAL2

RR2 RREAL2

SR2.2 SREAL2.2 RR2.5 RREAL2.5

------- -------

STRING VT_BSTR

S STRING

SS5.2 SSTRING5.2

RS5.2 RSSTRING5.2

------- KA DT

VT_BSTR VT_BSTR

S7-STRING VT_BSTR

G SG5.2 RG5.2 ------- KA DT

VT_BSTR VT_BSTR


<start address>The start address is the index of the data item within the area or block. Example: SWORD10: Word 10 is the start address for data to be sent or received If the start address is a special bit, the bit number is required.

<.bit number>Whenever the data type is BOOL, the bit number is required! Example: SX1.2: Bit 2 in byte 1 is the start address to be sent or received



OPC

Serv

er E

ther

net

Chap

ter 5

: Ite

m ID

Syn

tax


5.5 PLC-5 Item ID SyntaxThe OPC Item IDs have the following valid format

<area>[file number]<start address>[.array]<> mandatory [ ] optional

<area>

Syntax Orientation1 Access RightsOutput File O BIT Read / Write

Input File I BIT Read

Integer File N WORD Read / Write

Binary File B WORD Read / Write

Float File F DOOBLE WORD Read / Write1 BIT oriented means, that per physical address one bit is addressed WORD oriented means, that per physical address a word (16 bit) is addressed DOUBLE WORD oriented means, that per physical address a double word (32 bit) is addressed

<file number>The file number can be entered optionally. If the file number is not entered, the default file number is used.

Default file number

O Output File 0

I Input File 1

N Integer File 7

B Binary File 3

F Float File 8

<start address>The start address is the index of the data item within the area or block. Inputs and Outputs are addressed octal. Integer Files, Binary Files and Float Files decimal.

Address Format

O Output File octal

I Input File octal

N Integer File decimal

B Binary File decimal

F Float File decimal

Start address is the word number, the float number or the bit number.


ID Syntax


<:word> bzw. <:float> bzw. </bit>For addressing a special bit of a word, the following Syntax is used:

<:word/bit>

NOTE

When writing bits the whole word is written!

Examples:

Syntax DescriptionO.0 Word 0 of Output File 0

O:0/12 Bit 10 (12 octal = 10 decimal) of Output File 0

O/12 Bit 10 (12 octal = 10 decimal) of Output File 0

I:37 Word 31 (37 octal = 31 decimal) of Input File 1

I4:37/2 Bit 2 in Word 31 (37 octal = 31 decimal) of Input File 4

I:1/0 Bit 0 of Word 1 of Input File 1

B3/26 Bit 26 of Binary File 3

B12:5.15 15 words array in Binary File 12, starting with Word 5

B12:5/15 Bit 15 in Word 5 of Binary File 12

F8:0 Float 0

F9:10.16 16 doubleword array of Float File 9, starting with double word 10

N23:4 Word 4 of Integer File 23

N23:4.10 10 words array of Integer File 23, starting with word 4

N23:4/2 Bit 2 in Word 4 of Integer File 23 = Bit 66 of Integer File 23

N23/66 Bit 66 of Integer File 23

[.array]An array defines a grouping of one data type. If you want to read several data words from one data block, then you define an array of words. You access the data stored in an array using the standard syntax tog-ether with the array length separated by a dot. Example: N23:4.10. Learn more about arrays in chapter 5.4

OPC

Serv

er E

ther

net

Chap

ter 5

: Ite

m ID

Syn

tax


5.6 Mitsubishi Item ID SyntaxThe OPC Item IDs have the following valid format

[group.]<range><start address>[.array][suffix]<> mandatory [ ] optional

[group.]Items may be grouped. If there are gaps in the periphery, they can be skipped with using groups. The gap will then not be accessed. Therefore a group name is used in front of the item name, separated by a dot. (Group name.Item name) Example:Group1.Y10 Group2.Y30

<area>

Syntax Orientation1 Representation of the start address

Input Relay X BIT HEX

Output Relay Y BIT HEX

Internal Relay M BIT DEZ

Latch Relay L BIT DEZ

Annuciator F BIT DEZ

Edge Relay V BIT DEZ

Data Register D WORD DEZ

Link Register W WORD HEX

Timer Current Value TN WORD DEZ

Counter Current Value CN WORD DEZ

Direct Input DX BIT HEX

Direct Output DY BIT HEX

Index Register Z WORD DEZ

File Register R WORD DEZ1 BIT oriented means, that per physical address one bit is addressed WORD oriented means, that per physical address a word (16 bit) is addressed

<start address>The start address indicates the start address to read or write. The start address must be entered - depen-ding on the range - hexadecimal or decimal. Please refer to the table above. Examples: D20 (DEZ) X500 (HEX) R25 (DEZ)


ID Syntax


[.array]An array defines a grouping of one data type. If you want to read several data words from one data block, then you define an array of words. You access the data stored in an array using the standard syntax tog-ether with the array length separated by a dot. Example: X10.5. Learn more about arrays in chapter 5.4


Suffixe OPC data type ExamplesData Register RU

RU BCD KF SWAB BA

VT_R4 VT_R4 VT_I2 VT_I2 VT_I4 (VT_UI2*) VT_BOOL | VT_ARRAY

D20RI W40KF TN5SWAB CN4BA Z20RU R10KF

Link RegisterTimer Current ValueCounter Current ValueIndex RegisterFile Register


OPC

Serv

er E

ther

net

Chap

ter 5

: Ite

m ID

Syn

tax


5.7 ArraysAn array defines a grouping of one data type. If you want to read several data words from one data block, then you define an array of words. You access the data stored in an array using the standard syntax tog-ether with the array length separated by a dot.

Arrays are NOT allowed with: ● BOOL● DATE AND TIME● DATE● TIME● TIME OF DAY● STRINGS (already an array of characters)

as well as with all suffixes, that are string or bool to the client:

● BA (already an array of bits)● KA● S5T● KT● D● T● DT● DU● TOD


ID Syntax


5.8 SuffixeWith the help of a suffix a value can be described in another format. The S7 and Send/Receive syntax allows the direct entry of a data type, which means that only for special data types a suffix is neccessary.

Suffix SyntaxBitArray BA

BCD BCD

Date D

Date and Time DT

Date and Time (SQL) DU

ASCII to Hex KA

S5-KG KG

S5-KT-Format KT

Signed to Real RI

Unsigned to Real RU

S5 Time S5T

Swab Bytes SWAB

Time T

Time of Day TOD

TimeReal TR

5.8.1 Suffix BAWith the Suffix BA the data stored in the PLC is interpreted and presented as an array of bits.

Suffix BA: Bit ArrayApplicable with: Byte (LByte, RByte), Word,

Int, Double Word, Double IntRange: True or False

5.8.2 Suffix BCDWith the Suffix BCD the data stored in the PLC is interpreted and presented as unsigned BCD code. For example the decimal value „65535“ is converted to „9999“.

Suffix BCDApplicable with: Byte (LByte, RByte), Word, Int,

Double Word, Doube IntRange: Byte:

Word: Int: Double Word: Double Int:

0 to 99 0 to 9999 0 to 9999 0 to 99999999 0 to 99999999

OPC

Serv

er E

ther

net

Chap

ter 5

: Ite

m ID

Syn

tax


5.8.3 Suffix DWith Suffix D the data stored in the PLC is interpreted and presented as data type DATE. The data type DATE uses a word (16 bits). The bytes contain the days since 01.01.1990.

Suffix D: DateApplicable with: Word

Range: 1990-01-01 till 2168-12-31

Rules using Suffix D:The years 1990 till 2089 can be entered two-digit or four-digit. The years starting at 2090 must be entered four-digit. 90 till 99 1990 till 199900 till 89 2000 till 2089Month and days can be enterd single-digit or two-digit. All signs are allowed for hyphen except from numbers (e.g. 89/01/17): Number of hyphens is arbitrary.

5.8.4 Suffix DTWith the Suffix DT the data stored in the PLC is interpreted and presented as data type DATE_AND_TIME. The data type DATE_AND_TIME uses 8 bytes (64 bits). The DATE_AND_TIME format contains year, month, day, hour, minute, second and millisecond. The proper use of the separators is required (hyphen, colon, dot)!

Suffix DT: Date and TimeApplicable with: Word, Int

Range: 1990-01-01-00:00:00.000 till 2098-12-31-24:59:59.999 or 1990-01-01-00:00:00 till 2089-12-31-23:59:59

Byte number Contains Range

Byte n Year 0 till 99

Byte n+1 Month 1 till 12

Byte n+2 Day 1 till 31

Byte n+3 Hour 0 till 23

Byte n+4 Minute 0 till 59

Byte n+5 Sekunde 0 bis 59

Byte n+6 Byte n+7

Millisecond 0 till 999 + weekday in the last 4 bytes1 = sunday7 = saturday


ID Syntax


Rules using Suffix DT:

Year four-digit 1990 till 2089Month two-digit 01 till 12Day two-digit 01 till 31Hour two-digit 00 till 23Minute two-digit 00 till 59Second two-digit 00 till 59Millisecond three-digit 000 till 999

5.8.5 Suffix DUWith the Suffix DU the data stored in the PLC is interpreted and presented as data type DATE_AND_TIME in SQL compatible format.

5.8.6 Suffix KAWith Suffix KA the data stored in the PLC is interpreted and presented as Hex.

Suffix KA: Applicable with: String, S7-String

Range: 0 till 9, A till F

5.8.7 Suffix KFWith Suffix KF the data stored in the PLC is interpreted and presented as signed integer (fixed-point number).

Suffix KFApplicable with: Byte (LByte, RByte, S5), Word (S5), Double

Word (S5)Range: Byte:

Word: Double Word:

-128 till 127 -32768 till 32767 -2147483648 till 2147483647

5.8.8 Suffix KGWith Suffix KG the data stored in the PLC is interpreted and presented as 4 byte floating point

Suffix KG Applicable with: Double Word, Double Int

Range: 0,1469368E-38 till 0,1701412E39

OPC

Serv

er E

ther

net

Chap

ter 5

: Ite

m ID

Syn

tax


5.8.9 Suffix KTWith Suffix KT the data stored in the PLC is interpreted as 2 byte TIMER constant. The 2 bytes contain besides the time value (range 0 to 999) a time base.

Suffix KT Applicable with: Word, Int

Range: 000.0 bis 999.3

5.8.10 Suffix RIWith Suffix RI the data stored in the PLC is interpreted and presented as signed REAL. When writing to the PLC, the value is rounded. Example: db9dw0RI - the value 10.7 is rounded to 11.

Suffix RI: signed RealApplicable with: Byte (LByte, RByte), Word, Int,

Double Word, Double Int

5.8.11 Suffix RUWith Suffix RU the data stored in the PLC is interpreted and presented as unsigned REAL. When writing to the PLC, the value is rounded.

Suffix RU: unsigned RealApplicable with: Byte (LByte, RByte), Word, Int,

Double Word, Double Int

5.8.12 Suffix S5TWith Suffix S5T the data stored in the PLC is interpreted and presented as data type S5TIME. S5TIME uses a word (16 bits) and contains the time value together with the time base. The S5T format contains hours, minutes, seconds and milliseconds.

Suffix S5T: S5TIMEApplicable with: Word, Int

Range: 0ms till 2h46m30s

5.8.13 Suffix SWABWith Suffix SWAB the high byte and low byte of the data stored in the PLC are changed.

Suffix SWABApplicable with: Word, Int, Double Word, Double

IntRange: Changes High Byte and Low Byte


ID Syntax


5.8.14 Suffix TWith the Suffix T the data stored in the PLC is interpreted and presented as data type TIME. The data type TIME uses a double word (32 bits). The data type contains days (d), hours (h), minutes (m), seconds (s) and milliseconds (ms). Miliseconds may be ommited. The range is from -2147483648 (-24d20h31m23s648ms) till 2147483647 (24d20h31m23s647ms).

Suffix T: TIMEApplicable with: Double Word

Range: -24D_20H_31M_23S_648MS till 24D_20H_31M_23S_647MS**

5.8.15 Suffix TODWith the Suffix TOD the data stored in the PLC is interpreted and presented as data type TIME_OF_DAY. The data type TIME_OF_DAY uses a double word (32 bits). The TIME_OF_DAY format contains hours:minutes:seconds and .milliseconds. Milliseconds can be omitted.

Suffix TOD: TIME OF DAYApplicable with: Double Word, Double Int

Range: 0:0:0.0 till 23:59:59.999

5.8.16 Suffix TRWith the Suffix TR the data stored in the PLC is interpreted and presented as data type TIME REAL.

Suffix TR: TIME REALApplicable with: Word, Int

Range: 0.01 till 9990.0

5.9 Bit MaskingWith a bit mask several bits of a data type can be read or written, by combining them to one decimal value. Bit masking of arrays is possible as well.

Example8 bits of data word 0 in data block 5 shall be read beginning with bit 2. Therefore the following syntax is used: db5.w0#2.8 ordb5.w0#2,8 ordb5.w0#2#8

OPC

Serv

er E

ther

net

Chap

ter 5

: Ite

m ID

Syn

tax


5.10 Special ItemsThis server offers additional items for each access path to acquire data about different aspects of the com-munication and to control the communication properties.

Special Item OPC Data TypePollinterval VT_I4Maxinterval VT_I4Storesettings VT_BOOLItemcount VT_I4Errorcount VT_I4Writecomplete VT_I4Status VT_BOOLWriteItemCount VT_I4WriteStatusMsg VT_BSTRServerCycle VT_I4DbOffset VT_I4DwOffset VT_I4

5.10.1 PollintervalThe POLLINTERVAL item is used to access the currently set poll interval. It is the same value displayed in the Access Path Definition window of the server. It indicates the current requested poll interval in millise-conds. A client can write new values to this item. In any case the value can always be read through OPC or. The range of valid values differs with respect to the settings. The value of zero or greater than zero indicates the new poll interval. A negative value indicates, that the polling is disabled. In this case the old positive value ist still displayed. When the client writes to this item, all items of that access path are updated immedi-ately.

Tag Type: INTEGER (signed long) / VT_I4Access: READ, WRITERange: 0 till 2147483647 valid values

-1 till -2147483648 topic inactive, no items are updated

NOTE: By writing a negative value to the POLLINTERVAL item, a client can conve-niently stop all update activities on the corresponding access path without having to deactivate the items.


ID Syntax


5.10.2 StoresettingsThe STORESETTINGS item is used to make the temporary poll interval changes to POLLINTERVAL via OPC to the hard disk. If the client writes a value of 1 to the STORESETTINGS item, the current set update interval is written to the server‘s configuration file. If the update interval has been changed via OPC and STORESETTINGS is not written to 1, the server will use the original update interval for that access path the next time it is started. Reading the item will always return 0. It does not matter, wether the client writes a 1 or a 0.

Tag Type: DISCRETE / VT_BOOLAccess READ, WRITERange: 0 or 1

5.10.3 MaxintervalThe MAXINTERVAL item is used to access the measured maximum update interval in milliseconds of all items for the corresponding access path for the last completed poll cycle.

Tag Type: INTEGER / VT_I4Access: READRange: 0 till 2147483647

5.10.4 ItemcountThe ITEMCOUNT item is used to access the number of active items of the corresponding access path. It is the same value displayed in the Access Path Definition window of the server under „Items“.


5.10.5 Errorcount The ERRORCOUNT item is used to access the number of all faulty (but active) items of the corresponding access path. If the state is „bad“, all items are faulty. The ITEMCOUNT item then corresponds with the ERRORCOUNT item.


NOTE: Use the ERRORCOUNT item to detect wrongly configured or invalid items

OPC

Serv

er E

ther

net

Chap

ter 5

: Ite

m ID

Syn

tax


5.10.6 WritecompleteThe WRITECOMPLETE item is used to access the state of pending write activities of the corresponding acces path. If the value of the WRITECOMPLETE item is „1“ all write activities are complete - no writes are pending. If values are written to any items of the access path the value of the WRITECOMPLETE item chan-ges to „0“ indicating write activity is currently in progress. If the server has completed all write activities the value of the WRITECOMPLETE item changes to „1“ if all writes were successful or to „-1“ if at least one write has failed. If the value of the WRITECOMPLETE item is not zero the client can write „1“ or „-1“ to it (write a „1“ to clear errors or a „-1“ to test a client reaction on write errors).

Tag Type: INTEGER / VT_I4Access: READ, WRITERange: -1, 0 or 1

5.10.7 StatusThe STATUS item is derived from the connection status of the fetch and write connection. If one of the con-nections has malfunctioned, the status indicates a malfunction. If no write connection is parameterized, only the status of the read connection is indicated.

5.10.8 WriteItemCountThe WRITEITEMCOUNT item shows the number of items written to the PLC. The number is incremented when the secure data transmission to the PLC has been concluded successfully. When an error occurs, the WRITESTATUSMSG item receives an error code. If an item is written several times in succession before the server is able to write the value, the last value will be written and not all intermediate values will be buffered. If this happens, the number is „1“. The item can be set to „0“ before writing and scanned after writing.

5.10.9 WriteStatusMsgThe WRITESTATUSMSG item shows the first error when write operation to the PLC fails. If this item does not contain a string or the first character is a blank, an error code is assigned. When an error occurs, the error code is retained until it is deleted by OPC client or the operator. The error code consists of 6 numbers separated by a semicolon (;) without blanks. Its meaning is shown below:

Error Code:

Identifier; DB; DW; Len; PLC Error; Connection error


ID Syntax


Identifier

Identifier1 DATA BLOCK2 FLAG3 INPUT4 OUTPUT5 PERIPHERY6 COUNTER7 TIMER8 SYSTEM_DATA9 ABSOLUTE_MEMORY10 EXPANDED DATA BLOCKS16 EXTMEM17 EXT_PERIPHERAL

DBSpecifies the block number for DATA BLOCK and EXPANDED DATA BLOCK. Otherwise 0 (i.e., can be disregarded).

DWSpecifies the start value at which the interval begins.

LenSpecifies the number of elements.

PLC ErrorIndicates the error supplied by the handling block from the PLC. It is only valid when the connection error is 0. For a description of the error codes, see the programming manual of the controller.

OPC

Serv

er E

ther

net

Chap

ter 5

: Ite

m ID

Syn

tax


0 No error1 Wrong Q/ZTYP in the handling block2 Area does not exist in the PLC (i.e., DB does not exist).3 Area in the PLC is too small.4 QVZ error occurred on the PLC.5 Error in the indication word (ANZW)6 No valid ORG format7 No free data buffer8 No free transport connections9 Error of communication partner10 Connection error (connection failed or could not be esta-

blished)11 Message error (error in the firmware)12 Trigger error (e.g., RECEIVE to SEND)13 Abort after RESET14 Job with READ/WRITE (PLC unable to trigger)15 Job does not exist16 System error

Connection error

1 BAD_CR_PARAMS2 NO_SLOT3 WAIT_CONNECT4 NOT_IMPLEMENTED5 BAD_LINE6 WAIT_DATA7 WAIT_SEND8 INTERNAL_ERROR9 NO_REQUEST10 NO_DRIVER11 UEBERLAST12 BLOCKED_DATA13 NO_ADAPTER14 ALREADY_RUNNING15 NOT_SUPPORTED16 TRY_AGAIN17 NO_MEMORY18 BAD_SIGNATURE19 DATA_ERR (Data error FETCH / WRITE)


ID Syntax


5.10.10 ServercycleThis items shows the number of complete updates of the server for the corresponding connection.

Tag Type: INTEGER / VT_I4Access: READ, WRITERange: -2147483648 till 2147483647

C H A P T E R 6 :OPC C L I E N T

OPC Server EthernetChapter 6: OPC Client

[ OPC Server Ethernet Manual / Chapter 6: OPC Client ]

6 OPC CLIENTThe Test OPC Client is a general-purpose OPC client. It is included with INAT OPC servers to ensure that users always have a reliable means to test the capabilities of the software. To start the program, choose OPC Test Client from the Start menu, in the OPC Server Programs folder.

6.1 Connect Client and ServerThe OPC Test Client connects to OPC server applications and displays real-time values as they are recei-ved. To get a list of available OPC Servers select Server > Connect.

The Client searches the registry on the local computer and generates a list of program ID’s for available OPC servers. It displays this list in a drop-down box.

Every OPC server has a unique program ID. This is a human-readable text string that is converted to a glo-bally unique identification number which COM then uses to identify the server. The ProgID of the INAT OPC server is „INAT TCPIPH1 OPC Server“. Select the INAT OPC server and press „OK“. COM will attempt to launch the OPC server if it is not currently running when the first client attempts to connect to it. If the server runs as a local executable then COM will run it. If the server runs as an NT service then COM will start it up. Similarly, when the last client application disconnects from an OPC server, the server will shut down.

OPC

Serv

er E

ther

net

Chap

ter 6

: OPC

Clie

nt


6.2 Add OPC Groups Choose “Add Group” from the Group menu to create a new OPC group on the connected OPC server. Enter a name for the group. If the edit box is left blank then the OPC server will assign a unique name for the group. Change the other settings as desired and click OK to create the group.

Update RateThe OPC server tries to keep the OPC client informed with values for an OPC group at the requested update rate for that group. If the requested update rate is too fast for the server to handle then it will return a revised update rate that it will use instead. Internally, the server tries to keep the data items at least as “fresh” as indicated by the update rate. However, the server will send values to the client no faster than the update rate in order to avoid overwhelming it.ActiveOPC servers only update values for active items in active groups. When an individual item is set inactive, the server stops sending updates for the item. When a group is set inactive, the server stops sending values for any items in that group. Client applications (such as HMI applications) can help to reduce the processing load on an OPC server by deacti-vating groups and items that are not currently needed.



6.3 Add OPC Items An OPC group serves as a logical collection of data items. Choose “Add Item” from the Item menu to create and and add OPC items.

To create an OPC item, enter the access path and the item ID in the edit box. In addition the data type may be entered.

Access PathThe Access Path must correspond with the connection name you use in the OPC server. The OPC server will return errors if the access path is invalid. Some clients do not offer an edit box for the access path. In that case, the access path must be entered together with the Item ID syntax. [Access Path Name]Item ID or Access Path Name.Item IDExample (PLC1 = access path name):[PLC1]DB5.W0PLC1.DB5.W0Item Name (Item ID)All OPC items must be identified by an item ID. This identifier is a server-specific string of characters that uniquely identifies a source of data to an OPC server. More than one OPC item may refer to the same item ID at the same time. Enter the item ID in the Item ID edit box (see chapter 5 „Item ID Syntax“).

With „Add Item“ the Item is transferred to the list of items to be added. When alle items are added for that group press „OK“.

OPC

Serv

er E

ther

net

Chap

ter 6

: OPC

Clie

nt


6.4 Browse the Server Address SpaceThe symbols created or imported in the OPC server are indicated in a tree view. The tree view displays “branches” in a hierarchical address space, while the list view displays the “leaves” that are available under the selected “branch”.

Each “leaf” represents an actual item. While browsing, the user may apply a number of filter criteria to search for a particular type of item. Double-click on a “leaf” and the client will place the fully qualified item ID for that item in the edit box. All OPC items have a native (“canonical”) data type. That is to say, there is a default format to the data that the server supplies for an item. When creating OPC items, client applications can specify a requested data type for each item. The OPC server will attempt to convert any data from the item to this format if possible.

6.5 Read real-time values Once items are added to an OPC group, the OPC Test Client continually updates the display for that group with real-time data. The data values appear in the list view on the right-hand side of the window. Each item is listed along with its item ID, active state, value, quality, and timestamp.

OPC servers only update values for active items in active groups. When an individual item is set inactive, the server stops sending updates for the item. When a group is set inactive, the server stops sending values for any items in that group. Client applications (such as HMI applications) can help to reduce the processing load on an OPC server by deactivating groups and items that are not currently needed.



Inactive Items are marked red

6.6 Write control values The OPC Test Client allows the user to write control values to items in an OPC group. Select the desired item in the list view and right-click on it. Select „Sync Write“

OPC

Serv

er E

ther

net

Chap

ter 6

: OPC

Clie

nt


In the dialog box, enter the control value to be written in the “Value” column. Specify the data type for the control value in the “Data Type” column. When ready, click the OK button to perform the write.

C H A P T E R 7 :A P P E N D I X

OPC Server EthernetAppendix

[ OPC Server Ethernet Manual / Appendix ]

7 APPENDIX

7.1 Win.iniWin.ini is an initialisation file, where pre-settings for application programs are stored. When the OPC server starts, the entries in the Win.ini are executed and the application starts with these settings.Enter „win.ini“ in the command line to open the win.ini:

The standard editor appears

If desired, change the entries. With the next start of the OPC server, these settings are used.

OPC

Serv

er E

ther

net

Inde

x

[ OPC Server Ethernet Manual / Index ]

Symbole200H1Connections.reg 20

AAccess Path 102Active / Passive connection establishment for Unsolicited

51Address Space 103Add OPC Groups 101Add OPC Items 102Alias Configuration 53Allow Cyclic Poll 41, 48Arrays 87ASCII to Hex 88

BBCD 88BitArray 88Bit Masking 92Browse the Server Address Space 103

CChronological Order is preserved 57Combine coherent blocks always (max) 57Communication Basics 26Configuration 38Configuration file 55Connection 39Connections 27Connection Establishment 47Connect Client and Server 100Copyright 2Counter 74, 77

DData types 56Date 88Date and Time 88Date and Time (SQL) 88DCOM Configuration 60Destination 42Destination: Ethernet Address 49

EEcho Written Data back to Client 56Errorcount 94

FFETCH active / FETCH passive 26

FETCH on EVENT 27Fetch on Event 41, 48First transition from Ethernet to MPI is echolink 45

HH1ChangeAddress.reg 20H1DoNotChangeAddress.reg 20H1 Connections 29H1 connections

change number 20H1 driver 19H1 Parameters 48H1 Parameter Settings 40H1 Registry Scripts 20H1 Station Address 59High Performance Protocol 47

IImport Step 7 Symbols 54Import Step 7 symbol comments 55INAT TCPIPH1 OPC Server 100Installation 14Introduction 8IP 28IP Address 29Item-Syntax 72Itemcount 94

JJob types 26

LLicensing 22Life ACKs, Life Data ACKs 47Line Type 51Local TSAP 43, 49Logging 67

MMAC Address 30Main window 65Maxinterval 94MELSEC-Q Connection 36Mitsubishi Item Syntax 85Modbus Connection 34Modbus Item ID Syntax 79MPI/PPI address 42MPI/PPI Parameters 46MPI Address of the Routing PLC 46Multicast Number 51

I N D E X

OPC Server EthernetIndex


NNetLink Connection 35New connection 39Not parameterizable connections 34No Header 42

OOLE for Process Control 9OPC

What is it? 9OPC Client 100OPC DA Specification 10OPC Overview 9OPC server types 8

PParameterizable connections 34PLC-5 Connection 35PLC-5 Item Syntax 83Pollinterval 93Poll interval 41, 48Port for Read 47Port for Unsolicited 47Port for Write 47Port number 29Priority 51ProgID 10Program ID 100Protocol TCP/UDP 47Protocol Timer Tick 55

RRead and Write through one connection 41, 48Read between Write (default: No) 57Read Optimisation 47, 51Read real-time values 103RecMsg 66RecNewValue 66Registry 20Remote TSAP 43, 49Resume Protocol 69RFC1006 Connections 31Routing PLC 46Routing TSAPs 44

SS5-KG 88S5-KT 88S5 Connections 32S5 Item ID Syntax 75S5 Time 88S7 Connections 33S7 Item ID Syntax 72S7 Subnet ID 45

Scope of Supply 9SendNewValue 66SEND / RECEIVE 26Send / Receive Item ID Syntax 81ServerCycle 66Servercycle 98Server Optimisation 57Server Options 58Server Settings 55Server Type 18, 21

Changing 21Server types 8Service 21Setting up a new connection 39ShowCreate Point 68ShowEvents 68ShowReceive 68ShowSend 68Show Access Path 68Show Activate Point 68Show Errors 68Show Poll Send and Receive 68Show Rec Values 68Show Send Values 68Show Server Icon in the task bar 56Show Symbols 68Shutting down the OPC Server 52Signed to Real 88Socket 29Special Items 93Standard connections

S7 34Standard TSAPs for S7 Connections 50Start Address 0 42Start Address 1 42Status 95Storesettings 94String Format 58Suffixe 88Suspend and resume the OPC Server 69Suspend Protocol 69Swab Bytes 88System Requirements 9

TTCP 28TCP/IP Connections 28TCP/IP Parameters 41TCP/IP Parameter Settings 40TcpIpH1.NET 55Time 88Timeouts 58Timer 74, 77TimeReal 88Time of Day 88TSAPs 30

OPC

Serv

er E

ther

net

Inde

x


TSAPs for S7 Connections 43

UUDP 28Unit ID 42Unsigned to Real 88Unsolicited Data from PLC 41, 48Update Rate 101Updating 24Upgrading 24Use PLC Header 43Use RFC1006 43

VVerbose 68

WWin.ini 108Writecomplete 95WriteItemCount 66, 95WriteStatusMsg 95Writes with immediate positive Confirm (default: No) 57Write access to PLC permitted 41, 48WRITE active / WRITE passive 26Write control values 104Write every item separately (off) 57Write Single Coil 42Write Single Register 42Write with Priority, Chronological Order is Preserved 57

OPC Server EthernetIndex


user´s manual opc s e - resolucom · the information in these documents is not binding. ... opc...

Documents