Show HN: Pyhoff – Connect Python ML Models to Beckhoff/WAGO IO Hardware

Show HN (score: 6)

Found: July 09, 2025

ID: 212

Description

API/SDK

Show HN: Pyhoff – Connect Python ML Models to Beckhoff/WAGO IO Hardware Built this Python package because I wanted to run hardware controlling ML stuff and other control algorithms directly connected to industrial I/O hardware without jumping into annoying PLC toolchains (Windows only, licensing hassle, no editor choice, proprietary version control - you name it). For sure its not for ms‑cycle loops, or uptime critical production stuff, but in applications with relaxed timing it allows for fast iteration on the setup - making prototyping a pleasure. Its easy to use, has no dependencies beside Python, its fully type annotated and MIT licensed. Internal it uses ModBus/TCP for hardware communication, the implementation is exposed, so it co-serves as ModBus/TCP client library.

I'd love to hear your use cases, feature ideas and PLC toolchain stories ;)

Docs: https://nonannet.github.io/pyhoff

More from Show

Show HN: Gore – A Doom Engine Port in Go

Show HN: Gore – A Doom Engine Port in Go Hi HN,I’ve been working on Gore – a port of the classic Doom engine written in pure Go, based on a ccgo C-to-Go translation of Doom Generic. It loads original WAD files, uses a software renderer (no SDL or CGO, or Go dependencies outside the standard library). Still has a bit of unsafe code that I'm trying to get rid of, and various other caveats.In the examples is a terminal-based renderer, which is entertaining, even though it's very hard to play with terminal-style input/output.The goal is a clean, cross-platform, Go-native take on the Doom engine – fun to hack on, easy to read, and portable.Code and instructions are at <a href="https://github.com/AndreRenaud/Gore">https://github.com/AndreRenaud/Gore</a>Would love feedback or thoughts.

Show HN: Doc81 – tech documentation tool designed in AI-native mind

Show HN: Doc81 – tech documentation tool designed in AI-native mind Hello HN!As a EM, I recently asked for a "good" handoff doc to my engineers who're leaving, but without proper structure, the first draft was pretty crappy. Studying and thinking hard about what readers(i.e., me) might want on header level and what would be a good representation in each section, we came up with a good template for handoff doc. The result was fantastic. I think we all can write better with a proper format and template. That is where I came up with this idea, doc81.Have fun, and let me know what you think!

Show HN: MCP-123, a 2-line MCP server/client (Windows-friendly)

Show HN: MCP-123, a 2-line MCP server/client (Windows-friendly) Got tired of every MCP example being overly verbose, or needing Docker or Mac-only scripts, so I threw together MCP-123. Point it at a tools.py, run `server.run_server(...)`, and the client auto-discovers/calls functions with OpenAI. I hope this is useful to you all.

No other tools from this source yet.