Per-route isolation and auto-reconnect
Protocol Bridge
Unattended channel mapping across Modbus, UDP, serial and MQTT — scale, deadband, reconnect, keep running.
What brings you here.
The situations this instrument was built for — and what it does about each one.
A Modbus register needs to land in SCADA, a CSV archive and a broker — without a person watching it.
One configuration file turns each flow into an unattended route with scale, deadband and periodic or on-change triggers.
One flaky endpoint must not take the whole line down.
Per-endpoint auto-reconnect with exponential backoff; a failed endpoint or route never stops the others.
Nobody wants to try out a configuration against a live plant.
bridge check validates every setting and every channel address while connecting to nothing.

Deadband + periodic triggers
Headless CLI with a minimal monitor
What you'll see.
One configuration file turns a flow such as Modbus register → scale → MQTT topic into unattended operation. Per-endpoint auto-reconnect with exponential backoff; a failed endpoint or route never stops the others. bridge check validates every setting while connecting to nothing, so it is safe to run against a live plant.
The monitor window
Pb.Monitor opens this window, refreshed twice a second — endpoints, routes, health, counts and last values. The CLI is the product; the window is an observer.

NK-06 datasheet
One file.
Copy it and run.
No installer, no package manager, no service account. Move the executable onto the air-gapped machine and open your work.
Quick answers
Does Protocol Bridge work offline?
Yes. Like every NOKTRA instrument it is offline-first: no cloud services, no telemetry, and any AI runs locally on your own machine. It is built for air-gapped networks.
What platform does Protocol Bridge run on?
Windows 10/11 x64. It ships as a single executable — no runtime install.
Is Protocol Bridge available for download now?
Not yet — it is in development. It is listed with no promised date, until a build exists you can run.