For the past year, I’ve been organizing a very special project over on hackaday.io. It’s the Travelling Hacker Box, a box full of random electronics junk, sibling to the The Great Internet Migratory Box Of Electronics Junk, and a project that has already traveled more than 25,000 miles. Earlier this month, I said the Hackerbox is going international, I asked for contributors to receive the project in faraway lands, and now it’s time for the final report. This is where the Travelling Hackerbox will be going over the next year.
How often do you see problems that need fixing? How often do you design your own solutions to them — even if they won’t be implemented at scale? Seeing that many of the municipal parking lots in his native Sri Lanka use a paper ticketing system which is prone to failure, [Shazin Sadakath] whipped up his own solution: an efficient RFID tag logging system.
Many of us have held a circuit board up to a strong light to get a sense for how many layers of circuitry it might contain. [alongruss] did this as well, but, unlike us, he saw art.
We’ve covered some art PCBs before. These, for the most part, were about embellishing the traces in some way. They also resulted in working circuits. [alongruss]’s work focuses more on the way light passes through the FR4: the way the silkscreen adds an interesting dimension to the painting, and how the tin coating reflects light.
To prove out and play with his algorithm he started with GIMP. He ran the Mona Lisa through a set of filters until he had layers of black and white images that could be applied to the layers of the circuit board. He ordered a set of boards from Seeed Studio and waited.
They came back a success! So he codified his method into Processing code. If you want to play with it, take a look at his GitHub.
Wanting to experiment with using optical mouse sensors but a bit frustrated with the lack of options, [Tom Wiggins] rolled his own breakout board for the ADNS 3050 optical mouse sensor and in the process of developing it used it to make his own 3D-printed optical mouse. Optical mouse sensors are essentially self-contained cameras that track movement and make it available to a host. To work properly, the sensor needs a lens assembly and appropriate illumination, both of which mate to a specialized bracket along with the sensor. [Tom] found a replacement for the original ADNS LED but still couldn’t find the sensor bracket anywhere, so he designed his own.
Since the Beginning of Time* humans have been irresistibly attracted to the blinking of an LED. At first there was one LED and it was good, but eventually there were many working in unison and the matrix was formed. Badge hacking at the Hackaday SuperConference challenged everyone to do something interesting with the display matrix and other yummy hardware on this year’s badge and we were in awe of what people managed to pull off.
We named three winners, and recognized the first hacker to solve the Crypto Challenge. Check out the presentations in the video below and then join us after the break for a close look at each winning hack. Three winners received $256 and the crypto challenge winner received $512; two of them told Hackaday they plan to donate their prize to charity.
*we of course mark the beginning of time as the Unix Epoch
We’ve been following the Heathkit reboot for a while now, and it looks like the storied brand is finally getting a little closer to its glory days. I was thumbing through the new issue of QST magazine while I was listening in on a teleconference for the day job – hey, a guy can multitask, can’t he? – when I spied an ad for the Heathkit GC-1006 digital clock, which they brand the “Most Reliable Clock”. As soon as the meeting was over, I headed over to the Heathkit website to check out this latest offering.
I had cautiously high hopes. After the ridiculous, feature-poor, no-solder AM radio kit (although they sensibly followed up with a solder version of that kit) and an overpriced 2-meter ham antenna, I figured there was nowhere for Heathkit to go but up. And the fact that the new kit was a clock was encouraging. I have fond memories of Heathkit clocks from the 80s when I worked in a public service dispatch center; Heathkit clocks were about the only clocks you could get that would display 24-hour time. Could this actually be a kit worth building?
Alas, the advertisement was another one of those wall-of-text things that the new Heathkit seems so enamored of. And like the previous two kits offered, the ad copy is full of superlatives and cutesy little phrases that really turn me off. Then again, most advertising turns me off, so I’m probably not a good gauge of such things. Nor am I sure I’m in the target demographic for this product – in fact, I’m not even sure to whom this product is being marketed. Is it the younger crowd of the maker movement? Or is it the old-timers who want to relive the glory days of Heathkit builds? Given the $100 price, I’d have to say the nostalgia market is the most likely buyer of this one.
To be fair, $100 might not be that much to spend on a decent clock. I’m a bit of a clock snob, and I’ve gotten to the point where I can almost tell which chip is in a clock just by looking at the controls. The feature set of a modern digital clock has converged to a point where every clock has almost exactly the same deficiencies. The GC-1006 claims to address a few of my hot button issues, like not being able to set the time to the exact second – I hate that! An auto-dimming display is nice, as is a 12- or 24-hour display, a 10-minute timer (nice for hams, who are required to ID their station every 10 minutes), and a battery backup that claims to last for 4 weeks.
Is this worth buying? At this point, I’m on the fence. Looking at an unboxing video, it appears to be a high-quality kit, and it would be fun to build. But spending $100 on a clock might be a tough sell to my loan officer.
Still, I think I might take one for the team here so we have a first-hand report of what the new Heathkit is all about. And it would be nice to build another Heathkit product. I’ll let you know how it goes.
1 kilobyte. Today it sounds like an infinitesimally small number. Computers come with tens of gigabytes of ram, and multiple terabytes of storage space. You can buy a Linux computer with 1 gig of RAM and secondary storage as big as the SD card you throw at it. Even microcontrollers have stepped up their game, with megabytes of flash often available for program storage.
Rapidly growing memory and storage are a great testament to technology marching forward to the beat of Moore’s law. But, we should be careful not to forget the techniques of past hackers who didn’t have so much breathing room. Those were the days when code was written in assembly. Debugging was accomplished with an expensive ICE (an In Circuit Emulator… if you were working for a big company), or a few LEDs if you were hacking away in your basement.
To keep these skills and techniques in play, we’ve created The 1 kB Challenge, a contest where the only limit is what you can do with 1 kB of program memory. Many Hackaday contests are rather loose with constraints — anyone can enter and at least make the judging rounds. This time 1 kB is a hard limit. If your program doesn’t fit, you’re disqualified, and that is a challenge worth stepping up to.
That said, this is Hackaday, we want people to be creative and work around the rules. The important thing to remember is the spirit of the design constraints: this is about doing all you can with 1 kB of program space. Search out the old and wise tricks, like compressing your code and including a decompression program in your 1 kB. Crafty hacks to squeeze more into less is fine. Using the 1 kB as a bootloader to load more code from an SD card is not fine.
Any Hackaday contest needs some awesome prizes, and this one is no different.