You can store arbitrary data encoded in binary as a pattern of zeros and ones. What you do to get those zeros and ones is up to you. If you’re in a particularly strange mood, you could even store them as strips of chocolate on Swedish pancakes.
Oddly enough, the possibility of the pancake as digital storage medium was what originally prompted [Michael Kohn] to undertake his similar 2013 project where he encoded his name on a paper wheel. Perhaps wisely, he prototyped on a simpler medium. With that perfected, four years later, it was time to step up to Modified Swedish Pancake Technology (MSPT).
Highlights of the build include trying to optimize the brightness difference between chocolate and pancake. Reducing the amount of sugar in the recipe helps increase contrast by reducing caramelization, naturally. And cotton balls placed under the spinning cardboard platform can help stabilize the spinning breakfast / storage product.
Even so, [Michael] reports that it took multiple tries to get the sixteen bytes (bites?) of success in the video below. The data is stenciled onto the pancake and to our eye is quite distinct. Improvement seems to be more of an issue with better edge detection for the reflectance sensor.
[LaForge] and [Holger] have been hacking around on cell phones for quite a while now, and this led to them working on the open cellphone at OpenMoko and developing the OsmocomBB GSM SDR software. Now, they are turning their sights on 3G and 4G modems, mostly because they would like to use them inside their own devices, but would also like to make them accessible to the broader hacker community. In this talk at the 33rd Chaos Communications Congress (33C3), they discuss their progress in making this darkest part of the modern smartphone useful for the rest of us.
This talk isn’t about the plug-and-play usage of a modern cell-phone modem, though, it’s about reprogramming it. They pick a Qualcomm chipset because it has a useful DIAG protocol, and in particular choose the Quectel EC20 modem that’s used in the iPhone5, because it makes the DIAG stream easily available.
Our story begins with a firmware upgrade from the manufacturer. They unzipped the files, and were pleasantly surprised to find that it’s actually running Linux, undocumented and without the source code being available. Now, [LaForge] just happens to be the founder of gpl-violations.org and knows a thing or two about getting code from vendors who use Linux without following the terms and conditions. The legal story is long and convoluted, and still ongoing, but they got a lot of code from Quectel, and it looks like they’re trying to make good.
Qualcomm, on the other hand, makes the Linux kernel source code available, if not documented. (This is the source on which Quectel’s code is based.) [LaForge] took over the task of documenting it, and then developing some tools for it — there is more going on than we can cover. All of the results of their work are available on the wiki site, if you’re getting ready to dig in.
If you’re at all like us, or like [Vadim], you’ve got a stash of development boards in a shoebox on a shelf in your closet. If you’re better organized that we are, it might even be labeled “dev boards”. (Ah well, that’s a project for another day.) Anyway, reach into your box and pull one out, and put it to use. Do something trivial if you need to, but a dev board that’s driving a silly blinker is better than a dev board sitting in the dark.
[Vadim]’s good example to us all is going to serve as the brains for an automated plant watering system. That’s a low-demand application where the microcontroller can spend most of the time sleeping. [Vadim]’s first step, then was to get a real-time clock working with the hibernation mode. There’s working code inline in his blog.
If you use Arduino, you’ll feel at home in the Energia ecosystem. But it’s like ordering a Quarter Pounder with Cheese in Paris: Energia is a Royale with Cheese (YouTube) — it’s the little differences. And maybe that’s the point of the exercise; it’s always a good thing to try out something new, even if it’s only minimally different.
So grab that unused dev board off the shelf, struggle through the unfamiliar development environment and/or toolchain, but remember to keep an eye out for the sweet little differences. The more tools that you’re familiar with, the more solutions will spring to mind when you’re hacking on your next project.
One of the sticking points for us with our own Internet of Things is, ironically, the Internet part. We build hardware happily, but when it comes time to code up web frontends to drive it all, the thrill is gone and the project is only half-done.
Note that everything happens inside the ESP8266 here, from hosting the web page to interpreting and then blinking back out the IR LED codes to control the remote. This is a sophisticated “hello world”, the bare minimum to get you started. The interface could look slicker and the IR remote could increase its range with more current to the LED, but that would involve adding a transistor and some resistors, doubling the parts count.
For something like $10 in parts, though, this is a fun introduction to the ESP and BASIC. Other examples are simpler, but we think that this project has an awesome/effort ratio that’s hard to beat.
Yup, another clock project. But here, [Jan] builds something that would be more at home in a modern art museum than in the dark recesses of a hacker cave. It’s not hard to read the time at all, it’s accurate, and it’s beautiful. It’s a linear RGB LED wall clock.
The technical details are straightforward: WS2812 LEDs, an Arduino, three buttons, and a RTC. You could figure that out by yourself. But go look through the log about building the nice diffusing plexi and a very clean wall-mounting solution. It’s the details that separate this build from what’s hanging on our office wall. Nice job, [Jan].
Morse code enthusiasts can be picky about their paddles. After all, they are the interface between the man and the machine, and experienced telegraphers can recognize each other by their “hands”. So even though [Edgar] started out on a cheap, clicky paddle, it wouldn’t be long before he made a better one of his own. And in the process, he also made what we think is probably the thinnest paddle out there, being a single sheet of FR4 PCB material and a button cell battery. This would be perfect for a pocketable QRP (low-power) rig. Check it out in action in the video below.
There’s not much to a Morse code paddle. It could, of course, be as simple as two switches — one for “dit” and one for “dah”. You could make one out of a paperclip. [Edgar]’s version replaces the switches with capacitive sensing, done by the ATtiny4 on board. Because this was an entry in the 1kB challenge, he prioritized code size over features, and got it down to a ridiculous 126 bytes! Even so, it has deluxe features like autorepeat. We’d have to dig into the code to see if it’s iambic. Continue reading “World’s Thinnest Morse Code Touch Paddle”→
There used to be a time, before running shoes had blinking LEDs and required placing on an inductive charger overnight, when we weren’t worried about whether or not we could dump the firmware running underneath our heels. Those are not the times that we’re living in. Nike came out with a shoe that solves the age-old problem of lacing: the HyperAdapt. And [Telind Bench] has torn them apart.
Honestly, we’re kinda “meh” about what’s inside. The “laces” are actually tubes with a small Kevlar-like cable running inside, and the whole thing torques up using a small, geared DC motor. That’s kinda cool. (We have real doubts about [Telind]’s guess of 36,000 RPM for the motor speed.) But in an age when Amazon gives away small WiFi-enabled devices for a few bucks as a loss-leader to get you to order a particular brand of laundry detergent, we’re not so dazzled by the technology here, especially not at the price of $720 for a pair of freaking shoes.
The only really interesting bit is the microcontroller, which is over-powered for the job of turning a wheel when a keyboard-style sensor is pressed by your heel. What is Nike thinking? We want to see the firmware, and we’d like it reverse engineered. What other chips are on board? Surely, they’ve got an accelerometer and are measuring your steps, probably tying in with an exercise app or something. Does anyone have more (technical) detail about these things? Want to make a name for yourself with a little stunt hacking?