Spectrum

Spectrum is what operators use. Nexus serves it as a web page, so there is nothing to install, patch or license on the machines that run it — any machine with a browser and a route to Nexus can open it.

This section is an overview

The full Spectrum guide — navigation, alarms, trends and the operator's day-to-day — is still being written. What is here is accurate for the version named at the top of this page.

At a glance

Property	Value
Install	None. It is a web page
Requires	A browser and a route to Nexus
Reaches Nexus on	8080 (HTTP) or 8443 (HTTPS) — see Ports and firewall
Per-seat licensing	None
Phones and tablets	Any browser with a route to Nexus
Native mobile apps	Planned; not yet available. The browser is the mobile story until they are

How it fits

Operators see what an engineer published from Studio. Screens, alarm configuration and reports are all authored there and pushed to Nexus, so the runtime has no separate configuration of its own to drift out of step.

Values arrive over a WebSocket, pushed from the tag engine — the same channel Nexus's own configuration console uses — so a screen reflects what the tag engine actually has rather than polling on its own schedule.

A screen is authored at whatever size it needs to be, so a phone-sized view can be built alongside the plant screen and served from the same Nexus. Both are ordinary Spectrum views.

Opening it

Point a browser at Nexus — https://nexus:8443/ on a certificate-configured install, or http://nexus:8080/ — and sign in. If a project requires a sign-in of its own, Spectrum asks for it inside the view.

On a plant-floor panel that should show nothing but the HMI, run Spectrum inside Lens instead of a browser.

When it will not load

Spectrum is served by the same process as everything else, so if the page does not come up the question is whether Nexus is reachable at all. Start with Troubleshooting.