Wattcher part #3 – creating a web database with AppEngine

In this latest installment, watch as the heroine takes Watt-hour averages, learns Google App Engine and creates a webapp custom-designed to store her sensor data. Wow! See data as it trickles in at http://wattcher.appspot.com

Next up: Graphs, diagrams and other pretty pictures!

Filed under: random — by ladyada, posted January 28, 2009 at 5:34 pm


Escape into an escapement

Found on the 3D replicators blog (which is not just a Bruce Sterling fantasy) This video demonstrating a possible 3D-printable stepper using a (hand-wound?) solenoid & escapement ring. Sure, it would be pretty slow…but you can make it at home!

Filed under: random — by ladyada, posted January 27, 2009 at 5:44 pm


tubes, t00bs and TuBez!

I am jealous of Joel Johnson who got to go to Electro-Harmonix in LIC. Watch for tube-joy! I wonder if all the boards are started in China, then shipped to the US for completion, assembly & testing. I love how crazy-messy it is, with scopes on top of old-style generators with random digikey bags everywhere (totally reminds me of my workplace)…thats how you can tell they are doing real engineering!

(Oddly enough, I once lived a couple miles away in Astoria and biked by there all the time on my way to the Queensborough)

Filed under: random — by ladyada, posted at 5:19 pm


Digikey

Digikey is a large $500 million dollar company with thousands of employees. One of them made an official video on how to make throwies (!?) using digikey parts. I like the disclaimer at the end, and the boppin’ background music. I hope they start making & selling kits! :D

Filed under: random — by ladyada, posted at 4:14 pm


Harper’s YBox2 load watching widget

Harper Reed, the CTO of SkinnyCorp (which makes the best tshirts!) has a YBox2. He also has some misbehaving computers. How to solve? EZ! Use your YBox2 kit as a load-monitor hooked up to a handy LCD display, hopefully he’ll post up the php and SPIN code he used to get it working (hint hint!). That will teach you to mess with Harper, web4!

Filed under: random,ybox — by ladyada, posted January 25, 2009 at 11:51 pm


The chemistry of home-etched PCBs

I saw this most-useful post on the synthDIY mailing list, and the author graciously allowed me to post it up…Enjoy!

As it happens, I am a bit of a chemist (or, more precisely, a chemical
engineer by training working in the field of hydrometallurgy, or the aqueous
extraction, separation and purification of metals from ores. (It turns out
I’m not much of an electronicist (yet), but we can’t all be good at
everything!)

Two things: 1) good etchants, and 2) reasonable disposal thereof:

I do hand-etching of pcb’s and I don’t use ferric chloride. The problem
with ferric chloride is that it is not easily reusable. The operative
reactions in a ferric chloride-based etchant are as follows. First, the
ferric will oxidize the copper metal to cupric, while being reduced to
ferrous:

2 Fe(3+) + Cu(0) –> 2 Fe(2+) + Cu(2+)

Next, the cupric will also participate in the oxidation of copper metal,
with both going to cuprous (by a reaction called “proportionation”):

Cu(2+) + Cu(0) –> 2 Cu(+)

Both reactions are just exchanges of electrons between ions.

The problem with ferric chloride is that the ferric ion Fe(3+) is not easily
regenerated from the ferrous ion Fe(2+). Reaction between ferrous and the
oxygen in air is slow:

4 Fe(2+) + O2 + 4 H(+) –> 4 Fe(3+) + 2 H2O

However, reaction between cuprous ion Cu(+) and oxygen is virtually
instantaneous:

4 Cu(+) + O2 + 4 H(+) –> 4 Cu(2+) + 2 H2O

All that is needed is some free acid (presumably hydrochloric acid, HCl, aka
“muriatic” acid, available in any pool supply shop or hardware store) to
combine with the reduced oxygen atoms and form water. Indeed, cupric can be
regenerated in the etchant simply by vigorously aerating the solution for a
few seconds with a stirring rod.

Another problem with ferric chloride etchant is that ferrous chloride is
harder to neutralize than cupric chloride. More on that below.

Basically, ferric chloride is a “one-shot” oxidant. Provided without acid,
it cannot be reoxidized, so it cannot be reused. Given that an etchant
solution will accumulate copper in solution, it seems far better to me to
avoid ferric chloride altogether and simply use acidified copper chloride,
or better yet, simply start with an alternative oxidant such as hydrogen
peroxide, and let copper accumulate in solution and eventually take over.
An acidic copper chloride etchant can be reused indefinitely, provided that
HCl is added periodically to provide the protons for the reoxidation
reaction. Indeed, such an etchant solution actually improves with age!

Now to address why cupric chloride is easier to dispose of than ferric (or,
more accurately, ferrous) chloride. The easiest way to dispose of metal
ions is to precipitate them as hydroxides with a base such as sodium
carbonate. Hence, cupric is precipitated from chloride solution thus:

CuCl2 + Na2CO3(s) + H2O –> Cu(OH)2(s) + 2 NaCl + CO2(g)

Ferrous is precipitated thus:

FeCl2 + Na2CO3(s) + H2O –> Fe(OH)2(s) + 2 NaCl + CO2(g)

Obviously, these are the same reaction, just with different metal ions. The
big difference is that Fe(OH)2 is only stable at pH values above about 8,
while Cu(OH)2 is stable at pH values above about 5. This means that copper
will precipitate much more readily, with less consumption of the base, and
it will not redissolve in neutral water (pH 7), while Fe(OH)2 will. In
other words, Cu(OH)2 is more stable in the environment. Either precipitate
may be filtered with a paper filter and dried in an oven to make a dry solid
cake for disposal. The filtrate solution is salt water which can be poured
down the sink.

Cheers,
Dave

David G. Dixon
Professor
Department of Materials Engineering
University of British Columbia
309-6350 Stores Road
Vancouver, B.C. V6T 1Z4
Canada

Filed under: random — by ladyada, posted at 11:39 pm


Wattcher, part 2!

OK so I spent some more time cleaning up my code today and have the next part of my “wireless data acquisition and reporting” project done. In this section, I show how to listen and parse XBee packets using python and then graph some useful data to prove that the sensors work. All in 165 lines of code (not including already-written libraries, of course)

Above, a photo screenshot of watching a laptop power supply hooked up to the Kill-a-Watt. Below, tracking watt usage while also watching the current power-line waveforms of a light-bulb dimmer

Filed under: random — by ladyada, posted at 11:09 pm


Wattcher! For when you want to watch your Watts

(Last week, Phil T. & I entered our prototype networked power meter “Tweet-a-watt” into the Greener Gadget competition here in New York. After much demand for how to do such a thing, I’ve decided to post up this work in progress)

This project documents my adventures in learning how to wire up my home for wireless power monitoring. I live in a rented apartment so I don’t have hacking-access to a meter or breaker panel. Since I’m still very interested in measuring my power usage on a long term basis, I will build wireless outlet reporters. Building your own power monitor isn’t too tough and can save money but I’m not a fan of sticking my fingers into 120V power. Instead, I’ll build on the existing Kill-a-watt power monitor, which works great and is available at my local hardware store.

My plan is to have each room connected to a 6-outlet power strip which powers all the devices in that room (each kill-a-watt can measure up to 15A, or about 1800W, which is plenty!). That way I can track room-by-room usage, for example “kitchen”, “bedroom”, “workbench”, and “office”.

This project will show how to:

  1. snag data from a Kill-a-Watt power meter
  2. use an XBee to read analog sensor data remotely
  3. put XBees into low power sleep mode
  4. have multiple sensors transmit to one receiver
  5. parse XBee sensor data using python on a home computer and/or an Arduino-type thing
  6. utilize Google App Engine ‘cloud computing’ to store that data and display it for later analysis

So far I’ve uploaded the first section which goes through the hardware steps of wireless-izing a Kill-a-Watt with an XBee modem!



Sam’s TagTool

A TagTool seems to be a sort of physical computing drawing tablet. Sliders and knobs change drawing parameters, and a minicomputer inside does the heavy lifting.
Sam T. built one into a suitcase using a Boarduino!

See the video which he kindly sent to me:



www.flickr.com
adafruit's items Go to adafruit's photostream
www.flickr.com
items in Adafruits More in Adafruits pool