<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>OT Fabric blog</title><description>Open-source protocol libraries and tools that break down OT data silos, built by people and AI agents together.</description><link>https://otfabric.io/</link><item><title>IEEE 2030.5 joins OT Fabric: go-ieee20305, ieee20305ctl and four reference stacks</title><link>https://otfabric.io/blog/introducing-ieee-2030-5/</link><guid isPermaLink="true">https://otfabric.io/blog/introducing-ieee-2030-5/</guid><description>IEEE 2030.5 is how utilities and aggregators tell inverters, batteries and chargers what to do, and the protocol California and Australia require for it. go-ieee20305 implements client, device agent and server under MIT, ieee20305ctl puts them on the command line, and ieee20305-interop tests both against four independent implementations.</description><pubDate>Fri, 23 Oct 2026 00:00:00 GMT</pubDate><category>announcement</category><category>ieee-2030-5</category><category>der</category><category>energy</category><category>interop</category></item><item><title>DNP3 joins OT Fabric: go-dnp3, dnp3ctl and four reference stacks</title><link>https://otfabric.io/blog/introducing-dnp3/</link><guid isPermaLink="true">https://otfabric.io/blog/introducing-dnp3/</guid><description>DNP3 is the SCADA protocol of electric, water and oil and gas utilities, and the open-source field around it has thinned out. go-dnp3 implements master and outstation under MIT, dnp3ctl puts it on the command line, and dnp3-interop tests both against four independent implementations.</description><pubDate>Tue, 20 Oct 2026 00:00:00 GMT</pubDate><category>announcement</category><category>dnp3</category><category>scada</category><category>energy</category><category>interop</category></item><item><title>OCPP joins OT Fabric: go-ocpp, ocppctl and five reference stacks</title><link>https://otfabric.io/blog/introducing-ocpp/</link><guid isPermaLink="true">https://otfabric.io/blog/introducing-ocpp/</guid><description>OCPP is the protocol between EV charging stations and the systems that run them. go-ocpp implements 1.6J, 2.0.1 and 2.1 in both roles, ocppctl puts it on the command line, and ocpp-interop tests both against five independent implementations.</description><pubDate>Mon, 19 Oct 2026 00:00:00 GMT</pubDate><category>announcement</category><category>ocpp</category><category>ev-charging</category><category>energy</category><category>interop</category></item><item><title>The industrial protocol stack landscape</title><link>https://otfabric.io/blog/industrial-protocol-stack-landscape/</link><guid isPermaLink="true">https://otfabric.io/blog/industrial-protocol-stack-landscape/</guid><description>Who implements Modbus, OPC UA, BACnet, IEC 104, IEC 61850, Siemens S7, OpenADR, OCPP, DNP3 and IEEE 2030.5? 134 open-source and commercial stacks, verified against their own release channels, and an interactive map to explore them.</description><pubDate>Sun, 18 Oct 2026 00:00:00 GMT</pubDate><category>ecosystem</category><category>research</category><category>open-source</category></item><item><title>LAN Tracker: a memory for your OT network</title><link>https://otfabric.io/blog/introducing-lan-tracker/</link><guid isPermaLink="true">https://otfabric.io/blog/introducing-lan-tracker/</guid><description>Network problems are one of the top causes of OT downtime, and most leave no trace. LAN Tracker keeps an evidence-based history of which device held which IP, what DHCP told it and which ports answered, so you can reconstruct an incident after the fact.</description><pubDate>Sun, 18 Oct 2026 00:00:00 GMT</pubDate><category>announcement</category><category>tools</category><category>networking</category><category>operations</category></item><item><title>Modbus Trace Explorer: packet traces in Modbus terms</title><link>https://otfabric.io/blog/introducing-modbus-trace-explorer/</link><guid isPermaLink="true">https://otfabric.io/blog/introducing-modbus-trace-explorer/</guid><description>Open a tcpdump or Wireshark capture of Modbus/TCP traffic and see latency per device, poll plans, exceptions, registers and connections. Then export what the devices really answered and replay it as a simulated device.</description><pubDate>Sun, 18 Oct 2026 00:00:00 GMT</pubDate><category>announcement</category><category>tools</category><category>modbus</category><category>troubleshooting</category></item><item><title>Introducing OT Fabric</title><link>https://otfabric.io/blog/introducing-ot-fabric/</link><guid isPermaLink="true">https://otfabric.io/blog/introducing-ot-fabric/</guid><description>OT Fabric brings open-source DNA and IT best practices to industrial connectivity, for people and AI agents alike. The OT toolset you always wished you had in your pocket, built by people and AI agents together.</description><pubDate>Mon, 12 Oct 2026 00:00:00 GMT</pubDate><category>announcement</category><category>roadmap</category></item><item><title>Why every protocol gets an interop suite</title><link>https://otfabric.io/blog/why-every-protocol-gets-an-interop-suite/</link><guid isPermaLink="true">https://otfabric.io/blog/why-every-protocol-gets-an-interop-suite/</guid><description>Every OT Fabric protocol is tested against independent implementations. Ten interop suites package 34 reference stacks as containers behind one contract, test them against each other first, and record what they find in our code and in theirs.</description><pubDate>Mon, 12 Oct 2026 00:00:00 GMT</pubDate><category>testing</category><category>interop</category></item></channel></rss>