How To Reverse Engineer A PCB

For [Peter]’s entry for the 2015 Hackaday Prize, he’s attempting to improve the standard industrial process to fix atmospheric nitrogen. Why? Fertilizers. He’s come up with an interesting technique that uses acoustic transducers in a pressure vessel, and to power that transducer, he’s turned to the greatest scrap heap in the world: eBay. He found a cheap ultrasonic power supply, but didn’t know offhand if it would work with his experiments. That’s alright; it’s a great opportunity to demo some basic reverse engineering skills.

A few months ago, [Dave Jones] posted a great video where he reverse engineers the front end of the new Rigol Zed. The basic technique is to make a photocopy, get some transparency sheets, grab a meter, and go to town. [Peter]’s technique is similar, only he’s using digital image manipulation, Photoshop, and a meter.

The process begins by taking pictures of both sides of the board, resizing them, flipping one side, and making an image with several layers. The traces on the bottom of the board were flooded and filled with the paint bucket tool, and components and traces carefully annotated.

With some effort, [Peter] was able to create a schematic of his board. He doesn’t know if this power supply will work with his experiments; there’s still some question of what some components actually do. Still, it’s a good effort, a great learning opportunity, and another log in [Peter]’s entry to The Hackaday Prize

An Open Source Pinewood Derby Track

There are a lot of reasons to consider reproducing. Tax breaks are near the top of the list, and a bizarre obligation to ensure the survival of the species following closely behind. The pinewood derby, though… Where else are you going to get a chance to spend hours polishing axles and weighing down bits of wood so they can roll faster?

The Lansing Makers Network has cub scouts around the shop, most likely goofing off while their fathers spend hours building their son’s pinewood derby racers. Where there’s a pinewood derby manufactory, there’s a need for a track to test these racers out.

blurry-scoreboard-gutsThe four-lane, 38-foot run was made out of five sections of cabinet plywood attached with 4″ lap joints. That’s the way to do it if you want a smooth running surface. The lanes are 1/4″ strips of maple plywood, and the last four feet of the track – after the finish line, of course – are a ramp that raises the lanes another 1/2″ above the ground. There’s very little need for a bunch of pillows or foam at the end of the track.

This is the 21st century, and no pinewood derby track would be complete without a few bits of electronics. The starting gate is activated with a push button. A solenoid keeps a quartet of pins in place until the race is started. When the start button is pressed, the solenoid releases, sending the cars on their way.

On their way down the ramp, the cars pass over an IR object sensor which records their starting time. Thanks to some more sensors at the finish line, the track records each car’s position in the race on a few seven-segment displays.

bass fire extinguisher

Putting Out Fires With A Dubstep Drop

Two engineering students from George Mason University have built a rather unorthodox fire extinguisher. It uses a subwoofer to send sound waves powerful enough to extinguish small fires.

Similar in concept to a giant smoke-ring canon, the device uses a subwoofer with a tube that has a smaller aperture opening at the end. When the bass drops (literally), this causes an intense wave of sound (well, air), to be expelled from the device. And as you can see in the video below, it’s quite effective at putting out small fires.

They use a small frequency generator and amplifier to power the system, and throughout extensive testing found 30-60Hz to work best. It’s not actually one big blast of air, but a pressure wave that goes back and forth — agitating the air, and separating it from the fire. There is a catch though.

One of the problems with sound waves is that they do not cool the fuel,” Isman said. “So even if you get the fire out, it will rekindle if you don’t either take away the fuel or cool it.

Continue reading “Putting Out Fires With A Dubstep Drop”

Hackaday Part Of TechCrunch NY Hackathon

The Hackaday Prize Worldwide is coming to New York! Hackaday is adding a hardware-centric twist to the TechCrunch Disrupt in May. They’re kicking off the conference with a weekend hackathon which traditionally has been a software event. This year Hackaday is partnering with TC to make a change. If you’re a software-only sort of person, grabbing a ticket to the event is extremely tough. But those Hackaday community members who want to prove they can make electrons do their bidding still have hope; Hackaday can get you in!

Twenty Hours of Hardware

Show up at 12:30pm on Saturday, May 2nd. By 9:30am the next morning you must have a working piece of hardware having been totally built on-site. Starting at 11am on Sunday you have 60-seconds to show off your build. We’re not kidding around when we say the judging criteria for this hackathon is “Awesomeness”. TC is putting up $5,000 to the winning team. Obviously someone who hangs out around Hackaday should be the winner here so go sign up!

Ticket Registration is a Hack:

TC hackathon tickets are released in shifts and gobbled up immediately, but because you are a friend of Hackaday we’ll can get you in for some epic hardware hacking. Even signing up is a bit of hack but here’s how:

  1. Follow this link which includes a promo code to get a Hackers – Friends of TC ticket
  2. Form/Find a team (up to 5 people) in advance through ChallengePost or you may do so onsite. You’ll notice the tags are software-related so put in “other” and add “hardware” and specific tags you can think of.

The Hardware

We’ll be bringing the basics: lots of dev boards, sensor breakout boards, and tools you need to hook them together. We’ll be posting information about the items we are bringing on our Hackaday Prize Worldwide: New York City page. Make sure you check in for updates so that you can familiarize yourself with what we’ll have on-hand. It is highly recommended that you set up any IDE or other dev tools before arriving at the event.


The 2015 Hackaday Prize is sponsored by:

Peripherals Behind The Iron Curtain

The article Home Computers Behind the Iron Curtain sparked a lot of interest, which made me very happy. Therefore, I decided to introduce more computer curiosities from the Iron Curtain period, especially from the former Czechoslovakia (CSSR).

As I mentioned in the previous article, the lack of spare parts, literature and technology in Czechoslovakia forced geeks to solve it themselves: by improvisation and what we would today call “hacking.”  Hobbyist projects of one person or a small party was eventually taken over by a state-owned enterprise, which then began to manufacture and deliver to stores with some minor modifications. These projects most often involved a variety of peripherals that could only be found in the Czechoslovakia with great difficulty.

Much like the production of components, the production of peripherals was also distributed throughout the eastern block so that each country was specializing in certain types of peripherals. For example, East Germany produced matrix printers, and Bulgaria made floppy disks drives. This meant industrial enterprises had to wait for vital computer parts, because the production in another country was not sufficient to cover even the local requirements, let alone the home user.

Continue reading “Peripherals Behind The Iron Curtain”

Showing An AVR Programmer Who’s Boss

[Bogdan] makes a good point. When you use a dev board you get programming, debugging, power sourcing, and usually a UART. When you go to the trouble of hooking up a programmer why don’t you get the same thing? Astutely, he points out that all you usually get with programmers is programming. So he set out to add features to the hardware he uses to program XMEGA.

The first part of the trick hinges on his use of PDI programming. This is slightly different from ISP programming. Both use a six-pin connector cable but with PDI two of these pins are unused. He took this opportunity to reroute the chip’s TX and RX pins through the cable, which now gives him an avenue to use a UART-to-USB adapter without adding any cables to his target board. Rather than add a second USB cable he rolled a USB hub into the mix. An LM1117 regulates the 5V USB rail down to 3.3V as a source for the target board.

The programmer being used is an Atmel ICE. As you might imagine he didn’t want to make permanent alterations to it. His modifications are all handled externally, with one IDC cable connecting the programmer to his added circuitry and another headed off to the target board. For now he’s jumpering RX/TX to the programming header but plans to route the signals on future PCBs.

Java Byte Code, Ahead Of Time Compilers, And A TI-99

Java famously runs on billions of devices, including workstations, desktops, tablets, supercomputers, and jewelry. Yes, jewelry. Look it up. [Michael] realized Java doesn’t run on Commodore 64s, TI-99s, and a whole bunch of other platforms. Not anymore.

Last year, [Michael] wrote Java Grinder, a Java byte-code compiler that compiles classes into assembly language instead of being part of a JVM. This effectively turns Java from a Just In Time compiled language to a normally compiled language, like C. He wrote this for the 6502/6510, the MSP430, and a Z80. The CPU in the TI-99/4A is a weird beast, though, and finally [Michael] turned this Java Grinder on that CPU, the TMS9900.

While most of the development was accomplished with the MESS emulator, [Michael] did manage to run Java on real hardware. His friend gave him a TI-99/4A a few years ago with a few cartridges. Cracking those cartridges open revealed one PCB that would hold an EEPROM. Writing his Java byte-code-derived assembly to a 28c64 EEPROM, he had a cartridge that would run compiled Java.

Right now, the demo is pretty simple with low-resolution graphics beeps and bloops of music, and generally not what you would expect from a TI/99. This is mostly due to the fact that the API for the TI-99 is extremely simple. You can check out the results of that programming endeavor below.

Continue reading “Java Byte Code, Ahead Of Time Compilers, And A TI-99”