RLX-NX — Backend service
Everything else connects to Nexus.
Nexus is the tag engine, historian, device drivers, alarms and reporting — plus the web server that serves Spectrum, the configuration console and the manual. Installed once per site, on a server.
Specifications
Pre-release. Describes Nexus as built.
| Interfaces | Value |
|---|---|
| Allen-Bradley | EtherNet/IP — ControlLogix, CompactLogix 5370+ |
| Modbus | TCP, and RTU over serial |
| OPC UA | Any conformant server |
| Web / API | 8080 HTTP, 8443 HTTPS |
| Report delivery | SMTP, FTP, SFTP |
| Deployment | Value |
|---|---|
| Windows | Server 2019+ or 10/11, 64-bit — packaged |
| Linux | Build from source. No .deb or .rpm yet |
| Runs as | Windows service, or a systemd unit |
| Historian | Built in — no separate database server |
| Scripting | Sandboxed — no filesystem or network by default |
How it works
Talks to your plant
Drivers are built in. There is no separate OPC server to license, install and keep running alongside Nexus.
Each device carries its own poll rate, and the diagnostics for a connection sit on the device itself rather than in a log you have to go and find.
Keeps the data
The historian is part of Nexus. Tag history, alarm history and the audit trail are recorded without standing up a database server.
When a device link drops, writes are buffered and forwarded when it recovers, so a network blip does not become a hole in the record.
Serves everything else
The same service that polls your devices serves the operator runtime, the configuration console, the REST API and the WebSocket feed.
The manual ships with Nexus and is served from it, so the documentation always matches the version you are running.
Reports out
Rendered reports go out over SMTP, or land on an FTP or SFTP target on a schedule.
The console
