AI-driventedge-dot is developed largely by AI coding agents, and it is alpha software. Check what it does before you rely on it, and report what you find.

OT connectors for thin-edge.io

Every fieldbus, one contract.

tedge-dot connects Modbus, OPC UA and SNMP equipment (with CAN bus, CANopen, PROFIBUS-DP and AVEVA PI in preview) to thin-edge.io. A lean driver publishes one protocol-neutral MQTT contract; small JavaScript flows turn it into measurements, alarms and device parameters in the cloud.

Get started Try it in 5 minutes GitHub

Protocols

Seven protocols, one shape of data

Every connector publishes the same sample, status and cmd envelopes on te/device/<device>/ot/<protocol>/…, so a flow, a dashboard or a cloud integration written once works for all of them. The connectors marked Preview are tested against simulators but not yet on real equipment.

Packages

Two packages, one contract

The same tedge-dot exists twice, written in Rust and in C, released together and held to the same test suites. Start with tedge-dot-c; configs and flows work unchanged on both. Whether both remain in the final product is not decided yet.

tedge-dot-cC

The default. About 25 times smaller, runs down to glibc 2.17, and ships every protocol, including the PROFIBUS-DP preview.

Binary: 457 KB
glibc floor: 2.17
Architectures: amd64 · arm64 · armhf
Protocols: 7

tedge-dot-rsRust

For the features only the Rust build has: SNMPv3 with SHA-2, CAN FD.

Binary: 12 MB
glibc floor: not pinned
Architectures: amd64 · arm64
Protocols: 6

Not sure which? Ask the package picker →

Quick start

Read a PLC in a minute

No gateway, broker or cloud needed for a first look: start the Modbus simulator and read it with the CLI.

# start the Modbus simulator on 127.0.0.1:5020
$ just sim modbus
# where the demo point lists live in a checkout
$ export TEDGE_DOT_POINT_LIBRARY_PATH=$PWD/demo/points.d
# read every point of every device, once
$ cargo run --manifest-path impl/rust/Cargo.toml -- read -c demo/config/modbus.toml
# or run the connector without a broker: samples as JSON lines
$ cargo run --manifest-path impl/rust/Cargo.toml -- run -c demo/config/modbus.toml --output stdout --duration 10s

Next: your first device in 5 minutes, then into Cumulocity.

Guides

Pick your scenario

Each guide runs end to end against the demo simulators.

Modbus TCP PLC to CumulocityInstall, point a connector at a PLC and watch measurements arrive.

Secured OPC UACertificates, trust and the tedge-dot pki CLI.

CAN bus and CANopen (preview)DBC signals and SDO objects over SocketCAN.

SNMP network devicesPoll, SET, and receive traps and informs.

AVEVA PI Web API (preview)PI points and AF attributes, pushed, with outage backfill.

A fleet of identical devicesOne point library, many instances.

Less data on a metered linkReport by exception, with a heartbeat.

Write to devices from the cloudDevice parameters, value maps and literal parameters.

Small and old gatewaystedge-dot-c: 457 KB, down to glibc 2.17.

Tools

Try it in the browser

Checked in CI against the same schema and test vectors the connectors use.

Config workbenchBuild a connector config, validated as you type, and see what it publishes and which measurements reach Cumulocity.

Package pickertedge-dot-rs or tedge-dot-c? Answer four questions.