Install the tools
Every OT Fabric command-line tool installs with the same line. Replace modbusctl with the tool you want:
curl -fsSL https://get.otfabric.io/modbusctl | shirm https://get.otfabric.io/modbusctl.ps1 | iexFrom cmd.exe: powershell -NoProfile -Command "irm https://get.otfabric.io/modbusctl.ps1 | iex".
Run the same line again to upgrade. That works for the tools with a repository of their own, such as iec104ctl or opcuactl, and for the tools that ship inside a library repository, such as otprobe in go-otfp or mbcapctl in go-modbus-capture. The list of tools is below.
What the installer does
Section titled “What the installer does”- It detects the platform: Linux on x86-64, ARM64 and ARMv7, macOS on Intel and Apple silicon, Windows on x86-64 and ARM64.
- It resolves the version once, the latest stable release or the one you pin, and uses exactly that release.
- It downloads the archive and the release’s SHA-256 checksums file, and refuses to install when the checksum is missing, malformed or does not match.
- It extracts only the expected binary and runs
<tool> versionas a smoke test before it replaces an installed copy. - It installs per user without
sudo, in~/.local/bin(or$XDG_BIN_HOME) and on Windows in%LOCALAPPDATA%\OTFabric\bin, and adds that directory toPATHunless you tell it not to.
The tools are single static binaries. There is no runtime, interpreter or package manager to install first.
Options
Section titled “Options”All options are environment variables, and they are the same for every tool.
| Variable | Default | Effect |
|---|---|---|
OTF_VERSION |
latest |
Install a specific version, 3.6.1 or v3.6.1. For a tool that ships inside a library repository, this is the library’s version |
OTF_INSTALL_DIR |
~/.local/bin; Windows %LOCALAPPDATA%\OTFabric\bin |
Install directory. PATH may be updated |
OTF_UNMANAGED_INSTALL |
unset | Install directory for CI, containers and device images. Never touches PATH or shell profiles. Cannot be combined with OTF_INSTALL_DIR |
OTF_NO_MODIFY_PATH |
0 |
1 leaves PATH and shell profiles alone |
OTF_TARGET |
detected | Force a target, for example linux-armv7 |
# A specific versioncurl -fsSL https://get.otfabric.io/modbusctl | env OTF_VERSION=3.6.1 sh
# CI, a Dockerfile or a device image: a fixed directory, no profile changescurl -fsSL https://get.otfabric.io/modbusctl | env OTF_UNMANAGED_INSTALL=/usr/local/bin sh$env:OTF_VERSION = '3.6.1'; $env:OTF_INSTALL_DIR = 'C:\Tools'irm https://get.otfabric.io/modbusctl.ps1 | iexThe installer exits 0 when the tool is installed, 1 when the installation failed and 2 on invalid input, so a pipeline stops at the install step instead of failing later. Under irm | iex PowerShell never exits, so it cannot close your terminal. Scripts, CI and containers has complete examples for GitHub Actions, GitLab CI and Dockerfiles.
Requirements
Section titled “Requirements”- Linux and macOS: a POSIX
sh(dash, bash, zsh or BusyBox ash),curlorwget(BusyBox wget works),tar, andsha256sum,shasumoropenssl. - Windows: Windows PowerShell 5.1 or PowerShell 7. Nothing else.
32-bit x86 and ARMv6 are not supported. On a 64-bit ARM kernel with a 32-bit userland, common on Raspberry Pi OS, the installer picks the ARMv7 build.
Without get.otfabric.io
Section titled “Without get.otfabric.io”The same scripts run straight from the installer repository and then download from GitHub Releases directly:
curl -fsSL https://raw.githubusercontent.com/otfabric/install/main/install.sh | sh -s -- modbusctl$env:OTF_TOOL = 'modbusctl'; irm https://raw.githubusercontent.com/otfabric/install/main/install.ps1 | iexFor machines without internet access, download the archive and the checksums file from the tool’s GitHub Releases page on another machine, check the archive with sha256sum -c, and copy the binary across. To build from source, each tool’s README has the steps; the tools with a repository of their own, apart from modbusctl and s7commctl, also install with go install github.com/otfabric/<tool>@latest and Go 1.26 or later.
Security
Section titled “Security”The checksums file comes from the same GitHub release as the archive. It proves that the download is intact, not who published it. In a pipeline, pin the version with OTF_VERSION so that every run installs the release you reviewed. Report vulnerabilities privately to security@otfabric.io, as described in each repository’s SECURITY.md.
| Tool | Protocol | Ships in | What it does |
|---|---|---|---|
bacnetctl | BACnet | bacnetctl | BACnet/IP discovery, property read and write, COV, alarms, BBMD and a simulated device. |
canbusctl | CAN bus | canbusctl | CAN, CAN FD and CAN XL: monitor, decode, record, replay, ISO-TP and simulation. |
canopenctl | CANopen | canopenctl | CANopen SDO, PDO, NMT, LSS, EMCY, EDS and DCF, CiA 402 drives and device simulation. |
dnp3ctl | DNP3 | dnp3ctl | DNP3 polling, control, discovery, file transfer and a simulated outstation. |
ethernetipctl | EtherNet/IP | ethernetipctl | EtherNet/IP discovery, attributes, cyclic I/O, Logix tags, EDS and adapter simulation. |
iec101ctl | IEC 60870-5-101 | iec60870ctl | IEC 101 on a serial line or terminal server: interrogate, monitor, command, unbalanced or balanced, and a simulated station. |
iec102ctl | IEC 60870-5-102 | iec60870ctl | IEC 102 meters: integrated totals, events, the clock and the REE profile, and a simulated meter. |
iec103ctl | IEC 60870-5-103 | iec60870ctl | IEC 103 protection relays: interrogation, commands, generic services, disturbance data and a simulated relay. |
iec104ctl | IEC 60870-5-104 | iec60870ctl | IEC 104 interrogation, monitoring, commands, file transfer and a simulated RTU. |
iec61850ctl | IEC 61850 | iec61850ctl | IEC 61850 MMS, GOOSE and Sampled Values: browse IEDs, control, reports and SCL. |
ieee20305ctl | IEEE 2030.5 | ieee20305ctl | IEEE 2030.5 device and server roles, registration, controls, certificates and a test server. |
knxctl | KNX | knxctl | KNXnet/IP discovery, tunnelling, routing, group monitoring, datapoint types and simulation. |
mbcapctl | Modbus | go-modbus-capture | Inspect, convert and validate MBCAP Modbus capture files. |
mbtracectl | Modbus | go-modbus-trace | Analyse Modbus/TCP traffic in pcap and pcapng traces and export MBCAP. |
mmstracectl | IEC 61850 | go-mms-trace | Analyse MMS, GOOSE and Sampled Values traffic in pcap and pcapng captures, offline. |
modbus-cli | Modbus | go-modbus | Minimal Modbus TCP and RTU client for quick probing and troubleshooting. |
modbusctl | Modbus | modbusctl | Modbus discovery, scanning, fingerprinting, SunSpec, recording, replay and simulation. |
nsdctl | IEC 61850 | go-iec61850-model | Look up, inspect and validate IEC 61850 logical nodes and NSD packages. |
ocppctl | OCPP | ocppctl | OCPP 1.6J, 2.0.1 and 2.1: probe a CSMS, simulate stations and serve a test CSMS. |
opcuactl | OPC UA | opcuactl | OPC UA discovery, browse, read and write, subscriptions, alarms, history and PubSub. |
openadrctl | OpenADR | openadrctl | OpenADR 3 VEN and Business Logic clients, notifications and a test VTN. |
otprobe | Multi-protocol | go-otfp | Find out which OT protocol an endpoint speaks, and which device answers. |
profinetctl | PROFINET | profinetctl | PROFINET discovery, DCP naming, I&M, diagnosis, topology, GSDML and cyclic I/O. |
s7commctl | Siemens S7 | s7commctl | S7 PLC discovery, rack and slot probing, memory read and write, blocks and diagnostics. |
sclgen | IEC 61850 | go-iec61850 | Generate Go types from IEC 61850 SCL schema bundles. |
sclparse | IEC 61850 | go-iec61850 | Detect, summarise and validate IEC 61850 SCL configuration files. |
sparkplugbctl | Sparkplug B | sparkplugbctl | Sparkplug B monitoring, publishing, payload coding and edge node and host simulation. |
sunspecctl | SunSpec | sunspecctl | SunSpec Modbus inverters, meters and batteries: detect, read, poll and simulate. |
The registry of tools lives in otfabric/install. The desktop apps, LAN Tracker and modbus-simulator are not on get.otfabric.io yet; download them from their GitHub Releases pages.
Uninstall
Section titled “Uninstall”Delete the binary: rm ~/.local/bin/<tool>, or on Windows %LOCALAPPDATA%\OTFabric\bin\<tool>.exe. If the installer added its directory to PATH, you can take that entry out again; the installer keeps no other state.