Introducing SLIK-DA 5 w/UAAdding UA to an Existing SLIK-DA 4 server
Presenters: Win Worrall Senior Applications /Development Engineer
Renee Sikes Applications Engineer
Introducing SLIK-DA 5 w/ UA
• Agenda – 1 Hour• An Introduction to OPC UA• Overview of SLIK-DA 5 w/ UA• Live Demonstration• Summary• Discussion, Questions & Answers
What is OPC UA?
• Unified Architecture• A collaborative working effort of the OPC
Foundation and its 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
OPCUnified
Architecture(UA)
Alarms & Events (A&E)
Historical Data Access
(HDA)
SecurityData
Exchange (DX)
XML Data Access
(XMLDA)
Commands
Batch
Data Access (DA)
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
OPCUnified
Architecture(UA)
Alarms & Events (A&E)
Historical Data Access
(HDA)
SecurityData
Exchange (DX)
XML Data Access
(XMLDA)
Commands
Batch
Data Access (DA)
UA Server(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 access
UA Product(s)
People
Connect please…Connect please…
approved
… check my trust list
Value Point #3
OPCUnified
Architecture(UA)
Alarms & Events (A&E)
Historical Data Access
(HDA)
SecurityData
Exchange (DX)
XML Data Access
(XMLDA)
Commands
Batch
Data Access (DA)
UA Server(s)
UA Client(s)
DCOM
Unified Architectureenables communications
and data sharingenterprise-wide
Value Point #4: Enterprise Data Communications
Embedded
Controllers
Mobile
Workstations
Servers
Enterprise
Profiles
• 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
• 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
What is a Profile? Why Profiles?
What is SLIK-DA 5 w/ UA?
• ActiveX and .NET toolkit for creating a custom OPC DA or OPC UA server in a variety of environments and languages– Now supporting Windows 7, Server 2008
(Standard and R2), x64 machines, and VS2010• Rapid development of a custom server
through simple properties, methods, and events– Hides OPC details and COM details from user– Allows static or dynamic tag creation
Adding OPC UA to your server
• SLIK-DA users can add OPC UA with absolutely no code changes– Some new, optional methods have been added
• API remains the same• Utility application for UA interface configuration • OPC UA & DA can run at the same time• This is not a wrapper – OPC UA calls have same
direct access to your data and application as OPC DA calls
Managing Security
• Two ways to manage security certificates– OpenSSL– Windows Certificate Store
• Location of stores can be changes in the UA configuration
• By default, SLIK-DA is set to use OpenSSL
New UA Methods in SLIK-DA 5
• SetOpcUAConfigFile()- set the path where the .xml config file is stored
• ReadOpcUAConfigFile()- reads in a .xml UA config file• SetOpcUAApplicationDirectory()- changes any references to
[ApplicatonPath] on the .xml file• GetOpcUAApplicationDirectory()- Returns the current
applicaton directory set in the config file• RestartOpcUAServer()- restarts the UA interface• SetOpcUAEnable()- disables or enables the UA interface• CreateOpcUACertificate()- accepts parameters to create the
certificate
Live Demonstration
Now, let’s take a look at a live demonstration:
Summary
• Add OPC UA in minutes• Avoid DCOM issues• Increase security of your data• Save time and money by
reducing engineering/development costs to implement UA and man hours spent on troubleshooting DCOM issues.
DCOM
Licenses and Ordering
• 2 Licenses– PN 41262150- SLIK DA 5 (for DA only)
• $795 for new license• Free upgrade if your V4 license is on current support contract
– PN 41262160- SLIK DA 5 w/ UA• $4495 for new license• $3695 for upgrade if your V4 license is on current support
contract
• Support Contracts– 20 % of list price
• $159 for SLIK DA 5• $899 for SLIK DA 5 w/ UA
Contact Information & Other Learning Opportunities
• Questions later?– Contact Renee
• Email: [email protected]
– Contact Win• Email: [email protected]
– Tech Support • Email: [email protected]• Phone: +1 704 849 2773
• For More Information:– SLIK-DA 5: http://nordyn.com– OPC UA Portal: http://softwaretoolbox.com/OPCUA
• Other learning opportunities:– Visit http://softwaretoolbox.webex.com for a listing of other
webinars.