Software Toolbox Technical Blog

While Halloween and this time of year offers a few good scares, our customers in manufacturing face year-round nightmares that are far less fun: connectivity issues that stop production and unreliable data collection that restricts their ability to make informed decisions.

When your SCADA system can't communicate with your PLCs, your MES is missing critical data, and your operators are working without visibility into what's actually happening on the production floor, you're dealing with the kind of problems that lead to unplanned downtime, missed targets, and lost productivity.

In this post, we'll run through how our TOP Server handles common connectivity challenges, cover some practical tips for getting the most out of your setup, and show you how using remote configuration tools can simplify management across multiple servers, which all enable you to focus on production instead of troubleshooting communication nightmares.

Welcome to the launch of Software Toolbox’s Summer of IoT blog series for 2025.

In the coming posts, we’ll explore how our solutions support the evolving world of the Industrial Internet of Things (IIoT), and more importantly, how they can help you advance your Industry 4.0 and digital transformation goals with practical, proven tools. We begin the series by exploring Unified Namespace (UNS), what it means, why it matters, and how Software Toolbox makes it practical for real-world industrial environments.

Unified Namespace, Real Results: Lessons and Tools that Deliver

In today’s fast-evolving industrial landscape, seamless connectivity and data integration are critical for operational success. At Software Toolbox, our solutions are designed to empower businesses by enabling UNS connectivity, bridging the gap between diverse systems and helping with efficiency, interoperability, and scalability.

Personally, as a presenter and attendee of ProveIt! 2025 and an attendee of 4.0 Solutions’ Edge Integration to UNS Workshop, I have had a lot of exposure to the topic of UNS this year. In this blog post, I will share not only what I have learned surrounding the topic, but how Software Toolbox’s solutions fit into the picture.

When working with Modbus communication, understanding the key concept of function codes is essential for ensuring efficient and accurate data exchange. Sometimes a device manual might only refer to the supported Modbus function codes and the range of offsets available for those function codes. A solid understanding of function codes is critical in achieving optimized performance and resolving potential communication issues.

After reading this blog, you'll know how you can leverage TOP Server’s Modbus driver to automatically handle the appropriate function codes for your application – while also taking advantage of its flexibility and other advanced features – to enhance performance, ensure compatibility with your devices, and reduce troubleshooting time.

When working with Modbus devices and TOP Server, one critical factor that can significantly influence communication efficiency is the concept of block sizes. Optimizing block sizes for your application ensures smooth data transfer between your Modbus device and TOP Server, improving overall system performance.

In this blog, we’ll talk about what Modbus block sizes are, why they matter, and how to configure them effectively in TOP Server for the best results. We’ll also cover what happens when a block request includes non-contiguous addresses or undefined memory, causing potential issues with valid data. Additionally, it is important to note that other drivers/protocols may utilize block sizes as well, so these concepts could apply to other protocols beyond just Modbus.

Welcome to the kickoff post of our Data Storage Deep Dive blog series! In this series, we will explore the crucial role of data storage solutions and Historians in industrial automation. Over the coming weeks, we’ll be looking into how solutions delivered by Software Toolbox can be utilized with Historians, helping you make the most of your industrial data.

Welcome to the kickoff of Software Toolbox’s Summer of IoT blog series! Over the next few blog posts, we’ll discuss how our products can play a role in the exciting world of Internet of Things (IoT), but more importantly, how they can be used to further your success in Industry 4.0 and Digital Transformation initiatives. The IoT landscape has grown exponentially over the past decade, transforming industries by connecting devices, systems, and people in unprecedented ways. IoT is reshaping how we interact with technology. At Software Toolbox, we recognize the power of IoT and are committed to providing solutions that facilitate this technological revolution.

Have you ever been confused on the difference between Modbus offsets and addresses? I’m sure you may have configured different Modbus devices from different manufacturers who follow different documentation standards, especially for memory mapping. As we all know, that can certainly increase implementation time. In this blog post, we are going to dive into how offsets and addresses compare and differ to hopefully provide a better understanding, cutting down that configuration time when using TOP Server. Before we start comparing offsets and addressing, let’s first get an understanding of what both are.

In the world of industrial automation and control systems, communication protocols play a crucial role in ensuring seamless data exchange between devices. Modbus started as a protocol used in Modicon, now Schneider Electric, PLCs in the 1970’s. It was adopted across the industry for its clarity and simplicity. With any protocol, including and especially with Modbus, there are areas where the parties to the communication, the client and server, can interpret the bit stream of data differently once exchanged because the Modbus protocol specification does not speak to those interpretations.