Lockheed Wants To Build The Next Lunar Lander

The United States is going back to the moon, and it’s happening sooner than you would think. NASA is going back to the moon in 2024, and they might just have the support of Congress to do so.

Getting to the moon is one thing, and since SpaceX launched a car to the asteroid belt, this future of boots on the moon after Apollo seems closer than ever before. But what about landing on the moon? There’s only ever been one Lunar Lander that has taken people down to the moon and brought them back again, and it’s doubtful that design will be used again. Now, Lockheed has their own plan for landing people on the moon, and they might be able to do it by 2024.

Continue reading “Lockheed Wants To Build The Next Lunar Lander”

Bike Computer Exploration Uncovers A Hidden Android

As a happy side-effect of the smartphone revolution, the world is now awash with tiny computers that are incredibly cheap thanks to the nearly unfathomable volumes in which their components are manufactured. There wouldn’t be a $10 Raspberry Pi Zero if the billions of smartphones that were pumped out before it hadn’t dropped the cost of the individual components to literal pennies. That also means that smartphone hardware, or at least systems that are very close to it, have started to pop up in some unexpected places.

When [Joshua Wise] recently took ownership of a Wahoo ELEMNT BOLT bike computer, he wondered how it worked. With impressive list of features such as Internet connectivity, GPS mapping, and Bluetooth Low Energy support, he reasoned the pocket-sized device must have some pretty decent hardware under the hood. With some poking and prodding he found the device was powered by a MediaTek SoC and incredibly had a full-blown install of Android running in the background.

So how does one find out that their lowly bike computer is essentially a cleverly disguised smartphone? If you’re [Joshua], you listen to who it’s trying to talk do when doing a firmware update over the Internet. He used mitmproxy running between his Internet connection and a WiFi access point setup specifically for the BOLT, from there, he was able to see all of the servers it was connecting to. Seeing the device pull some data down from MediaTek’s servers was a pretty good indication of whose hardware was actually inside the thing, and when it ultimately downloaded some Android .apk files from the Wahoo website, it became pretty clear what operating system it was running underneath the customized user interface.

Further examination of the Bolt’s software brought to light a few troubling issues. It turned out that the firmware made extensive use of Apache-licensed code, for which no attribution was given. [Joshua] contacted the company and was eventually referred to the Wahoo’s CEO, Chip Hawkins. Refreshingly, Chip was not only very interested in getting the licensing issues sorted out, but even had some tips on hacking and modifying the device, including how to enable ADB.

Before the publication of this article, we reached out to Chip Hawkins (yes, he really does respond to emails) for a comment, and he told us that not only has he made sure that all of the open source packages used have now been properly attributed to their original authors, but that his team has been providing source code and information to those who request it. He says that he’s been proud to see owners of his products modifying them for their specific needs, and he’s happy to facilitate that in any way that he can.

Open source license compliance is a big deal in the hacking community, and we’ve seen how being on the wrong side of the GPL can lead to lost sales. It’s good to see Wahoo taking steps to make sure they comply with all applicable licences, but we’re even more impressed with their positive stance on customers exploring and modifying their products. If more companies took such an enlightened approach to hacking, we’d all be a lot better off.

[Thanks to Roman for the tip.]

Reverse Engineering An Insulin Pump With An SDR And Decapping

Insulin pumps are a medical device used by people with diabetes to automatically deliver a measured dose of insulin into their bloodstream. Traditionally they have involved a canula and separate connected pump, but more recent models have taken the form of a patch with a pump mounted directly upon it. When [Pete Schwamb]’s daughter received  one of these pumps, an Omnipod, he responded to a bounty offer for reverse engineering its RF protocol. As one of the people who helped create Loop, an app framework for controlling insulin delivery systems, he was in a particularly good position to do the work.

The reverse engineering itself started with the familiar tale of using an SDR to eavesdrop on the device’s 433MHz communication between pump and control device. Interrogating the raw data was straightforward enough, but making sense of it was not. There was a problem with the CRC algorithm used by the device which had a bug involving a bitwise shift in the wrong direction, then they hit a brick wall in the encryption of the data. Hardware investigation revealed a custom chip in the device, and there they might have stalled.

But the international reverse engineering community is not without resources and expertise, and through the incredible work of a university researcher in the UK (whose paper incidentally includes a pump teardown) they were able with an arduous process supported by many people to have the firmware recovered through decapping the chip. Even once they had thus extracted the encryption code and produced their own software their problems were not over, because communication issues necessitated a much better antenna on the RileyLink Bluetooth bridge boards that translated Bluetooth from a mobile phone to 433 MHz for the device.

This precis doesn’t fully encapsulate the immense amount of work over several years by a large group of people with some very specialist skills that reverse engineering the Omnipod represents. To succeed in this task is an incredible feat, and makes for a fascinating write-up.

Thanks [Alex] for the tip.

3D Printing With Multiple Soluble Filaments

Complex 3D-printed designs often require the use of an automatically generated support structure around them for stability. While this enables some truly incredible results, it adds considerable time and cost to the printing process. Plus there’s the painstaking process of removing all the support material without damaging the object itself. If you’ve got a suitably high-end 3D printer, one solution to this problem is doing the supports in a water soluble filament; just toss the print into a bath and wait for the support to dissolve away.

But what if you’re trying to print something that’s complex and also needs to be soluble? That’s precisely what [Jacob Blitzer] has been experimenting with recently. The trick is finding two filaments that can be printed at the same time but are dissolved with two different solutions. His experimentation has proved it’s possible to do with consumer-level hardware, but it isn’t easy and it’s definitely not cheap.

You might be wondering what the possible application for this technique is. For [Jacob], he wanted to be able to print hollow molds in complex geometric shapes that would ultimately be filled with concrete. The molds required extensive internal supports that would have been all but impossible to remove if they weren’t printed in a soluble filament. But he also wanted to be able to dissolve the mold once the concrete inside had cured. So he needed one easy to dissolve filament for the supports, and a harder to dissolve one for the actual mold.

For the mold itself, [Jacob] went with High Impact Polystyrene (HIPS) which can be dissolved with an industrial degreaser called Limonene. It’s expensive, and rather nasty to work with, but it does an excellent job of eating away the HIPS so that’s one problem solved. Finding a water-soluble filament for the supports that could be printed at similar temperatures to the HIPS took months of research, but eventually he found one called HyroFill that fit the bill. Unfortunately, it costs an eye-watering $175 USD per kilogram.

So you have the filaments, but what can actually print them at the same time? Multi-material 3D printing is a tricky topic, and there’s a few different approaches that have been developed over the years. In the end, [Jacob] opted to go with the FORMBOT T-Rex that uses the old-school method of having two individual hotends and extruders. It’s the simplest method conceptually, but calibrating such a machine is notoriously difficult. Running two exotic and temperamental filaments at the same time certainly doesn’t help matters.

After all the time, money, and effort put into the project (he also had to write the software that would create the 3D models in the first place) [Jacob] says he’s not exactly thrilled with the results. He’s produced some undeniably stunning pieces, but the failure rate is very high. Still, it’s fascinating research that appears to be the first of its kind, so we’re glad that he’s shared it for the benefit of the community and look forward to seeing where it goes from here.

Emulate A Paper Tape, To Be Life And Soul Of The Cyphercon Party

The recent Cyphercon badge featured a very clever integrated paper tape reader, and had the hidden feature of a party mode in which all its lights would flash. When [Gigawatts] discovered this after the conference had ended, it was too late to find the tape to activate it. The solution? Build a tape emulator with a microcontroller hooked into the badge’s tape sensors to send the data directly into it.

It was a Tweet from [AND!XOR] that revealed the flashing hidden mode, and in case you missed it you can find all about the amazing badge in our review. The emulator takes a TI Stellaris LaunchPad LM4F120 and a set of jumper wires soldered directly to the jumper wires on the badge’s reverse. Hex values are created from a tape through an in-browser HTML page with a checkbox interface, a sketch converts the hex to tape, and the badge runs the code. The GitHub readme includes a description of the paper tape format as well as some sample tapes including a badge reset one for when you tire of party mode.

Most of us weren’t lucky enough to make it to Cyphercon and receive a badge. But we’re still impressed by the ingenuity of the badge’s designer, and by the complexity of the CTF game of which it formed a part.

Hackaday Links Column Banner

Hackaday Links: April 28, 2019

Lego is releasing a series of Braille bricks. As near as we can tell, these Braille bricks are standard 2 x 4 bricks, with studs corresponding to Braille letters on the top. There are also screen/pad printed legends on top. I don’t mean to be a downer, but why, exactly, is this being created now? Did it really take fifty years for someone to say, ‘hey, if you don’t put some studs on top of a brick, it becomes Braille?’ How is this not already a thing? This isn’t me being facetious — how did it take so long for this to be invented?

KiCon is this weekend, so here’s a tip for everyone in Chicago right now: get a hot dog. Don’t put ketchup on it, or else someone will shoot you.

KiCon and Moogfest in one weekend? Yes, and that means new toys. The Matriarch is Moog’s latest synthy boi and the apparent successor to last year’s Moog Grandmother. The Matriarch is a four-note paraphonic synth that is semi-modular; no, you don’t need patch cables to make noises, but there are ninety-odd patch points for modular fun. It’s two grand, which is getting up there in the synth game. If only Radio Shack were still around and sold Moog synths…

We’re all aware that Russia launches rockets out of Baikonur cosmodrome, and the first stages eventually make their way onto the steppes of Kazakhstan. The locals, few there are, end up recycling these rockets, scrapping them, and sometimes taking space tourists and photojournalist out to the crash site of these boosters. Russia has other spaceports, and now we’re getting pictures of booster crashes from the frozen north. These rockets came from the Plesetsk cosmodrome and fell in the boreal forests near Arkhangelsk where hunters discovered them. Yes, these boosters are carcinogenic, but that’s what you do when a few tons of aluminum and titanium fall in your backyard.

No spoilers, but oh man the after-credits scene in Endgame was hilarious.

A Retro Handheld Console As They Used To Be Made

Before there were Nintendo Switches, there were Game Boys. And before that there were all the successive generations of Game Boys and other consoles right back to the Game and Watch, and then those handheld Simon and Space Invaders games of the late 1970s. These devices typically packed a 4-bit microcontroller and an array of discrete LEDs, and movements in-game were simply created by alternate LEDs on the game field being flashed.

The TeleBall from [sv2002] is a handheld game in the vein of those early handheld games, in that it features a matrix of LEDs as a screen on which it can display simple games. So far it plays Breakout, and Tennis for Two, which might seem odd were it not for its built-in radio for two-person play with two consoles.

Inside the TeleBall is an Arduino Nano, a Maxim display driver for the LED matrix, and the familiar Nordic Semiconductor RF module. Control is via a potentiometer, and everything sits in a smart 3D-printed case. Everything is open-source, so should you wish to have your own you can head over to the project’s web site and grab all the files. You can watch it in action playing tennis with two consoles in the video below the break.

The original Tennis for Two created in 1958 was an oscilloscope game using an analogue computer, and is credited as the first video game created purely for entertainment purposes. If you’d like to see a recreation of it, we covered one over a decade ago.

Continue reading “A Retro Handheld Console As They Used To Be Made”