Nespresso Capsule Detector

Nespresso fans rejoice! If you like coffee (of course you do) and are a Nespresso fan, chances are you are one of two types of persons: the ones that chosen one type of capsule and stick to it or the ones that have a jar full of mixed capsules and lost track which coffee is which. Of course, there is a third, rarer, OCDish, kind. The ones that have every capsule organized neatly by color in a proper holder, full of style. In any case, if you forgot which color is which coffee because you threw the case away and forgot about it here’s an interesting weekend project for you: the Nespresso Capsule Detector.

[circuit.io team] made a neat Arduino-based project that can detect which capsule is which using an RGB color detector and display information about it on an LCD display. It’s a pretty simple project to make. If you have a 3D printer you can print the case, if not it’s fairly easy to come up with a working casing for the electronics and capsule.

The operation is simple, just drop the capsule in the hole and the Nespresso Capsule Detector will tell you which type it is, its intensity, its flavor tones and the optimal cup size for the coffee in question. We are just not sure if it can detect the Nespresso weddingbots correctly, but who knows?

Have a look:

Continue reading “Nespresso Capsule Detector”

The USB Killer: Now Faster, Better, More Anonymous

A few years ago, [Dark Purple] built the USB equivalent of an RJ45 connector wired into mains power. The USB Killer is a simple device with just a FET, a few high voltage caps, a DC/DC converter, and a USB connector. Plug this device into your computer and -220V is dumped directly into the USB signal wires. This kills your laptop dead.

Over the years we’ve seen the USB Killer evolve from a hand-etched PCB to something less discrete but more discreet. It was a crowdfunding campaign run by a company in Hong Kong, and a few months ago this new commercial version was released.

Now, the USB Killer V3 is out. It provides 1.5 times the power to your poor USB ports, with power surges twice as fast. There’s also an anonymous version that looks like every other USB thumb drive sourced from Hong Kong. This is your warning: never, ever plug an unknown USB thumb drive into your computer.

While a product announcement really isn’t news, it is extremely interesting to take a look at how something that should not exist is being marketed. As with all electronic destructive devices, it’s on your Amazon recommended products list alongside tactical kilts, fingerless gloves, beard oil, and black hoodies. This is pentesting gear, with an anonymous edition for your friend, the hacker called four chan. Don’t think too much about how you’re going to get data off a laptop you just killed, or how you would go undetected by destroying equipment; this is cool hacker stuff.

In addition, the USB Kill 2.0 is FCC and CE approved. This allows you to, “test in complete safety” (their emphasis, not ours).   We have no idea what this actually means.

Making Use Of Stellaris/Tiva Real-Time Clock

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.

royale-with-cheese-pulp-fiction-2_12-movie-clip-1994-hd-6pkq_ebhxj4mkv-shot0001
“I don’t know, I didn’t go into Burger King.”

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.

SPI On Embedded Linux

Are you already comfortable working with Serial Peripheral Interface (SPI) parts and looking for a challenge? We suspect many of you have cut your teeth on 8-bit through 32-bit microcontrollers but how much time have you spent playing with hardware interfaces on embedded Linux? Here a new quest, should you choose to accept it. [Matt Porter] spoke in detail about the Linux SPI Subsystem during his presentation at FOSDEM 2017. Why not grab an embedded Linux board and try your hand at connecting some extra hardware to one of the SPI buses?

The hardware side of this is exactly what you’d expect from any embedded SPI you’ve worked on: MOSI, MISO, a clock, and a slave select. [Matt] gives a succinct overview of SPI and reading datasheets. Our own [Elliot Williams] has done an excellent job of digging through the basics and most common gotchas if you need to get up to speed on all the SPI basics.

The fun details in the talk start at about 18:30 into the video when [Matt] jumps into the Linux side of SPI. You need a controller driver and a protocol driver. The controller driver is responsible for dealing with the pins (actual hardware) and the protocol driver handles the job of making sense of the SPI packets (messages containing any number of transfers) going in or out. In other words, the controller drive just want bits and pushes them in or out on hardware, the protocol driver makes those bits meaningful to the Linux system.

Adding SPI devices (think devices like LCDs and sensors) to your own embedded systems means telling the OS the particulars about that hardware, like max speed and SPI mode. There are three ways to handle this but the Device Tree is the preferred method for modern systems. This paves the way for the controller driver which implements an API set that the Linux SPI subsystem will use to work with your new hardware.

Protocol drivers follow the standard Linux driver model and are pretty straight forward. With these two drivers in place the new device is hooked into the OS and opens up common SPI API calls: spi_async(), spi_sync(), spi_write(), and spi_read(), and a few others.

Continue reading “SPI On Embedded Linux”

ESP8266 BASIC Sets Up A Web Remote In No Time

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.

Including some simple web-based scripting functionality along with the microcontroller basics is one of the cleverest tricks up ESP8266 BASIC’s sleeves. BASIC author [mmiscool] puts it to good use in this short demo: a complete learning IR remote control that’s driven through a web interface, written in just a few lines of BASIC.

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.

PIC Retrocomputer Boasts VGA, PS/2 Keyboard

You might think that our community would always strive to be at the cutting edge of computing and use only the latest and fastest hardware, except for the steady stream of retrocomputing projects that appear. These minimalist platforms hark back to the first and second generation of accessible microcomputers, often with text displays if they have a display at all, and a simple keyboard interface to a language interpreter.

Often these machines strive to use the hardware of the day, and are covered with 74 logic chips and 8-bit processors in 40-pin dual-in-line packages, but there are projects that implement retrocomputers on more modern hardware. An example is [Sebastian]’s machine based upon a couple of PIC microcontrollers, one of which is an application processor with a PS/2 keyboard interface, and the other of which handles a VGA display interface. The application it runs calculates whether a 4-digit number is a prime and displays its results.

His write-up gives a fascinating overview of the challenges he found in creating a reliable VGA output from such limited hardware, and how he solved them. Though this one-sentence description makes a ton of work sound easy, horizontal sync pulses are generated as hardware PWM, and pixel data is streamed from the SPI bus. The VGA resolution is 640×480, upon which he could initially place a 10×10 block of text. Later optimizations extend it to 14×14.

Sometimes it’s not the power of the hardware but the challenge of making it perform the impossible that provides the attraction in a project, and on this front [Sebastian]’s retrocomputer certainly delivers. We’ve featured many other retrocomputers before here, some of which follow [Sebastian]’s example using modern silicon throughout, while others mix-and-match old and new.

Can A Bundle Of Soda Straws Be A Camera?

This one is hard to classify. Is it a hack, or is it art? Perhaps it’s both. However you want to classify it, it’s pretty cool to turn a bundle of drinking straws into a camera.

strawcamera_012
Click for larger image

If you’re looking for the technology here, you won’t find much. There’s no lens, no shutter, and no electronics of any kind in [Mick Farrell] and [Cliff Haynes]’ Straw Camera. This is literally a box full of drinking straws standing on end, with a sheet of photo paper behind it. Each straw sends a spot of light that represents the average hue and luminance of its limited view of the subject directly to the film. The process of making an exposure consists of composing the scene, turning out the lights, loading the camera, and setting off a flash.

The resulting images are defocused but recognizable, like seeing familiar sights through a heavy fog. The straws make a strong texture over the ghostly image of the subject – indeed, the straws are the only thing in focus. The fact that the straws don’t form a perfect honeycomb due to settling and imperfections in the bundles is jarring at first, but as you see the images you get used to the extra texture.

When we first saw this, we wondered about the possibility of putting a simple photosensor at the bottom of each straw to capture similar images digitally. The TCS3200 would be about the right size, but given that there are about 32,000 straws in the bundle, the BOM might get a little out of hand. Still, a scaled down digital straw camera might yield some interesting images.

Thanks to [Stuart Rogers] for the tip.