Electromechanical Lunar Lander

One of the smash hits of the 1970s arcade was Atari’s Lunar Lander. A landing craft in orbit around a moon would descend slowly towards the surface, and through attitude and thrust controls the player had the aim of bringing it safely in to land. Many a quarter would have been poured into the slot by eager gamers wanting to demonstrate their suitability for astronaut service.

It was to this game that [Chris Fenton] turned when he was looking for inspiration for the 2016 NYCResistor Interactive show, and the result was a Lunar Lander game with a difference, one in which the gameplay was enacted through a physical lander and lunar surface. In this case the moon in question is a papier-mâché-covered inflatable ball, and the lander is a 3D-printed model on the end of a lead screw. Control is provided by an Arduino, with a rough facsimile of the original control panel and a set of microswitches on the model to detect a crash or a safe landing.

The result is a surprisingly playable game, as can be seen from the video below the break.

Continue reading “Electromechanical Lunar Lander”

Hackaday Prize Entry: Analyzing And Controlling Hand Tremors

For the millions of people suffering from Parkinson’s and other causes of hand tremor, there is new hope in the form of [mohammedzeeshan77]’s entry into the Hackaday Prize: a glove that analyzes and controls the tremors.

The glove uses an accelerometer and a pair of flex sensors to determine the position of the hand as it oscillates. A Particle Photon crunches the raw data to come up with the frequency and amplitude of the tremors and uploads it to the cloud for retrieval and analysis by medical staff.

Hand tremors can vary in frequency and severity depending on the cause. Some are barely perceptible movements, and others are life-disrupting shakes. By analyzing the frequency and amplitude of these tremors, doctors can better understand a patient’s condition.

The best part of this glove is that it also provides immediate relief to the wearer by stabilizing the hand. A rapidly spinning super precision gyroscope counteracts the tremor oscillations as it tries to maintain its position. The last time we saw innovation like this, it came with a set of attachments.

Hands-On The Hot New WeMos ESP-32 Breakout

Just two weeks ago our favorite supplier of cheap ESP8266 boards, WeMos, released the long-awaited LOLIN32 ESP-32 board, and it’s almost a killer. Hackaday regular [deshipu] tipped us off, and we placed an order within minutes; if WeMos is making a dirt-cheap ESP32 development board, we’re on board! It came in the mail yesterday. (They’re out of stock now, more expected soon.)

If you’ve been following the chip’s development, you’ll know that the first spin of ESP-32s had some silicon bugs (PDF) that might matter to you if you’re working with deep sleep modes, switching between particular clock frequencies, or using the brown-out-reset function. Do the snazzy new, $8, development boards include silicon version 0 or 1? Read on to find out!

Continue reading “Hands-On The Hot New WeMos ESP-32 Breakout”

Friday Hack Chat: Chip Gracey From Parallax

Learn the ins and outs of multi-core microcontrollers as Chip Gracey leads this week’s Hack Chat on Friday 5/5 at noon PDT. Chip founded Parallax and has now been working for more than a decade on the Propeller 2 design, a microcontroller which has 8 and 16 core options.

When it comes to embedded development, most people think of a single process running. Doing more than one task at a time is an illusion provided by interrupts that stop one part of your program to spend a few cycles on another part before returning. The Propeller 2 has true parallel processing; each core can run its own part of the program. From the embedded engineer’s perspective that makes multiple real-time operations possible. Where things get really interesting is how those cores work together.

Here’s your chance to hear about multi-core embedded first hand, from both the silicon design side and the firmware developer side. Join us for a Parallax Hack Chat this Friday at noon PDT.

Here’s How To Take Part:

join-hack-chatOur Hack Chats are live community events on the Hackaday.io Hack Chat group messaging.

Log into Hackaday.io, visit that page, and look for the ‘Join this Project’ Button. Once you’re part of the project, the button will change to ‘Team Messaging’, which takes you directly to the Hack Chat.

You don’t have to wait until Friday; join whenever you want and you can see what the community is talking about.

Tweezing Diodes

Surface mount diodes are simple enough — all you need to do is make sure you have the anode and cathode in the right order when you place them on the pad when you solder them. These SMD diodes come in industry-standard packages, but do you think there’s an industry-standard way of marking the cathode? Nope, not by a long shot. To solve the problem of figuring out which way the electrons go through his LEDs, [Jesus] built a simple pair of LED tweezers.

The purpose of these tweezers is to figure out which way is up on a LED. To do this, [Jesus] picked up a pair of multimeter and power supply compatible SMD test clips that are sufficiently tweezy. These tweezers come with red and black wires coming out the back, but cutting those leads off, peeling back the insulation and adding a CR2032 battery holder and 220Ω resistor turns these tweezers from a probe into an electrified poker.

To figure out what the arcane symbols on the bottom of an SMD diode mean, all [Jesus] has to do is touch each side of the pair of tweezers to one of the contacts on a LED. If it lights up, it’s that way around. If it doesn’t light up, the battery is dead, or the diode is backwards. It’s a great project, especially since these SMD test clip tweezer things can be had from the usual online retailers for just a few bucks. We would recommend a switch and marking which tweeze is ground, though.

Fail Of The Week: New Hackerspace Burglarized Days Before Opening

Starting up a new hackerspace from the ground up is a daunting task. Before you even think about the fun stuff like tools and a space, you’ve got a ton of social engineering to do. Finding like-minded people with the drive and passion for seeing the project through is a major stumbling block where many projects falter. If you get past that, then figuring out a corporate structure and getting funds together to start building something can be difficult, as can local permits and the endless red tape that always seems to accompany anything seen as new or innovative.

But finally the magic day comes for your group to open the doors on the new hackerspace, perhaps with an open house or some event to bring the community in and maybe rustle up some paying members. It should be a happy occasion, but for a new hackerspace near Houston, the grand opening celebration was thwarted when thieves broke into the space and cleaned out all their tools days before it opened.

Continue reading “Fail Of The Week: New Hackerspace Burglarized Days Before Opening”

Your Next Desktop… QNX?

QNX has a long checkered history as an embedded operating system. QNX was always famous for being a real time operating system with a microkernel architecture. That is, kernel functions run as a set of coordinated tasks instead of as a single piece of code. A recent release of QNX 7 (see video, below) allows it to run on 64-bit desktop computers and [elahav] decided to tackle turning this embedded RTOS into a desktop operating system.

That might sound far-fetched, but QNX is a POSIX-compliant system and has all the features you’d expect in a system like Linux or BSD. It just isn’t aimed at the desktop market and therefore doesn’t have a lot of tools for running the desktop. QNX isn’t the kind of RTOS you’ll find on an Arduino. It is more common in things like automobile systems (for example, it runs General Motor’s OnStar system).

He started with a mini ITX board and installed QNX. Usually, you develop for an embedded system on a workstation and then just ship the code over to the target system, but [elahav] took the time to get a build system working on the target. There was one problem. The built-in vi editor was primitive by modern standards. He is usually an emacs user, but even vim would be better than the “stock” vi. While an emacs port would be possible, it would also require porting over a lot of libraries, so his first project was to get the vim source code to compile.

Turned out not to be as easy as he had hoped. The build system expected certain GNU tools that didn’t exist yet (although standard versions of the tools, like grep, did exist). So he had to figure out how to cross compile vim. In retrospect, [elahav] decided he should have just ported the GNU tools first. He did have to remove some old code from vim that was aimed at an older version of QNX.

Continue reading “Your Next Desktop… QNX?”