What is this, 2009? Let’s face facts though – smartphones are computing powerhouses now, but gaming on them is still generally awful. It doesn’t matter if you’ve got the horsepower to emulate any system from the last millennium when your control scheme involves awkwardly pawing away at glass when what you need is real buttons. You need a real controller, and [silver] has the answer – a 3D printed phone mount for the original Xbox Controller.
It’s more useful than it initially sounds. The original Xbox used USB 1.1 for its controllers. With a simple OTG cable, the controllers can be used with a modern smartphone for gaming. The simple 3D printed clamp means you can have a mobile gaming setup for pennies – old controllers are going cheap and it’s only a couple of dollars worth of filament. The trick is using the controller’s hilariously oversized memory card slots – for some reason, Microsoft thought it’d be fun to repackage a 64MB flash drive into the biggest possible form factor they could get away with. The slots also acted as a port for online chat headsets, and finally in 2017, we’ve got another use for the form factor.
For the real die-hard purists, [silver] also shares a photo of a similar setup with a Nintendo 64 controller – including a big fat USB controller adapter for it, hanging off the back. Not quite as tidy, that one.
It’s a neat little project – we love to see useful stuff built with 3D printers. If you’ve been looking for something functional to print, this is it. Or perhaps you’d like to try these servo-automated 3D printed light switches?
The Internet of Things is fun to play with; there’s all manner of devices to automate and control remotely. It can be sketchy, though — make a mistake when coding your automatic plant watering system and you could flood your house. Make a mistake with a space heater and you could burn it down. Combine these risks with the fact that many people live in rental properties, and it can be a difficult proposition to bring the Internet of Things to your home.
[Suyash] came up with a way around this by building 3D printed light switch covers that add servo control. It’s a great solution that it doesn’t require the modification of any mains wiring, and interfaces with the standard switches in the normal way. It makes it a lot safer this way — there are municipal wiring codes for a reason. This is a great example of what you can do with a 3D printer, above and beyond printing out Yoda heads and keychains.
The backend of things is handled by the venerable ESP8266, with [Suyash]’s custom IoT library known as conduit doing the heavy lifting. The library is a way to quickly build IoT devices with web interfaces, and [Suyash] claims it’s possible to be blinking an LED from the cloud within 5 minutes using the tool.
The concept behind DIY electronic drum kits is fairly simple — small piezoelectric elements are used to generate a voltage when the drumpads are struck. That’s easy enough, but the mechanical design can be a difficult problem to approach. To solve that, [ryo.kosaka.10] decided to design an E-drum pad made with paper & 3D printed parts.
As far as E-drum triggers go, it follows the basic rules — a piezo element used as a trigger with some foam used for damping. For the striking surface, a Tama-brand mesh drum head is used. Being an off-the-shelf drum head, it has a good feel and playability. But the shell is where the creativity really shines through. While the top and bottom parts are 3D printed in the usual way, the main shell of the drum is made with several layers of thick paper laminated together with glue. This creates a surprisingly strong, sturdy shell and is also much faster and less wasteful than waiting for a similar part to 3D print.
To round out the guide, instructions are given on how to wire the piezo triggers up for either a regular E-drum sound module or an Arduino. It’s a nice touch, as those inexperienced with E-drums may not be entirely familiar with how they work – this way, anyone can give the project a try.
A garage door opener is a pretty classic hack around these parts. IR, Bluetooth, WiFi, smartphone controlled, web interfaces — we’ve seen it all. But if you want to keep track of people going in and out, you need some way of logging what’s happening. You could go ahead and roll up your own SQL based solution, tied into a custom web page. But there’s an easier way; you can build a garage door opener that logs events to Google Drive.
[WhiskeyTangoHotel] was looking for an ESP8266 project, and a garage door opener seemed just the ticket. It’s simple enough to code up, and control over WiFi comes in handy. Interfacing with the garage door was simple enough — the existing opener uses a simple push button, which is easily controlled by wiring up a relay to do the job. Logging is as simple as having the ESP8266 send requests to IFTTT which is set up to make posts to a Google Sheet with status updates.
The project is fairly basic, but there’s room for expansion. By using separate Maker Channel triggers on IFTTT, different users of the garage door could be tracked. It would also be easy to add some limit switches or other sensors to detect the door’s position, so it can be determined whether the door was opened or closed.
Emulators are a great way to reminisce about games and software from yesteryear. [Jorj Bauer] found himself doing just that back in 2002, when they decided to boot up Three Mile Island for the Apple II. It played well enough, but for some reason, crashed instantly if you happened to press the ‘7’ key. This was a problem — the game takes hours to play, and ‘7’ is the key for saving and restoring your progress. In 2002, [Jorj] was content to put up with this. But finally, enough was enough – [Jorj] set out to fix the bug in Three Mile Island once and for all.
The project is written up in three parts — the history of how [Jorj] came to play Three Mile Island and learn about Apple IIs in the first place, the problem with the game, and finally the approach to finding a solution. After first discovering the problem, [Jorj] searched online to see if it was just a bad disk image causing the problem. But every copy they found was the same. There was nothing left for it to be but problem in the binary.
There’s a lot of reasons you might want to emulate the keyboard on your Commodore 64. The ravages of time and dust may have put the original keyboard out of order, or perhaps you need to type in a long program and don’t fancy pecking away with the less-than-stellar feedback of the standard keys. [podstawek] has come up with the solution: a Commodore 64 keyboard emulator that works over serial.
It’s a simple concept, but one that works well. A Python script accepts incoming keypresses or pre-typed text, then converts them into a 6-bit binary code, which is sent to an Arduino over the serial connection. The Arduino uses the 6-bit code as addresses for an MT8808 crosspoint switch.
The MT8808 is essentially an 8×8 matrix of controllable switches, which acts as the perfect tool to interface with the C64’s 8×8 keyboard matrix. Hardware wise, this behaves as if someone were actually pressing the keys on the real keyboard. It’s just replacing the original key switches with an electronic version controlled by the Arduino.
[podstawek] already has the setup working on Mac, and it should work on Linux and Windows too. There’s a little more to do yet – modifying the script to allow complex macros and to enable keys to be held – so check out the Github if you want to poke around in the source. Overall it’s a tidy, useful hack to replace the stock keyboard.
It’s an ingenious trick — a Python script goes through the commit history of a repository, looking at every string of text greater than 20 characters, and analyzing its Shannon entropy. This is a mathematical way of determining if it looks like a relatively random string of numbers and letters. If it has high entropy, it’s probably a key of some sort.
Sharing source code is always a double-edged sword for security. Any flaws are out for all to see, and there are both those who will exploit the flaws and those who will help fix them. It’s a matter of opinion if the benefits outweigh the gains, but it’s hard to argue with the labor benefits of getting more eyes on the code to hunt for bugs. It’s our guess though, that a lot of readers have accidentally committed secret keys in a git repository and had to revert before pushing. This tool can crawl any publicly posted git repo, but might be just as useful in security audits of your own codebase to ensure accidentally viewable keys are invalidated and replaced.