Chips as furniture is now a thing. It started off with a 555 footstool from Evil Mad Scientist and moved on to an EPROM coffee table. Now [msvm] over on the War Thunder forums has constructed a Nixie tube driver table. It’s based on the K155, and as a neat little addition, he’s included a real vintage chip under glass in the table.
Have some tongs, an anvil, and a blowtorch? Make some bottle openers out of framing nails. There’s a lot of variety here in the shapes of the bottle openers.
[Stephen] used a solid state relay he found on eBay to drive some Christmas lights. The SSR failed. That meant it was time to see inside of this relay looked like. The short answer is, ‘a lot of goop and epoxy’, but the traces look big enough to support the current it’s rated for.
Imagine a part of your 3D printer breaks. That’s alright, just print another…. oh, yeah. Well, I guess it’s time to make a bearing bracket out of wood.
The Electronica MK-54 and MK-61 (actually the Электроника МК-54) were incredibly popular Soviet programmable calculators. Now there’s an emulator for them.
[Rue Mohr] found a very cheap TFT display on an Arduino shield. The chip for the display was an SPF5408, a chip that isn’t supported by the most common libraries. He eventually got it to work after emailing the seller, getting some libraries, and renaming and moving a bunch of stuff. If you have one of these displays, [Rue] just saved you a bunch of time.
The ancient computers of yesteryear had hardware that’s hard to conceive of today; who would want a synthesizer on a chip when every computer made in the last 15 years has enough horsepower to synthesize sounds in software and output everything with CD quality audio? [Brian Peters] loves these old synth chips and decided to make them all work with a modern microcontroller.
Every major sound chip from the 80s is included in this roundup. The Commodore SID is there with a chip that includes working filters. The SN76489, the sound chip from the TI99 and BBC Micro are there, as is the TIA from the Atari consoles. Also featured is the Atari POKEY, found in the 8-bit Atari computers. The POKEY isn’t as popular as the SID, but it should be.
[Brian] connected all these chips up with Teensy 2.0 microcontrollers, and with the right software, was able to control these via MIDI. It’s a great way to listen to chiptunes the way they’re meant to be heard. You can check out some sound samples in the videos below.
Thanks [Wybren] for the tip.
Continue reading “Teensys and Old Synth Chips, Together At Last”
It’s totally excellent when a simple concept results in something inspiring and fun. [Rich Decibel]’s Kequencer is a good example, starting off as many projects do: “I had an idea the other day and I couldn’t decide if it was good or not so I just built it to find out.” Be still our hackable hearts!
[Rich] built this sleek little sequencer from scratch and while the design may not seem very novel to begin with–eight square wave oscillators with on/off switches and pitch knobs, played in sequence–but the beauty of it is in the nuances of interaction and the potential for further hacking. From watching the video you can see how the controls can be used in very interesting ways to create and mutate adorable chippy tone patterns. Check it out after the crossfade.
Continue reading “Rich Decibel’s Kequencer”
We’ve all known the MSP430s under the Launchpad are designed to be low power, but who wants to bet how long the chip can last on only 20F worth of capacitors? A couple of hours? A day at max? [Kenneth Finnegan] setup a MSP430 with supercaps to find out. To make sure the chip is actually running, [Kenneth] programmed it to count from 0 to 9 over a period of 10 seconds, and then reset. To get it ultra low power, the chip is in sleep mode most of the time, and a raw low current LCD is used to display the output. While [Kenneth] simply checks the chip every few hours to see if it’s still counting, a setup much like the Flash Destroyer, tracking a clock and then storing the current value would get a more exact time of death. Either way, it’s been over 3 weeks…and still counting. Video after the rift.
Continue reading “Launchpad takes ultra low power to the extreme”
[James] is interested in reverse engineering some integrated circuits. One of the biggest hurdles in this process has always been just getting to the guts of the chip. He used acetone to dissolve the plastic case but had trouble getting through the epoxy blob. Commonly, the epoxy is soaked in nitric acid for a few minutes but [James] didn’t have access to that chemical. Instead he popped into the local music store and picked up some rosin (used to make violin bows sticky enough to grab the strings of the instrument). After boiling down the rock-hard rosin and the chip for 20 minutes, he got a clean and relatively undamaged semiconductor that he can easily peer into.
Quick: which pins are used for I2C on an ATmega168 microcontroller?
If you’re a true alpha geek you probably already know the answer. For the rest of us, ChipDB is the greatest thing since the resistor color code cheat sheet. It’s an online database of component pinouts: common Atmel microcontrollers, the peripheral ICs sold by SparkFun, and most of the 4000, 7400 and LMxxx series parts.
The streamlined interface, reminiscent of Google, returns just the essential information much quicker than rummaging through PDF datasheets (which can also be downloaded there if you need them). And the output, being based on simple text and CSS, renders quite well on any device, even a dinky smartphone screen.
Site developer [Matt Sarnoff] summarizes and calls upon the hacking community to help expand the database:
“The goal of my site isn’t to be some comprehensive database like Octopart; just a quick reference for the chips most commonly used by hobbyists. However, entries still have to be copied in manually. If anyone’s interested in adding their favorite chips, they can request a free account and use the (very primitive at this point) part editor. Submissions are currently moderated, since this is an alpha-stage project.”
According to the an article in the INQUIRER, it is very possible that all chips with the G84 and G86 architecture are faulty. The problem is said to be excessive heat cycling and when NVIDIA was questioned, they blamed their suppliers for the issue. Although NVIDIA is claiming that only a few chips that went to HP were affected, the INQUIRER points out that all the chips use the same ASIC across the board, which has not changed in the architecture’s lifetime. They also point out that Dell and ASUS are having the same issues.
The article then goes on to theorize why we have not seen more complaints. They say that failures of these type usually follow a bell curve distributed over the time domain and we are only on the initial up-slope. This is probably due to the different use patterns of the users. For example, people with laptops are turning their computers on and off more than desktop users, thus facilitating the heat cycling’s effect. They suggest the quick fix as more fanning, but eventually NVIDIA will have to do something about this.