<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Repair on IamMrCupp</title><link>https://mrcupp.com/tags/repair/</link><description>Recent content in Repair on IamMrCupp</description><generator>Hugo</generator><language>en</language><managingEditor>mrcupp@mrcupp.com (Aaron Cupp)</managingEditor><webMaster>mrcupp@mrcupp.com (Aaron Cupp)</webMaster><lastBuildDate>Mon, 10 Aug 2026 23:24:10 -0700</lastBuildDate><atom:link href="https://mrcupp.com/tags/repair/index.xml" rel="self" type="application/rss+xml"/><item><title>benchhud: Watching a Board Cook</title><link>https://mrcupp.com/post/2026-08-10-benchhud/</link><pubDate>Mon, 10 Aug 2026 21:00:00 -0700</pubDate><author>mrcupp@mrcupp.com (Aaron Cupp)</author><guid>https://mrcupp.com/post/2026-08-10-benchhud/</guid><description>&lt;h1 id="the-two-second-look-away"&gt;The two-second look away&lt;/h1&gt;
&lt;p&gt;Here&amp;rsquo;s the workflow I was trying to kill.&lt;/p&gt;
&lt;p&gt;Board&amp;rsquo;s drawing current it shouldn&amp;rsquo;t. You want to know which component is getting hot, so
you pick up the thermal camera, point it at the board, look at &lt;em&gt;its&lt;/em&gt; screen, find the bright
spot, then look back at the microscope and try to work out which part that was. Two
displays, two coordinate systems, and a mental transform between them that you redo every
single time.&lt;/p&gt;</description></item><item><title>Three Services, One Privacy Boundary</title><link>https://mrcupp.com/post/2026-08-10-bench-stack-privacy-boundary/</link><pubDate>Mon, 10 Aug 2026 20:00:00 -0700</pubDate><author>mrcupp@mrcupp.com (Aaron Cupp)</author><guid>https://mrcupp.com/post/2026-08-10-bench-stack-privacy-boundary/</guid><description>&lt;h1 id="when-a-feature-decides-your-architecture"&gt;When a feature decides your architecture&lt;/h1&gt;
&lt;p&gt;The bench runs three pieces of software I wrote:
&lt;a href="https://mrcupp.com/page/benchhud/"&gt;benchhud&lt;/a&gt; on the bench itself,
&lt;a href="https://mrcupp.com/page/bench-parts/"&gt;bench-parts&lt;/a&gt; holding inventory, and
&lt;a href="https://mrcupp.com/page/benchhud-intake/"&gt;benchhud-intake&lt;/a&gt; taking work in.&lt;/p&gt;
&lt;p&gt;Three services for a one-person repair bench sounds like someone enjoying microservices a
bit too much. It isn&amp;rsquo;t — or at least, it isn&amp;rsquo;t only that. &lt;strong&gt;The split is a privacy boundary,
and one feature drew the line.&lt;/strong&gt;&lt;/p&gt;
&lt;h2 id="the-feature"&gt;The feature&lt;/h2&gt;
&lt;p&gt;benchhud composites everything on the bench into one window and pushes that composite out as
a virtual camera, so OBS can pick it up and I can stream a repair.&lt;/p&gt;</description></item><item><title>The Bench Is Open</title><link>https://mrcupp.com/post/2026-08-09-board-repair-open/</link><pubDate>Sun, 09 Aug 2026 01:15:00 -0700</pubDate><author>mrcupp@mrcupp.com (Aaron Cupp)</author><guid>https://mrcupp.com/post/2026-08-09-board-repair-open/</guid><description>&lt;h1 id="taking-work"&gt;Taking work&lt;/h1&gt;
&lt;p&gt;Short version: I do board-level repair, and I&amp;rsquo;m taking work.
&lt;a href="https://mrcupp.com/page/electronics-repair/"&gt;Here&amp;rsquo;s the page&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Longer version below, because I think the &lt;em&gt;why&lt;/em&gt; matters more than the pitch.&lt;/p&gt;
&lt;h2 id="most-repair-isnt-repair"&gt;Most repair isn&amp;rsquo;t repair&lt;/h2&gt;
&lt;p&gt;Take a laptop somewhere with a dead port and you&amp;rsquo;ll usually get a quote for a logic board.
Not a component — the board. The diagnosis stops at &amp;ldquo;which module do we swap,&amp;rdquo; because that&amp;rsquo;s
the model the industry is built around: replacement at the largest convenient unit, billed
accordingly.&lt;/p&gt;</description></item><item><title>The Button That Did Nothing</title><link>https://mrcupp.com/post/2026-07-29-openboardview-macos-pdf-bridge/</link><pubDate>Wed, 29 Jul 2026 18:00:00 -0700</pubDate><author>mrcupp@mrcupp.com (Aaron Cupp)</author><guid>https://mrcupp.com/post/2026-07-29-openboardview-macos-pdf-bridge/</guid><description>&lt;h1 id="a-silence-worth-chasing"&gt;A silence worth chasing&lt;/h1&gt;
&lt;p&gt;When you&amp;rsquo;re tracing a fault on a board, the two things you want side by side are the board
and its schematic. &lt;a href="https://github.com/OpenBoardView/OpenBoardView"&gt;OpenBoardView&lt;/a&gt; does the
first half — open a &lt;code&gt;.brd&lt;/code&gt; file, tap a part, see its pins and nets and neighbours. It&amp;rsquo;s the
free replacement for the old Test_Link and Landrex tools, and it lives open next to my
microscope.&lt;/p&gt;
&lt;p&gt;Its best trick is cross-probing: click a designator on the board and the schematic PDF jumps
to that part. Click a part in the schematic and it lights up on the board. Once you&amp;rsquo;ve
worked that way, going back to scrolling a PDF by hand feels like doing arithmetic on paper.&lt;/p&gt;</description></item></channel></rss>