Bench Node
One Ethernet drop between your code and the bench.
A small, bounded control node for switches, fixtures, serial devices, and the awkward instruments that do not deserve a dedicated computer.
Not for saleA lab endpoint should expose an intentional interface, not a raw network tunnel into arbitrary hardware.
Intended workflow
Bench Node is organized around bounded operations rather than remote access. The intended interaction is a small typed command—select a switch position, pulse a line, query a state—whose electrical behavior remains inside a named adapter.
Why an adapter boundary matters
The node is not intended to make arbitrary GPIO safe by putting it on Ethernet. Each attached device still needs a documented voltage domain, default state, timeout, and recovery path. Those details belong in the adapter contract and eventually in its schematic and validation record.
Current boundary
This dossier describes a design study. Module selection, isolation, connectorization, enclosure, safety behavior, manufacturing files, and physical performance remain open.
- Compute
- ESP32-class MCUCandidate; exact module is not frozen
- Network
- Wired EthernetRequired; PHY and isolation are not selected
- Control
- Bounded GPIO and serial adaptersTarget interface contract
- Authority
- Local API with explicit allowlistsSoftware design boundary
01Interface contractplanned+
This is a named deliverable in the plan; no public file is attached yet.
02Schematics and BOMplanned+
This is a named deliverable in the plan; no public file is attached yet.
03Firmware and host SDKplanned+
This is a named deliverable in the plan; no public file is attached yet.
04Physical validation reportgated+
This artifact requires its named validation and explicit release before a public file or supporting claim appears here.
This register describes the current public claim boundary. “Planned” and “gated” entries are not downloadable deliverables.
Follow the build
Interested before it becomes a product?
Send the workflow you want to solve. Early conversations should shape the useful part of the specification—not manufacture demand for a frozen idea.
Start a conversation