Raylux 2026.12: Versions and licensing, Projects and Screens

Raylux now numbers its releases by year: this is 2026.12, the release after 1.0.10. It also stores each project as a folder of files instead of one large file, lets operators adjust trend charts while they watch them, adds confirmation prompts and enable conditions to buttons, and explains clearly on screen when a gateway has stopped because its licence ran out. We recommend it for every gateway.

Versions and licensing

• Releases are now numbered by year. 2026.12 is the twelfth release of 2026; the first release of next year will be 2027.1. The year is the part that matters for your licence.
• A licence covers every release of the year it was bought. A licence bought in 2026 covers 2026.12 and every later 2026 release. Moving to 2027 releases is an upgrade.
• The previous year keeps getting fixes. Once the first 2027 release is out, 2026 continues to receive bug and security fixes (numbered 2026.13, 2026.14 and so on), but no new features. Earlier years receive nothing further.
• The licence agreement is updated to version 1.2 to describe the new numbering and the fix policy. Nothing else in it changed.

Projects

• Each project is now stored as a folder of files. Screens, scripts, named queries and styles each live in their own file under a projects folder next to the gateway's configuration, which makes projects far easier to back up, compare and keep under version control.
• The change happens automatically on upgrade. The first time 2026.12 starts, it moves your existing projects into the new layout and keeps your previous configuration file alongside as a backup. Nothing needs to be exported or re-imported.
• Saving is all-or-nothing. If the gateway is interrupted in the middle of saving a project, the next start completes or discards that save, so a project is never left half-written.
• Two screens whose names differ only in capital letters are refused (for example "Home" and "home"), because Windows cannot store them as separate files.

Screens

• Operators can adjust trend charts while viewing them. Hide or show a pen, move it to another axis, remove it, override an axis range, or change the time window. The changes last only for that operator's session and never alter the project. A designer can switch this off per chart.
• Buttons can be enabled or disabled by a condition. Bind a button's Enabled setting to a tag or expression; while it is off, or while its value cannot be trusted, the button greys out and writes nothing.
• Buttons can ask for confirmation. Give a button a confirmation message and the operator must confirm before anything is written.
• Text fields can be set to numbers-only without having to set a minimum or maximum. A non-numeric entry is refused and nothing is written.
• Equipment symbols can hide their caption, giving the space back to the drawing, for screens that place a separate label beside the symbol.
• Reusable screen pieces on a scaled page are sized correctly. They were previously scaled twice.
• Trend charts respond correctly to touch on scaled screens.
• A multi-state label with no data no longer reads as "Stopped".

Devices and history

• Changing a device tag takes effect straight away. Editing or re-importing a device tag's address re-connects it to the device live, without restarting the gateway.
• History records a first value as soon as a tag starts recording, and can record a value at a set maximum interval even when it does not change, so a quiet tag still shows a continuous line on a trend.

Configuration console and designer

• The configuration console shows each tag's plausibility limits (the range and rate checks that mark a reading as suspect), read-only, next to the tag.
• The configuration console shows the Raylux version in its top bar once you are signed in. It is never shown to visitors who are not signed in.
• Every setting a component offers appears in the designer's property panel, including ones that have not been set yet.
• The designer's start-up screen shows the edition year.
• Browser tab icons no longer sit on a solid square. They adapt to light and dark browser themes.

Licence expiry

• A gateway whose licence has run out now says so plainly on screen. Operators see that the gateway has stopped and why, instead of screens that simply show no data. You can add a support contact (a name, phone number or email) for them to call; it appears on that notice.
• You cannot get locked out. The configuration console still admits you on an expired gateway, so a licence can always be added.

Does this affect me?

• Everyone upgrading from 1.0.x — install as usual. Your projects are converted automatically and your previous configuration is kept as a backup file. Tags, history, alarms and users are unchanged.
• Going back to a 1.0 release after upgrading — a 1.0 release refuses to start on the converted configuration, rather than risk damaging it. To go back, restore the backup file the upgrade keeps (raylux_project.json.v2.bak) along with the older version.
• You moved the gateway's data folder on Windows to a long path — keep the full path of the data folder short (the default C:\ProgramData\Raylux is fine). A very long path can prevent the project conversion on first start; the gateway then stops with a clear message and leaves your configuration untouched.
• You use licences — licences issued from now on name a year. Installing a licence issued under the new scheme needs 2026.12 or later.

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