Received: by 10.42.211.6 with SMTP id gm6mr2727464icb.18.1352440200232;
        Thu, 08 Nov 2012 21:50:00 -0800 (PST)
X-BeenThere: omaha-maker-group@googlegroups.com
Received: by 10.42.91.75 with SMTP id o11ls8522487icm.2.gmail; Thu, 08 Nov
 2012 21:49:59 -0800 (PST)
Received: by 10.42.162.74 with SMTP id w10mr5818686icx.15.1352440199553;
        Thu, 08 Nov 2012 21:49:59 -0800 (PST)
Received: by 10.42.162.74 with SMTP id w10mr5818685icx.15.1352440199541;
        Thu, 08 Nov 2012 21:49:59 -0800 (PST)
Return-Path: <nmschu...@gmail.com>
Received: from mail-ob0-f181.google.com (mail-ob0-f181.google.com [209.85.214.181])
        by gmr-mx.google.com with ESMTPS id ul6si73946igb.2.2012.11.08.21.49.59
        (version=TLSv1/SSLv3 cipher=OTHER);
        Thu, 08 Nov 2012 21:49:59 -0800 (PST)
Received-SPF: pass (google.com: domain of nmschu...@gmail.com designates 209.85.214.181 as permitted sender) client-ip=209.85.214.181;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of nmschu...@gmail.com designates 209.85.214.181 as permitted sender) smtp.mail=nmschu...@gmail.com; dkim=pass header...@gmail.com
Received: by mail-ob0-f181.google.com with SMTP id ta14so1276232obb.12
        for <omaha-maker-group@googlegroups.com>; Thu, 08 Nov 2012 21:49:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=message-id:subject:from:to:date:content-type:x-mailer:mime-version
         :content-transfer-encoding;
        bh=4Wlm0X1jyUuRPoF5m0kNA6MfRuKQ2bfonow3zUemSSA=;
        b=bT0W5qEXoUD1FBvAvfIuLUjaonbBgdngmRn4YPGdmubgjk9CBiOGQAh3JDYj0Y1Lge
         ETeKzogfggmOpzt3o/w+22NAtfOABjaGpjaSevtaJlTM0BFgcfQdz8il1mgWSW0NqAIL
         fzdjaTj1xLmf9+fMktK7zUWU9kWvJ7tc/fJc7SaC/Uk95uAKAU4LbZCnbkPXXu06wVRj
         1HwhtoW3r1u8MfWsFBu2QByaNHS5mlopvSOzyNFxJDNaq1btDnSGGAAyUT9uOmvzJns8
         xAWl8rEhorr3HeiuWkKS0etJbmpy6krjojYuKE9JrIRSAt/Yqv/2LqZb3waU7VwB9Iwi
         5K5A==
Received: by 10.60.7.41 with SMTP id g9mr6844852oea.18.1352440199240;
        Thu, 08 Nov 2012 21:49:59 -0800 (PST)
Return-Path: <nmschu...@gmail.com>
Received: from [192.168.1.10] (ip24-252-59-38.om.om.cox.net. [24.252.59.38])
        by mx.google.com with ESMTPS id k9sm22620506oeg.6.2012.11.08.21.49.58
        (version=SSLv3 cipher=OTHER);
        Thu, 08 Nov 2012 21:49:58 -0800 (PST)
Message-ID: <1352440197.29122.4.ca...@desmas-d.desmas>
Subject: Media blaster?
From: Nathan Schulte <nmschu...@gmail.com>
To: "omaha-maker-group@googlegroups.com" <omaha-maker-group@googlegroups.com>
Date: Thu, 08 Nov 2012 23:49:57 -0600
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.4.4-1
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

So, those of you that were at the space Monday evening may have noticed
one of the projects I'm working on.  For those that didn't, I'm doing
some automotive work on my car; specifically, doing some work on the
intake of my engine (a Honda 2.2L F22A1, if anyone is interested).

Anyway, a lot of the aluminum is pretty dirty with oil, carbon, dirt and
grime.  I've cleaned it up with some industrial degreaser, but that
doesn't do well enough.  I purchased some etching mag wheel cleaner
(acid based aluminum wheel cleaner) and preliminary results suggest it
might not work so well either (or it might just take a few repetitions,
we'll see).

That all got me thinking, how difficult is a DIY media blaster?  It
turns out, there's an ultra-cheap, environmentally friendly, DIY media
blaster solution using baking sodas.  Here's some visuals for reference:
http://www.youtube.com/watch?v=3UEGXwLUH24
http://www.youtube.com/watch?v=Fd8yqFJkn6A

I think I'm going to whip this up if there's nothing already available
at the space.  What does everyone think?

Also, I'm now a basic member with recurring monthly payments.  Yay!

--
Nate