OFS V3.3 – 2006/01/09)1

OPC Factory Server

Meeting Expert In Automation

Jerome Petit March 2006

OFS V3.3 – 2006/01/09)2

Summary

� OFS V3.3– Introduction

– New features

– Server Architecture– Application layers– Communication

– OPC DA Standard

– .NET Compatibility– OPC XML Standard

– Server adjustments

� Demo– OPC XML DA Client

OFS V3.3 – 2006/01/09)3

OFS Presentation(OPC Factory Server)

OFS V3.3 – 2006/01/09)4

OFS (OPC Factory Server)

� Schneider Electric OPC server for standard access to all Schneider Electric devices

� Provides interface between Schneider Electric devices and client applications (SCADA, HMI, IT, …)

� Multi devices– Quantum, Premium, Micro, Momentum, TSX Série 7, …

� Multipe communication protocols with PLCs– Modbus and Uni-TE V2.0 protocols

� Server access on LOCAL or REMOTE mode

� Multi clients connectivity

� Read / Write variables access by address or symbol– Variables send to the client only when they change state (notification)

– Synchronous or asynchronous communication

– Deadbanding for floating variables– Symbolic access to PLC variables via exported symbol files

OFS V3.3 – 2006/01/09)5

OFS V3.3 Parts numbers

� Offer has changed

– OFS Large : TLXCDLUOFS33– OPC server without limitation– OPC XML DA– Web Interface

– OFS Small : TLXCDSUOFS33– Server OFS with 1024 items MAX

– OFS Demo : Small package– Limited to 3 days of communication

OFS V3.3 – 2006/01/09)6

OFS V3 General description

� OFS V3 is fully compatible with – Unity PLCs– Premium PLCs– Quantum PLCs– S7 series 40 PLCs– April PLCs

� OFS V3 is fully compatible with all OPC clients DA 2.0a

� OFS V3 is fully compatible with previous versions of OFS

– OFS V3 is a superset of V2.55

� OFS V3 runs on the following OS : – Windows XP Professional– Windows 2003 server ( OFS V3.2 Only )

– Doesn’t mean terminal services - remote remains DCOM

OFS V3.3 – 2006/01/09)7

OFS V3.1 Enhancements

� Unity diagnostic buffer

– Available for Premium & Quantum diagnostic DFB

� Performance improvement

– Access to STU variables (Need Unity V2.0)

� Multi-clients architecture

– Synchronous call from one client doesn't lock others OPC Clients calls

� AppliStamp item for Unity PLCs

� Capability to get application checksum into a specific item

� String Items for legacy PLCs

– This bring capability to display a message using third part SCADA

OFS V3.3 – 2006/01/09)8

OFS V3.2 Enhancements

� Dynamic reload for .XVM after PLC download change.

– New data type for Unity exported file : .XVM

� Performances improvement

– Opening page using Unity XVM (Page opened with 300 items < 1 s)

– Notification : 1st value is read ASAP (No need to wait until the end of the notification period)

� Compatibility with Modbus TCP/IP gateways

– Share TCP Connection for Modbus devices

� Compatibility with third part devices (Modbus and Unitelway)

– at startup: device identification becomes optional

� Fast item validation

– Browse access with Vijeo : 5000 items in less than 1min

OFS V3.3 – 2006/01/09)9

OFS V3.3 versus OFS V3.2

OPC FactoryServerV3.2

�OFS

– OPC DA (COM / DCOM)

�OFS Web interface

�OFS Web Services

–OPC XML (W3C)–SOAP (W3C)–WSDL (W3C)

�OFS

– OPC DA (COM / DCOM)

OPC FactoryServerV3.3

OPC XML DA

OFS V3.3 – 2006/01/09)10

OFS V3.3 compatibility

� Compatibility with OPC DA (Data Access) standard version 1.0 and 2.0

– Local architecture based on Microsoft ® OLE / COM technology

– Remote architecture based on Microsoft ® OLE / DCOM technology

� Compatibility with .NET Microsoft ® environment– COM / DCOM technology

� Compatibility with OPC XML DA V1.01

� Web interface

OFS V3.3 – 2006/01/09)11

OFS Architectures(OPC Factory Server)

OFS V3.3 – 2006/01/09)12

Local access by COM

� Client application and OFS server are on the same PC

MODIC ON

Modbus networkX-Way network

OPC Factory ServerOPC Factory Server

SymbolsSymbolstablestables

LOCAL clientLOCAL clientApplicationsApplications

OFS V3.3 – 2006/01/09)13

Remote access by DCOM

� Client application and OFS server are on separate PCs connectedvia Microsoft ® TCP/IP network

MO D IC O N

Modbus network

Symbol DataSymbol Data(Concept, PL7, (Concept, PL7,

UnityUnity Pro)Pro)

Ethernet TCP/IP networkDCOMDCOM

X-Way network

Remote client Remote client applicationapplication

OFS serverOFS server

OFS V3.3 – 2006/01/09)14

OPC DA : access of a .NET client

� Compatibility with Microsoft ® .NET allows OPC .NET client applications to access OFS server via an Intranet in a .NET environment

Symbol DataSymbol Data(Concept, PL7, (Concept, PL7,

UnityUnity Pro)Pro)

Industrial network.NET client .NET client applicationapplication

OFS serverOFS server

Ethernet TCP/IP networkDCOM IntranetIntranet

WWindowsindows 2000 or XP2000 or XP.NET .NET FrameworkFrameworkOPC .NET APIOPC .NET API

� Note : communication between OPC .NET client and OFS server is realized via DCOM layer (or COM in local configuration). The protocol used is standard OPC DA protocol

OFS V3.3 – 2006/01/09)15

OPC XML : access of a SOAP XML client

� OPC XML client access data on OFS server via SOAP / XML protocol which respect OPC XML DA specification of OPC foundation

Symbol DataSymbol Data(Concept, PL7, (Concept, PL7,

UnityUnity Pro)Pro)

Industrial networkSOAP XML SOAP XML

clientclient

OFS serverOFS server

wwwwww

WWindowsindows 2000 or XP2000 or XP

Web clientWeb client

WWindowsindows 2000 or XP2000 or XP.NET .NET FrameworkFramework

SA .NET APISA .NET API

� Note : to access to Web client or SOAP client functions install Microsoft ® IIS component (Internet Information Services) on the OFS server station

OFS V3.3 – 2006/01/09)16

Installing OFS software

OFS V3.3 – 2006/01/09)17

OFS product

� OFS product contains 2 CD ROM – OFS CD ROM– Drivers

� OFS CD ROM includes :– OFS Server

– OFS Manager

– OFS Configuration Tool

– Documentation (English, French and German languages)– Sample symbol tables and sample applications

– 2 OPC test clients (Win 32 and .NET)

– Web client for accessing page view, data editor and server status

� Hardware and software configuration– Nominal : 850 MHz processor, 256 MB of RAM– Operating system : Windows XP & Windows 2000 professional

OFS V3.3 – 2006/01/09)18

Installation options

� Full station (client + server)– Configuration tool– OPC Factory server

– OFS manager tool

– OFS registration tool

– OPC Factory server simulator– OFS testing client (optional)

– OFS documentation (optional)

� Remote station– OFS remote server registration and OPC

proxy dlls

– OFS server test client

– OFS manager tool

– OPC automation interface 1.0 and 2.0

OFS V3.3 – 2006/01/09)19

Installation options (cont)

� .Net station– OPC .NET API – .NET sample client

– .NET framework (if not already installedon the machine )

� Web station (*)– IIS (if not already installed on the

machine )

– .NET framework (if not already installedon the machine )

– OFS Web site

� Web client station– JVM (if not already installed on the

machine )

– Internet explorer (if not already installedon the machine )

Note (*) : IIS must be installed before .NET framework

OFS V3.3 – 2006/01/09)20

IIS Installation

� From Control Panel1. Add Remove Programs

2. Add / Remove Windows components

3. Install Internet Information Services

OFS V3.3 – 2006/01/09)21

IIS Settings

� Run IIS Configuration– From administrative tool -> IIS– From Control Panel -> IIS

� Configure an Alias– Web site name is OFS

� Set FTP directory– From IIS FTP Server section– Create 2 virtual directory

– Name is ofs under wwwroot– Name is ftp under OFS dir

– Read & Write access must be enabled

� Set IIS Sercurity Policies– IIS user is IUSR_NameOfThePC– COM / DCOM Security must allow OFS use for this user

OFS V3.3 – 2006/01/09)22

OFS & Programming tools

OFS V3.3 – 2006/01/09)23

OFS and Exported Symbols Files

Project-

Database

Concept

ExportENABELED

Unity Pro

XL

CC2CAT OFS

Concept

Export-Files

PL7 Exported files

.SCY or .FEF

Project-

Database

CSV Files

For

legacy PLCs& third party devices Static symbol list

Dynamic exchanges

P Server

P UNIT Simulator

Legacy Quantum &Momentum

Legacy Premium

Micro

Serie 7Serie 1000

Unity DevicesConcept Simulator

Serie 7Serie 1000

P UNIT

Export File

.XVM

UNITY P-server requires :� 20 Mb of overhead � STU size ( 80Mb typical)

per opened project

Typically 100 Mb of RAM per opened project

OFS V3.3 – 2006/01/09)24

Variables

� Unity Pro available variables using .STU

– Elementary data type (EDT),

– Table, structure,

– Derived data type (DDT),

– Elementary function block (EFB),

– Derived function block (DFB).

– I/O derived data type (IODDT),

� Unity Pro available variables using .XVM

– Elementary data type (EDT),

– Table, Structure

– Derived data type (DDT).

– Derived function block (DFB). Public variables

– Elementary function block (EFB),

OFS V3.3 – 2006/01/09)25

Dynamic reload mechanism

OFS V3.2

Unity PRO.STU.XVM

COM/DCOM

Database symbols

Consistency check

OFS

Unity Client PServerCOM/DCOM

SCADA Programming PC

xxx.stu

XVM file

OFS V3.3 – 2006/01/09)26

Reload database mechanisms

� Start up time

� Runtime mode (Reload)

SCADA Unity ProXL

OFS123

4 50

1 PLC data information ( addresses, comments, …) import mechanism

2 OPC browse 3 OPC AddItem4 PLC read5 PLC write

0 Periodic consistency checkInconsistency is detected on the PLC

1 Reload Unity symbolsBuild (new) requests with new addresses

4 PLC read5 PLC write

OFS V3.3 – 2006/01/09)27

Performances

� PC : PIV 1.7 GHz - 512 Mo RAM - no other running application– Preload symbol enabled

� Browse Items

� AddItem

Browse STU XVM PL7 Concept (PRJ)10 000 items within the project(5000 loc + 5000 unlocated)when possible

18 s 6 s 6 s 6 s

AddItems STU XVM PL7 Concept (PRJ)Elementary variables : 1000 items 11s 2 s 2 s 3sElementary variables : 2000 items 22s 4s 4 s 7sElementary variables : 3000 items 34s 6s 8s 10sElementary variables : 5000 items 70s 17s 20s 23sStructured variables : 1000 items 11s 2 s 2 sStructured variables : 2000 items 22s 4s 5 sStructured variables : 3000 items 34s 7 s 8 sStructured variables : 5000 items 70s 18 s 21 s

OFS V3.3 – 2006/01/09)28

OPC DA V2.0 Standard(OLE for Process Control Data Access)

OFS V3.3 – 2006/01/09)29

OPC Standard and Foundation

� Industry’s requirements– Provide business applications with easy and common ACCESS to

industrial plant floor DATA

– INTEROPABILITY between automation / control, field devices andbusiness and office applications

� The answer : OPC (OLE for Process Control)– Standard INTERFACE which enables communication of

interoperable servers and clients applications

– Manages REAL TIME information

� OPC Foundation Charter– To develop an open and interoperable interface STANDARD– Based on Microsoft ® OLE technology (Object Linking and

Embedding)

– Schneider Electric is member of OPC Foundation

OFS V3.3 – 2006/01/09)30

COM

DCOM

OFS Application layer

C++ Application

SCADAs

OPC Server Object

OPC Group Object

OPC ItemObject

DEVICES

VB & VBaApplicatons

CustomInterface

(Standardon allOPC servers

Automation Interface Handler

Client Server

.NETProxy

OPC ItemObject

OPC ItemObject

OPC ItemObject

OPC ItemObject

.NETApplication

VB#C#

C++ Managed

.NET Framework

V1.1

Windows OS

OFS V3.3 – 2006/01/09)31

OPC: objects hierarchy

OPC Items

OPC group

OPC Server

OPC Items

OPC group

OPC Items

OPC group

� The OPC architecture is based on 3 nested

objects:

– The SERVER is a collection of OPC groups.

– The GROUP is a collection of OPC items.

– The ITEM is the association of a PLC variable through a

PLC communication network

– Each item has a value, a quality and a timestamp.

� Each OPC Object has different INTERFACES:

– Each interface is a set of methods handling a particular

aspect of the object (ex: add, read, write, remove,…).

OFS V3.3 – 2006/01/09)32

OPC Server – Objects & Interfaces

Status

+ AddGroup()+ GetErrorString()+ GetGroupByName()+ GetStatus()+ RemoveGroup()+ CreateGroupEnumerator()+ QueryOrganization();+ ChangeBrowsePosition();+ BrowseOPCItemIDs();+ GetItemID( );+ BrowseAccessPaths( );

IOPCServer

Update rateSync/AsyncActive/Inactive

+ GetState()+ SetState()+ SetName();+ CloneGroup();+ AddItems()+ ValidateItems()+ RemoveItems()+ SetActiveState()+ SetClientHandles()+ SetDatatypes

IOPCGroup

TimeStampQualityCanonical DataTypeValueActive/Inactive

+ QueryAvailableProperties()+ GetItemProperties ()+ LookupItemIDs()

IOPCItem

OPC Server Object OPC Group Object

OPC Item Object

OFS V3.3 – 2006/01/09)33

Notification (Asynchronous)

� For Notification mechanism.

� The client must subscribe to this mechanism

� Give the rate that he wants to be updated� The Notification is sent if :

– The group is Active– The Items are actives

Back to Application Code

Update changed Data

Back to Application Code

DEVICES

Active Groups & Items

R/W requests

Application Code

Event Data Change

Enable Subscription

Data

OPC ServerOPC Client

Data available

Callback procCache

Interfaces

OFS.EXE

OFS V3.3 – 2006/01/09)34

Synchronous Read/Write services

� Client Application is blocked during the time the server gets data

Back to Application Code

OPC ServerInterfaces

DEVICES

OPC read/write Sync

R/W request

Application code

Waiting data

Update Data

Synchronous READ/WRITE

Data

OPC Client

OPC Group

OPC Item

OPC Item

OPC Item

OFS.EXE

OFS V3.3 – 2006/01/09)35

Asynchronous Read/Write Services

� Asynchronous service call returns response immediately .The client is not blocked.

� The result is given later using the Notification mechanism.

� The client must subscribe to this mechanism

Back to Application Code

Update Data

Back to Application Code

DEVICES

OPC read/write Async

R/W requests

Application Code

Event Data Ready

Asynchronous READ/WRITE

Data

OPC ServerOPC Client

Data available

Callback procWait Data

Interfaces

OFS.EXE

OFS V3.3 – 2006/01/09)36

Push Data

� Notification mechanism enabled� The Device update data into the

server cache memory� Update rate for the group is

asynchronous with device update rate

Back to Application Code

Update changed Data

Back to Application Code

DEVICES

Active Groups & Items

Server Acknowledgement

Application Code

Event Data Change

Enable Subscription

Data from device

OPC ServerOPC Client

Data available

Callback procCache

Interfaces

OFS.EXE

OFS V3.3 – 2006/01/09)37

OFS Communication(OPC Factory Server)

OFS V3.3 – 2006/01/09)38

Internal Server behaviours

� Internal Architecture

� Communication management– Asynchronous

– Synchronous

� Requests Optimisation rules

OFS V3.3 – 2006/01/09)39

GlobalData Cache

Net-ManagerXway

Net-ManagerModbus

Var-Manager

Group 1

Group 2

Group n

Group-ManagerClient x

….

OFS : Data Architecture

�OFS precision is based on parameter : Group Min update rate

�Notified GROUPS have their own updates rates.

�Net Manager have updates rates depending frequencies of groups2 Groups with the same update rate are seen as 1 for Net Manager / Optimization

OFS V3.3 – 2006/01/09)40

Sending RequestsXway

Thread

Receiving Answers

Xway Thread

Global DataCache

PeriodicRequests to update data cache

Requestswaitinganswer

ToNetwork

Answersfrom Network

XWAY Asynchronous requests

OFS V2.55 : All request are sent at the beginning of the update period

OFS V3.0 : Requests are sent until #NbrMaxRequestnumber is reached.

1

23

4

5

6

OFS V3.3 – 2006/01/09)41

Direct addressing TCP/IP

Sending RequestsModbus+

Thread

Receiving Answers

Modbus+ Thread

Globa DataCache

PeriodicRequests to update data cache

Requestswaitinganswer

Answersfrom Network

To

network

Sent on all configured / available channels (Alias : Max channels settings) Synchronous on a connection

1

2 3

4

5

6

Request that are alreadyin the queue are not

added a second times

OFS V3.3 – 2006/01/09)42

Gateway Compatibility

� 1 TCP/IP connection needed per device behind a gateway– Most low cost devices allowed up to 8 connections

– Performances problem was reported

� OFS V3.2 allow TCP/IP connection sharing for a gateway– Each device must be defined as Modbus Gateway Device– TCP/IP connection will be limited to configured number

OFS V3.3 – 2006/01/09)43

Third part devices compatibility

� Provides standard protocol without caring the target– Alias can be defined as a basic device

– No identification sent to the device– Protocol doesn’t bring extra request– OFS behave as a third part OPC Server

OFS V3.3 – 2006/01/09)44

OFS : network request generation

� Read Request generator:

– Called for each sync/async read request

– Called each time something is activated / deactivated– Called if group update rate are modified

– Maximum Optimization is done

– Debug Interface to see what is generated

� Write Request generator :

– Called for each sync/Async write request– Optimization is done for register 0x,4x,%M,%MW

– Optimization is done for consecutive registers only

– No Debug Interface to see what is generated

OFS V3.3 – 2006/01/09)45

OFS : Modbus Read Request generator

� Located Variables : Merging technique

– Modbus read request : – 125 registers (same range) per request Max

– 2000 coils (same range) per request Max

– limitation is given by the answer and not by the request

– Ex 1 : Coils 0x10 and 0x25 : 1 request 10..25

– Ex 2 : Coils 0x 20 and 1x30 : 2 requests

– Ex 3 : Registers 4x10 and 4x 50 : 1 request 10..50

– Ex 4 : Registers 4x10 and 4x200 : 2 requests

– Ex 5 : Registers 3x100 and 4x110 : 2 requests

OFS V3.3 – 2006/01/09)46

OFS : Modbus Read Request generator

� Unallocated variables : Mixing technique

– One variable = one identifier (4 bytes) for Concept 2.6

– Read possible only if direct link with Concept is used

– Read request = one or more identifier (up to 66 per request)

– Limitation is given by the request and usually not by the answer

– Can mix any type in the same request

– Ex : One Bool , 2 Float and a Struct of 5 integer : One request

– New technique for V2 : Merging elements of the same structure because the

problem is the size of the request and not the answer

– With NOE only 1 request per PLC scan for unlocated variables and 4 for

registers.

OFS V3.3 – 2006/01/09)47

OFS : XWAY Read Request generator

� Located variables (No unallocated with PL7 language)

– Merging technique (Write Access)

– Mixing technique using UNITEV2 features (Read Object List)

– Limitation is given usually by the answer and not by the request

– Ex : %MW2 ,%MW3, %MW40, %MX5 , %MX8 => one request with 3 elements (MW2..3, MW40, MX5..8)

– Input/Output available for Digital and Analogue (no optimization)

OFS V3.3 – 2006/01/09)48

Request Optimization rule

� Available variables– Located variables – Unlocated / Structured variables

� Mixing technique (Read Block Offset Length)– Ex : %MW2 ,%MW3, %MW40, %MX5 , %MX8

=> one request with 3 elements (MW2..3, MW40, MX5..8)

� Mixing technique is available for Read and Write access

� HE CPU – Embedded port manage 1 Kb requests– Quantum : 16 requests per scan regardless data type– Premium : 20 requests per PLC scan time

� Quantum NOE– 12 requests per PLC scan time

– 8 for located – 4 for unlocated

OFS V3.3 – 2006/01/09)49

Troubleshooting(OPC Factory Server)

OFS V3.3 – 2006/01/09)50

OPC Server Adjustment

� Optimizing server for communication

� Diagnostic– Server Status– Communication status

OFS V3.3 – 2006/01/09)51

OPC Server Adjustments

� Communication adjustment, improving network performances

Define polling rate on the drivers by reducing the time you get answer faster from the driver

Time out Frame and device

Eliminate furtive bad quality

*****to be modified *****On UNITE V2, release TID time. useful when you get “No more TID” in the debug trace

Increase number of logical channels with the device (Modbus only)

OFS V3.3 – 2006/01/09)52

Performances in point to point link

� Reading several data into a same PLC can saturate P LC communication resources

– For Modbus the message is � error request to old (efef625a),

– For UNITE the message is � Xway driver Answer : 15hSpread out update rate from groups between each other (V2.55).

Decrease value of item #MaxPendingRequests

OFS V3.3 – 2006/01/09)53

The OFS Diagnostic Interface

� Should be enabled through the Configuration Tool BEFORE starting the Server

� Can be used only if the interactive user is the running user

� Error message can always be saved in a file (logging feature , can be enabled on the fly)

� Remote diagnostic can be done in a similar way through OFS Manager

OFS V3.3 – 2006/01/09)54

�5 different windows can be opened :

• Diagnostic window

• Status window

• Client window

• Variable manager window

• Network manager Network

The OFS Diagnostic Interface

OFS V3.3 – 2006/01/09)55

• Start-up messages

• Verbose mode option to get more messages or more details

• Symbol table verbose mode option

• Performance Info Mode

• Runtime messages (both error and informational)

Diagnostic window

OFS V3.3 – 2006/01/09)56

•General statistics about :

• Clients

• Groups (created, active)

• Items ( created, active)

• Read / write calls

• Notifications sent

Status window

OFS V3.3 – 2006/01/09)57

� For developers : A way to know exactlyitems & clients activity :

• Calls

• Creation of Groups and Items

• Active status of Groups and Items• (Server handles)

Client window

OFS V3.3 – 2006/01/09)58

2 kinds of information

Current Device configuration (read from the registry and may have been modified by OFS Manager)

List of all items currently known (from all groups, all clients, all devices)

Var manager window

OFS V3.3 – 2006/01/09)59

Communication statistic

Request sent on the network

Request queued

Setting from Configuration tool

Request access time

Request generated per groups

OFS V3.3 – 2006/01/09)60

OFS XML DA 1.0 Presentation(OPC Factory Server)

OFS V3.3 – 2006/01/09)61

OFS V3.3 : from OPC DA to OPC XML DA

OFS Server(Web server)

XML

Web Browsers

OPC XML

Web

Services

WSDL

OPC DA Client

MicrosoftApplications .NET

COM / DCOM

OPC XML Client

Applications :

Microsoft, IBM, SAP,...

SOAP

SOAP

COM / DCOM

OFS V3.3 – 2006/01/09)62

SOAP/XML Web services Use of unifying technology and standards

� FactoryCast Web services are based on the followingW3C standards :

– WSDL (Web Services Description Language)– the standard Web Services description language, in XML format.

– a standardized and self-documented library of data access functions

– SOAP (Single Object Access Protocol),– the standard exchange protocol c

– arried out via the HTTP channel (HyperText Transfer Protocol), crossing firewalls

– compatible with Internet use

– XML (eXtensible Markup Language):– the universal standard for data exchange

OFS V3.3 – 2006/01/09)63

SOAP/XML Web services“Server interface”

BuildBuild timetime

RunRun timetime

1 1 WhichWhich Web services do Web services do youyou publishpublish ??

2 2 HereHere are the Web services are the Web services availableavailable (WSDL interface)(WSDL interface)Modbus XML Data Access, Modbus XML Data Access, SymbolicSymbolic XML Data AccessXML Data Access

3 3 SOAP SOAP requestrequest : I : I needneed the the followingfollowing Data:Data:Qty_Prod_Line1, Stop_Time_Line1Qty_Prod_Line1, Stop_Time_Line1

4 4 SOAP SOAP answeranswer : OK, I have : OK, I have exexéécutedcuted youryour requestrequestandand I return the Data values I return the Data values ‘‘ 10, 10:39PM10, 10:39PM ’’

SOAP

SOAP

WSDL

OFS V3.3 – 2006/01/09)64

PLCPLCModbusXMLDAModbusXMLDA

SymbolicXMLDASymbolicXMLDA

Schneider Web services

HMIHMIIntranet / Internet

OFS V3.3OPC XML DA V1.01

ApplicationApplication

EthernetEthernet

HTTPHTTP(S)(S)ApplicationApplication

HTTPHTTP

RTOSRTOS

VxWorksVxWorksEthernetEthernet

TCP/IP

EthernetEthernet

TCP/IP

Windows 2000 / XPWindows 2000 / XP

HTTPHTTP(S)(S).NET OPC API.NET OPC API

.NET .NET FrameworkFramework

IIS 5.0

EthernetEthernet

OSOS

Windows, LinuxWindows, Linux ……

OFSOFS COM

.NET

OPC XML

OFS V3.3 – 2006/01/09)65

OPC XML V1.01 Overview

Ethernet TCP IP - HTTP (80)

IIS

.NET

OFS V3.3Large

PLC’s Protocol

OPC XML DA Methods

� GetStatus � Read � GetProperties� Write � SubscriptionPolledRefresh� Subscribe � Browse � SubscriptionCancel

Network

XML Client

Application

State less protocol

OFS V3.3 – 2006/01/09)66

OPC XML V1.01, One shot scenario

Network

Ethernet TCP IP - HTTP (80)

IIS

.NET

OFS V3.3Large

PLC’s Protocol

Browse1

Read2

Create group3

Get Values5

Read Values4

Clear group6

1’ & 2’ SOAP Request

1’, 2’ & 5’ SOAP Answer

XML Client

Application

OFS V3.3 – 2006/01/09)67

OPC XML V1.01, Optimized or Established scenario

Network

Ethernet TCP IP - HTTP (80)

IIS

.NET

OFS V3.3Large

PLC’s Protocol

Browse1

Subscribe2

Create group3

Subscriptionpolled Refresh

5

Read Values4

Clear group71’ & 2’ SOAP Request5’ -> Just subscribed handle is transferred

1’, 2’ & 5’ SOAP Answer

CancelSubscription

6XML Client

Application

OFS V3.3 – 2006/01/09)68

The End

Thanks for your attention