__ __ __ ___ / // /__ _____/ /__ ___ _ / _ \___ ___ __ / _ / _ `/ __/ '_/ / _ `/ / // / _ `/ // / /_//_/\_,_/\__/_/\_\ \_,_/ /____/\_,_/\_, / retro edition /___/Now optimized for embedded devices!!
| About | Successes | Retrocomputing guide | Email Hackaday |
the ‘mars rover‘ is a telepresence robot made by robo-hobbiest kerwin lumpkins. he created it as a mock up of the real mars rover, but on a more down-to-earth scale.
controlling the tank is a general purpose robotics development board, also designed by kerwin. the darc board takes input from infrared and sonar sensors, controls locomotion and camera aim, and has basic ability to make decisions based on a combination of its immediate environment and operator commands which are sent to the robot over a rf modem connection.
here’s what makes this cool. if the robot detects that a given command would place in in jeopardy (such as running into a kitchen cabinet) it will abort and send back a warning to the control station.
to better simulate a real mars rover system, kerwin uses some tivo-like time shift software to delay the incoming video signal 5 seconds. this makes controling the rover more difficult and is why onboard decision making is a must for your own martian explorer project.
[TheBserk] made himself a set of auto-locking and auto-retracting hidden blades inspired by those in the game Assassin’s Creed. As you can see in the demo (and build guides) after the break, they work really well. We don’t like the idea of sharpened metal ramming its way past our wrists. But it’s not the first time we’ve seen dangerous arm-mounted hacks.
Reminiscent of Taxi Driver, [TheBserk] uses drawer slides from the local home store for his build. They are cut to length, and modified using springs for the automatic action. There is a lock to keep the blade extended, and a pull-wire to actuate it. Although dangerous, the build is well done. We think someone has mechanical engineering in his future, and possibly a trip to the emergency room.
Build guide part 1
Build guide part 2
[Thanks Kentaro]
According to our CMS calculations (we use WordPress), this is Hackaday’s ten-thousandth published posts. We meant to build a confetti cannon, but we were too busy looking for interesting projects to feature multiple times per day.
We’d like to thank everyone who documents their projects to share what they’ve been up to in basements, garages, or hackerspaces with the ecosystem of hackers around the world. We hope that every time you publish a build log or project summary you think about sending us a link. We’re also grateful for those who find intriguing blog or forum posts and send in a tip even though it’s not their project (we wholeheartedly encourage it).
Our contributors and editors deserve kudos. Over the years a growing band of Hackaday alumni have helped keep the front page of Hackday a place you can count on for interesting uses for otherwise everyday things. You’ve heard many of their names, like [Philip Torrone], [Eliot Phillips], and [Caleb Kraft]. But most of what you see on the front page is the result of the writers sifting through tips and scanning a laundry list of RSS feeds to find new and interesting projects and project ideas. Their contribution is what keeps the front page fresh and new, but we continue to use the royal ‘we’ in our posts because it’s the project being featured that is paramount.
And finally we thank the regular readers, whose participation keeps the lights on, and whose comments build a community. Many started out as lurkers, inspired by the projects featured here until the point that they take the plunge and blink their first LED. The threads in the comments section of each post are the evolutionary ooze that often leads to the next amazing build. Keep reading, keep commenting constructively, and we’ll see you all back here for our 16,383rd post when we fill up these digits with ones.
Thank you.
We managed to spot some of the Revision3 team at CES, and its good to know that we have fans in high places! We took this shot with [Caleb], [Patrick Norton], [James], and [Veronica Belmont]. Unfortunately [Roger Chang] was a little camera shy, so he took the photo for us. Hi-Res Shot is available, as always.
Want to see what’s behind you when riding your sport bike without taking your eyes off the road? They make rear view cameras for that but [Nescioqd] wanted a rear display right in his helmet (PDF). He started by mounting a rear-pointing camera on the back of the bike, powered from the 12V feed for the taillight. On the display side of things he picked up a Myvu Crystal wearable display. This is like a pair of glasses that have small LCD screens were the lenses should be. [Nescioqd] removed one lens and mounted it inside the helmet.
Since the display resides inside the helmet there is some concern about being able to see at night with a bright screen below your eyeball. [Nescioqd] actually ran into the opposite problem at first, bright sunlight makes it difficult to see the image on the LCD screen. He fixed this by picking up a dark tinted helmet visor (the easiest solution) but we’d love to see a photoresistor used to regulate the backlight level.
It would be interesting to see both screens used, with rear-view on one side and an instrument display on the other.
