UptownMaker

I like the Arduino as a simple computing platform, but I've mentioned here before that I'd like to offload some of the more basic functions to a co-processor to let the Arduino have more CPU cycles for other stuff. That's true for many, MANY tasks, and one of the ones I've been fascinated with since college is the capturing and parsing of data from an infrared remote control. Adding IR to your project is a SUPERB way to add very complex I/O. I'm not sure if the Arduino has a library to read IR from remote controls, nor do I care, because it's likely to suck up an unacceptable number of CPU cycles. Thus, the IRduino: a shield with a small microprocessor (I'll probably use a PIC, since I know how to work those much better than AVRs) which decodes the signals from infrared remotes, packs it into three or four bytes (there are actually a LOT of possible codes out there, due to the number of encoding schemes). There would then be several options for sending t...

(click to enlarge) I'm not going to count this in the April Maker challenge. I don't know why. I hacked together a really hokey power supply for my tabletop foam cutter and as-yet-unbuilt acrylic bender (although strictly speaking, the portion of the foam cutter heating element that runs underneath the acrylic "table" has done a nice job of melting it). JTBarclay is using it for driving a 24V nigh-5W fan under a stir-plate, and Pat is building one for HIS foam cutter. It does a fairly good job, although it has no check on the amount of current it draws from the unregulated DC supply, which is a MAJOR short coming. The IC is an 8-pin PIC that I've programmed with a PWM controller that reads a pot to determine the duty cycle (at least, in this configuration it does). Because of the way the design works, you can put a limit on the duty cycle by inserting a resistor between the potentiometer and the ground rail. Using a smaller potentiometer is wise if you were ...