Signing Your 3D Prints

January 7, 2013 by 12 Comments

print

For all the 3D models out on the Internet, including the STL files on Thingiverse that are copied by other makers every day, there hasn’t been a good way to put your John Hancock on a three-dimensional piece of plastic you’ve designed. [Chris] has been thinking about the fact that an STL file released on the Internet is completely out of the creator’s hands for a while now, and he finally came up with a good solution to signing 3D prints.

[Chris] had been looking into ‘stamping’ a maker’s mark on the first few layers of a print, but this wasn’t always practical. Sometimes the bottom of a print needs to be a smooth surface, so [Chris] moved his initials up a few layers into the main body of the print.

By subtracting a 1.0 mm-thick version of his initials from the interior of a print, [Chris] is able to put his maker’s mark on the inside of a 3D object, visible only for a short time during the production process.

The signature isn’t impossible to remove, but it does give a little bit of credit to the original designer, all without some strange DRM scheme or metadata attached to an STL file.

You can check out [Chris]’ printer laying down a few layers of his logo after the break.

Continue reading “Signing Your 3D Prints” →

Reading Piano Rolls Without A Player Piano

January 7, 2013 by 22 Comments

detection-example

A while back, [Jacob] played around with a player piano. After feeding a roll into the machine and trying to figure out how a fifty year old machine using hundred year old technology can replicate a skilled pianist, he decided to take a crack at decoding piano rolls for himself. He came up with a clever way of doing it over Christmas break, using a camera and a few bits of OpenCV.

The old-school mechanics of a player piano use a bellows and valve system to suck air through dozens of holes, making the action hit a string whenever a hole is present in the piano roll. To bring this mechanism into the modern age, [Jacob] pointed a video camera at the active part of the piano roll and used OpenCV to translate holes in a piece of paper to a MIDI file.

The synthesized version sounds just as good as the original paper scroll-based version, as seen in the video after the break. There are a few sync issues in the video and the resulting MIDI file isn’t in the right key, but that’s easily fixed by anyone willing to replicate this project.

Continue reading “Reading Piano Rolls Without A Player Piano” →

Building A New Motherboard For A TRS-80

January 7, 2013 by 16 Comments

Trash80

The TRS-80 Model 100 was an amazing piece of kit when it was released. Able to run for a week with just four AA batteries and smaller than some laptops today, this portable version of the TRS-80 saw action with war correspondents covering the Falklands invasion. A pedigree a MacBook Pro will never be able to live up to, it seems.

[Hudson] picked up a non-functioning Model 100 with the express goal of replacing the 30-year-old electronics inside with an updated motherboard – and also pull up our retro site in the process. Armed with a Teensy++, [Hudson] pried open his ancient computer and set to work interfacing the display and keyboard to his AVR dev board.

The LCD display in the Model 100 has a resolution of 240×64, driven by ten Hitachi HD44102 display drivers. Each of these display drivers are responsible for the pixels in a 50×32 rectangle on the screen and are interfaced with a 30-bit wide bus consisting of chip select lines, and 8-bit data bus, and a few other random control lines. [Hudson] plugged this 30 pin header into his Teensy++ and after a bit of ingenuity regarding the strange electrical requirements of the LCD, was able to control every pixel on this 30-year-old display.

The next order of business was interfacing the keyboard with a modern microcontroller. The keyboard is laid out in a normal matrix, but with a few oddities: characters like ~, |, and curly brackets aren’t present on the Model 100. After working these problems out, [Hudson] set to work on a VT100 terminal emulator. This allowed him to run vi and lynx, enabling him to pull up the Hackaday retro site in a wonderful forty-column text mode.

Future improvements to this redesign include designing a proper PCB to replace the current protoboard design. The original Model 100 included a text editor and programming language, and adding a Forth implementation isn’t out of [Hudson]’s grasp. It’s an awesome build, and an excellent improvement that will allow [Hudson]’s Trash-80 to see another 30 years of use.

Playing A WAV File With 64 Bytes Of RAM

January 6, 2013 by 37 Comments

montage-final

[Jacques] thought his doorbell was too loud, so of course the first thing that came to mind was replacing the electronics and playing a WAV file of his choosing every time someone came knocking. What he ended up with is a very neat circuit: he used a six-pin microcontroller with 64 bytes of RAM to play an audio file. (French, Google translation)

The microcontroller in question is a PIC10F322. one of the tiniest PICs around with enough Flash for 512 instructions, 64 bytes of RAM, and a whole bunch of other features that shouldn’t fit into a package as small as a mote of dust. Without the space to store audio data on the microcontroller, [Jacques] turned to a 64 kilobyte I2C EEPROM. The PIC communicates with the EEPROM with just two pins, allowing it to read the audio data and spit it out again via PWM to an amplifier. The code required for this feat is only 253 instructions and uses just a few bytes of RAM; an impressive display of what a very small microcontroller can do.

Hardware SPI With Python On A Raspberry Pi

January 6, 2013 by 21 Comments

While the Raspberry Pi has very good support for an I2C bus, a lot of very cool chips – including the in system programmer for just about every ATtiny and ATmega microcontroller – use an SPI bus. [Louis] sent in a tutorial for getting hardware SPI on his Raspi, and even though it’s rather limited right now, it’s a step in the right direction.

Previously, [Brian Hensley] put up a tutorial for using the Linux SPI drivers with the Raspi. [Louis] wanted to play with SPI in Python, so he added a C extension to the spidev.c file (available here) that allows him to open an SPI connection, initialize, transfer, and close the connection.

After connecting an Arduino to the MOSI, MISO and SCK pins of his Arduino, [Louis] was able to transfer data from his Raspi over an SPI bus. It should be noted that a level shifter would be a really good idea here, but this is an excellent project if anyone would ever want to port AVRDude to Python.

 

Who Would Win In A Fight, Robot [Lemmy] Or Robot God?

January 6, 2013 by 52 Comments

[youtube=https://www.youtube.com/watch?v=3RBSkq-_St8&w=580]

So this is what happens when a fan of The Rock-afire Explosion grows up. Meet Compressorhead, a musical trio of hydraulic and pneumatic musical mastery.

Compressorhead is a lean band, consisting of only three members. Stickboy, the drummer, is a four-armed beast reminiscent of [General Grievous] that plays a 14-piece Pearl kit with a double bass. His listed influences include [Danny Carey] and the original MPC60.

Fingers is the guitarist and a wonder of mechanical linkages consisting of 78 hydraulically actuated fingers. Influences include [Yngwie Malmsteen], but with more fingers and less of an ego, we expect Fingers to be an even better guitarist than his idol.

Bringing in the low-end is Bones, the robotic tread-mounted bassist for Compressorhead. Like Fingers, he plays an unmodified instrument. He’s also the newest member of the band, completed in 2012.

If you’d like to check out Compressorhead in person, they seem to be touring Australia right now. If you’d like to schedule them, their rider lists a requirement of 65 Amp, 3 phase power, 3 liters each of hydraulic fluid and motor oil, and suspiciously no requirement for removing all the brown M&Ms from a package. Be sure to check out the videos of the band in action on their media site.

Thanks [BadWolf] for sending this one in.

Brute Forcing A GPS PIN

January 5, 2013 by 120 Comments

pin

[JJ] picked up a Garmin Nuvi 780 GPS from an auction recently. One of the more frustrating features [JJ] ran into is it’s PIN code; this GPS can’t be unlocked unless a four-digit code is entered, or it’s taken to a ‘safe location’. Not wanting to let his auction windfall go to waste, [JJ] rigged up an automated brute force cracking robot to unlock this GPS.

The robot is built around an old HP scanner and a DVD drive sled to move the GPS in the X and Y axes. A clever little device made out of an eraser tip and a servo taps out every code from 0000 to 9999 and waits a bit to see if the device unlocks. It takes around 8 seconds for [JJ]’s robot to enter a single code, so entering all 10,000 PINs will take about a day and a half.

Fortunately, the people who enter these codes don’t care too much about the security of their GPS devices. The code used to unlock [JJ]’s GPS was 0248. It only took a couple of hours for the robot to enter the right code; we’d call that time well spent.

You can check out the brute force robot in action after the break.

Continue reading “Brute Forcing A GPS PIN” →