OmniServer V2.7What’s New?

Your Host Today:

Win Worrall, Applications Engineer

OmniServer V2.7What’s New?

Agenda – 1 Hour A Brief Introduction of OmniServer Overview of OPC UA Live Demonstration

OmniServer OPC UA Config OPC UA Client Configuration

Summary Discussion, Questions & Answers

What is OmniServer?

http://www.softwaretoolbox.com/omniserver

User-Configurable Data Acquisition Tool

OPC/DDE Server OPC Server Interface DDE Server Interface FastDDE/SuiteLink Interface

Hardware Interfaces RS-232, RS-422, RS-485 Winsock (TCP/UDP/Telnet) LPT

Communicate to almost any device, including custom designed devices Variable length, character

delimited Protocols Known/Fixed Length

protocols

Applications for OmniServer

Solves the problem of writing custom drivers for unique devices.

Solves the problem of polling for multiple devices.

Is NOT a replacement for existing drivers. Use for devices that have no drivers.

Use OmniServer to interface computers with other computers or devices with other devices.

What is OPC UA?

Unified Architecture A collaborative working effort of the

OPC Foundation and it’s members since 1994

Objective to create a standard that Isn’t dependent on DCOM Can interoperate with non-Windows

platforms Is more secure than the original OPC Removes redundant code across

interfaces

Value Point #1 – Common Interface Usage

Common Interfaces=Less Programming=More Products

An example of how a “Read” is consolidated

OPC Classic DA:

IOPCSyncIO::Read IOPCAsyncIO::Read IOPCAsyncIO2::Read IOPCAsyncIO3::Read IOPCItemIO::Read

A&E: IOPCEventServer::GetConditionState

HDA: IOPCHDA_SyncRead::ReadRaw IOPCHDA_SyncRead::ReadProcessed IOPCHDA_SyncRead::ReadAtTime IOPCHDA_SyncRead::ReadModified IOPCHDA_SyncRead::ReadAttribute IOPCHDA_AsyncRead::ReadRaw IOPCHDA_AsyncRead::AdviseRaw IOPCHDA_AsyncRead::ReadProcessed IOPCHDA_AsyncRead::AdviseProcessed IOPCHDA_AsyncRead::ReadAtTime IOPCHDA_AsyncRead::ReadModified IOPCHDA_AsyncRead::ReadAttribute

OPC Unified Architecture

Read ReadHistory

Value Point #2 - Security

UA Server(s)UA Server(s)

UA Client(s)UA Client(s)

Security & Performance Thoughts

Data throughput must be significant Data is sensitive, no eavesdropping! Data received must match what was sent Work ONLY with those you trust! Withstand attacks: replay, alteration, spoofing,

DoS etc.

Value: 5

Security - Certificates

Digital Certificates are used for safe identification

A Certificate can represent a UA Server and UA Client

A Certificate can represent a Person (login)

Trust lists control accessUA Product(s)UA Product(s)

PeoplePeople

Connect please…Connect please…

approvedapproved

… check my trust list

… check my trust list

Value Point #3

UA Server(s)UA Server(s)

UA Client(s)UA Client(s)

DCOMDCOM

Unified Architectureenables communications

and data sharingenterprise-wide

Value Point #4: Enterprise Data Communications

EmbeddedEmbedded

ControllersControllers

MobileMobile

WorkstationsWorkstations

ServersServers

EnterpriseEnterprise

Terminology: UA “Tag” is now called a “Node”

Nodes are “Tags on Steroids”

Variables: Known as “Attributes” in OPC

Classic(Value, Quality, Timestamp etc.)

Methods: Something to Execute.

Parameters supported!

References: “Relationships” w/ other Nodes

Events: Notifications when “stuff”

happens

Profiles

What is a Profile? An identifiable block of

functionality that is

supported:

Methods needed

Information Model, i.e.

Type(s) of Data being

moved

Protocol & Security

“Data Access” is an

example of a Profile, as are

all OPC Classic interfaces

Why Profiles? Servers can “reveal” which

functionality they support

Clients can query a

Server’s Profiles

UA Products can decide if

the other has the

capabilities desired

Summary – Nodes, Models, Profiles

Nodes make up Information Models Profiles tell clients and servers what UA

services and information models are available.

Most UA developers are doing the DA profile for now in products on the street

Powerful capabilities of OPC UA bringing adoption from major vendors

Automation Vendor Adoption of OPC UA

ABB Beckhoff Siemens Rockwell Yokogawa GE Iconics Kepware & their many OEMs Software Toolbox And more…

Summary – Why UA?

No DCOM required ….No DCOM required Simple TCP/IP connection Firewall Friendly Platform Independent

Live Demonstration

Now, let’s take a look at a live demonstration:

OPC UA Summary

Client must know the Server’s Endpoint.

Clients and Servers have to share and Accept each other certificates.

If user authentication is used these have to match in the client and server.

No difference between Local and Remote Connections.

NO DCOM Required.

OmniServer v2.7 Pricing

Purchasing New Licenses Standard OmniServer Server Edition - $650 Professional Edition with Wedges - $895 OmniWedge Keyboard Wedge Edition - $295 All new licenses come with a 30 day

Support/Maintenance Agreement (SMA). 1 Year SMA - $200

Upgrading Existing Licenses Free Upgrades are provided for users on a

SMA or who have purchased 30 days before release.

v2.6 - $200 v2.5 - 50% of list price v1.x or v2.0 - contact us

Contact Information & Other Learning Opportunities

Questions later? Win Worrall

wworrall@softwaretoolbox.com 888-665-3678 x 1329 or 704-849-2773 x1329

For More Information: Visit our OmniServer Product Page at

http://www.omnidssi.com/html/documents.html

Other learning opportunities: Visit http://softwaretoolbox.webex.com for a

listing of other webinars.