OPC Data Logger New Release How to Avoid DCOM Using OPC UA Hello everyone, thank you for joining us on this webinar. My name is slim-shady and I am excited to show you how you can quickly, easily and reliably log your OPC data to a variety of destinations using the highly affordable, yet very powerful OPC DataLogger. Win Worrall Applications Engineer Email: wworrall@softwaretoolbox.com Direct Line: +1 (704) 708-6491

Agenda Introduction to the OPC Data Logger What are Write Backs Introduction to OPC Unified Architecture (UA) Live Demo Summary Questions & Answers Here is the agenda of todays webinar. I want to move through these slides quickly so that we can get to the live demonstrations as quickly as possible. So we’ll begin by introducing the OPC DataLogger, what it is, what it is not, and why it exists in the first place. Then we’ll move onto a live demo. We’ll then discuss some of the troubleshooting tools that exist within the product. Then we’ll wrap-up with a summary of what we’ve seen and then open-up the phones for some Q&A.

OPC Data Logger Features Wizard based configuration Multi-threaded Double-buffered for Reliability Multiple ways of collecting data Multiple ways of presenting data Multiple ways of storing data Supports Windows 2000, XP, Vista, 7, 2008 (x86 and x64) Runs as a Service OPC Self-Certified OPC LAB TESTED! TOPServer – Software Toolbox OMNIServer – Software Toolbox KEPServerEX – Kepware FactoryTalk Gateway – Rockwell Automation RSLinx - Rockwell Automation DASSIDirect 1.5 – Wonderware DASABCIP 3.5 – Wonderware DASGESRTP 1.5 – Wonderware FSGateway 1.5 – Wonderware DASABTCP 1.5 – Wonderware DASMBTCP 1.5 – Wonderware DASMBSerial 2.5 – Wonderware Simatic WinCC – Siemens Simatic WinCC Connectivity Station – Siemens Simatic NET OPC Servers – Siemens Simatic WinCC flexible 2007 – Siemens Simatic OPC XML Wrapper – Siemens IntelliMax – SENSYS Inc OPC DataHub – Cogent Real-Time Systems MatrikonOPC Universal Server – Matrikon MatrikonOPC Desktop Historian – Matrikon DHX OPC Server Suite – Cyberlogic MBX OPC Server Suite – Cyberlogic PI DA Server – OSISoft Inc InGear AB OPC Server – CimQuest InGear GE OPC Server – CimQuest InGear Modbus OPC Server - CimQuest Exaopc OPC Package – Yokogawa DeviceXPlorer – Takebishi DeviceXPlorer Melsec – Takebishi Validator – Cyberlogic Proficy HMI/SCADA Cimplicity 7.0 – GE AlarmWorx32 OPC A&E – Iconics ExperTune Plant – TriageExperTune Inc ChemCAD – Chemstations Inc OPC Analyzer – OPC Foundation

Flexibility Log data from 1..n OPC Servers (DA and/or UA) OPC Server A OPC Server B Flexibility – what does it mean? Well, it actually means YOU get a lot of freedom to define your logging needs. For example, you can log data from one OPC Server, or from multiple OPC Servers. The data could be logged to a common destination such as a Text File. Remember, the OPC Server in this case could be: An OPC Server feeding your HMI Your HMI itself, as many HMI’s are also OPC Servers. A custom application you’ve built that exposes an OPC Server interface. Database ‘A’ Database ‘A’

No limits to the # of database destinations Flexibility Log data from 1..n OPC Servers (DA and/or UA) Log data to 1..n Destinations (text files, databases etc) OPC Server A OPC Server A Likewise, you might have a single OPC Server that logs data to MULTIPLE destinations, like a couple of text files as well as a couple of databases! And it is here where the DOUBLE BUFFERING concepts comes into play… As a data logger, there are two performance indicators you need to be aware and prepared for: How fast can you consume the data from the OPC Server? How fast can you log the data? If you look at the example here with the multiple destinations, a text file is going to log data much faster than any database server can handle, yet the OPC DataLogger will not let the performance the textfile degrade because the database engines couldn’t keep-up for example. This is why you want double-buffering in your data logger! Database ‘A’ MySQL ORACLE SQLServer No limits to the # of database destinations

Flexibility Log data from 1..n OPC Servers (DA and/or UA) Log data to 1..n Destinations (text files, databases etc) Log & format the data in Detail or Table mode How the data is logged is up to you. We currently have 2 types, Detail and Table mode. Table mode is the top picture that shows a single row containing the values of all of your Tags. Whereas the Detail mode shows the complete details of a single Tag on each row. I’m personally a fan of the Detail mode as the information is much more useful for generating more meaningful reports with. We say LOG AND FORMAT the data because you might want to change the way your numbers or dates are formatted… for example, do you want your numbers to have thousand-separators, leading zeros’, a currency symbol, or do you want day/month/year or month/day/year etc.

You can even combine multiple read methods! Flexibility Log data from 1..n OPC Servers (DA and/or UA) Log data to 1..n Destinations (text files, databases etc) Log & format the data in Detail or Table mode Collect data by Subscription, Timer or Trigger The flexibility allows you to specify HOW and WHEN to actually get your data. You can subscribe to tags and simply log their values when their values change. This is usually the best way to go since you do not need to actively poll and log every reading of a tag when its value might not have even changed in ages. Sometimes you do need to collect values as specific time intervals and log them, perhaps due to regulatory requirements etc. This is what the Timer method can do for you. Lastly, one of the most powerful features of the OPC DataLogger is the ability to read the values based on when a Trigger says to do so. So let’s look at these triggers… Tags are constantly polled, but logged only when values change! At pre-determined intervals the data is requested and logged. The data is requested and logged only when a trigger is raised. You can even combine multiple read methods!

Monitored Item Trigger Flexibility Log data from 1..n OPC Servers (DA and/or UA) Log data to 1..n Destinations (text files, databases etc) Log & format the data in Detail or Table mode Collect data by Subscription, Timer or Trigger We have a Scheduled Trigger, which allows you to set a specific date and time. This is useful if you want do to short-term logging, like from this date to that date. In other words, you are not going to be continuously logging data. We have a Recurring Trigger, which is useful for those of you that have to log data at specific time intervals due to regulatory commitments etc. For example. Fire the trigger every 5 seconds or every 24 hours etc. Lastly, the Monitored Item trigger is useful if you want the trigger to execute when a Tag’s value changes, or when it changes to a specific value, or its value is within a specific range etc. We will see some of these in action during our live demo! This can be useful if you need to log only when a process values goes out of range; or only for a particular batch; or only when the process hits a particular temperature etc. The possibilities are as varied as your imagination. Scheduled Trigger Executes at a specified date & time Recurring Trigger Executes at specific time intervals Monitored Item Trigger Executes based on the condition of a Tag’s value

Flexibility Log data from 1..n OPC Servers (DA and/or UA) Log data to 1..n Destinations (text files, databases etc) Log & format the data in Detail or Table mode Collect data by Subscription, Timer or Trigger Mix-n-match ALL of the above scenarios Flexibility – we said we were flexible and we meant it --- so you can mix-n-match all of those examples that I just showed you!

What is a Writeback? Write to the OPC Server when an Event or Trigger in the OPC Data Logger occurs These Events include Database Connection going Offline Database Connection coming Online After every log to the Database Similar Events for Text/CSV Files Opened, Closed and after every log Trigger Types Scheduled, Recurring, Monitored Item

New Features in v 3.5.0.34 Support for OPC Unified Architecture (UA) standard Connect to an OPC UA server Support for security certificates

What is 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 OPC Unified Architecture (UA) Alarms & Events (A&E) Historical Data Access (HDA) Security Data Exchange (DX) XML Data Access (XMLDA) Commands Batch Data Access (DA) PULL FROM OPC FOUNDATION SLIDES

Common Interfaces= Less Programming=More Products An example of how a “Read” is consolidated OPC Classic OPC Unified Architecture 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 Read ReadHistory

Value Point #2 - Security OPC Unified Architecture (UA) Value Point #2 - Security Alarms & Events (A&E) Historical Data Access (HDA) Security Data Exchange (DX) XML Data Access (XMLDA) Commands Batch Data Access (DA) UA Server(s) UA Client(s) PULL FROM OPC FOUNDATION SLIDES

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… … check my trust list approved

DCOM Value Point #3 OPC Unified Architecture (UA) UA Server(s) Alarms & Events (A&E) Historical Data Access (HDA) Security Data Exchange (DX) XML Data Access (XMLDA) Commands Batch Data Access (DA) UA Server(s) UA Client(s) DCOM PULL FROM OPC FOUNDATION SLIDES

Value Point #4: Enterprise Data Communications Unified Architecture enables communications and data sharing enterprise-wide Enterprise Servers Workstations Mobile Controllers Embedded

Profiles What is a Profile? Why 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 Profiles tell clients and servers what UA services and information models are available. UA Products can decide if the other has the capabilities desired Most UA developers are doing the DA profile for now in products on the street

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 Demo Connect to a Remote OPC UA TOP Server using NO security Connect to a Local OPC UA TOP Server using security Connect to OPC UA OmniServer using security Monitor an OPC Item and log based on a Boolean value Monitor the Database Connection Write a False to a Bit when the connection goes down. Write a True to a Bit when the connection comes online. So here we are at last, the live demo! We’re going to log data from one OPC Server and log it to a Text file for use within Microsoft Excel. We want the data to be logged in a Detail mode because we want as much information about each Tag as possible. We’re not going to do any coding or scripting, we’re going to just use the wizards to setup the OPC DataLogger. Along the way, we’ll take a quick look at how you might log to a database instead of, or in addition to a Text file. [LIVE DEMO GOES HERE]

Troubleshooting Tools OPC Interoperability Testing Verify OPC connectivity and compatibility with OPC Server(s) Test Mode Test new configuration settings Does not affect background logging that may be in progress Events Window Export events to a text file (*.CSV) Events are logged to the Windows Event Viewer So in our demo, we logged data just fine and we saw it in Microsoft Excel. What if there problems and no data was logged? Well lets take a look at some of the tools available in the OPC DataLogger that can be used to help troubleshoot such problems… So I am going to show the OPC Interoperability screen, why Test mode exists, and then Events window. [LIVE DEMO GOES HERE TO SHOW THESE DIFFERENT SCREENS]

Affordable Text and CSV logging - $495 MySQL, SQL Server or Access logging - $795 each ORACLE or OBDC logging - $995 each No OPC Server Connection or Tag Counts No Database Connection or Text File Counts Troubleshooting Tools Included Buy just what you need Bundle and SAVE! The OPC DataLogger is very affordable. With solutions starting at just $495. Remember, the OPC DataLogger is not restricting how many Tags you can log, its not going to restrict how many OPC Servers you can connect to, and its not going to restrict how many textfiles or databases you can log to. All of the troubleshooting tools are included. Because of the plugin based nature of the product, if you just need to log to a text file then you don’t need to purchase the Database plugins allowing you to keep your costs down too.

The Swiss Army Knife of OPC Alternative Solutions OPC Data Hub The Swiss Army Knife of OPC As I have shown you the basics of the OPC Data Logger, we wanted to point out that if you need features the Data Logger doesn’t have, a great solution is the OPC Data Hub. The Data Hub can be used to tunnel the OPC Server data to the OPC Data Logger to avoid DCOM or to add secure data transport. The OPC Data Hub can provide changing data in an Excel worksheet as well as the ability to set up a script that can write back to the OPC Server. If DataHub is of interest to you, have a look on the website above or give us a call and we’ll discuss your specific needs and how the OPC DataHub may be able to fulfill them John ideas of things he’d like to see in the script….. DataHub can be used WITH Datalogger to provide additional functionality DataHub can be used as an alternative solution for logging data in different ways and provides some different functionality and approaches from DataLogger. (CW is this accurate?) For example, DataHub could be used to log data to a database and write data back to the OPC server as well If DataHub is of interest to you, have a look on the website above or give us a call and we’ll discuss your specific needs and how DataHub may be able to fulfill them www.softwaretoolbox.com/opcdatahub

www.OPCDataLogger.com More Information Free demo: Buy online: www.opcdatalogger.com/html/free_demo.html Buy online: www.opcdatalogger.com/html/ordering.html Questions: Win Worrall: Email: wworrall@softwaretoolbox.com Tel: +1 (704) 708-6491 Technical Support: Tel: +1 (704) 849-2773 Web: http://support.softwaretoolbox.com So at this point, I’d like to open-up the phones for Questions and Answers. www.OPCDataLogger.com