[Dan] has his own Stratasys Dimension SST 768 3D printer. It’s a professional grade machine which does an amazing job. But when it comes time to replace the cartridge he has to pay the piper to the tune of $260. He can buy ABS filament for about $50 per kilogram, so he set out to refill his own P400 cartridges.
Respooling the cartridge must be quite easy because he doesn’t describe the process at all. But the physical act of refilling it doesn’t mean you can keep using it. The cartridge and the printer both store usage information that prevents this type of DIY refill; there’s an EEPROM in the cartridge and a log file on the printer’s hard drive. [Dan] pulled the hard drive out and used a Live CD to make an image. He loaded the image in a virtual machine, made some changes to enable SSH and zap the log file at each boot, then loaded the image back onto the printer’s drive. A script that he wrote is able to backup and rewrite the EEPROM chip, which basically rolls back the ‘odometer’ on how much filament has been used.
This work clock functions in an unexpected way. With each passing second it displays a random four letter word on the right side of the display. Traditional word clocks tell the time in natural language, but this one is simply used as a learning opportunity.
[Iron Jungle] got his hands on the display for just five buck from Deal Extreme. Looks like the price has gone up two dollars but that’s still a bargain. He wanted to use all eight digits of the display, and was looking for an opportunity to control more than one i2c device at a time. He ended up rolling an EEPROM and DS1307 RTC into the design. He figured the could display 24-hour time on four of the digits, and pull a library of four-letter words off of the EEPROM to fill the rest. He grabbed a word list off of the Internet then used a Python script to remove words containing 7-segment unfriendly characters (K, M, V, W, X, Z). The final touch was to use a salvaged relay to give the clock a ticking sound. Hear it for yourself in the clip after the break.
Continue reading “Word clock of a different nature”
The teachers at [Jjshortcut’s] school were each given a Webkey by the administration as a promotional item of sorts, but most of the staff saw them as useless, so they pitched them. [Jjshortcut] got his hands on a few of them and decided to take one apart to see what made them tick.
He found that the device was pretty simple, consisting of a push button that triggers the device to open the Windows run prompt, enter a URL, and launch Internet Explorer. Since the microcontroller was locked away under a blob of epoxy, he started poking around the onboard EEPROM with his Bus Pirate to see if he could find anything interesting there. It turns out he was able to read the contents of the EEPROM, and since it was not write protected, he could replace the standard URL with that of his own web site.
While it’s safe to say that without a new microcontroller the Webkeys probably can’t be used for anything more exciting than launching a browser, [Jjshortcut] can always reprogram the lot and drop them in random locations to drive some fresh traffic to his web site!
Behold this ATtiny85 based EEPROM programmer. It seems like a roundabout way of doing things, but [Quinn Dunki] wanted to build to her specifications using tools she had on hand. What she came up with is an ATtinyISP USB programmer, pushing data to an ATtiny85, which then programs an EEPROM chip with said data.
The hardware is the next module for her Veronica 6502 computer build. When we last saw that project [Quinn] was planning to add persistent storage for the operating firmware. This will be in the form of an EEPROM programmed with this device. Using ISP and an ATtiny as a go-between means that she should have no problems reflashing the OS without removing the chip. But it all depends on how she designs the interface.
For example, she blew a whole bunch of time troubleshooting the device because garbage data was being written to the chip. In the end, having her manual bus programmer hooked up during the flashing operation was the culprit. Lesson learned, it’s onward and upward with the build.
We’ve been featuring [Quinn’s] projects a lot lately. That’s in part because they’re really interesting, but also because she does such a great job of documenting her experience.
[Zach’s] company is all about the safety and to reinforce those ideals they handed out POV display fans to each employee. “Being Safe is Cool”, get it? Gimmicky… yes, but now [Zach’s] got a tiny little POV fan to hack. Although he may not have known it, this isn’t the first time we’ve seen this hardware. These fans were handed out as a promotion at Black Hat a couple of years ago and prompted some reverse engineering action. The message is stored on an EEPROM and there’s even a female programming header that makes it easy to write reflash it with your own messages if you know how to craft the data.
This is where the two products diverge. The older project uses a serial connection and PonyProg to dump and data. [Zach] first tried using his Bus Pirate to dump the data but after having no success he grabbed his Arduino and managed to get the job done. Once the message encoding protocol was worked out, he wrote a sketch to flash the EEPROM. So if you can get your hands on one of these the work has already been done. See [Zach’s] custom messages in the video after the break.
But we’d like to see this taken to the next level. How about a wall-mounted device that waits for something, like an incoming email or tweet, then spins up the fan to display it?
Continue reading “More POV fan message hacking”
[Andrew] recently ordered some lockets to bejewel them with some LEDs but got a bonus small locket for free with the order. Not really having a plan for the small locket it kind of sat around until finally some inspiration hit. Meet the ee-locket which contains a tiny circular pcb with a 64k eeprom, a few passive support components and a male pin header on the back so you can quickly plug it into the micro of your choice.
While the uses of such a thing may not be obvious at first, just sitting down writing this I thought of a few applications, such as some form of key and lock system, mission impossible dreams, or just going full out geek at your next job interview. Its a pretty spiffy idea no matter what its used for, and we just love it when people shove electronics where no one expect them.
We’ve seen projects test the lifespan of an EEPROM before, but these projects have only tested discrete EEPROM chips. [John] at tronixstuff had a different idea and set out to test the internal EEPROM of an ATmega328.
[John]’s build is just an Arduino and LCD shield that writes the number 170 to memory on one pass, and the number 85 on the next pass. Because these numbers are 10101010 and 01010101 in binary, each bit is flipped flipped once each run. We think this might be better than writing 0xFF for every run – hackaday readers are welcomed to comment on this implementation. The Arduino was plugged into a wall wart and sat, “behind a couch for a couple of months.” The EEPROM saw it’s first write error after 47 days and 1,230,163 cycles. This is an order of magnitude better than the spec on the atmel datasheet, but similar to the results of similar experiments.
We covered a similar project, the Flash Destroyer, last year, but that tested an external EEPROM, and not the internal memory of a microcontroller.
Check out the hugely abridged video of the EEPROM Killer after the break.
Continue reading “Destroying an Arduino’s EEPROM”