Software Toolbox Technical Blog

In a prior blog post regarding redundancy, we learned how critical it is to plan for redundancy in the Industrial Automation space. We covered how the TOP Server Media-Level Redundancy Plug-In  facilitates duplicate or backup systems used to maintain reliable communications with the critical components in your environment which in turn minimizes data loss and increases the availability of your critical industrial data.

The engineering definition of redundancy is “the inclusion of extra components which are not strictly necessary to functioning, in case of failure in other components.” In the Industrial Automation space, redundancy is critical. Not planning for redundancy can easily result in vulnerability to financial losses due to unexpected downtime. There are multiple types of redundancy in the industry. In this blog, we will be covering “Media-Level Redundancy”.

If you are reading this post, chances are you have configured your TOP Server project and are communicating with your devices successfully. Perhaps, you also have a client application successfully writing and/or reading to or from TOP Server. Did you know all TOP Server drivers provide several different Scan Modes for controlling how client requests affect the polling frequency for your configured devices? In fact, these Scan Modes apply to all client connection types including OPC UA, OPC DA and AVEVA SuiteLink.

Continuing our Tech Support Corner blog series, this short post will discuss the five Scan Mode options available in the TOP Server Device Properties. Each Scan Mode serves a different purpose depending on your specific scenario. We will explain each mode, giving you a better understanding of which mode is best for your situation. Correctly setting the Scan Mode to match the capabilities of your device will help to provide optimal performance for your automation system.

If you are reading this post, chances are that you are somewhat familiar with TOP Server as well as how to configure it to communicate with various devices. Perhaps, you are also familiar with how to configure different settings, OPC UA endpoint settings, Licensing, Stop and Start the Service, and, if you are a developer, you might be familiar with the development resources that TOP Server offers such as the Remote Config REST API and the OPC.NET interface.

However, during our daily interaction with end-users, we often find that there is a misconception of what the TOP Server application is composed of and how each component contributes to delivering the product that you interact with daily.

Continuing our Tech Support Corner blog series, this short post will discuss the various components of TOP Server and clarify how each component contributes to the macro process that allows the application to deliver communication between your process devices and your various IT/OT systems.