Welcome to the Kepware Blog

Stay up-to-date with the latest in industrial automation and data connectivity by subscribing to the Kepware blog. Browse by recent posts, topics, or contributors.

Real-Time Tag Updates with KEPServerEX V5.18

Posted by Aron Semle

On-the-fly, real-time, dynamic—these are all words we use to describe how we want our software to work. Change is happening all the time in plants, and we need software that can keep pace with it without requiring that systems be shut down and rebooted. That’s why I’m excited to share a new feature we’ve added to KEPServerEX version 5.18 that will make your life easier.


OPC Enables Best of Breed Solutions

Posted by KyLeigh Corrigan

Before the introduction of OPC, client software vendors were responsible for writing their own device communication drivers. Any time an application needed to access data from a new device, a new driver had to be written. This approach worked fine when each vendor included all the connectivity requirements that their end users needed. But when they did not, end users were stuck with inaccessible silos of data.


Let Operations Drive Server Architecture

Posted by John Harrington

Many people ask, "What is the optimal architecture for KEPServerEX within a plant; how many servers and where?" As with most questions of this nature, the short answer is that it depends, but there is some guidance we can provide.


How OPC UA Protects Your Data

Posted by Aron Semle

OPC UA was designed with security in mind. One of the key ways OPC UA protects the integrity and confidentially of messages is through message encryption and signing. Although this sounds fancy, the technologies OPC UA uses to achieve this have a direct impact on how end users interact with OPC UA products. This blog describes that technology, and details how to use it to make secure OPC UA connections.


Some Thoughts on Industrial Internet of Things

Posted by Erik Dellinger

I recently read an article from the ARC Advisory Group discussing the industry’s latest hot topics around the Internet of Things (IoT). According to ARC, IoT is not necessarily a new concept in the industrial space—it has traditionally gone by Machine to Machine (M2M) and Industrial Ethernet, to name a couple. The differences with IoT today are centered on new technologies and better performance for traditional asset management and predictive maintenance systems. These new technologies are different in that they enable more connectivity through cloud-based applications, are storing and aggregating data more efficiently, and are providing better performance around mining the data that is collected.


Polling the Crowd: Kepware's OPC Tunneling Webinar Results

Posted by Candace Letizia

This new infographic contains feedback from attendees of the OPC Tunneling Webinar presented by Kepware's Sam Elsner and the OPC Foundation's Thomas Burke on November 21, 2013. Click the image below to discover how your peers rate their familiarity with OPC Unified Architecture and describe how they have used tunneling products in the past. Then, visit the linked resources to learn how you can utilize OPC tunneling easily and securely in your next project.


Polling the Crowd: Kepware's KEPServerEX Version 5.13 Webinar Results

Posted by Candace Letizia

View Kepware's new infographic with feedback from attendees of our KEPServerEX version 5.13 webinar, and discover what your peers are reporting as their biggest issues with scanning and pollingThen, learn how Kepware's new Device Demand Poll can be leveraged to resolve those issues through the additional resources made available in this infographic.


Communication On-Demand: Device Data When You Want It

Posted by Tony Paine

Classic off-the-shelf client/server interfaces like OPC are optimized for collecting information from any data source at some predefined cyclic interval. Within the client application, an end user can browse for information that is contained in one or more servers. The information of interest can then be selected and tied to UI controls for visualization, alarm and event objects for condition monitoring, or trends for historical analysis. As part of this, the end user will also set how often each piece of data should be polled from the data source. Although perhaps over-simplified, the rest of the scenario is as follows: the end user enters Run Mode, the server polls the data sources at the appropriate intervals and sends updates to the client when the value or quality of the data changes, and the client performs the necessary logic on the information as configured by the end user. The process continues until the client application is stopped.