Techno-babble of a Techno-dabbler
PCBs – Designing for Hackability
Nice board, but it needs a hack
With a heart full of Geek Pride, I recently unwrapped my first commercially fabricated PCB. As a beginner designer, I missed something in the initial design and realised while I was waiting for the board to arrive. Essentially, the board was obsolete by the time it got to me. The new changes would need to be hacked into place on the board. Oh well, no problem…
As soon as I started making modifications, something felt wrong. It felt like I was trying to hack a closed, commercial circuit. It was almost as though I was reverse engineering my own design, just to make a simple change.
Commercial designs are indifferent to hackers at best and are often deliberately hacker-hostile. This board is a prototype for an open-source design. It should actively encourage modification. It should be designed for hackability.
Don’t hide the design
The PCB fabricator, iTeadStudio, offers solder-mask in a range of funky colours. Ordinary transparent green is also an option. Naturally, I just had to have black solder-mask. It looks non-generic, “edgy”, very Death Star chic. Unfortunately, it also makes it very difficult to see the traces on the board, which is not good when you need to cut a trace.
Open hardware should be made to be understood. Black solder mask literally reduces the transparency of the design.
Test-points are hack-points
Inevitably, I brought out the oscilloscope to examine some of the radio frequency signals on the board. A few sensibly placed test points would have been moderately handy here, but I had none in the layout. It would have been extremely handy if the test points had been plated through-holes, then components could have been added to them instead of being haphazardly soldered to already populated holes and IC pins.
Holes are free, dig?
There are veritable fields of unused space on the board. At least some of that space should have been allocated to a prototyping grid. The fabricator doesn’t charge for holes, so why be parsimonious? More hack-points means more hackability.
Hackabillity is for hackers
Ultimately, this is an open-source design. I don’t expect that anyone will use it, but the design should consider that possibility. It should also consider that the hypothetical user is a hacker and will use the design for something I haven’t thought of. The more hackable the design, the more adaptable it is to unintended applications. We are hackers, we like unintended applications.
I’ll try to design my next board for hackabillity. I owe it to myself and to all the hackers out there.
The board in question is a “Tayloe Detector” for Software Defined Radio using a PC.