Raylux Manual

Appearance

Version 2026.20

Installing the client software ​

Studio and Lens are installed per user, on the machines that need them. Neither runs a service; both simply connect to a Nexus instance.

Download them from Nexus ​

Sign in to Nexus and open Downloads. It offers:

Nexus's Downloads page with cards for Raylux Studio and Raylux Lens, each showing a recommended Windows download and Linux/macOS marked Not availableThe Downloads page — one card per client, shown here on a trial gateway.

DownloadInstall it on
Raylux-Studio-Setup-<version>-x64.exeAn engineer's workstation.
Raylux-Lens-Setup-<version>-x64.exeA plant-floor panel PC.

Both are ordinary setup programs — run them and accept the elevation prompt. Each installs the Microsoft C++ runtime if the machine needs it.

"Not configured" on the Downloads page

Nexus serves these from its data directory, and they are put there by the Client installers for download component. If that component was cleared at install time, the page has nothing to offer. Re-run Nexus setup program, choose Custom, and select it.

Why these are separate from Nexus package

Nexus package always installs Nexus — it cannot be deselected. An engineer who downloaded "Studio" from it would end up running a Windows service they did not ask for, so Studio and Lens ship as their own setup programs.

Connecting Studio to Nexus ​

Studio opens on the Nexus Hub, a grid of the Nexus instances it knows about.

Studio's Nexus Hub showing three connection cards, two offline and one online with a Launch button, and an Add Connection cardThe Nexus Hub — one card per connection, plus Add Connection.

  1. Add a connection. Give it Nexus's address — myserver:8443 or myserver:8080.

    Studio's Add Connection dialog with Host, Port 8443 and a Verify Connection buttonAdd Connection — Host and Port, then Verify Connection before saving.

  2. Trust the certificate. On a self-signed certificate Studio asks you to verify it once, then remembers it. If the certificate later changes, Studio asks again — that is the point of it.

  3. Sign in with a Raylux account, then pick a project.

Studio needs an account with designer rights. The administrator you created at first run has them; for day-to-day work, create a Developer account instead.

Setting up a Lens panel ​

Lens shows one project full-screen, with no desktop behind it.

  1. Open Lens. It shows its own Hub, empty on a new install.

    Lens's Views hub, empty, with an Add View buttonAn empty Views hub — nothing to launch until a view is added.

  2. Add a view: Nexus address, then pick a project from the list it loads. Lens does not need an account to list projects — if the project requires a sign-in, Spectrum asks for it inside the view.

    Lens's Add View dialog, empty, with Name, Gateway and Project fieldsAdd View before loading — a bare host such as 10.4.1.20 defaults to HTTPS; give an explicit http:// address for a gateway that only serves plain HTTP.

    Lens's Add View dialog after loading, listing one project from the gatewayAfter Load, the Project list is populated from the gateway — this one was reached over plain http:// because it has no certificate.

  3. Choose Kiosk (full screen, no window chrome) or Windowed.

  4. Tick auto-launch if the panel should open this view on boot.

An auto-launching panel shows a countdown screen first, with Cancel focused, so a panel pointed at a Nexus instance that has gone away can still be reconfigured rather than looping.

Kiosk mode has no exit to the desktop

That is the point — an operator cannot get behind the HMI. Ctrl+Shift+H returns to the Hub, but only for a view that was launched from the Hub. A panel configured to launch from its environment has no escape, by design.