- Количество слайдов: 21
Omni. Server V 2. 7 What’s New? Your Host Today: Win Worrall, Applications Engineer
Omni. Server V 2. 7 What’s New? Agenda – 1 Hour u u u A Brief Introduction of Omni. Server Overview of OPC UA Live Demonstration u u Omni. Server OPC UA Config OPC UA Client Configuration Summary Discussion, Questions & Answers
What is Omni. Server? u u User-Configurable Data Acquisition Tool OPC/DDE Server u u Hardware Interfaces u u OPC Server Interface DDE Server Interface Fast. DDE/Suite. Link Interface RS-232, RS-422, RS-485 Winsock (TCP/UDP/Telnet) LPT Communicate to almost any device, including custom designed devices u u Variable length, character delimited Protocols Known/Fixed Length protocols http: //www. softwaretoolbox. com/omniserver
Applications for Omni. Server u u 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 Omni. Server to interface computers with other computers or devices with other devices.
What is OPC UA? u u u Unified Architecture A collaborative working effort of the OPC Foundation and it’s members since 1994 Objective to create a standard that u u 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 u DA: u u u IOPCSync. IO: : Read IOPCAsync. IO 2: : Read IOPCAsync. IO 3: : Read IOPCItem. IO: : Read A&E: u u OPC Unified Architecture IOPCEvent. Server: : Get. Condition. State HDA: u u u IOPCHDA_Sync. Read: : Read. Raw IOPCHDA_Sync. Read: : Read. Processed IOPCHDA_Sync. Read: : Read. At. Time IOPCHDA_Sync. Read: : Read. Modified IOPCHDA_Sync. Read: : Read. Attribute IOPCHDA_Async. Read: : Read. Raw IOPCHDA_Async. Read: : Advise. Raw IOPCHDA_Async. Read: : Read. Processed IOPCHDA_Async. Read: : Advise. Processed IOPCHDA_Async. Read: : Read. At. Time IOPCHDA_Async. Read: : Read. Modified IOPCHDA_Async. Read: : Read. Attribute u u Read. History
Value Point #2 - Security UA Server(s) UA Client(s)
Security & Performance Thoughts u u u 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, Do. S etc. Value: 5
Security - Certificates u u 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 access Connect please… UA Product(s) … check my trust list People approved
Value Point #3 DCOM UA Server(s) UA Client(s)
Value Point #4: Enterprise Data Communications Enterprise Servers Workstations Mobile Controllers Embedded Unified Architecture enables communications and data sharing enterprise-wide
Terminology: UA “Tag” is now called a “Node” Nodes are “Tags on Steroids” u Variables: u u Methods: u u Something to Execute. Parameters supported! References: u u Known as “Attributes” in OPC Classic (Value, Quality, Timestamp etc. ) “Relationships” w/ other Nodes Events: u Notifications when “stuff” happens
Profiles What is a Profile? u An identifiable block of Why Profiles? u functionality that is supported: u Information Model, i. e. Type(s) of Data being moved u u functionality they support u Methods needed u Protocol & Security “Data Access” is an example of a Profile, as are all OPC Classic interfaces Servers can “reveal” which Clients can query a Server’s Profiles u UA Products can decide if the other has the capabilities desired
Summary – Nodes, Models, Profiles u u 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 u u u u u ABB Beckhoff Siemens Rockwell Yokogawa GE Iconics Kepware & their many OEMs Software Toolbox And more…
Summary – Why UA? u u u 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 u u u 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.
Omni. Server v 2. 7 Pricing u Purchasing New Licenses u u u Standard Omni. Server Edition - $650 Professional Edition with Wedges - $895 Omni. Wedge Keyboard Wedge Edition - $295 All new licenses come with a 30 day Support/Maintenance Agreement (SMA). 1 Year SMA - $200 Upgrading Existing Licenses u u Free Upgrades are provided for users on a SMA or who have purchased 30 days before release. v 2. 6 - $200 v 2. 5 - 50% of list price v 1. x or v 2. 0 - contact us
Contact Information & Other Learning Opportunities u Questions later? u Win Worrall u u u wworrall@softwaretoolbox. com 888 -665 -3678 x 1329 or 704 -849 -2773 x 1329 For More Information: u Visit our Omni. Server Product Page at http: //www. omnidssi. com/html/documents. html u Other learning opportunities: u Visit http: //softwaretoolbox. webex. com for a listing of other webinars.