SCADA / HMI

Version 2026.25

Raylux 2026.25: Scripting, Alarms and Tags

Raylux 2026.25 gives scripts web requests and email, adds tag scaling and quality-check alarms, and gives the plant-floor client printing, file saving and an exit dock.

· All releases · Download this release

Raylux 2026.25 gives scripts web requests and email, adds tag scaling and quality-check alarms, and gives the plant-floor client printing, file saving and an exit dock. It also fixes a gateway that could hang when told to stop, makes Micro800 controllers connect, and speeds up expression tags.

Does this affect me?

  • Upgrading a running gateway: install over 2026.24 as usual. Projects, tags, history, users and alarm configuration are kept, and nothing in this release needs a gateway restart to configure.
  • A Map transform with a blank fallback now shows blank when no row matches. Before, it showed the input value. If you relied on that, open the transform and choose When no row matches › Pass the input through.
  • Bindings with a script or node transform on a tag now show the transformed value to every operator. Before, only the designer's preview showed it, and operator and kiosk screens showed the raw tag value. Check screens where you had worked around this.
  • A float tag that receives NaN or infinity now goes Bad quality and keeps the value it received. Before, it stayed Good. Stored NaN values now show as gaps in trends instead of 0.
  • Micro800 controllers connect. They were given a backplane path they do not accept, so they never connected. No action is needed; a path left in an existing Micro800 connection is ignored.
  • The gateway checks its license file every minute while running. Activating, replacing or removing a license takes effect without a restart. A license file that cannot be read for a moment does not stop the gateway; it keeps running on the last good license.

Scripting

  • Web requests and email from scripts. Scripts can call web services (raylux.net) and send email (raylux.mail.send). The gateway blocks requests to itself and to cloud metadata addresses. Settings › Outbound HTTP holds allowed and blocked hosts, limits and stored credentials, and every request is logged in the audit trail with its host.
  • Every script function works in every kind of script: gateway event scripts (Shutdown included), component scripts, transforms, script bindings, report data sources, alarm pipeline script steps and the project scripts they call. Timeouts and limits keep a busy script from slowing the gateway.
  • Project scripts can call each other, including back and forth, and runaway recursion ends with an error instead of hanging. A project script module can use raylux without importing it.
  • Event scripts run one at a time, in order. A tag change script keeps up to 5 waiting changes and tells the next run how many it missed.
  • Scripts that run at the same time are safer. The scripting engine's internal records are now protected when several scripts run at once.

Alarms

  • Webhook steps in alarm pipelines send to a web address, with headers, a body format and a message template.
  • Quality-check alarms. A tag's range, rate-of-change or stuck-value check can raise an alarm when it fails, at the priority you choose. The alarm clears when the value recovers. Turn it on in the tag editor's Quality page.

Tags

  • Tag scaling and clamping. Device tags can scale raw values (linear, square root, exponential filter or bit inversion), clamp them to a range, and use a percent deadband. Writes are converted back to the device's raw value. Set it in the tag editor's Scaling section.
  • Expression tags are much faster. Each expression is compiled once instead of on every update, so a gateway with many expression tags uses a fraction of the CPU it did. Alarm notification conditions get the same speedup.
  • Expression tags that use now() update at their tag group's rate. A provider written as [Default] instead of [DEFAULT] was falling back to a one-second group.
  • Tags inside a UDT live in the instance's provider and carry their engineering units.
  • Tag import checks a tag's quality settings and refuses a row with bad ones, with a message, instead of storing a tag that would not load.
  • Live values reach screens sooner. Small updates are no longer held back by the network stack, which cut update delay on busy screens from about 40 ms to about 1 ms.

Devices and drivers

  • Micro800 controllers connect (see above). The connection form clears and disables the path field for a Micro800.
  • Concurrent reads for Allen-Bradley connections. Set how many tag reads the gateway keeps in flight to one controller, from 1 to 1000 (default 200). Lower it for a small or busy controller. It applies live.
  • Editing an Allen-Bradley connection keeps its timeout. Before, saving any change reset it to 5 seconds.

Plant-floor client (Lens)

  • Print, save to PDF, full screen and exit from a screen. Screen actions can print, save as PDF, toggle full screen, close the client and open a web link in the browser.
  • Save files and use the camera and microphone. A screen action can save a file through the client's own save dialog. Camera and microphone work for the gateway's screens only. Each of these can be turned off per screen, or locked off for the whole machine.
  • Exit dock. A small tab in the bottom-right corner opens a dock showing the client version, the project and the gateway connection, with Exit and Back to Hub. A project setting hides the tab.

Designer and runtime

  • Date functions use local time everywhere. dateFormat() and the date part functions such as year() and hour() now agree, in the browser and on the gateway.
  • The Heat Trace Line component has a View setting to fix its orientation, and draws pipe crossings and buried sections more cleanly.
  • The Brand kit dialog shows a project's on-screen keyboard setting correctly and no longer resets it when you save another change.
  • The manual has a guide to choosing a binding, with measured costs for each kind, under Studio › Choosing a binding.

Gateway reliability

  • The gateway stops promptly. A gateway with expression tags that used now() could ignore a stop request and need to be killed. A rare crash while stopping is also fixed, and stopping no longer waits several seconds for scripts that had already finished.
  • The gateway log is written to disk every second, so the last lines before a power cut or forced stop are kept.

Downloads

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

The Windows installers need 64-bit Windows 10 or 11, or Windows Server 2019 or later. They are not code-signed yet, so Windows may warn before running them; check the SHA-256 checksum on the downloads page first.

The Linux packages, x86-64 and ARM64, need glibc 2.38 or later: Ubuntu 24.04, Debian 13, Raspberry Pi OS based on Debian 13, Fedora 39 or later.

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.