EthernetIP

The EthernetIP configuration pages define Ethernet/IP devices and their variables. Create the device entry first, then configure the variables that represent controller tags or mapped data points.

Use the device page for connection-level settings. Use the variable page for tag mapping, datatype selection, and naming used elsewhere in the project.

Keep the device and variable naming aligned with the PLC program and plant naming standard so the relationship remains clear across systems.

Device Settings

Each EthernetIP device defines a connection to a PLC or controller. Configure the connection endpoint, routing path, and timing options.

Create a new device with the Add button in the toolbar. The Add device dialog contains all device settings organized in the sections General, Connection, Scanning, and Diagnostics, with default values already filled in. Enter at least the Name and IP Address and press Create.

The device row shows Enable, Name, IP Address, Port, PLC, Path, Scan Rate, Template, and Description directly and these values can be edited in place. Press the Settings icon on a device row to open the Edit device dialog, which contains the same sections and all settings of the device. Press Save to apply the changes.

PLC Types

Select the PLC family that matches the controller. The PLC setting determines both the communication method and the format of the variable Address.

LGX and MLGX800 address variables by tag name and require a Path. MLGX, SLC500 and PLC5 address variables by data file and take no Path unless the connection routes over a DH+ bridge.

Variable Settings

Each EthernetIP variable maps a controller tag to a named variable in the EnvisionSCADA namespace.

Create a new variable with the Add button in the toolbar. The Add variable dialog organizes all variable settings in the tabs General, Scaling, Historian, and Gateway, with default values already filled in. Enter at least the Name and Address on the General tab and press Create. When the variable is created on a template device, it is also created on all instance devices that use the template. On a template device, start the Name with the {Device} replacer, so that each instance device gets its own variable. The Name must resolve to a different variable on each device; this is checked for every instance device before anything is saved, when a variable is created and when it is renamed.

The variable row shows Enable, Name, Asset, Type, Address, and Description directly and these values can be edited in place. Press the Settings icon on a variable row to open the Edit variable dialog, which contains the same tabs and all settings of the variable. Press Save to apply the changes. Changes made on a template device are also applied to the matching variable on all instance devices, while each instance keeps its own Modbus Address value. The Gateway tab settings Modbus Address, OPC UA, Writeable, MQTT Publisher, Kafka Device, Kafka Remap Device, and Kafka Remap Variable are also available as table columns, which are shown with Columns as described in the Configuration Tables article.

Supported Data Types

The Type field determines how the tag value is interpreted.

Variable Arrays

A variable can expand into an array by setting the Array size field to a value between 2 and 512. The variable itself is the first element and its Name must end in the first index, for example Temps[0]. The remaining elements are created automatically as Temps[1], Temps[2] and so on. The Address must end in an array index such as MyArray[0], matching the array as it is declared in the controller, and each element advances that index.

The element rows are managed by the first element: they follow its settings, appear locked in the variable list, and are edited by editing the first element. Changing the Array size adds or removes elements at the end. Renaming the first element or changing its address renames and re-addresses all elements. Setting Array size back to 0 while elements exist removes the elements.

To turn the elements into ordinary independent variables, use the Ungroup array action on the first element's row in the variable list, or the Configuration API (POST /API/Config/VariableArrays/Ungroup). All rows are kept and only the grouping is removed. This is one-way. The element count badge next to the first element's name folds and unfolds the element rows in the list.

Notes

The Address field uses the addressing format of the selected PLC family. For LGX and MLGX800, use controller-scoped or program-scoped tag paths such as TagName or Program:MainProgram.TagName. Array elements are addressed with square brackets, for example MyArray[0]. For MLGX, SLC500 and PLC5, use the data file address, for example N7:0.

The Path field specifies the CIP routing path to reach the target controller. For a direct connection to a controller in slot 0 use 1,0. For routing through an EN2T module in slot 2 of a remote chassis, use 1,2,2,192.168.1.20,1,0. Leave Path empty for MLGX, SLC500 and PLC5 unless the connection routes over a DH+ bridge.

A variable whose tag cannot be resolved on the controller is reported individually with status Format Error and does not affect the other variables on the device. When the controller cannot be reached, the device reports Channel State Offline and all its variables report Connection Lost.

Variables are referenced at runtime using the format DeviceName.VariableName, for example PLC1.Pump1_Speed.

A value written to a variable must match the tag type: a number for the numeric types, and true, false or a number for a BOOL, where any number other than 0 sets the bit. A value that does not match, for example text written to a REAL tag, is not sent and the controller keeps its value. The System Log records the rejected write, and the variable status shows FormatError until the next successful read of the variable.