Raylux 2026.20: Raylux Iris, Safer operator writes and Python in bindings

Raylux 2026.20 introduces Raylux Iris, which lets the AI assistant you already use look at your plant and help you understand what is going on. It also makes operator writes safer, makes Python in bindings work end to end, adds a batch of screen components and settings, and speeds up the Allen-Bradley driver. We recommend it for every gateway.

Raylux Iris

• Ask your plant what's wrong. The gateway now has a built-in MCP server, so an AI assistant that speaks MCP can read live tag values, active alarms, the alarm journal, history, devices and projects, and explain in plain English what it thinks is happening and why.
• Iris is read-only. Nothing an AI assistant can do through Iris writes a tag, acknowledges an alarm or changes configuration. Read-only Iris is included at no extra cost.
• It is off until you turn it on. An administrator enables it in the configuration console under Security › Iris MCP and issues an access key for each assistant. Each key acts with a role you choose and is checked on every call, so an assistant sees only what that role allows. Keys are shown once, refused over plain HTTP, and every call is recorded in the audit log under the key's name.
• What an assistant reads is sent to the AI service it uses, which may be a cloud service. Issue keys only to assistants you trust with that plant's data.
• New: a Tag access setting for the whole gateway, under Nexus Settings › Tag access. Open lets tags be read and written without signing in; Restricted requires a signed-in user or an access key. The change applies immediately and is recorded in the audit log.
• Groundwork for AI features inside Raylux. The configuration console has a new Security › Iris AI page for connecting an AI model provider, with spending budgets, rate limits and a record of every conversation. Everything on it is off by default. These features are licensed separately; trials include them, and pricing will follow.

Safer operator writes

• A write from a screen always goes to the right tag with the right value. One write policy now covers every control, values are checked before they are sent, and controls that cannot write safely say so instead of guessing.
• Screens tell operators the truth about their connection. Connection state, signing out, unknown symbols and the alarm table were all tightened up.
• The binding dialog and graph editor no longer lose or mix up a binding when you edit them.
• Momentary buttons can hold-to-jog, with a heartbeat so the output drops if the connection does.
• Button confirmations are configurable, with a confirmation popover by default.

Python in bindings

• Python works everywhere in bindings: script transforms, script bindings and the Run Script action, evaluated on the gateway.
• A format with an unquoted % now multiplies by 100 on the gateway too, so a value shows the same in every place.

Screens and components

• Alarm counts by folder: show how many alarms are active or unacknowledged under a folder, and their highest priority.
• The alarm table can filter by source, and Ack All works per device.
• Pages can scale proportionally while text keeps a fixed size.
• Trend pens can use view parameters in their tag path.
• Popups can set their title when opened, and popups have sensible defaults.
• Toggles have a checkbox appearance.
• SVG text honours font weight.
• Side and top docks slide in and out, and can push the page or cover it.
• The Moving Analog Indicator has square track ends by default, and its pointer sits on the bar.
• Number text inputs format their value when not being edited.

Studio

• The Project Browser shows views inherited from a parent project. Open one read-only, override it with a confirmation, or revert the override.
• The designer canvas looks like the runtime: parent-project styles, embedded views of inherited screens, containers, trends, alarm tables, reports and flex repeaters now draw as they do for operators.
• Selecting the view no longer jumps back to the last component.

Drivers and gateway

• The Allen-Bradley driver makes about three times fewer reads for the same tags, backs off when a poll overruns, and reports poll diagnostics.
• Tag groups keep their scan timing when several groups share a rate.
• The memory warning no longer flickers on a gateway that has just started.
• Projects can be deleted through the gateway API; a project that another project inherits from is protected.

Licence agreement

• The installers now carry version 1.3 of the licence agreement. It describes how licence keys are activated, the daily licence check, and the seven-day notice if a key is withdrawn, which earlier installers did not yet say. It also adds terms for Raylux Iris: AI output is advice to be reviewed by a qualified person, never a safety layer, and plant data goes only to the AI services you choose. The full text is at rayluxscada.com/eula.

Does this affect me?

• Everyone upgrading from 2026.19: install as usual. Projects, tags, history, alarms and users are kept.
• You don't want AI anywhere near your plant: nothing changes. Iris and the AI features are off until an administrator turns them on.
• You use Allen-Bradley devices: polling is lighter on the PLC. Values and scan rates are unchanged.
• Your screens write to tags: writes that were already valid behave as before. A write that was ambiguous or out of range is now refused with a message instead of being sent.

Installing

• Windows: Windows Server 2019 or later, or Windows 10 or 11, 64-bit. The gateway installs as a Windows service and starts on boot. Installing over an earlier release keeps your projects, tags, history and users. These downloads are not code-signed yet, so Windows will warn you the first time you run one.
• Linux: x86-64. Ubuntu 24.04 or later, Debian 13 or later, Fedora 39 or later, or RHEL, Rocky or Alma 10 or later. Install over an earlier package to upgrade; your data in /var/lib/raylux is kept. Studio and Lens are Windows-only; the gateway serves operator screens to any browser. The packages are not signed yet.

Downloads

• RayluxSetup-2026.20-x64.exe: the whole system for Windows (gateway, designer and plant-floor client). Start here if you are not sure.
• Raylux-2026.20-x64.msi: the gateway on its own for Windows, for scripted or unattended installs.
• Raylux-Studio-Setup-2026.20-x64.exe: the designer, for an engineer's workstation.
• Raylux-Lens-Setup-2026.20-x64.exe: the plant-floor client, for operator stations.
• raylux-nexus_2026.20_amd64.deb: the gateway for Debian and Ubuntu: sudo apt install ./raylux-nexus_2026.20_amd64.deb
• raylux-nexus-2026.20-1.x86_64.rpm: the gateway for Fedora and RHEL: sudo dnf install ./raylux-nexus-2026.20-1.x86_64.rpm