Create

Sign in to ReadmeX

or

How we handle your data: Privacy Policy

ReadmeX

Your AI reading companion

What would you like to catch up on?

Pick a briefing, or ask your own question.

Your community and people briefings stay personal to you.

Story

Developer Open-Sources a Hardware-in-the-Loop Workflow for Claude Code

AI summary

A Reddit developer reported using Claude Code across a multi-board hardware project involving PCBs, firmware, wiring, sensors, motors, CAD enclosures and virtual testing. The workflow generates fabrication files after ERC/DRC checks, verifies components against LCSC, and tests firmware against a PC-based virtual twin before physical production. The developer also open-sourced the method and a Claude Code skill for setting it up.

In-depth insight

The release provides a concrete, open-source example of Claude Code being used across an end-to-end hardware engineering workflow, although its capabilities and simulation accuracy remain based on one developer's unverified account.

Spent the last few weeks letting Claude Code do actual high-level hardware work: boards, enclosures, firmware, wiring harnesses, sensors, motors, etc.

Boards are Python scripts that go all the way to fab files, but only if ERC/DRC come back clean and every part checks out live against LCSC. Firmware runs against a virtual twin on the PC before you ever need to spend any dollars on components.

In my own project—a multi-board project with motors, dozens of sensors and a custom enclosure—it ran for weeks across several iterations, including the PCB(s), the mechanical assemblies, the control firmware, tooling, and more—with weight and balance checked on every CAD change.

Since you can make decisions based on a simulation that closely simulates the physics of reality (I would say within one order of magnitude of deviation), it can easily hyper optimize for specific use cases, such as weight, power saving, functionality or precision, all at your direction. You can have it generate hundreds of different variations for a part, run them all (sometimes overnight) to get the data you need, and make the decision based on that. In my personal project I currently have around 800GB of simulation data archived after only a few weeks, but a lot of work to show for it.

Stripped out my project stuff and open sourced the method + a Claude Code skill that sets it up for you. You do not need to keep using the skill, it simply is a good starting point.

https://github.com/Kemerd/claude-hardware-in-the-loop

With this, you can essentially create anything you'd like, test it in a virtual world, then order the parts, CNC what you need to, print what you need to, assemble it, and have it closely resemble the simulation results. Fair warning, this process can use a LOT of tokens.

Make those projects you've wanted to create but haven't had the time real!

submitted by /u/Kemerd [link] [comments]

#Claude Code#Anthropic#LCSC#NVIDIA Isaac Sim#Unreal Engine

Original · 1 min readRead the original
Group chat

No comments yet. Start the conversation.