Software Toolbox Technical Blog

If you’re an existing user of OPC Data Logger or in the market for an OPC logging solution, you likely agree that having a reliable and accurate record of your data is a top priority. One of the most valuable parts of investing in a data logging solution is being able to trust that all the data from your sources is captured. But what happens if you lose the connection to your database? What happens to the incoming data during that downtime? Software Toolbox offers several solutions for logging data and today we will focus on OPC Data Logger and its database logging capabilities. 

If you're a TOP Server user, you're likely accustomed to connecting to a device configured in TOP Server that is sending real-time data through one of its many available drivers. But did you know you can setup devices in a "Simulated" mode for a variety of client testing purposes when a live device isn't available?

Continuing our Tech Support Corner blog series, this post covers how the "Simulated" device property works, why you might implement it into your testing and a brief walkthrough on connecting a variety of client applications to a simulated device in TOP Server.

Software Toolbox has a long-standing history of offering supplemental solutions that fit right in with AVEVA™ (formerly Wonderware®) projects. Many of you will be familiar with our TOP Server for AVEVA™ that offers a variety of device connectivity options, and a variety of client interface options like SuiteLink, OPC DA, and OPC UA.

SuiteLink is a communications protocol that runs over TCP/IP at the application layer, created by Wonderware to replace/succeed FastDDE, in the mid-1990's. Unlike OPC DA, SuiteLink doesn’t rely on COM or DCOM technology, making SuiteLink a common choice for remote connectivity to Software Toolbox solutions.

Continuing our Tech Support Corner blog series, this post shares best practices and procedures to follow when attempting to troubleshoot a SuiteLink connection, specifically when it comes to using SuiteLink clients with TOP Server. While this post specifically uses TOP Server as the SuiteLink server, the same techniques and concepts also apply to OmniServer, which also has a SuiteLink client Interface and is commonly used with AVEVA solutions.

If you’re a user of the Allen-Bradley ControlLogix Ethernet driver in TOP Server for AVEVA, you may be familiar with the different protocol modes available during device configuration. The three distinct options of Symbolic, Logical Blocking, and Logical Non-Blocking provide users with advanced control over how data is read and addressed from the controller.

Configuring protocol modes is usually only suggested for advanced users who have a solid understanding of each mode, and how their Logix programs are structured. To that end, continuing our Tech Support Corner blog series, this blog post will break down each of these protocol modes, while exploring their benefits and drawbacks, to provide you a clear understanding of each protocol. This post will provide the advanced knowledge needed in a usable way to best serve your own project!