Hackaday Prize Entry: Octo, The Robotic Walker

Walkers like the Strandbeest are favorites due in part to their smooth design and fluid motion, but [Leandro] is going a slightly different way with Octo, an octopodal platform for exploring rough terrain. Octo is based on the Klann linkage which was developed in 1994 and intended to act as an alternative to wheels because of its ability to deal with rough terrain. [Leandro] made a small proof of concept out of soldered brass and liked the results. The next version will be larger, made out of aluminum and steel, and capable of carrying a payload.

The Strandbeest and Octo have a lot in common but differ in a few significant ways. Jansen’s linkage (which the Strandbeest uses) uses eight links per leg and requires relatively flat terrain. The Klann linkage used by Octo needs only six links per leg, and has the ability to deal with rougher ground.

[Leandro] didn’t just cut some parts out from a file found online; the brass proof of concept was drawn up based on an animation of a Klann linkage. For the next version, [Leandro] used a simulator to determine an optimal linkage design, aiming for one with a gait that wasn’t too flat, and maximized vertical rise of the leg to aid in clearing obstacles.

We’ve seen the Klann linkage before in a LEGO Spider-bot. We’re delighted to see [Leandro]’s Octo in the ring for the Wheels, wings, and walkers category of The Hackaday Prize.

LCaaS – Lawn Care As A Service?

As often happens while engaged in a mundane task, my mind wandered while I was mowing my small suburban plot of green this weekend. “Why, in 2017, am I still mowing the lawn?” In a lot of ways we’re living in the future  — we walk around with fantastically powerful computers in our pockets, some of us have semi-autonomous cars, and almost anything can be purchased at the touch of a finger and delivered the next day or sooner. We even have robots that can vacuum the floor, so why not a robot lawnmower?

It turns out we do have robotic lawnmowers, but unfortunately, they kind of suck: Continue reading “LCaaS – Lawn Care As A Service?”

Two-Bit Astrophotography

The Game Boy Camera is a 128×112 pixel sensor from 1998 that was probably the first digital camera in many, many homes. There’s not much you can do with it now, besides replicate old Neil Young album covers and attempting and failing to impress anyone born after the year 1995. Nevertheless, screwing around with old digital cameras is cool, so [Alex] strapped one fo these Game Boy Cameras to an old telescope.

For any astrophotography endeavor, the choice of telescope is important. For this little experiment, [Alex] used a 6” Fraunhofer telescope built in 1838 at the Old Observatory of Leiden. The Game Boy with Camera was attached to the scope using a universal cell phone adapter. Apparently the ‘universal’ in this universal cell phone adapter is accurate – the setup was easy and [Alex] quickly got an image of a clocktower on his Game Boy.

Turning to the heavens, [Alex] took a look at the most interesting objects you can see with a 6-inch telescope. Images of the moon turned out rather well, with beautiful 2-bit dithering along the terminator. Jupiter was a bright white spot in a sea of noise, but [Alex] could see four slightly brighter pixels orbiting where Stellarium predicted the Galilean moons would be.

Was this experiment a success? Between cloudy nights and a relatively small telescope, we’re saying yes. These are pretty impressive results for such a terrible digital camera.

Gyrators: The Fifth Element

A few years ago, there was a stir about a new fundamental component called a memristor. That wasn’t the first time a new component type was theorized though. In 1948 [Bernard Tellegen] postulated the gyrator. While you can’t buy one as a component, you can build one using other components. In fact, they are very necessary for some types of design. Put simply, a gyrator is a two-terminal device that inverts the current-voltage characteristic of an electrical component. Therefore, you can use a gyrator to convert a capacitor into an inductor or vice versa.

Keep in mind, the conversion is simply the electrical properties. Normally, current leads voltage in a capacitor and lags it in an inductor, and that’s what a gyrator changes. If you use a gyrator and a capacitor to make a virtual inductor, that inductor won’t magnetically couple to another inductor, real or simulated. There’s no magnetic field to do so. You also don’t get big voltage spikes caused by back EMF, which depending on your application could be a plus or a minus. But if you need an ungainly inductor in a circuit for its phase response, a gyrator may be just the ticket.

Continue reading “Gyrators: The Fifth Element”

Hacking Into…. A Wind Farm?

Pick a lock, plug in a WiFi-enabled Raspberry Pi and that’s nearly all there is to it.

There’s more than that of course, but the wind farms that [Jason Staggs] and his fellow researchers at the University of Tulsa had permission to access were — alarmingly — devoid of security measures beyond a padlock or tumbler lock on the turbines’ server closet. Being that wind farms are generally  in open fields away from watchful eyes, there is little indeed to deter a would-be attacker.

[Staggs] notes that a savvy intruder has the potential to shut down or cause considerable — and expensive — damage to entire farms without alerting their operators, usually needing access to only one turbine to do so. Once they’d entered the turbine’s innards, the team made good on their penetration test by plugging their Pi into the turbine’s programmable automation controller and circumventing the modest network security.

The team are presenting their findings from the five farms they accessed at the Black Hat security conference — manufacturers, company names, locations and etc. withheld for obvious reasons. One hopes that security measures are stepped up in the near future if wind power is to become an integral part of the power grid.

All this talk of hacking and wind reminds us of our favourite wind-powered wanderer: the Strandbeest!

[via WIRED]

Stalk Your Cats With A Browser-Controlled Robot

A good robot is always welcome around here at Hackaday, and Hackaday.io user [igorfonseca83]’browser-controlled ‘bot s is no exception. Felines beware.

[igorfonseca83] — building on another project he’s involved in — used simple materials for the robot itself, but you could use just about anything. His goal for this build was to maximize accessibility in terms of components and construction using common tools.

An Arduino Uno gets two D/C motors a-driving using an H-bridge circuit — granting independent control the wheels — an ESP8266 enabling WiFi access, with power provided by a simple 5V USB power bank. [igorfonseca83] is using an Android smartphone to transmit audio and video data; though this was mostly for convenience on his part, a Raspberry Pi and camera module combo as another great option!

Continue reading “Stalk Your Cats With A Browser-Controlled Robot”

Fixing Bugs In Ancient BASIC Games

Before everyone learned programming on Stack Exchange, things were much different. Computer magazines had BASIC programs in them, which readers would type out, line by line, and hit RUN. In theory, this is a terrible way to learn programming; it’s simply rote recitation without any insight into what the code is actually doing. Of course, copying and pasting from Stack Exchange is exactly the same thing, so maybe these magazines were ahead of the curve.

[0xA000] recently came across one of his old computer magazines containing the type-in listing for Blindganger, a game where you wander a maze blindly. When [0xA000] typed this game into his C64 back in 1988, the game didn’t work. Thirty years later, he decided to give it another go and ended up fixing bugs in an old computer game.

When [0xA000] typed this game into his computer back in 1988, the map just didn’t work, and the final screen revealed a maze where the walls were where they shouldn’t be. A quick Google turned up a disk image of the same game that had the same problem. This bug was obviously in the section of code that draws the map at the end of the game, so [0xA000] started looking there. The offending typo in the code was an $F4 instead of an $F5, or 244 instead of 255. This shifted the colors of the map by 11 positions, meaning the locations marked as visited in the final screen were wrong. Whether this bug cropped up in development or was just a simple typo when typesetting the magazine doesn’t really matter now; after 29 years, this bug is fixed.