SCADA / HMI

Version 2026.20

Raylux 1.0.10: Tags, Projects and Screens

This release lets one project share its screens, popups and styles with others, makes reusable screen pieces work fully when placed inside other screens, enforces limits on numeric entry fields, and fixes a tag import that could leave every live value bad until the gateway restarted.

· All releases

This release lets one project share its screens, popups and styles with others, makes reusable screen pieces work fully when placed inside other screens, enforces limits on numeric entry fields, and fixes a tag import that could leave every live value bad until the gateway restarted. We recommend it for every gateway, and especially for anyone who imports tags into a running system.

Tags

  • Re-importing tags no longer knocks live values offline. Importing a tag file with "overwrite existing" selected — or re-adding a tag that already existed — reset every affected tag to a bad value of zero, and it stayed that way until the gateway was restarted. An overwrite now updates the tags in place: live readings carry on, and only the tags whose settings actually changed are affected.
  • A changed start value or data type takes effect straight away. When an overwrite changes a memory tag's configured start value, the new value is applied; when the start value is unchanged, whatever an operator last wrote is kept. When a tag's data type changes, it switches to the new type instead of holding its old value.

Projects

  • A project can inherit from a parent project. Screens, popups, style classes, the project stylesheet, shared page settings and images defined in the parent are available in every child project, and a child can override any of them by defining its own with the same name. Edit a shared popup once in the parent and every plant project using it picks up the change. Pages and navigation stay in each project.
  • What is not inherited yet: tags and scripts stay per-project, and inheritance is one level deep — a parent cannot itself have a parent. For now the parent is set in the project definition; a designer control for it will follow.

Screens

  • Reusable screen pieces pass their settings all the way down. A reusable view placed inside another reusable view, a popup or a repeater now receives the settings its host passes it, so a motor or valve symbol placed several levels deep shows the right equipment's values. Settings written as a structured value are read correctly too; previously they were dropped and the piece showed no data.
  • Clicks and other events work inside reusable screen pieces. Labels, images and containers inside an embedded view now respond to their own click actions. Clicking something inside the piece no longer also triggers the click action of the view it sits in.
  • Numeric entry fields enforce their limits. A value outside the field's minimum or maximum is refused when the operator commits it, and it is rounded to the field's configured decimal places. If a limit is bound to a tag that cannot be read, the entry is refused rather than allowed through, so a missing limit can never let an out-of-range value reach the controller.

Does this affect me?

  • You import tag files into a running gateway — yes, install this release. An overwrite import no longer interrupts live values.
  • You build screens from reusable pieces or popups that take settings — yes. Nested pieces now show the right values and respond to clicks.
  • You write setpoints from numeric entry fields — yes. Configured limits are now enforced when a value is entered.
  • Everything else is unchanged. Your projects, tags, history, alarms and users are kept when you install over an earlier 1.0 release, and nothing needs to be reconfigured. A project without a parent behaves exactly as before.

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 1.0 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-1.0.10-x64.exe — the whole system for Windows: gateway, designer and plant-floor client. Start here if you are not sure.
  • Raylux-1.0.10-x64.msi — the gateway on its own for Windows, for scripted or unattended installs.
  • Raylux-Studio-Setup-1.0.10-x64.exe — the designer, for an engineer's workstation.
  • Raylux-Lens-Setup-1.0.10-x64.exe — the plant-floor client, for operator stations.
  • raylux-nexus_1.0.10_amd64.deb — the gateway for Debian and Ubuntu: sudo apt install ./raylux-nexus_1.0.10_amd64.deb
  • raylux-nexus-1.0.10-1.x86_64.rpm — the gateway for Fedora and RHEL: sudo dnf install ./raylux-nexus-1.0.10-1.x86_64.rpm

Next step

Run the latest release.

Every 1.0 release installs over the one before it and keeps your projects, tags, history and users. Follow new ones in a feed reader, no email needed.