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:

Download	Install it on
Raylux-Studio-Setup-<version>-x64.exe	An engineer's workstation.
Raylux-Lens-Setup-<version>-x64.exe	A 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.

1. Add a connection. Give it Nexus's address — myserver:8443 or myserver:8080.
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.
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.
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.