OPC Server Ethernet

User´s Manual
OPC S E R V E R E T H E R N E T
OPC Server Ethernet

Manual Version 1006-001
OPC Server Ethernet

[ OPC Server Ethernet Manual / Intro ]
COPYRIGHT
Intro
The 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 Technology
Ostendstrasse 50A
D-90482 Nuremberg
Tel: + 49 911 / 5 44 27-0
Fax: + 49 911 / 5 44 27-27
Web: www.inat.de
Email: info@inat.de
All rights reserved.

______________________________________________________
Step®, Simatic® und Sinec® sind eingetragene Warenzeichen der Siemens AG.
OPC Server Ethernet
Page 2
CONTENT
Intro
1 Introduction....................................................................................................................... 8
1.1 General .................................................................................................................................................. 8
1.2 Scope of Supply .................................................................................................................................... 9
1.3 System Requirements .......................................................................................................................... 9
1.4 OPC Overview ....................................................................................................................................... 9
1.4.1 What is OPC?.................................................................................................................................. 9
1.4.2 OPC DA Specification .................................................................................................................. 10
2 Getting Started........................................................................................................... 14
2.1 Installation of the OPC Server ............................................................................................................ 14
2.2 Installation of the H1 driver ................................................................................................................ 19
2.2.1 Change number of H1 connections .............................................................................................. 20
2.2.2 Allow overwriting the MAC Address .............................................................................................. 20
2.2.3 Do not allow overwriting the MAC Address ................................................................................... 20
2.3 Installing the Server as Service ......................................................................................................... 21
2.4 Changing Server Type......................................................................................................................... 21
2.5 Licensing ............................................................................................................................................. 22
2.5.1 Licensing with dongle .................................................................................................................... 22
2.5.2 Licensing with license request code .............................................................................................. 22
2.6 Updating and Upgrading..................................................................................................................... 24
2.6.1 Update ........................................................................................................................................... 24
2.4.2 Upgrade......................................................................................................................................... 24
3 Communication Basics ............................................................................... 26

3.1 Job types ............................................................................................................................................. 26
3.1.1 SEND / RECEIVE.......................................................................................................................... 26
3.1.2 WRITE active / WRITE passive..................................................................................................... 26
3.1.3 FETCH active / FETCH passive .................................................................................................... 26
3.1.4 FETCH on EVENT ........................................................................................................................ 27
3.2 Connections ......................................................................................................................................... 27
OPC Server Ethernet
3.2.1 TCP/IP Connections ...................................................................................................................... 28

3.2.2 H1 Connections ............................................................................................................................ 29
3.2.3 RFC1006 Connections .................................................................................................................. 31
3.3 S5 Connections .................................................................................................................................. 32
3.4 S7 Connections .................................................................................................................................. 33
3.4.1 Not parameterizable connections (Standard connections)............................................................ 34
Page 3
3.4.2 Parameterizable connections ....................................................................................................... 34

Intro
3.5 Modbus Connection ........................................................................................................................... 34

3.6 NetLink Connection ............................................................................................................................ 35
3.7 PLC-5 Connection .............................................................................................................................. 35
3.8 MELSEC-Q Connection ...................................................................................................................... 36
4 Configuration .............................................................................................................. 38
4.1 Required steps for OPC Communication ......................................................................................... 38
4.2 Setting up a new connection .............................................................................................................. 39
4.2.1 Edit TCP/IP Parameters ................................................................................................................ 41
4.2.2 Edit H1 Parameters ...................................................................................................................... 48
4.3 Shutting down the OPC Server .......................................................................................................... 52
4.4 Alias Configuration ............................................................................................................................ 53
4.4.1 Import Step 7 Symbols ................................................................................................................. 54
4.5 Server Settings ................................................................................................................................... 55
4.5.1 Protocol Timer Tick........................................................................................................................ 55
4.5.2 Configuration file ........................................................................................................................... 55
4.5.3 Data types .................................................................................................................................... 56
4.5.4 Echo Written Data back to Client .................................................................................................. 56
4.5.5 Show Server Icon in the task bar .................................................................................................. 56
4.6 Server Optimisation ............................................................................................................................ 57
4.6.1 Combine coherent blocks always (max)........................................................................................ 57
4.6.2 Chronological Order is preserved.................................................................................................. 57
4.6.3 Write every item separately (off) ................................................................................................... 57
4.6.4 Write with Priority, Chronological Order is Preserved.................................................................... 57
4.6.5 Writes with immediate positive Confirm (default: No) .................................................................... 57
4.6.6 Read between Write (default: No) ................................................................................................. 57
4.7 Server Options .................................................................................................................................... 58
4.7.1 String Format................................................................................................................................. 58
4.7.2 Timeouts ........................................................................................................................................ 58
4.8 H1 Station Address ............................................................................................................................. 59
4.9 DCOM Configuration .......................................................................................................................... 60
4.9.1 User ............................................................................................................................................... 60
4.9.2 Computer properties for client and server machine ...................................................................... 60
4.9.3 OPC Server Settings for Server PC .............................................................................................. 62
4.10 Main window ...................................................................................................................................... 65
4.11 Logging............................................................................................................................................... 67
OPC Server Ethernet
4.12 Suspend and resume the OPC Server ............................................................................................. 69
Page 4
5 Item ID Syntax ............................................................................................................. 72
Intro
5.1 S7 Item ID Syntax ................................................................................................................................ 72
5.2 S5 Item ID Syntax ................................................................................................................................ 75
5.3 Modbus Item ID Syntax ....................................................................................................................... 79
5.4 Send / Receive Item ID Syntax ........................................................................................................... 81
5.5 PLC-5 Item ID Syntax .......................................................................................................................... 83
5.6 Mitsubishi Item ID Syntax ................................................................................................................... 85
5.7 Arrays ................................................................................................................................................... 87
5.8 Suffixe................................................................................................................................................... 88
5.8.1 Suffix BA........................................................................................................................................ 88
5.8.2 Suffix BCD ..................................................................................................................................... 88
5.8.3 Suffix D .......................................................................................................................................... 89
5.8.4 Suffix DT........................................................................................................................................ 89
5.8.5 Suffix DU ....................................................................................................................................... 90
5.8.6 Suffix KA........................................................................................................................................ 90
5.8.7 Suffix KF ........................................................................................................................................ 90
5.8.8 Suffix KG ....................................................................................................................................... 90
5.8.9 Suffix KT ........................................................................................................................................ 91
5.8.10 Suffix RI ....................................................................................................................................... 91
5.8.11 Suffix RU ..................................................................................................................................... 91
5.8.12 Suffix S5T .................................................................................................................................... 91
5.8.13 Suffix SWAB ................................................................................................................................ 91
5.8.14 Suffix T ........................................................................................................................................ 92
5.8.15 Suffix TOD ................................................................................................................................... 92
5.8.16 Suffix TR...................................................................................................................................... 92
5.9 Bit Masking .......................................................................................................................................... 92
5.10 Special Items...................................................................................................................................... 93
5.10.1 Pollinterval ................................................................................................................................... 93
5.10.2 Storesettings ............................................................................................................................... 94
5.10.3 Maxinterval .................................................................................................................................. 94
5.10.4 Itemcount..................................................................................................................................... 94
5.10.5 Errorcount ................................................................................................................................... 94
5.10.6 Writecomplete ............................................................................................................................. 95
5.10.7 Status .......................................................................................................................................... 95
5.10.8 WriteItemCount ........................................................................................................................... 95
5.10.9 WriteStatusMsg ........................................................................................................................... 95
5.10.10 Servercycle................................................................................................................................ 98
6 OPC Client ....................................................................................................................... 100

OPC Server Ethernet
6.1 Connect Client and Server................................................................................................................ 100

6.3 Add OPC Items ................................................................................................................................. 102
6.4 Browse the Server Address Space .................................................................................................. 103
6.5 Read real-time values ....................................................................................................................... 103
Page 5
6.6 Write control values ......................................................................................................................... 104

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

7.1 Win.ini ................................................................................................................................................. 108
OPC Server Ethernet
Page 6
C H A P T E R 1:
INTRODUCTION
[ OPC Server Ethernet Manual / Chapter 1: Introduction ]
1 INTRODUCTION
Chapter 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 Protocols

OPC Server TCPIPH1 ● TCP/IP ● S7 Protocol
(Order No.: 100-3100-01) ● RFC1006 ● S5-AP
● PLC Header ● Modbus on TCP
● ISO (H1) ● AB PLC-5
● Melsec-Q
● Send / Receive
● NetLink
OPC Server H1 ● ISO (H1) ● S7-Protokoll
(Order No.: 100-3110-01) ● S5-AP
● Send / Receive
OPC Server TCPIP-S ● TCP/IP ● S7-Protokoll
(Order No.: 100-3120-01) ● RFC1006 ● S5-AP
● PLC Header ● Modbus on TCP
● AB PLC-5
● Melsec-Q
● Send / Receive
● NetLink
OPC Server TCPIP-I ● TCP/IP ● S7 Protocol
(Order No.: 100-3150-01) ● PLC Header ● S5-AP
● Modbus on TCP
● Send / Receive
● NetLink
OPC Server TCPIP-M ● TCP/IP ● Melsec-Q
(Order No.: 100-3160-01) ● PLC Header ● Send / Receive
OPC Server Modbus ● TCP/IP ● Modbus on TCP
(Order No.: 100-3140-01) ● PLC Header ● Send / Receive
● NetLink
OPC Server Ethernet
Page 8
1.2 Scope of Supply
Before 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 Manuals
Optional: 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
OPC Server Ethernet
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.
Page 9
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 model

The OPC Specification defines three hierarchical classes for data access:
OPCServer, OPCGroup und OPCItem
OPC Server Ethernet
Class: OPCServer
An 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.
Page 10
All INAT Ethernet OPC Servers have the following ProgID:
INAT TCPIPH1 OPC Server
Class: OPCGroup
An OPCGroup object structures the variables used by the server. The OPCGroup manages the single
process variables, the OPC items.
Class: OPCItem
An 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 server
Quality the latest quality read from the server
Time Stamp time when the latest value was read
OPC Server Ethernet
Page 11
OPC Server Ethernet
Page 12
C H A P T E R 2:
G E T T I N G S TA R T E D
[ OPC Server Ethernet / Chapter 2: Gettings Started ]
2 GETTING STARTED
Chapter 2: Getting Started
2.1 Installation of the OPC Server

The 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.

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.
Page 14
7. Select the installation language and click „OK“.

8. Select „Next“.
9. Accept the license agreement with „Yes“.

OPC Server Ethernet
11. Select the directory, where the server shall be installed

(Default: C:\Programme\INAT\OPC Server Ethernet\) and confirm with „Next“.
Page 15
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 Server Ethernet
Page 16

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“.
OPC Server Ethernet
18. To install the OPC components of the OPC Foundation, you must accept the license agreement. Select
„Next“.
Page 17
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!
OPC Server Ethernet
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.
Page 18
2.2 Installation of the H1 driver

If 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
OPC Server Ethernet
The installation of the PC-H1 protocol driver requires a system reboot
Page 19
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.
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 Address

With 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.
been made. Now it is no longer possible to change (overwrite) the Ethernet address during runtime.
NOTE
OPC Server Ethernet
Page 20
2.3 Installing the Server as Service

In 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 Type

The 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.
OPC Server Ethernet
Page 21
2.5 Licensing
NOTE
In conjunction with RAID systems and Cluster stations, Dongle licensing is
required!
2.5.1 Licensing with dongle

The 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.

OPC Server Ethernet
● 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.
Page 22
Example:

-----------------------------------------
Product : OPC-Server TCPIPH1
Order No : 100-3100-01
Customer : Company ABC
User : User XYZ
Request : 0DQR70H0CH3CMXL
Confirm :
=========================================
● Send the data:

- by fax to +49 911/54427-27 or
- by email to info@inat.de.
● Dueto 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 valid
Checksum is wrong Please check the codes
No valid license If the test runtime is over (by default 72h) the server ends
OPC Server Ethernet
Page 23
2.6 Updating and Upgrading

INAT 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 Update
Updates 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.06

Current 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 Upgrade
Upgrades 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.06

Current 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
OPC Server Ethernet
Page 24
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 Ethernet Manual / Chapter 3: Communication Basics ]
3 COMMUNICATION BASICS
Chapter 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 Types
Send Direct
Receive Direct
Fetch Active (Read Active)
Write Active
Fetch on Event Active
3.1.1 SEND / RECEIVE

SEND / 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 passive

The 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 passive

The 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
OPC Server Ethernet
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
Page 26
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 EVENT

FETCH 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 Connections
To 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
Connection
OPC
Active Passive
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.
OPC Server Ethernet
Page 27
Communication partner 2
Communication partner 1 H1 Connection

MAC Address 1 MAC Address 2
OPC local TSAP local TSAP
remote TSAP remote TSAP
Active TCP Connection Passive

IP Address 1 IP Address 2
Port Port
RFC1006 Connection
MAC Address 1 MAC Address 2
Port 102 Port 102
local TSAP local TSAP
remote TSAP remote TSAP
3.2.1 TCP/IP Connections

TCP/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
OPC Server Ethernet
verifying that the data reached the other end of the network
correctly. UDP uses port numbers to deliver data to the correct
applications process.
Page 28
3.2.1.1 Required Parameters for TCP connections

TCP/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 number
TCP/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 = SOCKET

197.12.18.13 80 197.12.18.13, 80
STATION A STATION B
Port Port
IP Address A 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-
OPC Server Ethernet
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-
Page 29
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 connections

H1 connections use the address information of TSAPs and MAC addresses
MAC Address Access to station

TSAPs Access to application
MAC Address
Ethernet 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.
TSAPs
H1 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 STATION B
Local TSAP
OPC Server Ethernet
Local TSAP
Remote TSAP Remote TSAP
MAC Adr. A MAC Adr. B

Page 30
3.2.3 RFC1006 Connections

TCP 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 STATION B
Local TSAP Local TSAP

Remote TSAP Remote TSAP
IP Address A IP Address B
OPC Server Ethernet
Page 31
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 Connection
Station A Station B
READ
OPC
WRITE
Read connection (passive)

OPC connection - Port
- Port for Read Write connection (passive)
- Port for Write - Port
RFC1006 and H1 Connection
Station A Station B
READ
OPC
WRITE
OPC connection Read connection (passive)

- Local TSAP - Local TSAP
- TSAP for Read - Remote TSAP
- TSAP for Write Write 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).
OPC Server Ethernet
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.
Page 32
3.4 S7 Connections

When communicating with a S7 PLC, read and write jobs can be handled via one connection.
TCP/IP Connection
Station A Station B
READ
OPC
WRITE
Read and Write

OPC connection connection (passive)
- Port for Read & Write - Port
RFC1006 or H1 Connection
Station A Station B
READ
OPC
WRITE
Read and Write

- Local TSAP - Local TSAP
- TSAP for Read & Write - 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.
OPC Server Ethernet
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
Page 33
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
Station A Station B
READ
OPC
WRITE
Read and Write

- Port for Read and Write - 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 Server Ethernet
Page 34
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
Station B with
Station A NetLink adapter
READ
OPC
WRITE
Read and Write

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
Station A Station B
READ
OPC
WRITE
Read and Write

OPC Server Ethernet
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.
Page 35
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
Station A Station B
READ
OPC
WRITE
Read and Write

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.
OPC Server Ethernet
Page 36
C H A P T E R 4:
C O N F I G U R AT I O N
[ OPC Server Ethernet Manual / Chapter 4: Configuration ]
4 CONFIGURATION
Chapter 4: Configuration
The INAT OPC server requires very small amount of configuration to function properly.
4.1 Required steps for OPC Communication
1. OPC Server Configuration

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
Set up connection
(Define Access Path) server. The connection defines the access path to
the hardware.
optional Server Settings
Users can change certain aspects of the server´s
behaviour. All these options and settings are descri-
optional Server Optimisation
bed in this chapter.
optional Server Options
2. Connect OPC Server and OPC Client

optional Define / Import symbols
Server and Client must be connected to communi-
optional
cate with each other. This is described in chapter 6.
DCOM Configuration
3. OPC Client Configuration

Connect OPC Server
2 and OPC Client In the OPC client you add OPC groups and items.
The handling of an OPC client is described in
chapter 6.
3 OPC Client Configuration
Add OPC Group
Add OPC Item
Read / Write
OPC Server Ethernet
Page 38
4.2 Setting up a new connection
For 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.
OPC Server Ethernet
● The following entries are required:
Page 39
Name
Enter a name for the connection. This access path name will be
used in the OPC client later, too.
Type of Connection
Select the used transport protocol H1 (ISO) or TCP/IP. When com-
municating via RFC1006 select TCP/IP.
Type of Protocol
Select 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 Server Ethernet
Page 40
4.2.1 Edit TCP/IP Parameters
4.2.1.1 Allow Cyclic Poll / Poll interval
If 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 permitted

Specifies 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 connection

Read 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 Protocol
Siemens S5-CPs, It is NOT possible to read and write through one con-
INAT S5-TCP/IP: 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 PLC

The 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 Event

Fetch 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 Server Ethernet
Page 41
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 name

Enter 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.
OPC Server Ethernet
4.2.1.11 No Header
When 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.
Page 42
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 RFC1006

With 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 TSAP

The 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
Local TSAP Remote TSAP
PLC
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:
OPC Server Ethernet
Page 43
First Group
contains device codes, for which ressources are provided in the S7

01: PG or PC
02: OS (MMI device)
03: e.g. Simatic S7 PLC
Second Group
contains the addresses of these components
Left Character (Bit 7....4):
Rack number multiplied by 2
Right 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 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 TSAPs
With 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 Server Ethernet
Page 44
Destination PLC
Parameters of the target device must be entered here.
S7 Subnet ID
Specify 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 Address
In case of a MPI subnet, enter the MPI address of the PLC. In case of a Profibus subnet enter the Profibus
addresse.
Slot Address
Enter 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 echolink

If you are using echolink that connects Industrial Ethernet with the subnet, check this button. Parameters of
the Routing PLC must be entered here.
OPC
ETHERNET
MPI (CPU) = 2 Profibus = 6
MPI (CP ) = 3
echolink Routing PLC
PROFIBUS
OPC Server Ethernet
Profibus = 2
Target PLC
Page 45
COM Port
Enter the Com Port of the echolink that is connected with the MPI interface of the S7 PLC.
Routing PLC
The 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 PLC

You 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 TSAPs
Press the button „Generate TSAPs“ when all settings are made. The TSAPs are generated and indicated.
OPC Server Ethernet
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.
Page 46
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 ACKs

This 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 / passive

Connection 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/UDP

TCP (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)
OPC Server Ethernet
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.
Page 47
4.2.2 Edit H1 Parameters

4.2.2.1 Allow Cyclic Poll / Poll interval

If 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 permitted

Specifies 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 connection

Read 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 Protocol
Siemens S5-CPs, It is NOT possible to read and write through one con-
INAT S5-TCP/IP: 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 PLC

The 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 Event

Fetch 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 Server Ethernet
Page 48
Advantages:
Data are only sent in case of an event
Cyclic poll is no longer required
Network traffic is reduced
4.2.2.6 Destination: Ethernet Address

Enter 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 TSAP

The 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

OPC Server Ethernet
PLC
The remote TSAPs are:

• TSAP for Read
• TSAP for Write
• TSAP for Unsolicited
Page 49
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 Group
contains device codes, for which ressources are provided in the S7
01: PG or PC
02: OS (MMI device)
03: e.g. Simatic S7 PLC
Second Group
contains the addresses of these components
Left Character (Bit 7....4):
Rack number multiplied by 2
Right 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 2E OPC communication with S7 CPU in rack 1, slot 14
NOTE:
OPC Server Ethernet
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.
Page 50
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 Number

Specifies 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 Priority
Priority 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.
OPC Server Ethernet
Page 51
● 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 Server

If 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 Server Ethernet
Page 52
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=Address
Example: speed=db5,W2
In this example the alias „speed“ represents the OPC item db5,W2
All 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=Address
OPC Server Ethernet
Example: Group1.speed=db5,W2
Page 53
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.

OPC Server Ethernet
DBs: Symbolic names of the data blocks are imported.

In addition arrays are resolved. Please note, that this enlarges
Arrays: the symbol file of the OPC server.
● You will find the imported items in the symbol file „tcpiph1.txt“.
Page 54
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 Tick

Here 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 file

All 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 file

To 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.
OPC Server Ethernet
4.5.2.2 Save several configuration files

There 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.
Page 55
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 Client

If 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 bar

If this selection is checked, the OPC server will be displayed as an icon in the task bar when the main
window is minimized.
OPC Server Ethernet
Page 56
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 thererfore
b) 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 preserved

The 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 Preserved

Write 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.
OPC Server Ethernet
Page 57
4.7 Server Options

4.7.1 String Format

There 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 string
S5 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.10
S5 syntax: db9s0.10
S7 string: db9g0.10 (forces a S7 string always)
4.7.2 Timeouts
AppTimeout [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 Server Ethernet
Page 58
4.8 H1 Station Address
In this dialog you are able to display the status of the network adapter and to change the current runtime
address if necessary.
Hardware Address
The hardware or Ethernet address of your network adapter is stored in a ROM
Chip on your adapter card.
Runtime Address
On default the field runtime address shows the same value as the hardware
address field.
Software Address
In 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 now
With 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.“
OPC Server Ethernet
Page 59
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 User
WORKGROUP DOMAIN
In a workgroup users that login on the In a domain, a group with all OPC
client and the server computer must be users should be created.
known on the other computer.
4.9.2 Computer properties for client and server machine

Browse to Console Root > Component Services > Computers and right click on My Computer. Select Pro-
perties.
OPC Server Ethernet
With General“, „Options“ and „MSDTC“ the default settings are used.
Page 60
Default Properties
Settings for Domain
WORKGROUP DOMAIN
Enable DCOM on this computer Enable Enable
Default Authentication Level None Connect
Standard Impersonation Level Anonym Identify
Default Protocols
On the Default Protocols Tab the Connection-oriented TCP/IP protocol should be moved to the top position.
OPC Server Ethernet
Page 61
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 PC

Browse 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 Server Ethernet
Page 62
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“

OPC Server Ethernet
Page 63
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 Server Ethernet
Page 64
4.10 Main window
The main window of the OPC server shows you the status of all access pathes during runtime.
ROW 1
Access Path
Name of the connection
The 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: / Write
Each 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 used
1 to 999: H1 connections
> 1000: TCP/IP connections
The 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
OPC Server Ethernet
Page 65
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 3
Identification
Data area (e.g. DATA BLOCK, FLAG, INPUT, OUTPUT etc.)
Green: the interval is being processed
Grey: no data are being requested
Red: the data area is not available or too short
Len:
Specifies the number of elements to be read
Items:
Specifies how many items are contained in this read interval and how many of them are active and/or inac-
tive
OPC Server Ethernet
Page 66
4.11 Logging
With 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:
OPC Server Ethernet
Page 67
ShowEvents
Detailed information that helps with troubleshooting.
ShowSend
Number of values, which were written from the server to the PLC up to now. Corre-
sponds with „WriteItemCount“ in the main window.
ShowReceive
Number of frames, which the server has read from the PLC up to now. Corresponds
with „RecMsg“ in the main window.
Show Poll Send and Receive
Records the PLCs response times. If “Show Send” or “Show Receive” are selected
and „Show Poll“ is not active, the logger entries are reduced drastically
Show Errors
Corresponds with the connection error for read and write in the main window.
ShowCreate Point
Shows the sum of items, which were created for this connection in the OPC client
and were registered in the server.
ShowActivate Point
Sum of items, which are active for this access path at the moment.
Show Access Path
Shows the connections, which are triggered by the OPC client.
Show Rec Values
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. Show Rec Values corresponds with
RecNewValue in the main window.
Show Send Values
Number 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 Symbols
Symbol file information is logged.
Verbose
OPC Server Ethernet
Activates or deactivates all logger entries, respectively.
Page 68
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 Server

Click the icon in the headline of the main window.
Suspend Protocol
This 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.
OPC Server Ethernet
Page 69
OPC Server Ethernet
Page 70
C H A P T E R 5:
I T E M ID S Y N TA X
[ OPC Server Ethernet Manual / Chapter 5: Item ID Syntax ]
5 ITEM ID SYNTAX
Chapter 5: Item ID Syntax
5.1 S7 Item ID Syntax

The 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 Note
Data Block DBx. BYTE Read / Write With blocks a block number
x is required (x = 1 to
Instant Block DIx. BYTE Read / Write 65535). There must be a dot
or a comma between block
number and data type
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 / Write
1 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 Server Ethernet
Page 72
<data type>

Examples
Syntax DB / DI M E/A PE /PA C/T Array Auffix OPC Data Type
BIT X DB5.X4.3 MX1.3 ------- ------- ------- ------- -------

VT_BOOL
BIT DB5.4.3 M1.3 E4.3 PE4.5 ------- ------- -------
VT_BOOL I4.3 PI4.5
A4.3 PA1.3
O4.3 PO1.3
BYTE B DB5.B2 MB4 EB4 PEB4 ------- DB5.B2.4 BA VT_BOOL | VT_ARRAY
VT_UI1 Byte DB5.Byte2 MByte4 EByte4 PEByte4 DB5.Byte2.4 BCD VT_UI1
FB4 IB4 PIB4 MB4.3 RI VT_R4
FByte4 IByte4 PIByte4 MByte4.3 RU VT_R4
AB5 PAB5 FB4.4
AByte5 PAByte5 FByte4.4
OB5 POB5 POB5.3
OByte5 POByte5 usw.
WORD W DB5.W3 MW4 EW4 PEW4 C5 DB5.W3.2 BA VT_BOOL | VT_ARRAY
VT_I4 Word DB5.Word3 MWord4 EWord4 PEWord4 Z5 DB5.Word3.2 BCD VT_I2
(VT_UI2*) FW4 IW4 PIW4 T5 MW4.2 D VT_BSTR
FWord4 IWord4 PIWord4 EWord4.2 DT VT_BSTR
AW5 PAWord5 PAWord5.3 DU VT_BSTR
AWord5 PAWord5 C5.3 KF VT_I2
OW5 POW5 Z5.10 KT VT_BSTR
OWord5 POWord5 T5.2 RI VT_R4
QWord5 usw. RU VT_R4
S5T VT_BSTR
SWAB VT_I4 (VT_UI2*)
TR VT_R4
INT I DB5.I3 MI4 EI4 PEI4 ------- DB5.I3.2 BA VT_BOOL | VT_ARRAY
VT_I2 Int DB5.Int3 MInt4 EInt4 PEInt4 DB5.Int3.2 BCD VT_I2
FI4 II4 PII4 MI4.4 DT VT_BSTR
FInt4 IInt4 PIInt4 FInt4.3 DU VT_BSTR
AI5 PAI5 AInt5.3 KT VT_BSTR
AInt5 PAInt5 OI5.2 RI VT_R4
OI5 POI5 OInt5.5 RU VT_R4
OInt5 POInt5 POInt5.4 S5T VT_BSTR
usw. SWAB VT_I2
TR VT_R4
DOUBLE DW DB5.DW3 MDW4 EDW4 PEDW4 ------- DB5.DW3 BA VT_BOOL | VT_ARRAY
WORD Dword DB5. MDWord4 EDWord4 PEDWord4 MDW4.2 BCD VT_I4
VT_R8 Dword3 FDW4 IDW4 PIDW4 FDW4.2 KF VT_I4
(VT_UI4*) FDWord4 IDWord4 PIDWord4 EDW4.4 KG VT_R4
ADW5 PADW5 ADWord5.8 RI VT_R4
ADWord5 PADWord5 PEDW4.8 RU VT_R4
ODW5 PODW5 PADW5.4 S5T VT_BSTR
ODWord5 PODWord5 PODW5.4 SWAB VT_R8 (VT_UI4*)
QDW5 usw. T VT_BSTR
TOD VT_BSTR
DOUBLE D DB5.DI3 MDI4 EDI4 PEDI4 ------- DB5.D3.2 BA VT_BOOL | VT_ARRAY
INT DI DB5.DInt3 MDInt4 EDInt4 PEDInt4 DB5.DI3.2 BCD VT_I4
VT_I4 DInt FDI4 IDI4 PIDI4 DB5.DInt3.4 KG VT_R4
OPC Server Ethernet
FDInt4 IDInt4 PIDInt4 MDI4.5 RI VT_R4

ADI5 PADI5 EDI4.5 RU VT_R4
ADInt5 PADInt5 ADI5.2 SWAB VT_I4
ODI5 PODI5 PEDI4.5 T VT_BSTR
ODInt5 PODInt5 PADInt5.2 TOD VT_BSTR
QDI5 usw.
Continuation next page...
Page 73
REAL R DB5.R2 MR4 ER4 PER4 ------- DB5.R2.2 ------- -------

VT_R4 Real DB5. MREAL4 EREAL4 PEREAL4 DB5.
REAL2 IR4 PIR4 REAL2.4
IREAL4 PIREAL4 MR4.5
AR4 PAR4 ER4.4
AREAL4 PAREAL4 AREAL4.5
OR4 POR4 PER4.2
OREAL4 POREAL4 PAR4.7
POR4.3
usw.
STRING S DB5.S1.2 MS2.3 ------- ------- ------- ------- KA VT_BSTR
VT_BSTR String DB5. MString2.3
String1.2
S7- G DB5.G2.2 MG2.3 ------- ------- ------- ------- KA VT_BSTR
STRING
VT_BSTR
* if „also unsigned“ is selected as data type (Server Settings)
Note: Counter and Timer

Counters 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
OPC Server Ethernet
[suffix]
With the help of a suffix a value can be described in another format. Learn more about suffixes in chapter
5.8
Page 74
5.2 S5 Item ID Syntax

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

[Group.]
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
Expanded Data DXx WORD Read / Write 65535).
Blocks
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 OB BYTE Read / Write
Bytes
System Data Area RS or BS WORD Read
Absolute Memory AS WORD Read
1 BYTE oriented means, that per physical address a byte is addressed
OPC Server Ethernet
Page 75
<data type> for data blocks and expanded data blocks

Syntax Example Array Suffixe OPC Data Type
BIT D DB5D4.12 ------- ------- -------

VT_BOOL
BYTE DB DB5DB3 DB5DB3.5 BA VT_BOOL | VT_ARRAY
VT_UI1
LEFT BYTE DL DB5DL4 DB5DL4.2 BA VT_BOOL | VT_ARRAY
VT_UI1
RIGHT BYTE DR DB5DR2 DB5DR2.5 BA VT_BOOL | VT_ARRAY
VT_UI1
WORD DW DB5DW4 DB5DW4.5 BA VT_BOOL | VT_ARRAY
VT_I4 BCD VT_I2
(VT_UI2*) D VT_BSTR
DT VT_BSTR
DU VT_BSTR
KF VT_I2
KT VT_BSTR
RI VT_R4
RU VT_R4
S5T VT_BSTR
TR VT_R4
DOUBLE WORD DD DB5DD3 DB5DD3.2 BA VT_BOOL | VT_ARRAY
VT_R8 BCD VT_I4
(VT_UI4*) IEEE VT_R4
KF VT_I4
KG VT_R4
RI VT_R4
RU VT_R4
SWAB VT_R8 (VT_UI4*)
T VT_BSTR
TOD VT_BSTR
STRING S DB5S2.3 ------- ------- -------
VT_BSTR
OPC Server Ethernet
Page 76
<data type> for all other areas

Syntax M E/A P / OB C/T/ mit Array sinnv. OPC
RS / AS Suffixe Datentyp
BIT M4.3 E4.3 ------- ------- ------- ------- -------
VT_BOOL F4.3 I4.3
A4.3
Q4.3
BYTE B MB4 EB4 PB4 ------- MB4.3 ------- -------
VT_UI1 FB4 IB4 OB4 FB4.4
AB5 EB4.4
QB5 IB4.5
AB5.2
QB5.5
PB4.2
OB4.3
WORD W MW4 EW4 PW2 C5 MW4.2 BA VT_BOOL | VT_ARRAY
VT_UI2 FW4 IW4 OW2 T5 FW4.4 BCD VT_I4* / VT_UI2**
VT_I4 AW5 RS4 EW4.5 D VT_BSTR
QW5 BS4 IW4.2 DT VT_BSTR
AS5 AW5.5 DU VT_BSTR
QW5.2 KF VT_I2
PW2.10 KT VT_BSTR
OW2.3 RI VT_R4
C5.5 RU VT_R4
T5.3 S5T VT_BSTR
RS4.2 SWAB VT_I4* / VT_UI2**
BS4.7 TR VT_R4
AS5.2
DOUBLE D MD4 ED4 PD5 ------- MD4.4 BA VT_BOOL | VT_ARRAY
WORD FD4 ID4 OD5 FD4.2 BCD VT_I4
VT_R4(*) AD5 ED4.6 IEEE VT_R4
VT_UI4** QD5 ID4.2 KF VT_I4
AD5.6 KG VT_R4
QD5.2 RI VT_R4
PD5.4 RU VT_R4
OD5.9 SWAB VT_I4
T VT_BSTR
TOD VT_BSTR
STRING S MS4.5 ------- ------- ------- ------- ------- -------
VT_BSTR FS4.5
Note: Counter and Timer

Counters 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>
OPC Server Ethernet
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.
Page 77
<.bit number>

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]
[suffix]
5.8
OPC Server Ethernet
Page 78
5.3 Modbus Item ID Syntax

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

[Group.]
Example:
G1.40001
G2.R2
G3.S20.30
<area>
Syntax Number Orientation1 Access Rights
Discrete Inputs I 1xxxxx BIT Read
E
DI
DE
Discrete Outputs A 0xxxxx BIT Read / Write
O
Q
DA
DO
DQ
Input Register ER 3xxxxx WORD Read
IR
Register R 4xxxxx WORD Read / Write
(Holding Register) HR
1 BIT oriented means, that per physical address one 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
OPC Server Ethernet
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“
Page 79
<data type>
Syntax Syntax Syntax Syntax with Suffix OPC Data Type

R E/A ER Array
BIT X RX5.2 E255 ------- ------- ------- -------
VT_BOOL HRX5.2 I255
4X5.2 DE255
DI255
125543
WORD ohne R50 ------- ER120 R50.2 BA VT_BOOL | VT_ARRAY
VT_I2 HR50 IR120 HR50.2 BCD VT_I2
400050 312034 400050.2 D VT_BSTR
ER120.2 WDT* VT_BSTR
IR120.2 KT VT_BSTR
312034.2 RI VT_R4
RU VT_R4
S5T VT_BSTR
SWAB VT_I2
DOUBLE D RD50 ------- ERD120 RD50.3 BA VT_BOOL | VT_ARRAY
WORD HRD50 HRD50.3 BCD VT_I4
VT_I4 4D50 4D50.3 SWAB VT_I4
ERD120.3 KG VT_R4
IEEE VT_R4
TR VT_R4
RI VT_R4
RU VT_R4
T VT_BSTR
WDT*** VT_BSTR
STRING S RS5.4 ------- ERS5.4 ------- KA VT_BSTR
VT_BSTR SWAB VT_BSTR
* Suffix WDT (Wago Date and Time) uses 4 registers (8 bytes)
<start address>
Example: ER120: Input Register 120 is the start address for data to be read
<.bit number>
HRX5.2: Bit 2 of Holding Register 5 is addressed here
[.array]
[suffix]
OPC Server Ethernet
5.8
Page 80
5.4 Send / Receive Item ID Syntax

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

<job>
Syntax
SEND S
RECEIVE R
<data type>
Syntax Syntax Syntax Array Suffix OPC Data Type

Send Receive
BIT X SX1.2 RX1.2 ------- ------- -------
VT_BOOL
BIT none S1.2 R1.2 ------- ------- -------
VT_BOOL
BYTE B SB4 RB5 SB4.4 BA VT_BOOL | VT_ARRAY
VT_UI1 BYTE SBYTE4 RBYTE5 SBYTE4.5 BCD VT_UI1
RB5.2 RI VT_R4
RBYTE5.2 RU VT_R4
CHAR C SC4 RC5 SC4.2 BA VT_BOOL | VT_ARRAY
VT_BSTR CHAR SCHAR4 RCHAR5 SCHAR4.2 DT VT_BSTR
RC5.4
RCHAR5.4
WORD W SW10 RW10 SW10.2 BA VT_BOOL | VT_ARRAY
VT_I4 WORD SWORD10 RWORD10 SWORD10.2 BCD VT_I2
(VT_UI2*) RW10.2 D VT_BSTR
RWORD10.2 KF VT_I2
KT VT_BSTR
RI VT_R4
RU VT_R4
S5T VT_BSTR
TR VT_R4
INT I SI4 RI5 SI4.2 BA VT_BOOL | VT_ARRAY
VT_I2 INT SINT4 RINT5 SINT4.2 BCD VT_I2
RI5.5 KT VT_BSTR
RINT5.5 RI VT_R4
OPC Server Ethernet
RU VT_R4
S5T VT_BSTR
SWAB VT_I2
TR VT_R4
Continuation next page...
Page 81
SD6 RD6 SD6 BA VT_BOOL | VT_ARRAY

DOUBLE D
WORD DW SDW6 RDW6 SDW6 BCD VT_I4
VT_R8 DWORD SDWORD6 RDWORD6 SDWORD6 KF VT_I4
(VT_UI4*) RD6 KG VT_R4
RDW6 RI VT_R4
RDWORD6 RU VT_R4
SWAB VT_R8 (VT_UI4*)
T VT_BSTR
DOUBLE INT DI SDI6 RDI6 SDI6.2 BA VT_BOOL | VT_ARRAY
VT_I4 DINT SDINT6 RDINT6 SDINT6.2 BCD VT_I4
RDI6.5 KG VT_R4
RDINT6.5 RI VT_R4
RU VT_R4
SWAB VT_I4
T VT_BSTR
REAL R SR2 RR2 SR2.2 ------- -------
VT_R4 REAL SREAL2 RREAL2 SREAL2.2
RR2.5
RREAL2.5
STRING S SS5.2 RS5.2 ------- KA VT_BSTR
VT_BSTR STRING SSTRING5.2 RSSTRING5.2 DT VT_BSTR
S7-STRING G SG5.2 RG5.2 ------- KA VT_BSTR
VT_BSTR DT VT_BSTR
<start address>
Example: SWORD10: Word 10 is the start address for data to be sent or received
<.bit number>
Example: SX1.2: Bit 2 in byte 1 is the start address to be sent or received
[.array]
[suffix]
5.5
OPC Server Ethernet
Page 82
5.5 PLC-5 Item ID Syntax

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

<area>
Syntax Orientation1 Access Rights
Output 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 / Write
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

OPC Server Ethernet
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.
Page 83
<: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 Description
O.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]
Example: N23:4.10. Learn more about arrays in chapter 5.4
OPC Server Ethernet
Page 84
5.6 Mitsubishi Item ID Syntax

[group.]<range><start address>[.array][suffix]
[group.]
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 DEZ
<start address>
OPC Server Ethernet
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)
Page 85
[.array]
Example: X10.5. Learn more about arrays in chapter 5.4
[suffix]
5.5
Suffixe OPC data type Examples
Data Register RU VT_R4 D20RI
RU VT_R4 W40KF
Link Register BCD VT_I2 TN5SWAB
Timer Current Value KF VT_I2 CN4BA
SWAB VT_I4 (VT_UI2*) Z20RU
Counter Current Value BA VT_BOOL | VT_ARRAY R10KF
Index Register
File Register
OPC Server Ethernet
Page 86
5.7 Arrays

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
OPC Server Ethernet
Page 87
5.8 Suffixe
With 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 Syntax
BitArray 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 BA
With the Suffix BA the data stored in the PLC is interpreted and presented as an array of bits.
Suffix BA: Bit Array
Applicable with: Byte (LByte, RByte), Word,
Int, Double Word, Double Int
Range: True or False
5.8.2 Suffix BCD

With 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 BCD
OPC Server Ethernet
Applicable with: Byte (LByte, RByte), Word, Int,

Double Word, Doube Int
Range: Byte: 0 to 99
Word: 0 to 9999
Int: 0 to 9999
Double Word: 0 to 99999999
Double Int: 0 to 99999999
Page 88
5.8.3 Suffix D

With 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: Date
Applicable 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 1999
00 till 89  2000 till 2089
Month 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 DT
With 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 Time
Applicable 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 Millisecond 0 till 999 + weekday in the
Byte n+7 last 4 bytes
OPC Server Ethernet
1 = sunday
7 = saturday
Page 89
Rules using Suffix DT:

Year four-digit 1990 till 2089

Month two-digit 01 till 12
Day two-digit 01 till 31
Hour two-digit 00 till 23
Minute two-digit 00 till 59
Second two-digit 00 till 59
Millisecond three-digit 000 till 999
5.8.5 Suffix DU
With 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 KA
With 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 KF
With Suffix KF the data stored in the PLC is interpreted and presented as signed integer (fixed-point
number).
Suffix KF
Applicable with: Byte (LByte, RByte, S5), Word (S5), Double
Word (S5)
Range: Byte: -128 till 127
Word: -32768 till 32767
Double Word: -2147483648 till 2147483647
5.8.8 Suffix KG
With 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 Server Ethernet
Page 90
5.8.9 Suffix KT

With 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
Range: 000.0 bis 999.3
5.8.10 Suffix RI
With 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 Real

Double Word, Double Int
5.8.11 Suffix RU
With 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 Real
Double Word, Double Int
5.8.12 Suffix S5T

With 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: S5TIME
Range: 0ms till 2h46m30s
5.8.13 Suffix SWAB

With Suffix SWAB the high byte and low byte of the data stored in the PLC are changed.
Suffix SWAB
Applicable with: Word, Int, Double Word, Double
Int
OPC Server Ethernet
Range: Changes High Byte and Low Byte
Page 91
5.8.14 Suffix T
With 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: TIME
Applicable with: Double Word
Range: -24D_20H_31M_23S_648MS till
24D_20H_31M_23S_647MS**
5.8.15 Suffix TOD

With 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 DAY
Applicable with: Double Word, Double Int
Range: 0:0:0.0 till 23:59:59.999
5.8.16 Suffix TR
With the Suffix TR the data stored in the PLC is interpreted and presented as data type TIME REAL.
Suffix TR: TIME REAL
Range: 0.01 till 9990.0
5.9 Bit Masking

With 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.
Example
8 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 or
db5.w0#2,8 or
OPC Server Ethernet
db5.w0#2#8
Page 92
5.10 Special Items

This 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 Type
Pollinterval VT_I4
Maxinterval VT_I4
Storesettings VT_BOOL
Itemcount VT_I4
Errorcount VT_I4
Writecomplete VT_I4
Status VT_BOOL
WriteItemCount VT_I4
WriteStatusMsg VT_BSTR
ServerCycle VT_I4
DbOffset VT_I4
DwOffset VT_I4
5.10.1 Pollinterval
The 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_I4
Access: READ, WRITE
Range: 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
OPC Server Ethernet
having to deactivate the items.
Page 93
5.10.2 Storesettings
The 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_BOOL
Access READ, WRITE
Range: 0 or 1
5.10.3 Maxinterval
The 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_I4
Access: READ
Range: 0 till 2147483647
5.10.4 Itemcount
The 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“.
Access: READ
Range: 0 till 2147483647
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.
Access: READ
Range: 0 till 2147483647
OPC Server Ethernet
NOTE:
Use the ERRORCOUNT item to detect wrongly configured or invalid items
Page 94
5.10.6 Writecomplete

The 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).
Access: READ, WRITE
Range: -1, 0 or 1
5.10.7 Status
The 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 WriteItemCount
The 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 WriteStatusMsg
The 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
OPC Server Ethernet
Page 95
Identifier
Identifier
1 DATA BLOCK
2 FLAG
3 INPUT
4 OUTPUT
5 PERIPHERY
6 COUNTER
7 TIMER
8 SYSTEM_DATA
9 ABSOLUTE_MEMORY
10 EXPANDED DATA BLOCKS
16 EXTMEM
17 EXT_PERIPHERAL
DB
Specifies the block number for DATA BLOCK and EXPANDED DATA BLOCK. Otherwise 0 (i.e., can be
disregarded).
DW
Specifies the start value at which the interval begins.
Len
Specifies the number of elements.
PLC Error
Indicates 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 Server Ethernet
Page 96

0 No error
1 Wrong Q/ZTYP in the handling block
2 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 format
7 No free data buffer
8 No free transport connections
9 Error of communication partner
10 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 RESET
14 Job with READ/WRITE (PLC unable to trigger)
15 Job does not exist
16 System error
Connection error
1 BAD_CR_PARAMS
2 NO_SLOT
3 WAIT_CONNECT
4 NOT_IMPLEMENTED
5 BAD_LINE
6 WAIT_DATA
7 WAIT_SEND
8 INTERNAL_ERROR
9 NO_REQUEST
10 NO_DRIVER
11 UEBERLAST
12 BLOCKED_DATA
13 NO_ADAPTER
14 ALREADY_RUNNING
OPC Server Ethernet
15 NOT_SUPPORTED
16 TRY_AGAIN
17 NO_MEMORY
18 BAD_SIGNATURE
19 DATA_ERR (Data error FETCH / WRITE)
Page 97
5.10.10 Servercycle
This items shows the number of complete updates of the server for the corresponding connection.
Access: READ, WRITE
Range: -2147483648 till 2147483647
OPC Server Ethernet
Page 98
C H A P T E R 6:
OPC C L I E N T
[ OPC Server Ethernet Manual / Chapter 6: OPC Client ]
6 OPC CLIENT
Chapter 6: OPC Client
The 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 Server

The 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
OPC Server Ethernet
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.
Page 100

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 Rate
The 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.
Active
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 deacti-
vating groups and items that are not currently needed.
OPC Server Ethernet
Page 101
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 Path
The 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 ID
Example (PLC1 = access path name):
[PLC1]DB5.W0
PLC1.DB5.W0
Item 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 Server Ethernet
Page 102
6.4 Browse the Server Address Space

The 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,
OPC Server Ethernet
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.
Page 103
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 Server Ethernet
Page 104

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.
OPC Server Ethernet
Page 105
OPC Server Ethernet
Page 106
C H A P T E R 7:
APPENDIX
[ OPC Server Ethernet Manual / Appendix ]
7 APPENDIX
Appendix
7.1 Win.ini
Win.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 Server Ethernet
Page 108
[ OPC Server Ethernet Manual / Index ]
INDEX
Index
Symbole FETCH on EVENT 27
Fetch on Event 41, 48
200H1Connections.reg 20 First transition from Ethernet to MPI is echolink 45
A H
Access Path 102 H1ChangeAddress.reg 20
Active / Passive connection establishment for Unsolicited H1DoNotChangeAddress.reg 20
51 H1 Connections 29
Address Space 103 H1 connections
Add OPC Groups 101 change number 20
Add OPC Items 102 H1 driver 19
Alias Configuration 53 H1 Parameters 48
Allow Cyclic Poll 41, 48 H1 Parameter Settings 40
Arrays 87 H1 Registry Scripts 20
ASCII to Hex 88 H1 Station Address 59
High Performance Protocol 47
B
BCD 88
I
BitArray 88 Import Step 7 Symbols 54
Bit Masking 92 Import Step 7 symbol comments 55
Browse the Server Address Space 103 INAT TCPIPH1 OPC Server 100
Installation 14
C Introduction 8
Chronological Order is preserved 57 IP 28
Combine coherent blocks always (max) 57 IP Address 29
Communication Basics 26 Item-Syntax 72
Configuration 38 Itemcount 94
Configuration file 55
Connection 39
J
Connections 27 Job types 26
Connection Establishment 47
Connect Client and Server 100 L
Copyright 2
Licensing 22
Counter 74, 77
Life ACKs, Life Data ACKs 47
D Line Type 51
Local TSAP 43, 49
Data types 56 Logging 67
Date 88
Date and Time 88 M
Date and Time (SQL) 88
MAC Address 30
DCOM Configuration 60
Main window 65
Destination 42
Maxinterval 94
Destination: Ethernet Address 49
MELSEC-Q Connection 36
OPC Server Ethernet
E Mitsubishi Item Syntax 85

Modbus Connection 34
Echo Written Data back to Client 56 Modbus Item ID Syntax 79
Errorcount 94 MPI/PPI address 42
MPI/PPI Parameters 46
F MPI Address of the Routing PLC 46
FETCH active / FETCH passive 26 Multicast Number 51
Page 109
N Scope of Supply 9
Index
SendNewValue 66
NetLink Connection 35 SEND / RECEIVE 26
New connection 39 Send / Receive Item ID Syntax 81
Not parameterizable connections 34 ServerCycle 66
No Header 42 Servercycle 98
Server Optimisation 57
O Server Options 58
OLE for Process Control 9 Server Settings 55
OPC Server Type 18, 21
What is it? 9 Changing 21
OPC Client 100 Server types 8
OPC DA Specification 10 Service 21
OPC Overview 9 Setting up a new connection 39
OPC server types 8 ShowCreate Point 68
ShowEvents 68
P ShowReceive 68
ShowSend 68
Parameterizable connections 34 Show Access Path 68
PLC-5 Connection 35 Show Activate Point 68
PLC-5 Item Syntax 83 Show Errors 68
Pollinterval 93 Show Poll Send and Receive 68
Poll interval 41, 48 Show Rec Values 68
Port for Read 47 Show Send Values 68
Port for Unsolicited 47 Show Server Icon in the task bar 56
Port for Write 47 Show Symbols 68
Port number 29 Shutting down the OPC Server 52
Priority 51 Signed to Real 88
ProgID 10 Socket 29
Program ID 100 Special Items 93
Protocol TCP/UDP 47 Standard connections
Protocol Timer Tick 55 S7 34
Standard TSAPs for S7 Connections 50
R Start Address 0 42
Read and Write through one connection 41, 48 Start Address 1 42
Read between Write (default: No) 57 Status 95
Read Optimisation 47, 51 Storesettings 94
Read real-time values 103 String Format 58
RecMsg 66 Suffixe 88
RecNewValue 66 Suspend and resume the OPC Server 69
Registry 20 Suspend Protocol 69
Remote TSAP 43, 49 Swab Bytes 88
Resume Protocol 69 System Requirements 9
RFC1006 Connections 31
Routing PLC 46 T
Routing TSAPs 44 TCP 28
TCP/IP Connections 28
S TCP/IP Parameters 41
S5-KG 88 TCP/IP Parameter Settings 40
OPC Server Ethernet
S5-KT 88 TcpIpH1.NET 55
S5 Connections 32 Time 88
S5 Item ID Syntax 75 Timeouts 58
S5 Time 88 Timer 74, 77
S7 Connections 33 TimeReal 88
S7 Item ID Syntax 72 Time of Day 88
S7 Subnet ID 45 TSAPs 30
Page 110
TSAPs for S7 Connections 43
Index
U
UDP 28
Unit ID 42
Unsigned to Real 88
Unsolicited Data from PLC 41, 48
Update Rate 101
Updating 24
Upgrading 24
Use PLC Header 43
Use RFC1006 43
V
Verbose 68
W
Win.ini 108
Writecomplete 95
WriteItemCount 66, 95
WriteStatusMsg 95
Writes with immediate positive Confirm (default: No) 57
Write access to PLC permitted 41, 48
WRITE active / WRITE passive 26
Write control values 104
Write every item separately (off) 57
Write Single Coil 42
Write Single Register 42
Write with Priority, Chronological Order is Preserved 57
OPC Server Ethernet
Page 111
Index
OPC Server Ethernet
Page 112

OPC Server Ethernet

Uploaded by

Copyright:

Available Formats

You might also like

OPC Server Ethernet

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OPC Server Ethernet

Uploaded by

Copyright:

Available Formats

User´s Manual