Pour-over coffee brewing is a simple and cheap hands-on alternative to using an automatic coffee maker. Although coffee aficionados often choose pour-over just for the manual brewing experience, this didn’t stop [Elias] from automating his pour-over coffee setup with an elaborate delta-robot: the DeBrew.
The coffee-brewing robot is built around a delta assembly from a 3d printer controlled by a BeagleBone Black. The BeagleBone drives stepper motors, displays information on a small open-source hardware HDMI LCD display, and serves up a web interface to control the machine. The radius of the pouring pattern, water temperature, and grind coarseness of the DeBrew can all be customized though its web interface.
For those who want to build their own pour-over robot, [Elias] has made a SketchUp drawing of the design and all of his Python source code available as open-source. Check out the video after the break where [Elias] explains how his delta pour-over bot works.
Continue reading “Delta Coffee-Brewing Bot”
A student team at Ohio State University has designed and built a custom Controller Area Network (CAN) data acquisition system complete with a sensor interface, rider display, and a Linux-based data logger for a RW-2x motorcyle.
They call their small, convenient micro-controller circuit board the Magic CAN Node, and it measures automotive sensors throughout the electric vehicle. This includes a variety of thermistor resistors to check changes in temperature. A few 0-5V and 0-12V sensors to monitor brake pressure transducers along with some differential air pressure sensors can be added too. Since the vehicle is basically a “rolling electromagnetic noise bomb”, they wanted to keep all of these analog sensors as close to the source as possible.
The Magic CAN Node is based on a Texas Instruments microcontroller called the TMS320F28035. This keeps the energy consumption at a low level.
For message handling, the team, led by [Aaron], tapped into the built-in CAN module within the F28035. All of the CAN plugs have two of the pins shorted to GND or +12V, so when there’s only one plug connected, the analog switch IC will connect a 120 ohm resistor across the CAN lines.
Continue reading “Custom CAN System Logs Motorcyle Data like Magic”
[Josh Datko] was wandering around HOPE X showing off some of his wares and was kind enough to show off his CryptoCape to us. It’s an add on board for the BeagleBone that breaks out some common crypto hardware to an easily interfaced package.
On board the CryptoCape is an Atmel Trusted Platform Module, an elliptic curve chip, a SHA-256 authenticator, an encrypted EEPROM, a real time clock, and an ATMega328p for interfacing to other components and modules on the huge prototyping area on the cape.
[Josh] built the CryptoCape in cooperation with Sparkfun, so if you’re not encumbered with a bunch of export restrictions, you can pick one up there. Pic of the board below.
Continue reading “The CryptoCape For BeagleBone”
While the BeagleBone is usually compared to the Raspberry Pi, there are a few features that make the ‘Bone a vastly more capable single board computer. There is a small difference in the capabilities of the processor, but the real power of the BeagleBone comes from the PRUs available: two small cores that give the BeagleBone the hardware equivalent of bitbanging pins. [Texane] has put up two great tutorials for using the PRU in the BeagleBone that should be required reading for every BeagleBone owner.
The first tutorial goes over the capabilities of the PRUs in the BeagleBone and setting up the software environment to develop your own hardware interfaces with the PRU. While writing code for the PRU has usually involved the Beagleboard packages, TI has recently released a version of Code Composer Studio that gives the option to compile C code for the PRU.
[Texane] used this C compiler to rehash the earlier, assembly only PRU program, making development significantly easier. There’s still a bit of inline assembly, and the inline assembly support isn’t as advanced as in GCC, but it’s still much easier than the assembly only variant.
While [Texane] is using the PRU in his BeagleBone to develop something at a synchrotron facility, three are a few things where really fast hardware bitbanging comes in handy: it can be used to make a video card for a vintage mac, or any sort of VGA video card, really. Very cool stuff, especially now that you can write something in C.
The BeagleBone Black has been featured in an improbable number of awesome project, ranging from driving thousands of LEDs for a video display, to 3D printer controller boards. There’s a lot you can do with a tiny Linux board that’s much more powerful than the Raspberry Pi – if you can find one, that is. The BeagleBone Black has been out of stock everywhere for months now, with little sign of when distributors will receive some new stock.
Luckily, the BeagleBone Black is open source. Anyone can make them. Finally, someone did. It’s called Blue Steel, and notwithstanding the inevitable Zoolander references, it’s pretty much the same as the BeagleBone Black we all know and love.
There are a few differences between Blue Steel and the BeagleBone Black: Blue Steel doesn’t have an HDMI output, and the 4GB of on-board Flash featured on the BeagleBone isn’t found on Blue Steel. Still, it has the same processor, same amount of RAM, and the same connectors found in the BeagleBone Black.
You can pre-order Blue Steel here, with the boards eventually shipping at the end of the month. It’s the same price as the BeagleBone Black, not ideal considering the missing HDMI port and Flash storage. Still, you can actually buy it now, something you can’t say about the BeagleBone.
We live in a connected world where social media is ubiquitous and many people feel compelled to share every waking moment with anyone who will listen. In this type of world, wearable computers like Google Glass allow us to share experiences like never before. A Glass user can take photos, record video and audio, or potentially even stream video live on the Internet with the greatest of ease. That might be great for the Glass user, but what about the rest of us? As wearable computing becomes more and more mainstream, people are naturally going to become divided on the issue of privacy. Is it a good thing to have “cyborgs” with wearable computers and cameras constantly at the ready, or is it a privacy nightmare? The cyborg war is coming, and [Julian] has already chosen his side.
It would seem that [Julian] lands on the side of the privacy advocates, based on his “glasshole” script. Glasshole is a relatively simple bash script that relies on some other common network security tools to take care of the heavy lifting. The basic premise relies on the fact that every manufacturer of network interface devices is assigned their own MAC prefix. This is a piece of the MAC address that is unique to that manufacturer.
[Julian’s] script uses a utility called arp-scan to obtain a list of all MAC addresses on a given wireless network. It then loops through each address and compares it to the known Google Glass MAC prefix. If it finds a match, it will make an audible beeping noise to alert the script user. The script then launches aireplay-ng in de-authentication mode. This will send spoofed disassociate packets to the client (in this case the Google Glass device), hopefully forcing them to disconnect from the access point. The script runs continuously, ensuring that once the device reconnects to the network it will get booted off once again. The script is designed to be run on a small Linux computer such as a Raspberry Pi or a BeagleBone black. This way, the user can carry it around with them as a sort of portable defense mechanism.
How do you fit into the cyborg war? Will you stand proudly with your computer on your face for all to see? If so, what kind of countermeasures would you deploy to prevent this type of attack from working on you? If not, what other types of interesting attacks can you think of to keep the cyborgs at bay?
The bragging rights of owning a vintage arcade machine are awesome, but the practicality of it – restoring what is likely a very abused machine, and the sheer physical space one requires – doesn’t appeal to a lot of people. [Jason] has a much better solution to anyone who wants a vintage arcade machine, but doesn’t want the buyer’s remorse that comes with the phrase, “now where do we put it?” It’s a miniaturized Ms. Pacman, mostly scale in every detail.
The cabinet is constructed out of 1/8″ plywood, decorated with printed out graphics properly scaled down from the full-size machine. Inside is a BeagleBone Black with a 4.3″ touchscreen, USB speakers, and a battery-backed power supply.
The control system is rather interesting. Although [Jason] is using an analog joystick, the resistive touch screen monopolizes the ADC on the BeagleBone. The solution to this problem would be to write a driver, or if you’re [Jason], crack the joystick open and scratch away the resistive contact until you have a digital joystick. A nice solution, considering Ms. Pacman doesn’t use an analog joystick anyway.
Pictures over on [Jason]’s G+ page, along with a vertical video that G+ displays properly. Thanks, Google.