Things don’t always run the way we want them to or operate at the ideal temperature out of the box. Instead of spending extra for power controls that may or may not meet your needs, wouldn’t it make more sense to dial in the ideal level from the source? That’s what [dekuNukem] had in mind when he decided to make Powerduino, an arduino-compatible programmable power strip.
With Powerduino, [dekuNukem] can control the electrical consumption of all kinds of things without ever worrying about the irreversible deadliness of mains voltage. It actually uses a Teensy 3.1 which can be programmed with the Arduino IDE through the micro USB connector. He’s really tricked it out to the point of putting Kill A Watt meters to shame. A wi-fi module lets him control any of the outlets from anywhere, and the RTC module lets him make customized schedules for them. Powerduino has an SD card slot for logging energy consumption, and a 20 x 4 LCD screen makes it easy to directly interface with the power strip.
The Powerduino code is up on GitHub, and [dekuNukem]’s walkthrough video is after the jump.
Continue reading “Go On a Power Trip with Powerduino”
It may not look like much, but the above pictured device is [qquuiinn’s] handy little watch that indicates time through pulsed vibrations. Perhaps we should refrain from labeling it as a “watch,” however, considering it’s [qquuiinn’s] intention to remove the need to actually look at the thing. Vibrations occur in grandfather clock format, with one long vibration for each hour, accompanied by one, two, or three short pulses for the quarter-hour increments.
The design is straightforward, using an ATTiny85 for the brains along with a few analog components. The vibration motor sticks to the protoboard with some glue, joining the microcontroller, a coin cell battery, and a pushbutton on a small protoboard. The button allows for manual time requests; one press responds with the current time (approximated, probably) in vibrations. The build is a work in progress, and [qquuiinn] acknowledges the lack of an RTC (real-time clock) causes some drift in the timepiece’s accuracy. We suspect, however, that you’d address that problem—twice daily—when you replace the battery: it only lasts ten hours.
Sometimes the projects we think are easy to design are the ones on which we end up making the most mistakes. The UNIX clock that you see in the picture above is one of these projects. For our readers that don’t know it, UNIX time is the number of seconds since 00:00 on January 1st 1970. The clock that [James] designed is based on an Arduino Pro Mini board, an RTC chip to store the time, a custom made display board and two buttons to set the date/time.
One of the mistakes that [James] made was designing the boards on which will be soldered the seven-segment displays before actually choosing the ones he’ll use, as he was thinking they’d be all the same. The displays he ended up with had a different pitch and needed a different anode voltage, so he had to cut several traces on the PCBs and add another power supply. It also took [James] quite a while to remove the bits that his hackerspace’s laser didn’t cut through. We strongly advise a good look at his very detailed write-up if you are starting in the electronics world.
If you find this Unix time display too easy to read here’s one that’s a bit more of a challenge.
[Paulo’s] garden lights are probably a bit more accurately automated than anyone else’s on the block, because they use latitude and longitude clock to decide when to flip the switch. Most commercial options (and hobbiest creations) rely on mechanical on/off timers that click on an off every day at the same time, or they use a photosensitive element to decide it’s dark enough. Neither is very accurate. One misplaced leaf obscuring your light-dependent resistor can turn things on unnecessarily, and considering the actual time of sunset fluctuates over the year, mechanical switches require constant adjustment.
[Paulo’s] solution addresses all of these problems by instead relying on an algorithm to calculate both sunrise and sunset times, explained here, combined with swiftek’s Timelord library for the Arduino. The build features 4 7-segment displays that cycle through indicating the current time, time of sunset and of sunrise. Inside is a RTC (real time clock) with battery backup for timekeeping along with an Omron 5V relay to drive the garden lamps themselves. This particular relay comes with a switch that can force the lights on, just in case.
Check out [Paulo’s] project blog for the full write-up, links to code and more details, then take a look at some other home automation projects, like the SMS-based heater controller or occupancy-controlled room lighting.
Segments rise from a sheer white surface to reveal the time in this papercraft digital / analog clock build by [Jacky Mok].
New York-based designer [Alvin Aronson] is responsible for the original, titled “D/A Clock,” which he built as a student at RISD using Corian instead of paper. [Aronson]’s design is also massive in comparison. It measures one meter wide by a half meter tall. Without access to either a 3D printer or to a laser cutter, [Jacky] instead reduces the scale of his interpretation and relies on cardstock as the primary construction material. His experience with papercraft typography leads to a design that anyone with an Exacto knife and a slice of patience should find manageable. [Jacky] ignores the Exacto option, however, and cuts his pieces with a tool we saw earlier this year: the Silhouette Portrait.
The clock’s electronics include an Arduino Uno, a servo motor controller, twenty-eight servos and an RTC breakout board that handles timekeeping. Each servo drives its own segment by sliding a paperclip forward or backward inside a small, hollow aluminum rod. Though we’re still holding out for a video of the finished papercraft build, you can watch a video of Aronson’s original clock after the break and see what inspired [Jacky’s] design.
Need another clock to envy? Last month’s build by [ebrithil] uses twenty-two servos to individually spin the segments. If you prefer that your clocks light up, [Aaron’s] o-scope transformation has you covered.
Continue reading “An elegant timepiece from paper and a fistful of servos”
[Brendan Sleight] has been hard at work on this wearable piece of tech. He doesn’t wear much jewelry, but a wedding ring and some cufflinks are part of his look. To add some geek he designed a set of cufflinks that function like traffic lights. Since he still had some program space left he also rolled in extra features to compliment the traffic light display.
That link goes to his working prototype post, but you’ll want to look around a bit as his posts are peppered with info from every part of the development process. The coin-sized PCB hiding inside the case plays host to a red, amber, and green surface mount LED. To either side of them you’ll find an ATtiny45 and a RV-8564-C2. The latter is a surface mount RTC with integrated crystal oscillator, perfect for a project where space is very tight.
The design uses the case as a touch sensor. Every few seconds the ATtiny wakes up to see if the link is being touched. This ensures that the coin cell isn’t drained by constantly driving the LEDs. The touch-based menu system lets you run the links like a stop light, or display the time, date, or current temperature. See a quick demo clip after the break.
Continue reading “Traffic light cufflinks”
One look at this display and you know there’s a whole lot of pins that need to be wired up. Now look at what those display modules are mounted on. That’s right, [Kemley] is using point-to-point soldering to rig up this big display. It sports four sixteen segment modules on top for alpha-numeric information, and eight large seven segment modules for displaying numbers only.
We’re not certain as to how the electronics are arranged. When talking about the 16-segment modules he mentions that all four are in parallel with NPN transistors to switch the common anode of each. That’s easy enough to understand. But when you get a look at the transistor board you’ll see 24 of them in use. He’s included a 150 ohm resistor on the collector of each transistor. It must be set up to only allow one segment of each group to switch on at a time? We’d guess that each segment is divided into two (upper and lower pins are multiplexed separately), which would explain the double set of transistors. As for date and time, an Arduino board monitors a DS1307 RTC and manages the scanning of the display.