Slashdot Mirror
Hardware Hacking Projects for Geeks
Fullam takes the reader from the very basics of hardware hacking and quickly gets up to speed with some fun and interesting hacks. Projects start out easy and increase in complexity and cost as the book progresses. Hardware Hacking covers many popular hacks we've all seen before, such as the "Macquarium" (Mac Aquarium), a web-enabled coffee machine, and the Blinkenlights building-sized display.
The book is divided into two main parts, the first covering basic hacks, and the second covering more advanced hacks.
Part One:
Starting with the basics, Fullam takes the reader through a crash course in electronics, covering concepts like soldering, using a voltmeter, identifying various electronic components and reading schematics. This section of the book is by no means a replacement for a course in electrical engineering, but it is definitely a solid primer for those of us who weren't born with a soldering iron in our hands. If you've never played with electronics before and don't know the difference between a resistor and a capacitor, this section should get you up to speed fairly quickly.
After the brief basics lesson, the next chapter dives right in to the first project, which is a portable laptop power supply made with a pile of D-cell batteries, a battery holder and some wire. This project is very simple and requires no soldering at all, yet it gives the reader a quick and easy way to make something useful with very little investment in time or money.
Each of the projects is presented in a well-organized manner, starting out with a brief summary and some background information about where the hack originated. A list of necessary tools and materials is also given, followed by a project overview, outlining the major tasks required to get the project completed. Each project outline gives estimates for the cost range, time required and difficulty level for the hack.
After the introductory stuff is out of the way, step-by-step instructions are given on how to assemble, modify or hack the device in question. The instructions are easy to follow and are complete with images or illustrations where appropriate. Many pages contain sidebars that contain additional information related to the project, such as more photos, hints and tips, and links to relevant websites. These sidebars really help to fill in any gaps that may be present in the main text.
At the end of each chapter, Fullam has an "extensions" section, where he suggests ways the hacks can be hacked further, to improve upon the design or alter them to offer more or different functionality. This is one point where the book really shines, advocating the true spirit of hacking and encouraging creativity and experimentation whenever possible throughout the book.
At the end of each chapter is a "Bill of Materials" and schematics for the hack. The bill of materials outlines in great detail all tools and hardware required for the project, including approximate costs as well as sources where they can be purchased.
Some of the highlights in the first section of the book include the "Macquarium," a water-based PC cooling system, and the infamous Furby hack. The Macintosh mod teaches some valuable lessons on using a Dremel tool and working with Plexiglas, which are great skills any budding case modder would want to have. The water-based PC cooling project is one of the more useful hacks presented in the book, showing the reader how to create an inexpensive but effective means to cool down an overclocked CPU. And hacking the Furby to give it a new vocabulary is... well, definitely a great topic for conversation if nothing else. If you have to ask why someone would do such a thing, you wouldn't understand the answer.
Part Two:
Part Two of the book starts off with another more advanced lesson in electronics. It delves into more detail, describing different types of resistors, capacitors and connectors. It also introduces transistors, looking at integrated circuits and surface-mount components as well. One thing I found particularly useful was the section explaining how to read and interpret manufacturers' data sheets for integrated circuits.
The advanced hacks featured in Part Two of Hardware Hacking are a little more exciting than those featured in the first half of the book, but are definitely more involved. The section starts off with a chapter on building a PC-based PVR, using Mandrake Linux. Sample code is included to create shell scripts for a simple, text-based interface, although Fullam does briefly mention some of the more popular GUI-based PVR software available, such as Freevo and MythTV.
Another great hack featured in the advanced section is the "Building-Size Display" hack, reminiscent of Blinkenlights. The chapter starts off with instructions on how to build a display matrix on a much smaller scale, using a series of ultra bright LEDs, but later shows how the project can be expanded to create a 12-story display using an entire building.
Some other mentionable hacks in the advanced chapters include a cubicle intrusion-detection system, an Internet-enabled toaster and coffee maker, and a remote object tracker. These projects provide instructions on how to use more advanced components such as photodiodes, lasers, GPS receivers and microcontrollers (such as the BasicStamp2, in particular).
Two other noteworthy projects in Part Two include a MAME cabinet and a wearable computer.
Plans for the MAME cabinet are very well done, taking the reader through cutting MDF, building the cabinet, installing the software and interfacing the controls to his PC. This chapter goes into great detail, even covering things like creating a monitor bezel and a backlit marquee, and using T-molding for that authentic arcade machine look.
The wearable computer hack is very interesting, covering a wide range of concepts I would never have considered. Fullam gives ideas on what to use for a head-mounted display (HMD), what types of motherboards and CPUs work best, and looks at various power sources, including batteries, solar panels and different generators. The chapter also presents ideas for input devices, such as keyboards and mice, but also speech recognition systems, cameras and GPS receivers. At the end of the chapter, there is an extensive list of websites related to wearable computer projects, offering much more reading to the interested hacker.
The appendixes, while quite brief, do offer more information on topics like creating and editing schematics, using microcontrollers and using different power sources. There is also a list of resources for further reading and a short list of parts suppliers.
Hardware Hacking also has an accompanying website, where readers can download all of the images, illustrations and schematics from the book. The files are available in EPS, PDF and TIFF formats, although they are all gzipped, and are not readily viewable without downloading and extracting first. The website supposedly has code downloads as well, but the links are broken as of this writing, so you'll be stuck typing in code from the book until the site is fixed.
Overall Thoughts
Overall, I was very impressed with this book. Fullam has given the geek community a valuable resource that will provide inspiration for aspiring and veteran hackers alike. It covers many projects that I have personally wanted to build or learn more about, and presents concepts that would be of interest to many fellow Slashdotters.
The only things preventing me from giving this book a 10 are the aforementioned issues with the accompanying website (which I'm sure will be fixed soon) and the quality of some of the photos. Most of the photographs in the book are crisp and clear, but some are rather grainy or pixelated, as if they were enlarged from a website image. Fullam does make mention of the image quality, stating that many photos actually were taken from the original Web sources, and "the clarity of the photograph suffers in print." It's a small point, but definitely noticeable in certain sections of the book. However, as mentioned, the images are available online, and often do look better on a monitor in full color, as opposed to the black and white images in the book.
I highly recommend Hardware Hacking Projects for Geeks to anyone with an interest in those fun projects that only nerds can understand.
You can purchase Hardware Hacking Projects for Geeks from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.
Turning my CDR into a toaster?
...was never designed to spark and fill the room with flames and magic smoke. The local fire company has asked that I refrain from future hacking efforts.
all you needed to start hacking was curiosity and desire?
It's funny how even the art of hacking has been commoditized these days.
My own advice, just do it.
-- You see, there would be these conclusions that you could jump to
I want a books that includes all the components to hack.Z ZZZZZZ.jpg">How to Play Air Guitar (it includes a free genuine air guitar) ;)
like this book: http://images.amazon.com/images/P/1844110036.01.L
Consensus is good, but informed dictatorship is better
Yeah, my thoughts exactly.
I consider myself a hacker. I make stuff. But I don't need a book to give me instructions. I do read a lot. Books on engineering, electronics, chemistry, biology, well, anything really. And I use all these bits of knowledge to make things by applying the knowledge to solve a problem.
Having a book that contains step by step hacks seems like reading a cookbook to become a chef. It just doesn't work that way.
Why not? Isn't hacking just making something do it wasn't designed to to, or improving the way it does what it was designed to do?
Back when, my Commodore 1541 disk drive (1st gen with the built in PSU) would overheat all the time. They all would, it was a design flaw. One day I jammed unsharpened pencils into the screw holes, putting it on stilts. Never had any overheating problems, plenty of airflow.
That was a simple hack, and the fact that I told my friends what I did, and they all did the exact same thing doesnt diminish it. Hell, I'm sure millions of other folks came up with the same, or similar idea.
I don't need no instructions to know how to rock!!!!
how about turning my mac into a pc??? or has that already been done.
serenity now!
If you want to complain about dupes, what about that "Have you Meta Moderated lately?" article that always seems to be on the main page?
...
If a book gives step by step instructions on the 'hack', can it really be considered a hack anymore?
Don't forget that the free exchange of ideas is integral to the hacker ethic. This makes for inspiration for other hacks.
Where does the school board find them and why do they keep sending them to ME?
I'm going to go ahead and point out my UPS modding thread from yesterday, complete now with additional instructions, a few pictures, and a hand-drawn diagram of how to do an APC SmartUPS.
4 299.
/. journal, and mabey make a decent little webpage with instructions and pics and stuff. Mabey I'll submit it to /..
http://slashdot.org/comments.pl?sid=98025&cid=837
Pictures here:
elvis.netmar.com/~will/ups/
I'm going to write this up more formally, and at least put it in my
Anyway, this is a great geek hardware hacking project. If you have any questions on how to do it, let me know. I always read replies.
~Will
sig?
One of the simplest and coolest hardware hacks of all time is hooking up a carbon microphone (like old-style telephone handsets had), a miniature speaker, and a 9 volt battery. point the speaker at the carbon mike and move it closer, voila! Instant oscillator. Probably the world's simplest electrical oscillator. And it shows how remarkably powerful an amplifier the carbon microphone is. (I believe the carbon microphone was invented by Thomas Edison.)
-- SKYKING, SKYKING, DO NOT ANSWER.
Make a Tattoo Gun
,second one from the smallest. ( this is your needle)
Things you'll need:
* bic pen (this is your tube that houses the needle)
* 4 or 5" section of guitar string
* tooth brush ( this gets bent like a "7" and joins the pen to the motor)
* an eraser from a pencil (this joins the shaft of the motor to the needle/guitar string)
* small battery operated motor (from a "walkman" or a hand held fan)
* some tape (to join everything together)
Putting the pieces together:
1. Take the guitar string and bend a little bit of the end down or up.
2. Take out the ink tube of the pen, and cut it to about a 3 or 4" length, now file down the brass tip of the pen to get the ball out, make the hole big enough to allow passage of the needle.
3. Insert the needle into the pen.
4. Now take the tooth brush and cut off the bristles making it about 4" long. Heat it up in the middle with a lighter and bend it in to a "7" and hold in place untill stiff.
5. Join/tape the pen needle assembly to the tooth brush.
6. Now take the eraser from the pencil and shove it onto the shaft of the motor, try to get it as dead center as possible. Join the pen/needle/tooth brush to the motor/eraser assembly, tape the brush to the motor.
7. Take the bent part of the needle/guitar stirng and stick it into the eraser, IMPORTANT- the needle must be purposely OFF CENTER.
8. Now all that is left to do is find a power source, I used the plug-in adapter frrom a cd player. i guess you could hook up some batteries to a switch and then to the contacts of the motor.
Just try to explain that to the TSA people at the airport when you try to haul your "laptop battery" through security.
"No Officer, this pile of batteries with wires sticking out everywhere is just a spare battery for my laptop...wait - what are you doing with those handcuffs - heeeelp".
Have to start somewhere.
"they help build stupid peoples' egos..."A very elitist statement that clearly shows the size of your ego...
"Who are in control, they are not in control of anything - they don't even control themselves!" - Glen Beck
Listen, I hate those so-called "software developers" just as much as you do. And for a long time, I've been trying to figure out where this kind of bitterness-driven reasoning ends. I mean, even most software developers don't really understand the science behind what they're doing. As far as I can tell, after thinking about this for 6 years: as long as the "P/NP" problem is undecided, no one can honestly say that they understand computers.
The problems are, for lack of a better word, attitude based. Hubris is all the more obvious when accompanied by ignorance (n.b. I didn't say stupidity). I am a pretty good programmer and am conversant in formal mathematics, though the idea of "software development" (in as many words) is abhorrent to me. So yeah, you're irked by people doing trivial "hacks" and bragging about it. I have similar irritations.
But these irritations are illusory. Get over it; I am.
But back to the point, Mr. (2, Troll) (*), I am considering getting this book as a simple introduction to some stuff which I was not fortunate enough to learn at such a young age, as to mistake it for "innate ability" or a symptom of some "superior intelligence"... I suspect many other people here are doing it for the same reason. Honestly, do you think Archimedes (or, for that matter, Enrico Fermi or even Einstein) would know how to do these "true hacks" without some education and/or training?
(*): I see you've now been upmodded to (4, insightful). Oy vey.
"for those of us who weren't born with a soldering iron in our hands."
Um.. Ouch? The poor mother..
I'm not really a "geek," nor do I play one on TV. But after looking through a book like this, I might just be motivated to try and become one. This book is one that appeals to the "mad scientist" in all of us, the one that is always looking for ways to build the better mouse trap or the perfect home "do it all device." While some of us less "handy types" would be better off not coming anywhere near this book, there are enough projects listed here that even someone with little or no hardware experience would find at least a handful of projects doable. Projects like the "Macintosh aquarium" or the laptop PC power supply. In fact the book is divided into Basic and Advanced Hacks and techniques, so if you've started off with a couple of the basic projects finished, you can move on to more advanced ones. Very cool.
And for each project, there is a graph for project cost, time and difficulty on the beginning page. For some projects, there's a list of what items you will need. There are also extensive step by step instructions for each "project," along with drawings, photos and diagrams. You'll love this book if you're one of those people who loves taking apart products and trying to "improve" upon their original design.
On the other hand, if you want to become a chef, you are definitely going to read quite a few cookbooks. It's only by mastering the basics that you'll become an expert.
The review says that the book contains "all you need to know to get started in the wonderful world of hardware hacking". By following the instructions and having a clear explanation of the rationale behind them, one would quickly gain enough knowledge and understanding to become a hacker in the sense you describe.
Perhaps the title should have been "for Wannabee Geeks" instead. :-)
Using HTML in email is like putting sound effects on your phone calls. Just say <strong>no</strong>.
Having a book that contains step by step hacks seems like reading a cookbook to become a chef. It just doesn't work that way.
No, I agree, it doesn't work that way. But it can start that way. Your cooking analogy is particularly apt. I started out just following recpies by rote. As I did it, I got confidence that I was indeed capable of cooking yummy things without destroying the kitchen. Then I started playing with recipes to see how things would change if I altered the script. Now I'm reasonably good at making up good dishes on the fly, without recipe, based just on what I have or what I can get that's fresh. Following someone else's directions isn't really hacking; but it can be a good place to start developing an interest in so doing.
Absolutely. And I want to comment on this line:
:-)
Perhaps the title should have been "for Wannabee Geeks" instead.
The truth is that every geek is a "Wannabee Geek" in some sense. By friend is great at electronics and cars but knows nothing about computer programming. Whereas there are alot of projects that I would like to do, but know too little about (analog)electronics to do so. Furthermore, I would think that there are alot of people like me since you can learn alot about the software aspects of computers by exploration, but electronics isn't so accessable in the everyday home. This book seems like a great way to learn about the basic of EE and end up with a cool project in the process.
I have hacked up an old phone and connected it to my PCs parallel port. This, in combination with a perl script and a couple other programs, results in a machine that waits for calls with "UNAVAILABLE" or "PRIVATE" Caller ID tags, answers only those calls, plays prerecorded wave files designed to emulate a conversation, uses silence detections to allow the telemarketer to speak and think he's talking to a real human, and records the entire conversation. I have example WAV files of these conversations and a How-to page at http://www.pagerealm.com/tc2k. The example WAVs are VERY entertaining!
Really simple, all I used was a soldering iron, solder, blue LED. You can pick everything up at the local Radio Shack. The Radio Shack I visited had 3000mcd super bright blue LEDs. I eventually bought a 9000mcd super bright blue LEDs but I found out later that it's super bright coz the manufacturers tighten the angle of projection meaning brighter center spot thus higher mcd. 3000mcd still works well. My first concern was whether the LED was brighter than the normal red LEDs since they are on different ends of the wavelength and red is easier to pick up. Didn't really matter if you have a good enough pattern or surface, like a mouse pad made for optical mice.
I modded my blue Logitech Optical Mouse (USD$20 the last time I checked). Removed the regular red LED and replaced with the blue LED. Now my mouse glows blue. Looked kinda weird previously coz the mouse was blue, with semi-transparent blue plastic but glowed red underneath.
Easy modding... takes less than 15 minutes, unless you lose a spring or something.
$5 / month hosted VPS on linux = awesome!
Your assertion applies to 99.9% of non-fiction published in the last five years anyways, but people continue to buy the books. Ever occur to you that the compilation and presentation of all that free material in a coherent informative package is something of worth in and of itself?
In point of fact you do the author a tremendous diservice by trivializing the work in such a fashion. Let me propose a little experiment, you take tomorrow with google, a few hours with LaTex the next day, and none of us will hold our breath waiting for your publishing contract. See the point? You hypothesize that creation of the work is nothing more than collecting stuff off websites amd stuffing it into a pdf. I'm suggesting that would never have been published. First off, most websites give professional editors fits, if you want to make an editor think you're incompetent, then stick wsith the plan you suggest. If you want to thought of as a writer, understand that most of the job is going to be taking that flood of google results and turning it into material fit for the printed page.
But wait, there is more... What about those websites that google turned up? That site that talks about teaching your TiVo to fetch your pipe and slippers for example. Did that site try to present the information clearly and completely, or did the author assume a bunch of knowledge on your part? Were any procedures provided likewise described? While I don't doubt that all the info is available, is it all consumable?
Like the other reply to this, I also have to ask if it is as trivial as you pretend, where is your Hacker's cookbook? And I'm guessing your Pullitzer prize is in the mail? I for one recognize that it isn;t that simple, and I have neither the time nor the temprament to undertake such an activity. Will I buy his book? No. Like you I will go to google and undertake essentially the same process you would, or the author did. However, I don't disparage the process, or that the author has obviated it for those willing to pay for the privilege. I personally feel that the process is part of the experience, and often the source of new ideas to explore. However, that in no way imparts any license to disparage the author's work, or to trivialize the process by which it was created, since it is essentially a macrocosm of the process each of us would apply to that same material. The difference being that when you or I do it, we do it for an audience of one, an audience, I hasten to add, we are intimately familiar with. The author undergoes that process for an audience of far larger than one, and without the benefit of familiarity.
Now re-read your first post, is this a skill you think you really have? Is that how you preent information effectively? Hell, and your audience was just /. members, a group you have some familiarity with....
To update an aphorism:
Those who can, do. Those who can't criticize the former on /.
"Talk minus action equals nothing" - Joey Shithead, D.O.A.
"Talk minus action equals