Gyroman Walks With Just One Motor

May 8, 2016 by Elliot Williams 11 Comments

For some reason, we seem to really want our robots to walk on two legs like we do. And this despite how much the robots themselves want to be made out of motors, which match up so naturally with wheels. The result is a proliferation of inventive walking mechanisms. Here’s another.

Gyroman is a 3D printed gyroscope with legs. The gyroscope is geared down to lift one leg and then the other. First-semester physics, that we still find a little bit magical, makes the gyro precess and the robot turns a bit. Time these just right and it walks. See the video below for a demo. (Admittedly, Gyroman looks like he’s had a bit too much to drink as he winds down.)

Continue reading “Gyroman Walks With Just One Motor” →

Thinking Of You: IoT Style

May 7, 2016 by Elliot Williams 9 Comments

Do you have loved ones who live far away? Or do you just want an interesting starter ESP8266 project to get your feet wet? If the answer to either of these questions is “yes”, we’ve got just the project for you. [Craig Lindley] built a “thinking of you” button-and-LED display device that helps people keep in touch, in a very simple way.

We like the minimalism of the design. One party presses their button, electrons flow, WiFis WiFi, data travels through a set of tubes, and an LED far away glows a pre-arranged color. The other side can signal back to say “hi” as well. It’s a cute item to have on your desk, or wherever you spend the most time. If you’re new to all of this, you can hardly beat the circuit for its simplicity.

Yeah, you could totally just send the other person a text message or an e-mail. But then you don’t get an excuse to play around with NodeMCU, and it just lacks the personal hacker touch. The code is available in a zip file here, and if you want to stay in touch with someone other than [Craig]’s sisters, you’ll probably want to customize it a bit.

Fail Of The Week: ESP8266 Heats Temperature Sensor

May 6, 2016 by Elliot Williams 61 Comments

[Richard Hawthorn] sent us in this interesting fail, complete with an attempted (and yet failed) clever solution. We love learning through other people’s mistakes, so we’re passing it on to you.

First the obvious-in-retrospect fail. [Richard] built a board with a temperature sensor and an ESP8266 module to report the temperature to the Interwebs. If you’ve ever put your finger on an ESP8266 module when it’s really working, you’ll know what went wrong here: the ESP8266 heated up the board and gave a high reading on the temperature sensor.

Next came the clever bit. [Richard] put cutouts into the board to hopefully stop the flow of heat from the ESP8266 module to the temperature sensor. Again, he found that the board heats up by around four degrees Celcius or nine degrees Farenheit. That’s a horrible result in any units.

What to do? [Richard’s] first ideas are to keep hammering on the thermal isolation, by maybe redoing the board again or adding a heatsink. Maybe a daughterboard for the thermal sensor? We can’t see the board design in enough detail, but we suspect that a flood ground plane may be partly to blame. Try running thin traces only to the temperature section?

[Richard]’s third suggestion is to put the ESP into sleep mode between updates to reduce waste heat and power consumption. He should be doing this anyway, in our opinion, and if it prevents scrapping the boards, so much the better. “Fix it in software!” is the hardware guy’s motto.

But we’ll put the question to you ~~electronics-design backseat drivers~~ loyal Hackaday readers. Have you ever noticed this effect with board-mounted temperature sensors? How did you / would you get around it?

Fail of the Week is a Hackaday column which celebrates failure as a learning tool. Help keep the fun rolling by writing about your own failures and sending us a link to the story — or sending in links to fail write ups you find in your Internet travels.

35 MPH NERF Darts!

May 5, 2016 by Elliot Williams 15 Comments

Did you know the muzzle velocity of a NERF dart out of a toy gun? Neither did [MJHanagan] until he did all sorts of measurement. And now we all know: between 35 and 40 miles per hour (around 60 km/h).

First, he prototyped a single beam-break detector (shown above) and then expanded his build to two in order to get velocity info. A Propeller microcontroller took care of measuring the timing. Then came the gratuitous statistics. He took six different darts and shot them each 21 times, recording the timings. Dart #3 was the winner, but they all had similar average speeds. You’re not going to win the office NERF war by cherry-picking darts.

Anyway, [MJ] and his son had a good time testing them out, and he thinks this might make a good kids’ intro to science and statistics. We think that’s a great idea. You won’t be surprised that we’ve covered NERF chronographs before, but this implementation is definitely the scienciest!

Thanks [drudrudru] for the tip!

Reverse Engineer Your Robot Lawnmower

May 4, 2016 by Elliot Williams 21 Comments

Your home is your castle, and you are king or queen of all you survey. You’ve built your own home-automation system from scratch. Why would you possibly settle for the stock firmware in your robotic lawnmower? [Daniel Wiegert] wouldn’t either, so in Project Landlord he has started to reverse-engineer it.

You can hardly blame him. The Worx Landroid‘s controller board uses an NXP LPC1768 ARM Cortex-M3, and the debug pins are labelled on the backside. The manufacturer didn’t protect the flash memory. It’s just begging to have its firmware dumped. So far, [Daniel] has managed to both brick and unbrick the device, and has completely mapped the controller’s pinout, so he’s on his way to complete control.

Right now, he’s got a working proof-of-concept firmware on his GitHub that’s able to drive the machine around a little bit and set the brakes. It’s running FreeRTOS, and [Daniel] is looking for other people to get in on the project. He’s done the hard initial work, so get in there and reap the rewards! Just don’t neglect to remove the blade before custom firmware.

Will custom firmware in a robotic lawnmower change the world? Probably not. But it is awesome, and will certainly make a difference in the lives of people whose robot mowers continually get stuck behind the hydrangeas.

The HackadayPrize2016 is Sponsored by:

Your Quadcopter Has Three Propellers Too Many

May 4, 2016 by Elliot Williams 50 Comments

While studying failure modes for quadcopters, and how to get them safely to the ground with less than a full quad of propellers, a group of researchers at the Institute for Dynamic Systems and Control at ETH Zurich came up with a great idea: a mode of flight that’s like the controlled spinning descent of a maple seed.

The Monospinner runs on the absolute minimum number of moving parts. Namely, one. Even a normal helicopter has a swash plate for adjustable blade pitch, and a tail rotor to keep it from spinning. Give up the idea that you want to keep it from spinning, and you can achieve controlled flight with a lot less. Well, one motor and a whole lot of math and simulation.

The Monospinner is carefully weighted so that it’s as stable as possible while spinning, but so far it’s unable to spin itself up from a standstill. In initial tests, they attached it to a pivot to help. The best part of the video (below) is when the researcher throws it, spinning, into the air and it eventually stabilizes. Very cool.

Continue reading “Your Quadcopter Has Three Propellers Too Many” →

I Am Satoshi Nakamoto

May 3, 2016 by Elliot Williams 74 Comments

OK, you got me. I’m not. Neither is Dorian Nakamoto, pictured above, and neither is this [Craig White] guy. Or at least, his supposed proof that he is “Satoshi” doesn’t stand up to scrutiny. Indeed, you can re-create it yourself and pretend to be “Satoshi” too.

If you haven’t been following along, “Satoshi Nakamoto” is the person or group of people who invented Bitcoin, and who holds a decent fortune’s worth of the currency. He’s been exceedingly careful at keeping his identity secret. So much so, that upon hearing another “We Found Satoshi” story in the news, we actually laughed at our wife this morning. But then it was picked up by the BBC and is forthcoming in the Economist. Serious journalism.

Well, if you read the BBC piece, they note that “Security expert Dan Kaminsky said the procedure was almost ‘maliciously resistant’ to validation.” Hint: If Dan “DNSSEC” Kaminsky can’t verify a signature, there’s a good chance it’s not the real deal.

The really embarrassing part is that this [Craig White] character claimed to be Satoshi in December 2015. If he actually were Satoshi, who is probably a cryptographic genius, do you think it would take him five months to figure out a cryptographically sound way of proving his identity? Nope.

So here’s how he did it, according to [Patrick McKenzie]’s GitHub, linked above. There is a hashed secret out there that only “Satoshi” knows. Hashes are one-way functions; they produce a number that’s easy to calculate if you know the original data, but devilishly hard to work from the hash backwards to get the data out. This hashed value is public, and part of the blockchain, so we can be pretty sure that it hasn’t been altered.

[Craig] claimed to have some text from Sartre hashed with “Satoshi’s” key, and that this proves his identity. But instead of providing the hash of the Sartre text, [Craig] apparently substituted a hash from the blockchain. When this supposed Sartre hash is validated against the blockchain, of course, it works. In short, he swapped hashes, and people failed to notice.

So I’m not “Satoshi”, and neither is this guy. Who is? The mystery continues. And given how careful “Satoshi” has been so far, it’s likely to remain so for a long while. But one thing’s for sure, when “he” does choose to reveal himself, it won’t be difficult to verify. After all “Satoshi” knows “Satoshi’s” password.

Image via the BBC, of another guy who isn’t “Satoshi”.

(Late Edit: Here’s another really nice writeup, this one by [ErrataRob].)