Specifications

Plain specs, one scroll.

The figures below describe Nexus as built, with a described deployment and screenshots of a running system.

Specifications

Version 2026.20.

Interfaces	Value
Allen-Bradley	EtherNet/IP — ControlLogix, CompactLogix 5370+
Siemens	S7 — S7-300, S7-400, S7-1200, S7-1500
Modbus	TCP, and RTU over serial
AutomationDirect	CLICK and CLICK PLUS — TCP and RTU
Omron	FINS — TCP and UDP
DNP3	Outstation polling, with sequence-of-events timestamps
BACnet/IP	Building plant and HVAC
OPC UA	Client and server — connect out, or be connected to
Web / API	8080 HTTP, 8443 HTTPS — UI, REST and WebSocket
Report delivery	SMTP, FTP, SFTP

Deployment	Value
Nexus, Windows	Server 2019+ or 10/11, 64-bit — packaged installer
Nexus, Linux	.deb for Debian/Ubuntu, .rpm for Fedora/RHEL — x86-64. ARM64 on request
Runs as	Windows service, or a systemd unit
Studio & Lens	Windows only, installed per user
Historian	Licensed module — no separate database server to deploy
Dependencies	None — no database server, no OPC server, no runtime to install

Not sure about a particular controller? Check your PLC by family, model or part number.

In service

One deployment, described exactly.

A dairy ventilation system

Twelve rows of fans (52 fans in all) staged against barn temperature and measured air speed over the herd, with PID control of fan speed and staging delays on the way up and down.

The panel runs the gateway itself. There is no server in the building for it to depend on.

On the hardware

An ARM64 single-board panel with a 1024 × 600 touchscreen, talking Modbus TCP to an AutomationDirect CLICK PLC on the same network.

Nexus holds 131 device tags, records history, evaluates the alarms and serves the screens, in about 38 MB of memory.

What the operator sees

Five screens: an overview with live air speed and fan rows, setpoints, trends, the alarm list, and a PIN-gated page for PID tuning.

The same screens open in a browser on a phone or a desk, because they are served rather than installed.

52 Fans staged on temperature and measured air speed, under PID control.
131 Device tags polled over Modbus TCP from a single CLICK PLC.
5 Operator screens, served to the panel and to any phone on the network.
0 Servers in the building. The touchscreen panel is the gateway.

What it looks like

Screenshots of a running system.

Spectrum in a browser showing the Riverbend Water Reclamation overview: main readings across the top, four area cards for the lift station, EQ tank, aeration and clarifier all running, a plant-flow strip, level bars, a trend and an empty alarm list. — **Fig. 1** Spectrum, the operator runtime, in a browser tab, showing Riverbend, a simulated water-reclamation plant. Values are live from Nexus, and the screen was authored in Studio.

Studio with the Riverbend Water Reclamation overview open on the canvas: the project tree on the left, the EQ Tank area card selected, and its position and size in the Properties panel. — **Fig. 2** The same screen under edit in Studio, bound to live tags: the values move while you design.

The Nexus console for the Riverbend gateway: tag and device counts, CPU and memory, historian status, a Nexus load chart, a connected Modbus TCP device and a live event stream. — **Fig. 3** Nexus's own console: counts, load, historian state and every connected device. Served by Nexus, so there is nothing extra to install to see it.

The Nexus Hub: a grid of Nexus connections, each showing its address and online state, with a launch action. — **Fig. 4** Studio opens on the Nexus Hub, which lists every gateway it knows about instead of one hard-wired connection. One workstation, however many sites.