Making The Tiny Air65 Quadcopter Even Smaller

First person view (FPV) quadcopter drones have become increasingly more capable over the years, as well as much smaller. The popular 65 mm format, as measured from hub to hub, is often considered to be about the smallest you can make an FPV drone without making serious compromises. Which is exactly why [Hoarder Sam] decided to make a smaller version that can fit inside a Pringles can, based on the electronics used in the popular Air65 quadcopter from BetaFPV.

The 22 mm FPV drone with camera installed and looking all cute. (Credit: Hoarder Sam)
The 22 mm FPV drone with camera installed and looking all cute. (Credit: Hoarder Sam)

The basic concept for this design is actually based on an older compact FPV drone design called the ‘bone drone’, so called for having two overlapping propellers on each end of the frame, thus creating a bone-like shape. The total hub-to-hub size of the converted Air65 drone ends up at a cool 22 mm, merely requiring a lot of fiddly assembly before the first test flights can commence. Which raises the question of just how cursed this design is when you actually try to fly with it.

Obviously the standard BetaFPV firmware wasn’t going to fly, so the next step was to modify many parameters using the Betaflight Configurator software, which unsurprisingly took a few tries. After this, the fully loaded drone with camera and battery pack, coming in at a whopping 25 grams, turns out to actually be very capable. Surprisingly, it flies not unlike an Air65 and has a similar flight time, losing only about 30 seconds of the typical three minutes.

With propellers sticking out at the top and bottom – with no propeller guards – it’s obviously a bit of a pain to launch and land. But considering what the donor Air65 went through to get to this stage, it’s honestly quite impressive that this extreme modification mostly seems to have altered its dimensions.

Continue reading “Making The Tiny Air65 Quadcopter Even Smaller”

The Great Northeast Blackout Of 1965

At 5:20 PM on November 9, 1965, the Tuesday rush hour was in full bloom outside the studios of WABC in Manhattan’s Upper West Side. The drive-time DJ was Big Dan Ingram, who had just dropped the needle on Jonathan King’s “Everyone’s Gone to the Moon.” To Dan’s trained ear, something was off about the sound, like the turntable speed was off — sometimes running at the usual speed, sometimes running slow. But being a pro, he carried on with his show, injecting practiced patter between ad reads and Top 40 songs, cracking a few jokes about the sound quality along the way.

Within a few minutes, with the studio cart machines now suffering a similar fate and the lights in the studio flickering, it became obvious that something was wrong. Big Dan and the rest of New York City were about to learn that they were on the tail end of a cascading wave of power outages that started minutes before at Niagara Falls before sweeping south and east. The warbling turntable and cartridge machines were just a leading indicator of what was to come, their synchronous motors keeping time with the ever-widening gyrations in power line frequency as grid operators scattered across six states and one Canadian province fought to keep the lights on.

They would fail, of course, with the result being 30 million people over 80,000 square miles (207,000 km2) plunged into darkness. The Great Northeast Blackout of 1965 was underway, and when it wrapped up a mere thirteen hours later, it left plenty of lessons about how to engineer a safe and reliable grid, lessons that still echo through the power engineering community 60 years later.

Continue reading “The Great Northeast Blackout Of 1965”

BASICODE: A Bit Like Java, But From The 1980s

Those of us ancient enough to remember the time, or even having grown up during the heyday of the 8-bit home computer, may recall the pain of trying to make your latest creation work on another brand of computer. They all spoke some variant of BASIC, yet were wildly incompatible with each other regardless. BASICODE was a neat solution to this, acting as an early compatibility standard and abstraction layer. It was essentially a standardized BASIC subset with a few extra routines specialized per platform.

But that’s only part of the story. The BASICODE standard program was invented by Dutch radio engineer Hessel de Vries, who worked for the Dutch national radio broadcaster Nederlandse Omroep Stichting (NOS). It was designed to be broadcast over FM radio! The idea of standardization and free national deployment was brilliant and lasted until 1992, when corporate changes and technological advancements ultimately led to its decline.

Continue reading “BASICODE: A Bit Like Java, But From The 1980s”

They Don’t Make $37 Waveform Generators Like They Used To

[CreativeLab] bought a cheap arbitrary waveform generator and noted that it only had a two-pin power cord. That has its ups and downs. We feel certain the intent was to isolate the internal switching power supply to prevent ground loops through the scope probes or the USB connector. However, it is nice to have all your equipment referencing the same ground. [CreativeLab] agrees, so he decided to do something about it.

Opening the box revealed that there was hardly anything inside. The main board was behind the front panel. There was also the power supply and a USB board. Plus lots of empty space. Some argue the case is made too large to be deceptive, but we prefer to think it was to give you a generous front panel to use. Maybe.

It was a simple matter to ground everything to a new three-pin connector, but that left the problem of the USB port. Luckily, since it was already out on its own board, it was easy to wire in an isolator.

Honestly? We’d have hesitated to do this unless we had made absolutely sure it didn’t pose some safety hazard to “jump over” the switching power supply. They are often isolated for some reason. However, the likelihood is that it is just fine. What do you think? Let us know in the comments.

A similar unit had a reverse engineering project featured on Hackaday many years ago. While these used to be exotic gear, if you don’t mind some limitations, it is very easy to roll your own these days.

Continue reading “They Don’t Make $37 Waveform Generators Like They Used To”

BlueSCSI: Not Just For Apple

Anyone into retro Macintosh machines has probably heard of BlueSCSI: an RP2040-based adapter that lets solid state flash memory sit on the SCSI bus and pretend to contain hard drives. You might have seen it on an Amiga or an Atari as well, but what about a PC? Once upon a time, higher end PCs did use SCSI, and [TME Retro] happened to have one such. Not a fan of spinning platters of rust, he takes us through using BlueSCSI with a big-blue-based-box.

Naturally if you wish to replicate this, you should check the BlueSCSI docs to see if the SCSI controller in your PC is on their supported hardware list; otherwise, your life is going to be a lot more difficult than what is depicted on [TME Retro]. As is, it’s pretty much the same drop-in experience anyone who has used BlueSCSI on a vintage Macintosh might expect. Since the retro-PC world might not be as familiar with that, [TME Retro] gives a great step-by-step, showing how to set up hard disk image files and an iso to emulate a SCSI CD drive on the SD card that goes into the BlueSCSIv2.

This may not be news to some of you, but as the title of this video suggests, not everyone knows that BlueSCSI works with PCs now, even if it has been in the docs for a while. Of course PCs owners are more likely to be replacing an IDE drive; if you’d rather use a true SSD on that bus, we’ve got you covered.

Continue reading “BlueSCSI: Not Just For Apple”

Building The LEM’s Legs

If you built a car in, say, Germany, for use in Canada, you could assume that the roads will be more or less the same. Gravity will work the same. While the weather might not be exactly the same, it won’t be totally different. But imagine designing the Lunar Excursion Module that would land two astronauts on the moon for the first time. No one had any experience landing a craft on any alien body before.

The LEM was amazing for many reasons, but as [Apollo11Space] points out, the legs were a particularly thorny engineering problem. They had to land on mostly unknown terrain, stay upright, allow for the ascent module to take off again, and, of course, not weigh down the tiny spaceship. They also had to survive the blast of the LEM’s engine.

Continue reading “Building The LEM’s Legs”

A metal needle tip comes to a point against a white background. A scale bar in the lower left shows a 300 micrometer length.

Etching Atomically Fine Needle Points

[Vik Olliver] has been extending the lower resolution limits of 3D printers with the RepRapMicron project, which aims to print structures with a feature size of ten micrometers. A molten plastic extruder would be impractical at such small scales, even if a hobbyist could manufacture one small enough, so instead [Vik]’s working on a system that uses a very fine needle point to place tiny droplets of UV resin on a substrate. These points have to be sharper than anything readily available, so his latest experiments have focused on electrochemically etching his own needles.

The needles start with a fine wire, which a 3D-printed bracket holds hanging down into a beaker of electrolyte, where another electrode is located. By applying a few volts across the circuit, with the wire acting as an anode, electrochemical erosion eventually wears through the wire and it drops off, leaving an atomically sharp point. Titanium wire performs best, but Nichrome and stainless steel also work. Copper wire doesn’t work, and by extension, nor does the plated copper wire sometimes sold as “stainless steel” by sketchy online merchants.

The electrolyte was made from either a 5% sodium chloride solution or 1% nitric acid. The salt solution produced a very thin, fine point, but also produced a cloudy suspension of metal hydroxides around the wire, which made it hard to tell when the wire had broken off. The goal of nitric acid was to prevent hydroxide formation; it produced a shorter, blunter tip with a pitted shaft, but it simply etched the tip of the wire to a point, with the rest of the wire never dropping off. Some experimentation revealed that a mixture of the two electrolyte solutions struck a good balance which etched fine points like the pure salt solution, but also avoided cloudy precipitates.

If you’re interested in seeing more of the RepRapMicron, we’ve looked at a previous iteration which scribed a minuscule Jolly Wrencher in marker ink. On a more macro scale, we’ve also seen one 3D printer which used a similar resin deposition scheme.