Skip to content
hotloopdocs
GitHub

HotLoop documentation

Plant-floor software written in Go. It reads your equipment, keeps every reading, and won't move a machine nobody armed. These docs say what has been proven and what hasn't, and they don't round up.
Install HotLoopThe lineupRelease notes

The family

Section titled “The family”

HotLoop is seven products for the plant floor: four that grow with a site (IoT, Edge, Gateway, and Edge Relay), plus Flow for wiring, Cascade for workflows, and Transmitter for putting a PLC’s values on the wire. They ship on four release lines, so each carries its own version. Each section in the sidebar shows only what that product ships, and a bigger product links back to the pages it carries from a smaller one.

HotLoop core line

Version 4.18.11

One codebase, one version. IoT to Edge to Gateway is the path a site grows along, and Edge Relay is the headless forwarder beside them.

Flow line

Version 2.8.1

Its own release line, running next to HotLoop.

Cascade line

Version 1.0.2

Its own release line, running next to HotLoop.

Transmitter line

Version 1.1.0

Its own release line, running next to HotLoop.

Not sure which one fits the box? The lineup has the table, the sizes, and the way up from one product to the next.

Start here by what you’re doing

Section titled “Start here by what you’re doing”
Monitor a machineRead the equipment, keep the history, raise the alarms.
Run a line HMIDashboards bound to a screen, and an OPC UA server for your SCADA.
Connect sitesFleet management, multi-site roll-ups, and scheduled reports.
Wire logic in FlowRun your Node-RED flows on a Go runtime.
Automate business workflows in CascadeAlarms and schedules become checkpointed workflows.
Forward from a small boxPoll, forward over Sparkplug B, and buffer when the uplink dies.

The latest from each line

Section titled “The latest from each line”

How to read these docs

Section titled “How to read these docs”

“Verified” means it ran against the real thing: a real OPC UA server, a real broker, Ignition itself. Anything tested against a simulator or a stand-in says exactly that, and a page that describes something nobody has run on a bench says so before it tells you how to use it.

Pages follow main, and the latest release is what you have installed. A page that describes something newer than the release carries a Next release badge and a box at the top. A page that has moved since the release says so. The page header and the release notes tell you which side of the line you’re on, so you find out here, not after an upgrade.

The docs are synced from the products’ own repos, at their current main, and rebuilt every release. Two of those repos are private, so the sync runs from a clone and its result is committed here.

Where to go next

Section titled “Where to go next”