RLX-ST — Designer
Where the screens get built.
Studio is the engineering tool. It builds the screens, tags, alarms and reports that Nexus runs, and publishes them to a gateway. It installs per user, on an engineer’s workstation — not on the server.
Specifications
Pre-release. Describes Studio as built.
| Installation | Value |
|---|---|
| Installs on | An engineering workstation, per user |
| Platform | Windows 64-bit. Studio is Windows-only |
| Ships as | Its own setup program |
| Authentication | An account with designer rights |
| Connection | Value |
|---|---|
| Opens on | The Nexus Hub — a grid of known gateways |
| Transport | HTTPS to the gateway, 8443 |
| Certificates | Trust on first use; warns if one changes |
| Publishing | Audited — who pushed which page, and when |
How it works
Builds what the gateway runs
Screens, tags, alarms and reports are authored in Studio and published to a gateway, where Nexus serves them to operators.
Publishing is an audited action — the gateway records which designer pushed which page, and when.
Works across gateways
Studio opens on the Nexus Hub: a grid of every gateway it knows about, rather than one hard-wired connection. One workstation, however many sites.
Trusts a certificate once
On a self-signed certificate Studio asks you to verify it once and then remembers it. If that certificate later changes, it says so rather than connecting quietly.
That is trust-on-first-use, the same model as SSH — workable on a plant network with no public CA in sight.
Windows only, deliberately
Studio and Lens are Windows programs. A Linux gateway is a headless gateway: it runs Nexus and serves Spectrum, and you engineer it from a Windows workstation.
Studio at work
