Guy builds AI driven hardware hacker arm from duct tape, old cam and CNC machine (github.com)
224 points by scaredpelican 33 days ago | 46 comments



Animats 33 days ago | flag as AI [–]

Interesting. Not clear what it really does. The hardware is an oscilloscope probe on a 3-axis CNC mechanism. That's called a "flying probe", and you can buy one.[1]

Fine. But what does the AI do? It "ingests the project", but what does that mean? Finding all the pins? That's a start. Using a SPICE model to figure out what should be on each pin, and checking? Now that would be impressive. Probably something in between.

The usual use for this sort of thing is that you probe a known-good board to find out what voltages and signals appear where, and then compare with newly manufactured boards. That's a common production check.

There's potential here. If the AI has some concept of what the board under test is doing, and can diagnose problems, that's quite useful.

[1] https://huntron.com/products/access2.htm

xyzzy123 33 days ago | flag as AI [–]

I think the novel idea here is you jam some hardware together (whatever you like) that can do "physical real world" things with a well understood interface and then spin up Claude with access to it.

The way I'm thinking about it is, it's a _workflow_ innovation?

So you ask for data sheets for all the visible chips and get PDFs in an output directory with minimal user interaction except to flip the board, ask for a basic idea of connectivity, get a stitched high res surface image etc.... which of course are all currently possible, but you can do them potentially with very low effort. There doesn't have to be a _software stack_ ahead of time. You ask Claude to do the thing, it will figure out how to do it, write some code, pull in some OSS and make the thing happen. You can take this project's software or leave it.

You might say "tell me where you think the JTAG headers are" and it will come up with a workflow to do its best at that task (most likely with variable results...), but nonetheless this is not a thing you can ask of any commercial product I am aware of today. With probes, stuff can get interesting.

Of course experienced hardware & reverse engineers already can do all this stuff and have a plethora of workflows for it but I still think it's an interesting POC of a generalisable approach. You can take or leave this particular software stack. Also, the hardware barely matters, you can duct tape whatever to whatever.

_flux 33 days ago | flag as AI [–]

What does it do with a single probe, though? You need two to actually probe anything, right?

So I'm wondering how is the second probe problem dealth with. I've considered something similar but with small weight attached to a pogo pin, so the CNC arm could then just move it around, which would not be very easy to get completely reliable as there may be components on the board.

apimade 33 days ago | flag as AI [–]

From my understanding is you’d probe the board during different operations, process the results and deduct what signals are useful and traffic transmitting across the board (I.E private keys, what protocols are used, debug interfaces, firmware components, chip functions, etc).
numpad0 33 days ago | flag as AI [–]

feels like the author is hallucinating an instant solution to a problem with scope size of "research team and five years" class
lanceski 33 days ago | flag as AI [–]

"Ingests the project" — does that mean it has schematics, or is it reverse-engineering from scratch? If you already have a netlist, the AI is basically scripting probe placement. The interesting case is the undocumented board, and I haven't seen evidence that's what's actually being attempted here.

I believe the standard production check is more like you check continuity between known nets, given that you're the manufacturer, you already know where they are exposed, and therefore you can perform those checks before adding any components. Post component checks are a lot more complicated because active components and passive components will modify the visible voltages and characteristics, often to the point where you won't have the same degree of physical insight.

I would assume once machines are set up that this is only really done if you're not confident of your manufacturing line for some reason (eg. maintenance, reconfiguration) or you are pushing limits somewhere, for example, particularly small vias or traces very close to the edge of the board.

To make this useful, you would want two flying probes because otherwise it's not going to be telling you much you don't already know.

anvil 33 days ago | flag as AI [–]

The interesting case is the populated board with no documentation. If you're reverse-engineering something - no netlist, no Gerbers - you need to infer topology from live measurements. That's where autonomous probing with some AI layer makes sense, even if this project undersells it.
Animats 33 days ago | flag as AI [–]

That's a blank board test. This is straightforward given the netlist and Gerber files.[1] It's just a continuity check between known points. Does not require AI.

[1] https://bayareacircuits.com/bare-printed-circuit-board-elect...


It’s hard to imagine anyone wanting this to be real more than I do, but this is nowhere close to being ready to do actual work. Photographing real PCBs is hard, there is no fiducial maths, no actual probing is being done. It's just photos of a photo being piped into an agent. If it actually did what it claims, no reasonable person would exclude it from the demo video.

https://gainsec.com/2026/04/16/autoprober/


Could an agent no develop a bespoke correction algorithm for the photos of the photo?
hhayes 33 days ago | flag as AI [–]

Sure, but now you're stacking one imprecise system on top of another. We tried something similar — adding correction layers to compensate for bad inputs — and the errors compound fast. Better to fix the upstream problem than patch around it with more ML.

Why feed it photos of a photo when you could just feed it the photo that was printed out?
Havoc 33 days ago | flag as AI [–]

Can't say I fully understand it but this certainly smells like someone is getting hired off a single github repo as CV

not a bad strategy. one repo that shows you can duct tape commodity hardware together and let an agent handle the workflow beats 50 leetcode solutions on your profile.

the interesting part is the cost ratio. commercial flying probe setups run 5 figures with proprietary software. this is a weekend build that gets you most of the way there for under 500 bucks.

ghurtado 33 days ago | flag as AI [–]

Nowadays the former seems to be a requirement for the latter, so I'm inclined to agree with you

> someone is getting hired off a single github repo as CV

Isn't that a good thing?

kuizu 33 days ago | flag as AI [–]

A similar concept, but with multiple probes at the same time, was published in this blog series as open source hard- and software: https://www.schutzwerk.com/en/blog/proboter-01/ They explain some of the use cases in this demo video https://youtu.be/TYEjZA-xbGo?is=osWXCrBkLOi4JHxO
odie5533 33 days ago | flag as AI [–]

Guy builds car from stick of gum, paperclip, and an old vehicle
jre61 33 days ago | flag as AI [–]

Technically the title says "CNC machine" which isn't really "duct tape and gum" level scrappy -- that's actual precision equipment. Though I get the joke, the spirit is right that the AI integration is the impressive part, not the hardware sourcing.


It's both cool and a bit confusing. Is this an attempt to commoditize flying-probe testing for PCBs? An attempt to use LLMs to reverse-engineer circuits? Both?

It almost feels like it would benefit from being split into two projects. If I'm testing my own PCBs, I probably don't want an agent in charge, at least not routinely. There's just no reason for the added cost, complexity, or non-determinism. And if I'm reversing someone else's design, then going through the effort of building an auto-prober seems like an overkill, especially since a single probe is seldom enough. Even the simplest serial interface will often have one line for clock and another for data, so you're gonna be manually making connections either way.

claytonia 33 days ago | flag as AI [–]

Cool demo, but letting an AI Agent drive a physical probe may have problems. AI is probabilistic, but hardware is precise. If the model miscalculates a pin's position by even 0.1mm, the probe may crush the board. I am curious how the author actually bridges the gap between the Agent’s 'guess' and the sub-millimeter precision needed to avoid damaging hardware?
par1970 33 days ago | flag as AI [–]

I think this is roughly solved. Tell the agent to do all of its calculations in python.
delfinom 32 days ago | flag as AI [–]

...OR if you are developing a PCB, you have the design data, and pick and place data and the gerber data.

Any combination of such gives you positions of everything within micrometers.

This is not a new problem. Testing of PCBs has been solved a billion times over and the world has had bed of nails tester and flying probe testers for 4 decades old.

We have a 8 finger flying probe machine at our facility that literally all we do is load the board in, load in the design data. It identifies points of interests, learns the fiducials and we let it do a characterization run. We then have engineering review of the resulting data and just let it fly afterwards.

None of this requires AI.

But nowadays any linear regression qualifies as AI so imma go slap a label on it.

jstanley 33 days ago | flag as AI [–]

A spring-loaded probe would seem sufficient.
Jamesbeam 33 days ago | flag as AI [–]

Finally i don’t need to press any buttons on my bionic arm any longer, the AI can find the pin on its own.

What a glorious time to be alive.

Claude really is going to bring pleasure to the people.

https://www.youtube.com/watch?v=YgtO5sebA9U


I watched the linked in video:

https://videos.files.wordpress.com/gD3kAWlO/autoprober-demo....

But I am not sure what do I see there? Is that some 3D printing?

esbranson 33 days ago | flag as AI [–]

> digitally guided fabrication

> New York[1]

[1] https://www.governor.ny.gov/news/keeping-new-yorkers-safe-go...

gbgarbeb 33 days ago | flag as AI [–]

Kathy Hochul is cracking down on illegal flying probe machines.
lrvick 33 days ago | flag as AI [–]

This looks super useful, but I wish authors could stop doing these silly "source available" plays.

Instead of donating to a project one has to buy GPU time to convert it to FOSS.

nullc 33 days ago | flag as AI [–]

Maybe put the probe on a spring loaded linear sensor, and move down until it hits a target offset (could just be read by a simple flag in an optical sensor)-- resulting in hitting a constant target force.
zombot 32 days ago | flag as AI [–]

GitHub, that crappy POS, is down again.

> Cannot retrieve latest commit at this time.

Or is it GitHub Security, stopping us from cloning this dangerous repo?

vatsachak 33 days ago | flag as AI [–]

Same guy who made the Flock hacking tool

Would be cool if you could use this (with 2 probes) to build a wiring net for reverse engineering.

why not just take a photo with your phone and upload that to the llm

I figured this was some kind of home-grown prosthetic arm whose wearer could, using AI, draw any artwork online, speak ASL, perform minor surgery on themselves and so much more so long as their supply of tokens lasted.

Perhaps a smidge disappointed when I had a look and discovered it wasn't that :)

sanieldoe 33 days ago | flag as AI [–]

This is amazing! Limitation breeds creativity indeed
burgerone 33 days ago | flag as AI [–]

Annoyingly misleading title unfortunately.

Wow that's nuts. What a great idea! I wonder how much of this the commercial flying probe machines can do already. Pretty cool to be able to have this on a home scale.

How does this only have a single star.

This is genuinely mind blowing.

noel771 32 days ago | flag as AI [–]

The gap between "proof of concept" and "production-ready flying probe" is substantial. Automated probing still needs reliable fiducial registration and impedance-aware contact force — problems that commercial vendors spent years solving. As far as I can tell, this is demonstrating intent more than capability.