OPC UA- Avoiding DCOM with Software Toolbox Products

1. OPC UA- Avoiding DCOM with Software Toolbox Products Presenters: Kevin Rutherford Senior Applications Engineer Renee Sikes Applications Engineer

2. OPC UA- Avoiding DCOM with Software Toolbox Products • Agenda – 1 Hour • An Introduction to OPC UA • Overview of Software Toolbox Products with UA • TOP Server • OmniServer • OPC DataLogger • SLIK-DA 5 • Live Demonstration • Summary • Discussion, Questions & Answers

3. 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

4. Value Point #1 – Common Interface Usage Data Access (DA) Batch Alarms & Events (A&E) OPCUnifiedArchitecture(UA) Commands Historical Data Access (HDA) XML Data Access (XMLDA) Security Data Exchange (DX)

5. Common Interfaces=Less Programming=More ProductsAn 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

6. Value Point #2 - Security Data Access (DA) Batch Alarms & Events (A&E) OPCUnifiedArchitecture(UA) Commands Historical Data Access (HDA) UA Server(s) XML Data Access (XMLDA) Security Data Exchange (DX) UA Client(s)

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

8. 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) Connect please… … check my trust list approved People

9. Value Point #3 DCOM Data Access (DA) Batch Alarms & Events (A&E) OPCUnifiedArchitecture(UA) Commands Historical Data Access (HDA) UA Server(s) XML Data Access (XMLDA) Security Data Exchange (DX) UA Client(s)

10. Value Point #4: Enterprise Data Communications Unified Architectureenables communicationsand data sharingenterprise-wide Enterprise Servers Workstations Mobile Controllers Embedded

11. What is a Profile? Why Profiles? 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

12. What is TOP Server?

13. TOP Server UA Client Driver And if you connect the OPC UA Client to a Remote TOP Server… You have a secure OPC UA Tunnel: • Connect any client application to the TOP Server UA Client driver locally • Easily access other driver data in the Remote TOP Server via the UA Server Interface with No DCOM!

14. What is OmniServer? • User-Configurable Data Acquisition Tool • OPC/DDE Server • OPC Server Interface • DDE Server Interface • FastDDE/SuiteLinkInterface • 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

15. Applications for OmniServer • Solves the problem of writing custom drivers for unique 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.

16. What is OPC Data Logger? • OPC Client Application that logs data to text files and a variety of ODBC databases, including SQL, MySQL, Access, Oracle • Allows logging based on exceptions, timers, or triggers • Allows formatting of data presentation • Easy configuration wizards let you start logging data quickly

17. 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 • 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

18. Software Toolbox Product Summary • TOP Server OPC Server • I/O application with pre-built device drivers • OmniServer OPC Server • I/O application for custom protocol development • OPC DataLogger • OPC client application for logging data to databases • SLIK-DA • ActiveX/.NET tool for developing a custom OPC server

19. Live Demonstration Now, let’s take a look at a live demonstration:

20. DCOM Summary • Use Software Toolbox OPC UA products to: • Avoid DCOM issues when making remote connections • Increase security of your data • Need to avoid DCOM issues, but only have DA products? • Contact us for other tunneling options

21. Contact Information & Other Learning Opportunities • Questions later? • Support@softwaretoolbox.com • +1 704 849 2773 • For More Information: • Visit our OPC UA portal: http://softwaretoolbox.com/OPCUA • TOP Server: http://toolboxopc.com • OmniServer: http://www.omnidssi.com/ • OPC Data Logger: http://opcdatalogger.com • SLIK-DA 5: http://nordyn.com • Other learning opportunities: • Visit http://softwaretoolbox.webex.com for a listing of other webinars.