[Sal] sent us his digital electric meter monitor, which immediately made us nostalgic for some of Forrest Mims’ books. Sal’s schematic and circuit description are similar to Forrest’s style, and we mean that as a compliment. Even in today’s world of CAD and EDS packages, sketching out a circuit by hand is sometimes both easier and faster. The schematic isn’t the only classic aspect of [Sal’s] design. He’s collecting data using a parallel port on an unused PC: in this case, a Toshiba Libretto running Windows 95. Before cheap flash-based microcontrollers and dev boards were available, the PC parallel port was the go-to hardware hacking interface for many of us. Plenty of the software running those old hacks was written in basic, and [Sal’s] meter is no exception. His software runs on Microsoft QBasic, which shipped with Windows 95.
The circuit takes advantage of the digital meter’s output: a 10 ms pulse for every 1 Wh of energy used. An IR photo detector from RadioShack detects the meter pulses, which are amplified by an LM324 Op Amp. An NPN transistor then shifts the output to send it to two 74LS73 JK flip flops. The first flip flop uses a transistor to drive an LED for visual output. The second JK flip flop sends the data to the PC. The flip flop has the effect of dividing the number of meter pulses by two, creating a much longer toggled signal that a PC can better detect.
Although using an AVR or PIC would consume less power, [Sal’s] setup has already more than paid for its power usage. By monitoring and adapting his electrical usage, [Sal] is saving $20 a month on his electric bill. We’ve included [Sal’s] circuit diagram and source code after the break (apologies to our readers on RSS).
Continue reading “Digital Electric Meter Monitor Goes Old School”
The current marketplace allows hobbyists to easily find inexpensive, well-documented displays, but what if you wanted to interface with something more complicated, such as the screen on an iPod Nano 6? [Mike] has given us a detailed and insightful video showing his process for reverse engineering a device with little-to-no documentation. Here he covers the initial investigation, where one scours the web in search of any available information. In [Mike’s] example, the display uses an MIPI D-PHY interface, which he has never worked with. He learns that the MIPI Alliance will provide design specs in exchange for a signed NDA (Non-Disclosure Agreement) and a modest $8000 fee. Nice.
[Mike] shows off some serious hardware hackery, tackling some extremely difficult soldering in order to set up a proper test platform. He then demonstrates how to use a rather awesome oscilloscope to better understand the display protocol. We found it fascinating to see the video signals displayed as waveforms, especially when he shows how it is possible to count the individual binary values. The amount of information he uncovers with the oscilloscope is nothing short of amazing, proving these little devices are more complex than they seem.
[via Hacked Gadgets]
Continue reading “Reverse Engineering an LCD Display”
Looking for a throw back to your childhood, or maybe you just appreciate things that light up and look amazing? Well, [Baron] has a really impressive project for you. Not only does it look stunning and incorporate all of the things we love, it’s actually a pretty novel design. These lamps are built completely out of LEGO Technic pieces, the brand of LEGO that have holes drilled through them so you can build more advanced creations.
[Baron] used these parts with the drilled holes to create a dot matrix in which he placed colored transparent LEGO dots in the holes. The method of creating patterns is very similar to the way it’s done on the “Lite-Brite”. We especially love the theme of these lamps and they would match well with your LEGO mystery box. What’s really great about this tutorial is that it lays down the foundation for LEGO-built lamps that could be more interactive, involve more control (like RGB LEDs), or even introduce some LEGO mechanics!
That’s the best and most obtuse title you’ll ever see for a Hackaday post, but surprisingly it’s pretty accurate. [Bob] over at the Sector67 hackerspace took part in a 111-day accelerator program in Shenzhen last year to improve his manufacturing skills. He’s just about ready to release his first product, a Bluetooth device that connects to an ice fishing tip-up. The blog for the device recounts the challenges of taking a project from a circuit to a finished product, and illustrates the difference between building something with an Arduino and selling thousands of devices.
The circuit boards for BlueTipz come in panels of eight, but what’s the best way to populate and solder five thousand devices in a reasonably short amount of time? [Bob] hired a few students from the local college to help him out in assembling all these devices. The plastic enclosures were made at a local plastics manufacturer, but the molds were made in China. The manufacturer needed to modify the molds a bit, but after a few days, [Bob] had five thousand enclosures ready to stuff full of electronics.
With the devices assembled, it’s time for programming, and that means building a programmer. [Bob] put all the guts for the device into a plastic box and 3D-printed a mount for the bare BlueTipz board. Put a board on the mount, press a button, and the tech now has a functioning device in his hands.
Besides manufacturing, there’s also a whole lot of testing that went into the design of BlueTipz. Because this is a device for ice fishing—a cold and potentially windy operating environment—[Bob] built a test rig in a freezer. The test rig triggers the device’s sensor, waits two minutes (the amount of time it would take for an ice fisherman to check the tip-up) and resets. They claim the battery life is good for 600 fish, and with this testing rig they were able to verify their calculated battery life with real-world data: without actually catching six hundred fish, of course.
Not only does [Bob] have a good bit of product development under his belt, he was also kind enough to go over the stuff everyday electronic design just doesn’t cover. Developing a product is something you can only learn by doing, and we’re glad [Bob] chose to share his experiences with us.
Can you spot the serial port in the pic above? You can probably see the potential pads, but how do you figure out which ones to connect to? [Craig] over at devttys0 put together an excellent tutorial on how to find serial ports. Using some extreme close-ups, [Craig] guides us through his thought process as he examines a board. He discusses some of the basics every hobbyist should know, such as how to make an educated guess about which ports are ground and VCC. He also explains the process to guessing the transmit/receive pins, although that is less straightforward.
Once you’ve identified the pins, you need to actually communicate with the device. Although there’s no easy way to guess the data, parity, and stop bits except for using the standard 8N1 and hoping for the best, [Craig] simplifies the process a bit with some software that helps to quickly identify the baud rate. Hopefully you’ll share [Craig’s] good fortune if you reach this point, greeted by boot messages that allow you further access.
When [Scott] saw our announcement of a contest to win a Fubarino, he had the remarkable insight that designing new hardware wasn’t required. Instead, he took a Simon soldering kit and added a Hackaday easter egg that beeps our favorite URL in Morse code.
[Scott]’s entry began with a Sparkfun Simon Says Soldering Kit. It’s a great kit featuring an ATMega328, four buttons and LEDs, and a speaker. Stock, this board comes programmed with a run-of-the-mill Simon game, but it also includes a serial bootloader and a set of serial pins for reprogramming.
The new firmware for [Scott]’s Simon uses Morse code for ‘hackaday.com’ to determine the time in between the button flashes for each round. Compared to the old-school Simon toy from the 70s, [Scott’s] version seems just slightly more difficult; the game is basically the same, but trying to remember the pattern when the buttons don’t light up in a regular pattern is more challenging than usual.
Because [Scott] isn’t the greatest at Simon, he added another method to generate the full Morse for ‘hackaday.com’. While pressing one button starts a new game, holding down two buttons simultaneously will write out the full Morse of ‘hackaday.com’ on the upper left-hand button: a great easter egg that also adds some difficulty to a classic game.
This is an entry in the Fubarino Contest. Submit your entry before 12/19/13 for a chance at one of the 20 Fubarino SD boards which Microchip has put up as prizes!
Here’s one of those ideas that makes us wonder: “Why didn’t we come up with that?” The LVL1 in Louisville, Kentucky is hosting an event they call the Quadcopter Ultimate Aerial Combat Competition (QUACC). Kudos to them on coming up with a very professional name for the event. At risk of drawing cease-and-desist orders from the defunct TV program, we’ll always think of this as Battlebots in the Sky. (Lawyers: please don’t make us take that down… it’s an homage to the awesomeness that was at least the first few seasons of the show).
So why are we publicizing local events on Hackaday? It’s not the event, but the idea that’s spectacularly worth sharing! You’ve got to check out their contest rules as well as the Q&A list. Registration is closed, but the lucky ones who claimed a spot for the low price of $40 will be issued a regulation quadcopter today. They have a week to play around with it, testing out different ideas for disabling their enemy. A match ends when either one competitor defeats the other, or when a competitor’s battery runs dry. A new battery is the issued to the winner for use in the next round.
We’d love to hear your ideas for weaponizing (or adding countermeasures to) these delicate, lightweight aircraft. Aerosol accelerant and a BBQ igniter? How about shielding and a type of EMP, or some other system that will disrupt controller commands of your opponent? Obviously if you launch a similar competition at your hackerspace we want to hear about it!