We often think of ham radio operators talking to exotic faraway lands, and that’s true for hams using the HF bands (below 30 MHz), especially if they have nice antennas. Modern living has made it much harder to have those big antenna farms, and today’s ham is more likely talking on VHF or UHF frequencies with very limited range under normal circumstances. Sure, you can use a repeater or bounce your signal from a satellite or the moon, but normal direct communication is normally going to be less than a typical commercial FM radio station. But on April 7th, two hams communicated across the Atlantic on 432 MHz — a UHF frequency. The distance was almost 4,000 km.
Notice we didn’t say they talked, but they communicated. The contact was via a somewhat controversial mode called FT8 which uses weak signal techniques to allow two computers to send limited amounts of information to each other. However, on April 10, the two stations reported a single sideband voice contact after they noticed the band conditions improving on the FT8 signal.
After three years of online publications, HardwareX may have solidified itself as an academic journal for open-source hardware. We originally wrote about HardwareX back in 2016. At the time, HardwareX hadn’t even published its first issue and only begun soliciting manuscripts. Now after three years of publishing, six issues as of October 2019 (with the seventh scheduled for April 2020), and an impact factor of 4.33, it’s fair to say that Elsevier’s push into open-access publications is on a path to success.
To give you a bit of background, HardwareX aims to promote the reproducibility of scientific work by giving researchers an avenue to publish all the hardware and software hacks that often get buried in traditional manuscripts. The format of HardwareX articles is a bit different than most academic journals. HardwareX articles look more like project pages similar to Hackaday.io. (Maybe we inspired them a bit? Who knows.)
Let’s face it — people are gonna touch their faces. Sometimes faces itch, especially during allergy season. But the first step toward quitting something like that is to become cognizant of just how often you do it.
This no-touch-face bracelet is awesome because it’s simple and it works. It uses a Circuit Playground Express programmed in Make code, but it would be easy to port it to Arduino or CircuitPython. If you want to make something more elegant, we’re all for it, but you could be using this in the meantime to help condition yourself away from the habit. Check out the demo after the break.
Radio may be dead in terms of delivering entertainment, but it’s times like these when the original social network comes into its own. Being able to tune in stations from across the planet to get fresh perspectives on a global event can even be a life saver. You’ll need a good antenna to do that, which is where this homebrew loop antenna for the shortwave radio bands shines.
To be honest, pretty much any chunk of wire will do as an antenna for most shortwave receivers. But not everyone lives somewhere where it’s possible to string up a hundred meters of wire and get a good ground connection, which could make a passive loop antenna like this a good choice. Plus, loops tend to cancel the electrical noise that’s so part of life today, which can make it easier to pull in weak, distant stations.
[Thomas]’s design is based on a length of coaxial cable, which should be stiff enough to give the loop some stability, like a low-loss RG-8 or RG-213. The coax braid and dielectric are exposed at the midpoint of the cable to create a feed point, while the shield and center conductor at the other ends are cross-connected. A 1:1 transformer is wound on a toroid core to connect to the feedpoint; [Thomas] calls it a balun but we tend to think it’s more of an unun, since both the antenna and feedline are unbalanced. He reports good results from the loop across the shortwave band.
The shortwave and ham bands are a treasure trove of information and entertainment just waiting to be explored. Check them out — you might learn something, and you might even stumble across spies doing their thing.
If you’ve got a 3D printer, you’re probably familiar with the reinforced belts that are commonly used on the X and Y axis. These belts either come as long lengths that you attach to the machine on either end, or as a pre-sized loop. Traditional wisdom says you can’t just take a long length of belt and make your own custom loops out of it, but [Marcel Varallo] had his doubts about that.
This is a simple tip, but one that could get you out of a bind one day. Through experimentation, [Marcel] has found that you can use a length of so-called GT2 belt and make your own bespoke loop. The trick is, you need to attach the ends with something very strong that won’t hinder the normal operation of the belt. Anything hard or inflexible is right out the window, since the belt would bind up as soon as it had to go around a pulley.
It seems the key is to cut both ends of the belt very flat, making sure the belt pattern matches perfectly. Once they’ve been trimmed and aligned properly, you stitch them together with nylon thread. You want the stitches to be as tight as possible, and the more you do, the stronger the end result will be.
[Marcel] likes to follow this up with a bit of hot glue, being careful to make sure the hardened glue takes the shape of the belt’s teeth. The back side won’t be as important, but a thin layer is still best. The end result is a belt strong enough for most applications in just a few minutes.
Would we build a 3D printer using hand-stitched GT2 belts? Probably not. But during a global pandemic, when shipments of non-essential components are often being delayed, we could certainly see ourselves running some stitched together belts while we wait for the proper replacement to come in. Gotta keep those face shields printing.
Anyone who worked in the tech field and lived through the Y2K bug era will no doubt recall it as a time seasoned with a confusing mix of fear and optimism and tempered with a healthy dose of panic, as companies rushed to validate that systems would pass the rollover of the millennium without crashing, and to remediate systems that would. The era could well have been called “the COBOL programmers full-employment bug,” as the coders who had built these legacy systems were pulled out of retirement to fix them. Twenty years on and a different bug — the one that causes COVID-19 — is having a similarly stimulative effect on the COBOL programmer market. New Jersey is one state seeking COBOL coders, to deal with the crush of unemployment insurance claims, which are killing the 40-year-old mainframe systems the state’s programs run on. Interestingly, Governor Phil Murphy has only put out a call for volunteers, and will apparently not compensate COBOL coders for their time. I mean, I know people are bored at home and all, but good luck with that.
In another throwback to an earlier time, “The Worm” is back. NASA has decided to revive its “worm” logo, the simple block letter logo that replaced the 50s-era “Meatball” logo, the one with the red chevron bracketing a starfield with an orbiting satellite. NASA switched to the worm, named for the sinuous shape of the letters and which honestly looks like a graphic design student’s last-minute homework assignment, in the 1970s, keeping it in service through the early 1990s when the meatball was favored again. Now it looks like both logos will see service as NASA prepares to return Americans to space on their own launch vehicles. Wait a minute, what happens when we stand this thing upright?
Looking for a little help advancing the state of your pandemic-related project? A lot of manufacturers are trying to help out as best they can, and many are offering freebies to keep you in the game. Aisler, for one, is offering free PCBs and stencils for COVID-19 prototypes. It looks like their rules are pretty liberal; any free and open-source project that can help with the pandemic in any way qualifies. Hats off to Aisler for doing their part.
And finally, history appears to have been made this week in the amateur radio world with the first direct transatlantic contact on the 70-cm band was made. It seems strange to think that it would take 120 years since transatlantic radio became reduced to practice by the likes of Marconi for this accomplishment to occur, but the 70-cm band is usually limited to line of sight, and transatlantic contacts at 430 MHz are usually done using a satellite as a relay. The contact was between stations FG8OJ on Guadaloupe Island in the Caribbean — who was involved in an earlier, similar record on the 2-meter band — and D4VHF on the Cape Verde Islands off the coast of Africa, and used the digital mode FT8. The 3,867-km contact was likely due to tropospheric ducting, where layers in the atmosphere form a refractive tunnel that can carry VHF and UHF signals much, much further than they usually go. While we’d love to see that record stretched a little more on each end, to make a truly transcontinental contact, it’s still quite an accomplishment, and we congratulate the hams involved.
In these dire times of self quarantining, social distancing, and life as know it coming to a halt, time itself can become rather blurry, and even word clocks may seem unnecessarily precise — especially if you happen to have a more peculiar circadian rhythm. And let’s face it, chances are your usual schedule has become somwehat irrelevant by now, so why bother yourself with dates or an exact time anyway? If you can relate to this, then [mwfisher3] has the perfect clock for you, displaying only the day of the week and a rough estimate of how far that day has progressed.
Using a Raspberry Pi and a spare touch screen, [mwfisher3] had an easy game to begin with, so the clock itself is just Chrome running in Kiosk mode, displaying a local web site with the hours of the day mapped to an array of their textual representation. A few lines of JavaScript are then updating the web site content with the current day and “time”, and a Python script is handling the screen’s back light based on the readings from a Philips Hue motion sensor, using the phue library.
While this is definitely one of the simpler clock projects we’ve seen, this simplicity offers actually a great introduction to some easy JavaScript-based web displays on a Raspberry Pi without much fuzz and distraction. But if that’s not your thing, and you like things more mechanical, we’ve recently covered this day clock that follows the same idea, and then there’s also this light box for an artistic approach of getting a rough estimate of the time.
To be honest, pretty much any chunk of wire will do as an antenna for most shortwave receivers. But not everyone lives somewhere where it’s possible to string up a hundred meters of wire and get a good ground connection, which could make a passive loop antenna like this a good choice. Plus, loops tend to cancel the electrical noise that’s so part of life today, which can make it easier to pull in weak, distant stations.
