He started by exporting the elevation data of Portland using software called QGIS, a free opensource geographical information system — it’s extremely powerful software, but takes a bit to learn. Luckily, [Scott] made a tutorial for us. All you need to do is add the road data, put all the slices into an illustrator file, clean up some of the files, and you’re ready to start laser cutting.
He used 1/8th thick sheets of Baltic birch plywood, a staple material around laser cutters because it burns quickly and easily and is very flexible, which means that it’s harder to break. The map measures 12″ x 24″ — but once it’s laser cut, be ready for a multi-leveled jigsaw puzzle! The small pieces of elevation data can be very tricky!
There are a few classic video games that rely on vector graphics and special monitors. Asteroids is incomplete if you’re not playing it in its original arcade format. The same goes with Tempest, Lunar Lander, and the 1983 Star Wars arcade game.Emulation of these games is possible, even with MAME, but the display – like every display you can buy today – is still rasterized. The solution to this problem is to create a vector display output for MAME that works in conjunction with adapter boards and DACs connected to a monitor.
The build uses a custom board equipped with a Teensy 3.1 microcontroller and a 12-bit DAC to convert XY coordinates sent by MAME to vectors that can be displayed on any XY monitor. This, of course, requires a patch to MAME, which the maintainers rejected as being an, “unacceptably hacky way to achieve the intended result.” It does achieve the intended result, though: allowing dozens of vector games playable on whatever monitor supports vector graphics.
So far, [Trammell] and [Adelle] have gotten their system working on Vectrex consoles, analog oscilloscopes set to XY mode, and vectorscopes that litter every broadcast station and surplus shop. Check out [Trammell] and [Adelle]’s talk, and if you want to build the V.st vector display driver, the board is available from OSHPark.
In recent weeks, the FAA has solicited input from hobbyists and companies in the ‘drone’ industry, produced rules and regulations, and set up a registration system for all the quadcopters and flying toys being gifted over the holiday season. Whether or not the FAA is allowed to do this is a question being left to the courts, but for now, the FAA has assuredly killed a hobby for more than six million people. The FAA has introduced an updated Temporary Flight Restriction (TFR) for a 30-mile radius around Washington, DC.
Previously, there had been a blanket ban on drones, UAS, and model aircraft within a 15-mile radius of a point inside Reagan National Airport. This point covered the District of Columbia proper, and the suburbs of Bethesda, College Park, and Alexandria – basically, everything inside the beltway, and a mile or two beyond. The new flight restriction for drones covers a vastly larger area – all of the DC metro area, Annapolis, half of Baltimore, and all of northern Virginia. This area encompasses a population of more than six million people.
The DC metro area has, since 9/11, become some of the most complex airspace in the entire country. There are several military bases, Aberdeen proving grounds, the US Naval academy, and of course the White House, Capitol building, and the Pentagon. Even commercial airliners are subject to some very interesting regulations. For the same reason general aviation shuts down in southern California every time the president visits LA, you simply can’t fly model aircraft within the beltway; it’s a security measure, and until now, flying clubs in the DC area have dealt with these restrictions.
The new TFR has effectively shuttered more than a dozen flying clubs associated with the Academy of Model Aeronautics. DCRC, a club with a field in the middle of some farmland in Maryland, has closed down until further notice. The Capital Area Soaring Association has also closed because of the TFR.
Although called a Temporary Flight Restriction, this is a rule that will be around for a while. The FAA says this restriction is here for good.
If DC motors are the “Hello World” of making things move, servo motors are the next logical step. [Simone Giertz] is following this exact path with the Wake-up Machine and her newly released Chopping Machine. [Simone] discovered that the best way to wake up in the morning is to be repeatedly slapped in the face by a robot. The Wake-up Machine was custom designed to do exactly that. Who could sleep through being repeatedly slapped in the face? A beefy gearmotor from ServoCity spins a Halloween prop arm round and round, providing “refreshing” slaps.
The system is triggered by an alarm clock. The clock’s alarm output is connected to an Arduino Uno. The Uno then activates a relay, which spins up the motor. [Simone] realizes that she could have skipped the Arduino here, but it was the path of least resistance in for this project. If the slapping hand isn’t enough to get you going, the Wake-up machine does have a secret weapon: It may just grab your hair, turning a video shoot into a painful ordeal.
Simone’s latest project is the Chopping Machine. ServoCity must have liked her first videos, as they’ve sponsored her for this project. The machine consists of two knives that … well, chop. Two high-powered servos are controlled by an Arduino Nano. The servos raise spring-loaded knives, which then drop down, chopping vegetables, fingers, and anything else in their path. The whole machine is built with aluminum channel stock, and a huge wooden cutting board. Of course, just building the machine wasn’t enough. [Simone] filmed a parody infomercial for any perspective Chopping Machine buyers, and to put fear in the heart of anyone named Chad.
Click past the break for a couple of [Simone’s] vlogs describing the machines.
[Alexander Graf] gave an absolutely hilarious talk at 32C3 about the security flaws he found in cable modems from two large German ISPs. The vulnerability was very serious, resulting in remote root terminals on essentially any affected cable modem, and the causes were trivial: unencrypted passwords in files that are sent over TFTP or Telnet to the modems, for instance.
While [Alexander] was very careful to point out that he’d disclosed all of these vulnerabilities to the two German cable ISPs that were affected, he notably praised one of them for its speedy response in patching up the holes. As for the other? “They’d better hurry up.” He also mentions that, although he’s not sure, he suspects that similar vulnerabilities are present in other countries. Oh dear.
A very interesting point in the talk is the way that [Alexander] chose to go about informing the cable ISPs. Instead of going to them directly and potentially landing himself in jail, he instead went to the press, and let his contacts at the press talk to the ISPs. This both shielded him from the potential initial heat and puts a bit of additional pressure on the ISPs to fix the vulnerability — when the story hits the front page, they would really like to be ahead of the problem.
There’s even a bone for you die-hard hardware hackers out there who think that all of this software security stuff is silly. To get the modem’s firmware in the first place, at minute 42 of the talk, [Alexander] shows briefly how he pulled the flash chip off the device and read it into his computer using a BeagleBone Black. No JTAG, no nothing. Just pulling the chip off and reading it the old-fashioned way.
If you’ve got an hour, go watch [Alexander]’s talk. It’s a fun romp through some serious vulnerabilities.
Measuring the body’s electrical signals is a neat trick… if you can get your equipment dialed in enough to establish dependable measurements. The technique is called Surface ElectroMyography (SEMG) though you’ll hear many call this ECG. They’re essentially the same technology; the Electro CardioGraph instruments monitor the activity of the heart while SEMG Instruments monitor electrical signals used to control other muscles. Both types of hardware amount to an instrumentation type amplifier and some form of I/O or display.
This topic has been in my back pocket for many months now. Back in May we Hackaday’ites descended on New York City for the Disrupt NY Hackathon event. We arrived a day or so early so that we might better peruse the Korean BBQ joints and check out the other electronics that NY has to offer. On Saturday we gathered around, each shouting out the size of his or her t-shirt preference as we covered up our black Hackaday logo tees with maroon maroon ones (sporting the Hackaday logo of course) for a 24-hour craze of hardware hacking.
There were two individuals at our tables who were both hacking away on hardware to measure the electrical field produced by the body’s muscles in some form or another. The electrical signals measured from the skin are small, and need careful consideration to measure the signal despite the noise. This is a fun experiment that lets you work with both Instrumentation Amplifiers and OpAmps to achieve a usable signal from the movement of your body.
GoPro cameras are getting pretty sophisticated, but they can’t yet read minds: you have to tell them when to start recording. Fortunately, they can be remote controlled very easily over a WiFi connection, and this neat tutorial from [euerdesign] shows how you can use an ESP8266 to build a very cheap GoPro remote. The idea is simple: you press a button connected to the ESP8266, which is programmed with the details of the ad hoc WiFi network that the GoPro creates. It then posts a simple URL request to the GoPro, which starts recording. Total cost? A few bucks for the ESP8266, a button and a few bits of wire.
What the remote does is defined by the URL you set it to request: pretty much all of the features of a GoPro can be controlled this way. If you wanted to get fancy, you could expand this to create a multiple button remote that could do other things, such as change frame rate or start streaming to the interwebs in a situation where you don’t want to risk a smartphone or something equally expensive.