Day: April 12, 2012

When [Matt] came across a small video camera made to fit onto a keychain, the first thing that came to mind is a time-lapse video throwie. Like the LED + coin cell battery + magnet we’ve seen we’ve seen before (and deployed…), [Matt]’s video throwie would be deployed in interesting spots for a few days and shoot a time-lapse video until the battery ran out.

The camera [Matt] picked up has the capability of shooting video or still pictures and writing them to a microSD card. To make his camera film a time-lapse video, [Matt] connected an ATtiny45 to the camera shutter and power buttons and uploaded a short bit of code that would snap a picture ever 15 seconds.

Right now, [Matt] is having a few problems with his video throwie. When the camera is turned on, it iterates through the SD card to find the next unused file name. This eats up a few seconds, so the current setup will slowly speed up the time-lapse video. This isn’t an insurmountable problem, so we’re looking forward to the very interesting videos these tough little cameras will film.

What happens if you’re a prolific developer and decide to release all of the source code from your work? Well, you should get a huge pat on the back from all interested parties. And so we say thank you to [Hunter Davis] for releasing the source code for his 70+ Android apps. But just making the decision isn’t the end of things, you’ve got actually get the code out there. And herein lies the hack. Instead of archiving and posting all of those projects he wrote a script to crawl, init, and push his projects to Github automatically.

This process is made pretty easy because of the Github API. Looks like he used version 2 for his script but you’ll want to check out version 3 if you’re looking to write your own script. His script takes the API key and username as command line arguments, then traverses his local source tree. Along the way it uses some text manipulation to sanitize the directories for use as the name of the repository. Once that’s established it steps into the directory, creates a repository, adds and commits all the files, then pushes them to Github.

Following [Hunter’s] example makes it really easy to share your code. We hope more will follow suit, putting their work out there for others to learn from and build upon.

We’re going to have to take [Mike’s] word for it that he built Conway’s Game of Life with high-definition video output. That’s because this screenshot is his only proof and it looks a bit fuzzy to us. But we are interested in the project which used an FPGA to generate a 1080p VGA output of the classic programming challenge.

One of the biggest benefits of using an FPGA for this application is the hardware’s parallel processing ability. For every frame of the game, the area around each living cell must be analyzed to produce the next evolutionary step. Most of the time this means processing all of the pixels in the playing area, which is the case here. [Mike] is using VHDL to program a Papilio Plus which has a Spartan 6 chip on it. He separated his code into the different components when writing about it. This makes it easy to find the chunks relating to the game if that’s what you’re interested in. If you just want to see how he implemented the VGA interface that’s well documented as well.

If you’re not familiar, Conway’s Game of Life has simple rules regarding when a cell will live, die, or be reborn. As [Mike] points out, every programmer should give it a shot at some point. We’ve seen many iterations from the very large to the very small.

Here’s a picture of the internals of an AT&T Microcell. This hardware extends the cellular network by acting as its own cell tower and connecting to the network via a broadband connection. So if you don’t get service in your home, you can get one of these and hook it up to your cable modem or DSL and poof, you’re cellphone works again. [C1de0x] decided to crack one open and see what secrets it holds.

On the board there are two System-0n-Chips, an FPGA, the radio chip, and a GPS module. There is some tamper detection circuitry which [C1de0x] got around, but he’s saving that info for a future post. In poking and prodding at the hardware he found the UART connections which let him tap into each of the SoCs which dump data as they boot. It’s running a Linux kernel with BusyBox and there are SSH and ROOT accounts which share the same password. About five days of automated cracking and the password was discovered.

But things really start to get interesting when he stumbles upon something he calls the “wizard”. It’s a backdoor which allow full access to the device. Now it looks like the developers must have missed something, because this is just sitting out there on the WAN waiting for someone to monkey with it. Responses are sent to a hard-coded IP address, but a bit of work with the iptables will fix that. Wondering what kind of mischief can be caused by this security flaw? Take a look at the Vodafone femtocell hacking to find out.

The first part of the cache is a box (the black one on the left) which contains a mysterious hand crank and a smaller box that has a combination lock on it. The second stage is the wooden box on the right. It’s got a hole in the side to receive the hand crank. This connects to the dynamo inside, letting you build up some electricity as it spins. Inside the case you’ll see two red lights blink as the crank is turned, but when you push the button on the outside of the box nothing will happen. That is, unless you’re looking through a camera which can pick up infrared light. The code (710 in this case) is displayed in an array of IR LEDs, and is used to open that combination lock. We wonder if there’s any clues about using a camera or if you have to figure this out on your own.

From what we can tell, it’s being used almost like an 8-track tape. A PWM signal is stored on one circular slice of the disk, then the head can be moved back to that same “track” to play back the wave form. The head doesn’t move during playback, but just keeps reading the same track of bits. To the right you can see an Arduino board. This allows for MIDI control of the track selection. [Alexis] shows off some keyboard control in the video after the break. There’s a buffer chip on the breadboard which allows the audio output to be quickly switched off as the floppy drive head is moved. This keeps garbage out of the sound until the new track can be read.

Former Hackaday contributor [mikeysklar] has been trying to etch a QR code into a sheet of copper. Although his phone can’t read the CuR codes he’s made so far, he’s still made an impressive piece of milled copper.

The biggest problem [mikey] ran into is getting Inkscape to generate proper cnc tool paths instead of just tracing a bitmap image. He’s got the CNC part of his build under control, but he still can’t find a QR code reader that will register his work.

We’re no stranger to QR codes here at Hack a Day, and it’s very possible the only thing that could be stopping [mikey]’s QR code from being read by a phone is the contrast of the image. We’re thinking a little bit of printer’s ink forced into the non-copper part of the PCB would make the QR code register. Since [mikey] already has a very nice negative etching of his QR code, he could easily use his new board as a printing plate, making infinite paper copies of his copper-based QR code.

If you’ve got any ideas on how [mikey] can get his QR code working, post them in the comments.