Red Lion Workbench vs Tool Kit and Red Lion Workbench

Abstract

If you have used Sixnet ISaGRAF with the Sixnet Series RTUs you know there are essentially two I/O Tag databases. The I/O tags are created in the Tool Kit, then exported to ISaGRAF. With the introduction of the Red Lion Workbench that same dynamic exists with some changes. A new dynamic is introduced where the Red Lion Workbench has the one data base. This document describes the difference between the two.

Products

ST-IPm-8460\VT-mIPm-138-D\VT-mIPm-248-D

Use Case: Creating I/O Tags in the Sixnet I/O Tool Kit or Red Lion Workbench

Required Software

Red Lion Workbench version 1.0.3 or greater.

Sixnet I/O Tool Kit version 5.0.101 of later.

One Tag Database –Red Lion Workbench

When using one tag (variable) database it is best to configure/program most RTU functions within the Red Lion Workbench. This will prevent conflicts in I/O updates and protocols. Create all variables in the Red Lion Workbench. For peer-to-peer and I/O transfers use the fieldbus configuration in Red Lion Workbench. The Sixnet I/O Tool Kit would basically be used to configure IP address, User Authentication, telnet, FTP, SSH, Firewall and Firmware upgrade. Below is an image showing the data type types supported and the function/features configured in the Red Lion Workbench versus the tool kit.

Basic configuration in Sixnet I/O Tool Kit

In the Sixnet I/O Tool Kit add an ST-IPm-8460. Set the IP address and set the serial COM Parameters. To use fieldbus configuration set the serial protocol to ‘User Defined.’ Configure user authentication to set a user name and password in Linux. Enable telnet, FTP and Set Firewall rules in the advanced button of the Ethernet port configuration.

Create variables, programs and fieldbus configuration in Red Lion Workbench

When creating a new program use any of the variables natively in the Red Lion Workbench. Set-up peer-to-peer transfers in the fieldbus configuration. Configure datalogging using the ‘LogFileCSV’ function block.

Two Tag Databases – Sixnet I/O Tool Kit and Red Lion Workbench

When using two databases there is a potential for conflicting operations, so care has to be taken to avoid that. One way to avoid conflict is by separating the operations in the RTU. Create the tags in the tool kit and have the configurations in the RTU handle most of the RTU operation (Datalogging, I/O Transfers and slave driver communication). Red Lion Workbench only provides the logic program. Below is an image showing how that works.  

Configuration

The Sixnet I/O Tool Kit is always used to configure communication parameters, firewall settings, user configuration and upgrade firmware.

Create Tags in the Sixnet I/O Tool Kit

In the I/O Modules tab Virtual Modules, Remote I/O Link modules that have I/O Tags. These I/O tags are used by slave protocols configured, peer-to-peer transfers, sixlog (datalog) configuration. The data types supported are listed below.

Export Tags from Sixnet I/O Tool Kit to Red Lion Workbench

Use File-Export-I/O Definitions to export tags to Red Lion Workbench. Since the Red Lion Workbench supports much more data types the Sixnet I/O Tool Kit data types are mapped to the Red Lion Workbench. Below is a matrix on how they are mapped. Inputs should only be used to input data to the Red Lion Workbench from physical I/O points and communication drivers. Output tags exported to the Red Lion Workbench program are always written to by the Red Lion Workbench. Create the program, compile and load to the RTU via the Red Lion Workbench.

© HMS Networks AB 2025