Software Toolbox Technical Blog

In case you're not familiar with OmniServer, it is a user-configurable I/O server solution that you can configure through a user-friendly interface to communicate with various devices that do not already have off-the-shelf drivers written for them.

A question that our support engineers at Software Toolbox sometimes receive from both new and veteran OmniServer users alike is whether an item in the OmniServer sequence builder, which is used to build the send and/or receive message for a device protocol, requires a formatting code or not.

Continuing our Tech Support Corner blog series, this blog post covers under what situations a formatting code is required for an item defined in the OmniServer sequence builder of a protocol and when a code isn't required.

If you've heard of the Cogent DataHub, you may be aware that it supports email and/or SMS notifications of defined conditional events based on a variety of data from it's various supported interfaces (MQTT, OPC UA, OPC DA, DDE, ODBC and more).  Having the right people receive alerts (such as when a tank has reached a critical level or a critical piece of machinery is offline) in a timely fashion can be the difference between simple downtime and a major liability.

This blog post will discuss how to use variable distribution lists in conjunction with the Cogent DataHub's Email/SMS capabilities to ensure the right decision makers will always receive important notifications as quickly as possible.

Hopefully you received one of my emails or possibly heard from a colleague about our latest TOP Server release.  If not, you may not have heard about the key new features in TOP Server for Wonderware V6.7.

In this post, I'm going to go through some of the key features released in V6.7 in more detail, including a continued focus on security enhancements, updates to the Configuration API capabilities, enhancements to the Torque Tool Ethernet driver and more, including how they benefit you as a TOP Server user.

As you may be aware, OPC Data Logger is an OPC lab-certified solution for dynamic, event driven logging of process data to standard SQL/ODBC databases, including Microsoft Azure SQL, or text/CSV files.  The wizard-based interface provides easy, flexible configuration that easily scales for project both large and small.

In this blog post, I'll cover some exciting new features that you may not be aware of from recent releases that are available in the current version.

With industrial processes, it's only possible to manage what is being effectively measured.  Without keeping tabs on key metrics in a process, you'll never be able to determine if the efficiency of the process is getting better or worse.

In this short blog post, we'll discuss the progression from raw process data to information to the actions that can be taken and decisions that can be made using that information.  We'll also discuss how the context (or how you're looking at data) can affect the information you're consuming.

DCOM Security and the headaches it tends to create are undoubtedly familiar to any OPC Classic user in the industrial automation industry. Stories about experienced DCOM woes are just part of the territory.

In this second part of a "DCOM Horror Stories" sidebar to our continuing Tech Support Corner blog series, this blog post covers a DCOM user scenario where the user was a little too thorough in locking down their DCOM configuration, resulting in a locked out system. And it includes a reminder of options that help you avoid DCOM configuration altogether.

You may or may not be familiar with Dream Report - a real-time report generator that is quickly and easily configurable via a very easy-to-use interface with a ton of flexibility relating to not only collection and archiving of data and alarms but also for analysis and options for report generation.

In this post, I'll review three of the top features released in the recent V5.0 release of Dream Report and how they benefit you, either as an new or existing Dream Report user.

Any OPC Classic user in the industrial automation industry has almost certainly had their interactions with Windows DCOM security.  And most, if not all, are stories that we all shake our heads at and nod in understanding of the difficulties of traversing the pitfalls of DCOM security configuration.

In this first part of a "DCOM Horror Stories" sidebar to our continuing Tech Support Corner blog series, this blog post covers a DCOM user scenario involving the Microsoft Windows Cortana search capabilities being sidelined by DCOM security misconfiguration. Additionally, it covers what options are out there for avoiding DCOM entirely for situations like this.