opc gs e - RESolu COMresolucom.com/Document/opc_gs_e_01UK.pdf · 1.1 Installation of the OPC Server...

OPC ServerManual Version 0207-004ek

Getting Started

��

C O P Y R I G H T

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 licence agreement (i.e., one-time licence) 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 technological advances.

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

All rights reserved.

I M P O R TA N T N O T E S

You will find the recent version of this manual at: www.inat.de

_______________________________Windows 98, ME, 2000, NT, XP and 2003 are registered trademarks of the Microsoft Corp.

S C O P E O F S U P P LY

Before getting started with INAT OPC Server, check the following list of ele-ments that should be contained in the OPC Server package. • CDROM with � INAT OPC Servers � INAT Demo Software � INAT Manuals � OPC Test Client • Manual „Getting Started“• Optional Dongle• Optional Certifi cate

CONTENT

1 Installation and Licencing ..........................................................................61.1 Installation of the OPC Server .................................................................6 1.2 Installation of the H1 driver ....................................................................81.3. Installation of the Server as Service .......................................................81.4 Licencing the OPC Server .......................................................................9

1.4.1 Licencing with Dongle ...................................................................91.4.1 Licencing with licence confi rm code ..............................................9

1.5 Updating and Upgrading your OPC Server ........................................... 111.5.1 Update ........................................................................................ 111.5.2 Upgrade ....................................................................................... 11

2 Confi guration .............................................................................................142.1 General ................................................................................................142.2 Setting up a S7 connection ...................................................................20

2.2.1 S7 connections: General .............................................................202.2.2 Special Settings for S7 connections ............................................22

2.3 Setting up a S5 connection ..................................................................252.3.1 S5 connections: General .............................................................252.3.2 Speciel Settings for S5 Connections ...........................................272.3.3 Setting up connections on PLC side (S5 CP) .............................282.3.4 Programming handling blocks .....................................................40

2.4 Setting up a Modbus connection ..........................................................412.5 Setting up a NetLink / IBHLink connection ...........................................432.6 Setting up a Send / Receive connection ..............................................442.7 Setting up a PLC-5 connection ............................................................462.8 Setting up a MELSEC-Q connection ....................................................47

3 Client Settings ..........................................................................................503.1 OPC Test Client ....................................................................................50

C H A P T E R 1 :

I N S TA L L AT I O N

Chapter 1: Installation and Licencing

1 INSTALLATION AND LICENCING

1.1 Installation of the OPC Server1. 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. Insert the CDROM „OPC Server“. If autostart is not activated in your PC, use start.exe or index.html. If autostart is activated, the following dialogue appears:

„Installation“: a list of the files to install INAT OPC Server.„Software Overview“: a downloadable overview with INAT software and manu-als. „Informative Literature“: a downloadable overview with INAT informative litera-ture (press releases, manuals etc).

3. Select „Installation“. The following window appears. You are asked to select the required OPC Server.

Chap

ter 1

: Ins

talla

tion

and

Lice

ncin

g

4. Click the OPC Server Ethernet.5. Save the fi le in a directory of your choice.6. Run the .exe file. Be sure that there are no Windows programs running.7. Select the installation language and accept the licence conditions. Select

the directory, where the fi le shall be saved. Default: C:\Programs\INAT\OPC Server Ethernet\

8. Select complete, minimal or user installation.9. After the OPC Server installation, the Hardlock Device Driver and the OPC

Core Components are installed - if selected! If using a OPC Server, that consists of the ISO (H1-) driver, please read chapter 1.2 Installation of the H1 driver.

10. 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. This provides the opportunity to test the functional range of the diverse Server Types without installing another software.

Note: If you have already installed and licenced a server and change the server type your licence expires. You need a new licence confi rm code or a new dongle!

11. If you do not licence the OPC Server, it runs for 72 hours after every start or restart.


1.2 Installation of the H1 driver

NoteDuring 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: 1. After the installation of the OPC Server the window „network“ in the

system control opens. 2. Here you have to add „protocol“. Confirm the button „Disc“ and enter the

directory, where the H1 driver has been saved. 3. After the restart of your PC the OPC Server can be licenced.

1.3. Installation of the Server as ServiceAfter the installation the OPC Server runs as application. To install the Server as service, select Start > Programs > INAT > OPC Server Ethernet > Install 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.

Chap

ter 1

: Ins

talla

tion

and

Lice

ncin

g

1.4 Licencing the OPC Server

1.4.1 Licencing with DongleLicencing with dongle is the easiest form of licencing. The Server is portable and permanently licensed. You don´t have to deal with authorization codes.

1.4.1 Licencing with licence confirm code

NoteBefore licencing your OPC Server, the H1 driver has to be installed (this pertains only OPC Servers, that support the H1 protocol)

� After successful tests with the unlicenced test version install the Server at the final hardware location. Select „Help“ in the menu and then „Licen-cing“.

� 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 licence.

� Use the button Clipboard. The data for the licencing request are now available in the clipboard for pasting them to your favorite Email program. Note: The request code is unique for your system!


� Send the Licence Request Codevia Fax to 0911/54427-27 orvia Email to [email protected].

� Due to the contract with INAT you will get an unlimited Licence Confirm Code or a limited Licence Confirm Code for test purposes. Under Licence the following messages are possible:

Licence Status: Meaning:ok your licence is validChecksum is wrong Please check the codesno valid licence If the test runtime is over (by default 72h)

the server ends

Chap

ter 1

: Ins

talla

tion

and

Lice

ncin

g

1.5 Updating and Upgrading your OPC ServerINAT OPC Servers are improved and extended with helpful features on a regu-lar 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 licence and want to use the latest version by replacing it with your earlier version, please determine, if it is an Update or an Upgrade.

1.5.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.00.04Current Server: 3.03.38

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

1.5.2 Upgrade

Upgrades are not free. If the version number of your OPC Server begins with another number than the version number of the current version in the Internet, it is an Upgrade.

Example:

Your Server: 2.05.06Current Server: 3.03.38

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!You fi nd the version number of your Server in the menu Help >About... in your Server.

C H A P T E R 2 :

C O N F I G U R AT I O N

Chapter 2: Confi guration

2 CONFIGURATION

2.1 General � The configuration of the INAT OPC Server is very easy. � Start the Server via Start > Programs > INAT > OPC Server Ethernet

� Select Configuration > Access Path Definitions...

� Select Configuration > New

Chap

ter 2

: Con

fi gur

atio

n

Name: Enter a connection name.Type of Connection: Here you select the desired transport pro-

tocol in the Ethernet network: TCP/IP or H1 (select TCP/IP when using RFC1006)

Type of Protocol: Here you select the used application protocol S5, S7, Modbus, NetLink, PLC-5 or MELSEC-QIf NO application protocol is used (raw data) select „Send / Receive“.

� Depending on the selected protocol, the TCP/IP or the H1 parameteriza-tion window appears.

� For all protocols the following general connection parameters are provi-ded:

General connection parameters Allow Cyclic Poll / Poll interval: The read interval function specifies in msec the intervals at which user data are to be updated for process visualization. To keep the network load as low as possible, the intervals should be based on the importance of the particular user data (i.e., as short as necessary but as long as possible). When deactivating „Allow Cyclic Poll“, data are no longer read cyclic, but only if the Client requests it. This enables synchronous and asynchonous read jobs. Write Access to PLC PermittedThis item specifies whether a write access to the PLC is to be esta-blished. Write-accesses can be disabled in general here.

Continuation next page...


General connection parameters Read and Write through one ConnectionWith all application protocols (exception S5 protocol) it is possible to read and write through one connection. This is the default setting. There is only one port for read and write required when communica-ting via TCP/IP. There is only one TSAP for read and write required when communicating via RFC1006 or H1.

Exception: S5 protocolSiemens S5 CPs, INAT S5-TCP/IP

It is NOT POSSIBLE to read and write through one connection. One connection is required for the write job and another connection is required for the read 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.

Local TSAP, Remote TSAPTSAPs are required with H1 connections and with RFC1006 connec-tions. Local TSAPYour own TSAP (Transport Service Access Point) specifies the con-nection address in the system by which data is to be exchanged. Remote TSAPRemote TSAP for Read, Remote TSAP for Write and TSAP for Unso-licited specifies the connection address of the other system. Remote TSAP for Read, for Write and for Unsolicited should be addressed differently.

TSAPs are 2 bytes up to 16 bytes in length. Be sure to enter the TSAP (standard TSAPS) of S7 connections in the HEX field (see chapter 2.3). To be able to establish the connection, your Own TSAP must correspond to the TSAP of the other system.


Chap

ter 2

: Con

fi gur

atio

n

General connection parameters Connection active / passiveSelect the type of connection establishment (i.e. which station is to initiate connection establishment). At regular intervals, the active station attempts to set up the appropriate connection. There must not be the same entry on both sides of the connection.Special Settings: Read OptimisationWith activation of the radio button Read optimization, the OPC Server combines data bytes to blocks of a size, which can determine under Bytes for a new block. This procedure is very helpful if large gaps exist in the datablock structure of your PLC.Example: If you enter the value 100 bytes, all data ranges of 100 bytes and bigger are ignored by the Server, if they contain no data. In this way you are able to adjust the read procedure to the data structure of your PLC.

Special TCP/IP ParametersDestination: IP Address or NameIn a TCP/IP network each station is addressed with a unique desti-nation address. If the connection is set “active“, enter the IP address of the communication partner. If the connection establishment is “passive“ enter a joker address (0.0.0.0). No HeaderWhen communicating with a station, that supports only the „TCP/IP protocol“, select „No Header“. In this case the application software on both sides is responsible for monitoring. PLC HeaderFor communication with INAT components (S7-TCP/IP, S5-TCP/IP, echolink) you should activate the PLC Header. The header provides a frame counter, frame length infromation and the posibility to send acknowledges. RFC1006With the activation of RFC1006 the H1 frames, which have to be transmitted, are implemented in a TCP/IP frame. This special TCP/IP channel enables you to communicate with the Siemens CPs of the S5 and S7 series.Continuation next page...


Special TCP/IP Parameters Port for Read, Port for Write, Port for UnsolicitedThe port number is a 16-bit address from 0 to 65535. It specifies the channel via which the applicable connection is to be established. You should use a port between 1024 and 65535. On both sides of the connection, the port number must be the same. Port for Read, Write and Unsolicited should be addressed differently. Life Acks / Life Data AcksThis item „Life Acks / Life Data Acks“ activates the connection monitoring function which is restricted in many socket libraries. These telegrams are used to transfer the connection status to process visualization.The default setting of the „Life Acks“ and „Life Data Acks“ is activated.Protocol TCP/ UDPTCP is a secure protocol with checksum and confirmation. UDP is not a secure protocol. It is handled by datagam services. The TCP protocol should be selected for normal data transmission.High Performance Protocol(together with S7, Modbus, PLC-5 and MELSEC-Q)With activation of the High Performance Protocol, read and write requests are intelligently converted into a single field access to the target device. This reduces the number of data packets that must be transported over the network. This means greater shares of user data, better utilization of data packets and reduction of the network load. The server works particularly fast in this mode. Note: The S7-TCP/IP CP does not support the High Performance Protocol. It may not be activated.

Chap

ter 2

: Con

fi gur

atio

n

Special H1 ParametersDestination: Ethernet Address, CardIf the connection is set „active“, enter the Ethernet address of the partner station in the H1 network. The Ethernet address has a length of 6 Bytes. Enter the number of the Ethernet card, that is connected with the ISO (H1) network. Line Type„Line Type“ specifies whether the telegrams 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.Priority„Line 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.


2.2 Setting up a S7 connection

2.2.1 S7 connections: GeneralWhen communicating with a S7 PLC, read and write jobs can be handled via one connection. This works with Siemens CPs as well as with INAT CPs (INAT S7-TCP/IP, echolink).

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

Chap

ter 2

: Con

fi gur

atio

n

NOT PARAMETERIZABLE CONNECTIONS• Only on the OPC side a connection must be paramete-

rized, NOT on the PLC side.• Standard connections are used: these standard con-

nections use standard TSAPs / standard Ports.• There is only a limited number of standard connections

available. If they are not sufficient, „parameterizable connections“ must be used.

• Standard connections are available with Siemens CPs and with INAT S7-TCP/IP-CP.

• Standard connections with Siemens CPs are handled via RFC1006 or H1.

• Standard connections with INAT S7-TCP/IP are handled via TCP/IP with PLC Header.

PARAMETERIZABLE CONNECTIONS• The connection must be parameterized on both sides

of the communication (one connection in the OPC Server AND one connection in the S7-CP).

• If the communication is handled via echolink, parame-terizable connections are required.

Normally the standard connections are sufficient. That´s why in this manual only this connection type is explained. Please refer to the Online Help of the OPC Server or the Manual to learn more about „parameterizable connections“.


2.2.2 Special Settings for S7 connections

Special Parameters for S7 connectionsRead and Write through one connectionThis is the default setting. There is only one port for read and write required when communicating via TCP/IP. There is only one TSAP for read and write required when communicating via RFC1006 or H1. Fetch on EventIf Fetch on Event is activated, data from the PLC will no longer be polled cyclic, but transferred if a event occurs Note: This option can only be used with the INAT S7-TCP/IP and S5-TCP/IP RFC1006With the activation of RFC1006 the H1 frames, which have to be trans-mitted, are implemented in a TCP/IP-frame. This special TCP/IP channel enables you to communicate with the Siemens CPs of the S5 and S7 series.


Chap

ter 2

: Con

fi gur

atio

n

Special Parameters for S7 connectionsTSAPs – Special rules for S7With „not parameterizable connections“(= standard connections), stan-dard TSPAs are used:

Rules for Standard TSAPs – Siemens S7

First group: contains device codes, for which ressources are provided in the S7.01 PG or PC02 OS (MMI device)03 Simatic S7 PLCSecond group: contains the addresses of these componentsLeft character (Bit 7...4)

Rack number multiplied by 2.

Right character (Bit 3...0)

Slot (< 16) of the CPU. For S7-300 always slot 2 is used

00 Direct addressingExamples: 01 00 PC with OPC Server; direct addressing03 02 OPC communication with S7 CPU in rack 0, slot 203 43 OPC communication with S7 CPU in rack 2, slot 3 Standard TSAPs must be used on PLC side (remote TSAP of the OPC Server station); the own TSAP (local TSAP of the OPC Server station) is arbitraty, but should contain the same format (e.g. 01 01)

Note: Enter the standard TSAPs in the HEX fi eld! The remote TSAP of S7 connections is always 03 XY. X is the rack number multiplied by 2 and Y is the slot of the CPU.



Special Parameters for S7 connectionsPort for Read and WriteWhen using INAT S7-TCP/IP with standard connections, use the standard port 991.

� Confirm with „OK“. � The connection is parameterized in the OPC Server now.� Exit the OPC Server and start it again.� Process data can be accessed with the OPC Client now. Read chapter 3

for more details.

Chap

ter 2

: Con

fi gur

atio

n

2.3 Setting up a S5 connection

2.3.1 S5 connections: GeneralIf data shall not only be read from a S5 PLC with Siemens CP or with INAT S5-TCP/IP CP, but also be written to the S5 PLC, a write connection is required besides the read connection. With the INAT OPC Servers only ONE connection has to be set up. Via the port numbers or via the TSAPs the read connection and the write connection are defined.

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 CP: one read connection and one write connection). When communicating via TCP/IP, the port for read must be the same on both sides of the connection. The same ist with the port for write: it must be the same on both sides of the connection, too. When communicating via RFC1006 or via H1, the local TSAP on the local side and the remote TSAP on the remote side must be the same. The remote TSAP


on the local side and the local TSAP on the remote side must be the same. If there is a echolink used (S5 PLC is connected to the echolink), it is possible to read and write through one connection.

The connections must be parameterized on both sides of the connection (one connection for read and write in the OPC Server and one connection in the echolink). When communicating via TCP/IP, the port for read and write must be the same on both sides of the connection. 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.

Chap

ter 2

: Con

fi gur

atio

n

2.3.2 Speciel Settings for S5 Connections

Special Settings for S5 ConnectionsRead and Write through one ConnectionRead and Write through one connection is NOT POSSIBLE when using a Siemens CP or the INAT S5-TCP/IP. But it is possible when using INAT echolink.Unsolicited Data from PLCBesides cyclic polling (Fetch Active) and writing (Write Active) the Server supports unsolicited data from PLC as well. As for the read and write connection you have to choose a corresponding port number for this kind of connection. Note that the port numbers for read, write and event connections have to be different. Unsolicited Data from PLC is supported with Siemens CPs and with INAT S5 CPs as well. For the mode „Unsolicited Data from PLC“ the connection establishment active or passive can be chosen indepen-dent from the connection establishement of read and write connec-tions. Fetch on EventThe Fetch on Event protocol is activated via the read connection. Data from the PLC will no longer be polled cyclic, but transferred if a event occurs.Note: This option can only be used with the INAT S7-TCP/IP CP and S5-TCP/IP CP.


� Confirm your entries with „OK“. � The connection in the OPC Server is parameterized now.� Exit the OPC Server and start it again to activate the changes. � The corresponding connections of the read connection and of the Write

connection have to be parameterized on the other side (PLC side, S5 CP).

� See that the corresponding Ports / TSAPs are used.

2.3.3 Setting up connections on PLC side (S5 CP) To read data from the PLC, a Fetch Passive connection is parameterized on PLC side. To write data to the PLC, a Write Passive connection is parameterized on PLC side.

Examples S5 Connection

S5-TCP/IP OPC communication via TCP/IP with PLC Header

see chapter 2.2.3.1

Siemens CP OPC communication via TCP/IP with RFC1006 Header

see chapter 2.2.3.2

Siemens CP OPC communication via ISO (H1) see chapter 2.2.3.3

Chap

ter 2

: Con

fi gur

atio

n

2.3.3.1 OPC communication via TCP/IP with PLC Header: S5-TCP/IP� In the INAT parameterization software, select Connection > New. Select

the network and the type of protocol S5.

� Select the job type „Fetch Passive“ for the read connection. Confi rm with „OK“.

� The port number of the Fetch Passive connection in the S5 CP must be the same like the port for read in the OPC connection.


Settings in OPC Server

Settings in S5-TCP/IP

Chap

ter 2

: Con

fi gur

atio

n

� Along the lines of the Fetch passive connection, a Write passive connec-tion must be parameterized in the S5-TCP/IP.

� Select the job type „Write Passive“ for the write connection. Confi rm with

„OK“. � The port number of the Write Passive connection in the S5 CP must be

the same like the port for write in the OPC connection.


Settings in OPC Server

Settings in S5-TCP/IP

� The connections are parameterized now.

Chap

ter 2

: Con

fi gur

atio

n

2.3.3.2 OPC communication via TCP/IP with RFC1006 (Siemens CP)� In Step 5 parameterize a Fetch passive connection and a Receive pas-

sive connection.

Settings in Step 5

� Select „FETCH“ as job type and passive connection esta-blishment (P).

� Enter the local TSAP and the remote TSAP.� Be sure, that local TSAP and remote TSAP are the same

crosswise.Settings in OPC Server


The „local TSAP“ of the Fetch passive connection in the S5-CP (in this example fetch_s5) and the „TSAP for Read“ in the OPC connection must be the same. The „remote TSAP“ of the Fetch passive connection in the S5-CP (in this example tsappc01) and „Own TSAP“ in the OPC connection must be the same.

Chap

ter 2

: Con

fi gur

atio

n

� Along the lines of the Fetch passive connection, a Write passive connec-tion (Receive passive) must be parameterized in the S5-CP.

Settings in Step 5

� Select the job type „RECEIVE“ and passive connection establishment (P).




The „local TSAP“ of the Write / Receive passive connection in the S5-CP (in this example write_s5) and the „TSAP for Write“ in the OPC connection must be the same. The „remote TSAP“ of the Write / Receive passive connection in the S5-CP (in this example tsappc01) and „Own TSAP“ in the OPC connection must be the same.

Chap

ter 2

: Con

fi gur

atio

n

2.3.3.3 OPC communication via ISO (H1) (Siemens CP1430)� In Step 5 parameterize a Fetch passive connection and a Write / Receive

passive connection.

Einstellungen in Step 5

� Select the job type FETCH“ and passive connection esta-blishment (P).




The „local TSAP“ of the Fetch passive connection in the S5-CP (in this example FETCHXXX) and the „TSAP for Read“ in the OPC connection must be the same. The „remote TSAP“ of the Fetch passive connection in the S5-CP (in this example OPCSERVV) and „Own TSAP“ in the OPC connection must be the same.

Chap

ter 2

: Con

fi gur

atio

n

� Along the lines of the Fetch passive connection, a Write / Receive pas-sive connection must be parameterized in the S5-CP.

Settings in Step 5

� Select the job type „RECEIVE“ and passive connection establishment (P).




The „local TSAP“ of the Write passive connection in the S5-CP (in this example WRITEXXX) and the „TSAP for Read“ in the OPC connection must be the same. The „remote TSAP“ of the Write passive connection in the S5-CP (in this example OPCSERVV) and „Own TSAP“ in the OPC connection must be the same.

2.3.4 Programming handling blocksThe following handling blocks are used with the Fetch / Write communication: Synchron, Send-All, Receive-All. Be sure, that these blocks are programmed in your PLC program.

� Now you can access process data with your OPC client. Read chapter 3 for more details.

Chap

ter 2

: Con

fi gur

atio

n

2.4 Setting up a Modbus connection

2.4.1 Modbus connections: GeneralWhen communicating with a Modbus PLC, read and write jobs can be handled via one connection. The connection must only be parameterized on the OPC side. On PLC side, there are no more settings required.

Special Settings for Modbus connectionsWrite Single Coil (05), Write Single Register (06)If your Modbus device does not provide the Opcode „Write Multiple Coils (15)“, activate „Write Single Coil (05)“. If your Modbus device does not support the Opcode „Write Multiple Registers (16)“, activate „Write Single Register (06)“ Start Addres 0/1Address spaces of Modbus devices are 0-based or 1-based - depen-ding 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. Unit IDThe Unit ID is the slave address of the destination device.



Special Settings for Modbus connectionsPort for Read, Port for WriteThe port number is the channel number via which a connection is identified. For Modbus communication the port 502 is used as default. The port can be changed. Be sure to use the same port on both sides of the connection.

� Confirm with „OK“. The connection is parameterized in the OPC Server now.

� Exit the OPC Server and start it again. � On the PLC side, there are no more settings required. � Now you can access process data with your OPC client. Please refer to

chapter 3 for more details.

Chap

ter 2

: Con

fi gur

atio

n

2.5 Setting up a NetLink / IBHLink connection NetLink is an application protocol to read data from S7 PLCs / write data into S7 PLCs via a NetLink / IBHLink Adapter. Read and write jobs can be handled via one connection.

TCP/IP Parameters for NetLink connectionsRead and Write through one connectionThis is the default setting. There is only one port for read and write required. MPI Address PLCEnter the MPI Address of the S7 in the MPI subnet.Port for Read, Port for WriteThe port number is the channel number via which a connection is identified. The port number 1099 should not be changed. � Confirm with „OK“. The connection is parameterized in the OPC Server

now. � Exit the OPC Server and start it again. � On the PLC side, there are no more settings required. � In NetLink- / IBHLink adapter the IP address and the own MPI address

must be entered.


2.6 Setting up a Send / Receive connection With Send / Receive communication, data are transferred without application header i.e. raw data are transferred. The communication partner may be any station, that supports the Send / Receive Direct interface.

TCP/IP Parameters for Send / Receive connectionsWrite Access to PLC permittedWith „Write Access to PLC permitted“, data can be sent.Read and Write through one ConnectionSend / Receive is possible via one connection. Unsolicited Data from PLCWith „Unsolicited Data from PLC“, data can be received.No Header / PLC Header / RFC1006 HeaderDefine whether the PLC Header or the RFC1006 Header shall be used. Stations, that support only the „pure“ TCP/IP protocol should use „No Header“.


Chap

ter 2

: Con

fi gur

atio

n

TCP/IP Parameters for Send / Receive connectionsISO-on-TCP (RFC1006): Local TSAP, remote TSAPTSAP are required with H1 connections and with RFC1006 connec-tions. Local TSAPYour own TSAP (Transport Service Access Point) specifies the con-nection address in the system by which data is to be exchanged. Remote TSAPRemote TSAP for Read, Remote TSAP for Write and TSAP for Unso-licited specifies the connection address of the other system. Remote TSAP for Read, for Write and for Unsolicited should be addressed differently.

TSAPs are 2 bytes up to 16 bytes in length. Be sure to enter the TSAP (standard TSAPS) of S7 connections in the HEX field (see chapter 2.3). To be able to establish the connection, your Own TSAP must correspond to the TSAP of the other system.Port for Read, Port for Write, Port for UnsolicitedThe port number is a 16-bit address from 0 to 65535. It specifies the channel via which the applicable connection is to be established. You should use a port between 1024 and 65535. On both sides of the connection, the port number must be the same. Port for Read, Write and Unsolicited should be addressed differently. � Confirm with „OK“. � The connection is parameterized in the OPC Server now.� Exit the OPC Server and start it again.

NoteFor Send / Receive communication a special Item Syntax is used. Please refer to the Online help to learn more about that Syntax.


2.7 Setting up a PLC-5 connection Read and write jobs can be handled via one connection. If the standard port is used (2222), no parameterization is required on PLC side.

TCP/IP Parameters for PLC-5 connectionsRead and Write through one connectionThis is the default setting. There is only one port for read and write required. Port for Read and WriteThe port number is the channel number via which a connection is identified. For PLC-5 communication the port 2222 is used as default. The port can be changed. Be sure to use the same port on both sides of the connection. � Confirm with „OK“. The connection is parameterized in the OPC Server

now. � Exit the OPC Server and start it again. � On the PLC side, there are no more settings required.

NoteFor PLC-5 communication a special Item Syntax is used. Please refer to the Online help to learn more about that Syntax.

Chap

ter 2

: Con

fi gur

atio

n

2.8 Setting up a MELSEC-Q connection MELSEC-Q is an application protocol to read data from Mitsubishi Q-Series PLC / write data into Mitsubishi Q-Series PLC. Read and write jobs can be handled via one connection. The connection must be parameterized on both sides of the communication (one connection in the OPC Server and one con-nection in the MELSEC-Q).

TCP/IP Parameters for PLC-5 connectionsRead and Write through one connectionThis is the default setting. There is only one port for read and write required. Port for Read and WriteThe port number is the channel number via which a connection is identified. The port must be the same on both sides of the communi-cation.

� Confirm with „OK“. The connection is parameterized in the OPC Server now.

� Exit the OPC Server and start it again.

NoteFor MELSEC-Q communication a special Item Syntax is used. Please refer to the Online help to learn more about that Syntax.

C H A P T E R 3 :

C L I E N T S E T T I N G S

Chapter 3: Client Settings

3 CLIENT SETTINGS 3.1 OPC Test Client You have parameterized the connection in the OPC Server and (if required) in the PLC ==> you can access data with your OPC Client. A OPC Test Client is part of the scope of supply of the OPC package. This Test Client has been installed together with the Server. � Start the OPC Test Client with Start > Programs

� With Server > Connect you establish the connection between Client and

Server

� The OPC Server Prog ID of INAT Ethernet Servers is INAT TCPIPH1 OPC Server� Select Group > Add Group and enter a name for the new group

� Confi rm with „OK“.� Select Item > Add Item and enter Access Path and Item

Chap

ter 3

: Clie

nt S

ettin

gs

NoteAccess Path: enter the name you have parameterized as connection name in the OPC Server. Item: enter the Item for the required data.

� Confi rm with „OK“.� In the Client you can now see the required Item.

NotePlease refer to the Online Help for a detailed description of the Item Syntax.

Index

AAccess Path Defi nitions ...................... 14Allow Cyclic Poll ................................. 15

CClient Settings .................................... 49Confi guration ...................................... 13

General ........................................... 14Modbus connection ......................... 41NetLink / IBHLink connection ........... 43S7 connection ................................. 41Send / Receive connection ............. 44

Connection active / passive ................ 17Copyright .............................................. 2CP1430 ............................................... 37

EEthernet Address ................................ 19

FFetch on Event ................................... 27

HH1 Parameters ................................... 19Handling blocks .................................. 40

IIBHLink connection ............................. 43Installation ............................................ 5

of the H1 driver .................................. 8of the OPC Server ............................. 6

LLicencing .............................................. 9Local TSAP ......................................... 16

MMELSEC-Q connection ...................... 47Modbus connection ............................ 41MPI Address PLC ............................... 43

NNetLink / IBHLink connection . 43, 46, 47No Header .......................................... 17

OOPC Test Client .................................. 50

PPLC-5 connection ............................... 46PLC Header ........................................ 17Port ................................................ 18Port for Read ...................................... 18Port for Unsolicited ............................. 18Port for Write ...................................... 18

RRead/Write through one Connection .. 16RFC1006 ............................................ 17

SS5 connection ..................................... 25Server Type .......................................... 7Service ................................................. 8Standard TSAPs ................................. 23Step 5 ................................................ 33

I N D E X

Inde

x

TTCP/IP Parameters ............................ 17Test Client ........................................... 50TSAP ................................................ 16

Rules for S7 .................................... 23

UUnit ID ................................................ 41

WWrite Access to PLC Permitted .......... 15

W H I C H P R O T O C O L S A R E S U P P O R T E D ?

ServerProtokolle

TCPIPH1(100-3100-01)

TCPIP-S(100-3120-01)

TCPIP-I(100-3150-01)

Modbus(100-3140-01)

H1(100-3110-01)

TCPIP-M(100-3160-01)

TCP/IP � � � � � �RFC1006 � � � � � �PLC Header � � � � � �ISO (H1) � � � � � �S7 Protocol � � � � � �S5-AP � � � � � �Modbus on TCP � � � � � �MELSEC-Q � � � � � �PLC-5 � � � � � �Send/Receive � � � � � �NetLink � � � � � �

opc gs e - RESolu COMresolucom.com/Document/opc_gs_e_01UK.pdf · 1.1 Installation of the OPC Server...

Documents

Transcript of opc gs e - RESolu COMresolucom.com/Document/opc_gs_e_01UK.pdf · 1.1 Installation of the OPC Server...