Watch out, Gen X-ers — there’s a nostalgia overload heading your way, courtesy of this over-the-air TV simulator. And it has us feeling a little Saturday morning cartoon-ish, or maybe even a bit Afterschool Special.

[Shane C Mason]’s “FieldStation42” build centers around a period-correct color TV, and rightly so — a modern TV would be jarring here, and replacing the CRT in this irreplaceable TV would be unthinkable. Programming comes via painstakingly collected sitcoms, dramas, news broadcasts, and specials, all digitized and stored on disk and organized by the original networks the programs came from. Python running on a Raspberry Pi does the heavy lifting here, developing a schedule of programs for the week that makes sense for the time of day — morning news and talk, afternoon soaps, the usual family hour and prime time offerings, and finally [Carson] rounding out the day, because that’s all we had for late night.

As for switching between stations, rather than risk damaging the old TV, [Shane] really upped his nostalgia game and found an old antenna rotator control box. These were used to steer the directional antenna toward different transmitters back in the day, especially in fringe areas like the one he grew up in. He added a set of contacts to the knob and a Pi Pico, which talks to the main Pi and controls which “channel” is being viewed. He also added an effect of fading and noise in the video and audio between channels, simulating the antenna moving. The video below shows it in action.

For those who missed the Golden Age of TV, relax; as [Shane] correctly surmises after going through this whole project, Golden Ages only exist in your mind. Things were certainly different with 70s mass media, a fact which this build captures neatly, but that doesn’t mean they were better. Other than Saturday mornings, of course — those were objectively better in every way.

A disclaimer: Not a single cable tie was harmed in the making of this backpack cyberdeck, and considering that we lost count of the number of USB cables [Bag-Builds] used to connect everything in it, that’s a minor miracle.

The onboard hardware is substantial, starting with a Lattepanda Sigma SBC, a small WiFi travel router, a Samsung SSD, a pair of seven-port USB hubs, and a quartet of Anker USB battery banks. The software defined radio (SDR) gear includes a HackRF One, an Airspy Mini, a USRP B205mini, and a Nooelec NESDR with an active antenna. There are also three USB WiFi adapters, an AX210 WiFi/Bluetooth combo adapter, a uBlox GPS receiver, and a GPS-disciplined oscillator, both with QFH antennas. There’s also a CatSniffer multi-protocol IoT dongle and a Flipper Zero for good measure, and probably a bunch of other stuff we missed. Phew!

As for mounting all this stuff, [Bag-Builds] went the distance with a nicely designed internal frame system. Much of it is 3D printed, but the basic frame and a few rails are made from aluminum. The real hack here, though, is getting the proper USB cables for each connection. The cable lengths are just right so that nothing needs to get bundled up and cable-tied. The correct selection of adapters is a thing of beauty, too, with very little interference between the cables despite some pretty tightly packed gear.

What exactly you’d do with this cyberpack, other than stay the hell away from airports, police stations, and government buildings, isn’t exactly clear. But it sure seems like you’ve got plenty of options. And yes, we’re aware that this is a commercial product for which no build files are provided, but if you’re sufficiently inspired, we’re sure you could roll your own.

Thanks to [KC] for the tip on this one.

Thanks a lot, Elon. Or maybe not, depending on how this report that China used Starlink signals to detect low-observable targets pans out. There aren’t a lot of details, and we couldn’t find anything approximating a primary source, but it seems like the idea is based on forward scatter, which is when waves striking an object are deflected only a little bit. The test setup for this experiment was a ground-based receiver listening to the downlink signal from a Starlink satellite while a DJI Phantom 4 Pro drone was flown into the signal path. The drone was chosen because nobody had a spare F-22 or F-35 lying around, and its radar cross-section is about that of one of these stealth fighters. They claim that this passive detection method was able to make out details about the drone, but as with most reporting these days, this needs to be taken with an ample pinch of salt. Still, it’s an interesting development that may change things up in the stealth superiority field.

Another week, another example of how the fine print on the EULA is never your friend. This time around it’s the popular Wyze security cameras, where there’s an unconfirmed report that a recent firmware update nerfed the “Recording Cooldown” setting menu, making the option to have no cooldown period between recording a paid feature. As we understand it, Wyze cameras previously had a cooldown feature, intended to keep the camera from overheating or killing the battery if the motion sensor detects a lot of continual movement. But it looks like earlier firmware revs allowed users to bypass the default five-minute period between recordings, a reasonable choice for anyone using these as security cameras. Now, bypassing the cooldown seems to require a paid subscription. We have to stress that we don’t know anything beyond this one unconfirmed report, but this enshittification is certainly something we’ve seen before, so it at least rings true, and it seems like another solid example of the fact that with cheap IoT appliances, you never truly own your stuff.

We hate to be the bearers of bad news — well, that might be a stretch given the two articles above — but this is really the kind of news we hate to hear. The Eugene Makerspace in Eugene, Oregon, suffered a major fire in their community shop on September 15. Judging by the pictures, the place was pretty thoroughly destroyed, and the fact that it was an early morning fire probably contributed to the lack of injuries. Their GoFundMe campaign is doing pretty well, but they could certainly use some help getting back on their feet. If you’re in a position to contribute, we’re sure they’d appreciate it.

When it comes to OpenAI’s newest AI model, you’d better watch what you think — or rather, you’d better not think too much about how the model thinks. Trying to get inside the model’s “head” is apparently against the terms of service, with users getting nastygrams from OpenAI warning them to step off. The “Strawberry” AI model has a feature that lets users have a glimpse into the “chain of thought” used to answer a question or complete a task, which on the face of it seems to be exactly what they don’t want users to do. But the chain of thought is only a hand-waving summary of the raw thought process, filtered through a separate AI model. This is what OpenAI doesn’t want people probing, and any attempts at engineering tricky prompts to reveal the raw chain of thought will potentially get you banned.

And finally, although motorsports aren’t really our thing, we have to admit a certain sense of awe at this video that exposes some of the extreme engineering that goes into top fuel drag racing. Specifically, this video concentrates on drag racing, where nitromethane-fueled engines-on-wheels scream down a quarter-mile track in less than four seconds. Everything about this sport is extreme, especially the engines, which run themselves almost to death for the few seconds they are under full power. The video is packed full of tidbits that boggle the mind, such as these engines burning out their sparkplugs about halfway through the course, with the engine continuing to run in diesel mode thanks to the high compression and temperatures. Drivers experience a brain-squishing 8 g of acceleration during a run, which consumes over 30 gallons of fuel and exerts so much force on the engine that the connecting rods get compressed. The supercharger alone takes 800 horsepower to run, and yet the engine still produces enough power that the car is going 60 miles per hour before it covers its own length. Oh, and that ridiculous exhaust plume? That’s raw fuel that is purposely left unburned until it escapes the exhaust tips, which are angled to provide additional down-force to make sure as much torque as possible gets from the tires to the track. Enjoy!

Nothing can ruin a restoration project faster than broken knobs. Sure, that old “boat anchor” ham rig will work just fine with some modern knobs, but few and far between are the vintage electronics buffs that will settle for such aesthetic affrontery. But with new old stock knobs commanding dear prices, what’s the budget-conscious restorationist to do? Why, fix the cracked knobs yourself, of course.

At least that’s what [Level UP EE Lab] tried with his vintage Heahkit DX60 ham transmitter, with pretty impressive results. The knobs on this early-60s radio had all cracked thanks to years of over-tightening the set screws. To strengthen the knobs, he found some shaft collars with a 1/4″ inside diameter and an appropriate set screw. The backside of the knob was milled out to make room for the insert, which was then glued firmly in place with everyone’s go-to adhesive, JB Weld. [Level UP] chose the “Plastibonder” product, which turns out not to be an epoxy but rather a two-part urethane resin, which despite some initial difficulties flowed nicely around the shaft collar and filled the milled-out space inside the knob. The resin also flowed into the channels milled into the outside diameter of the shaft collars, which are intended to grip the hardened resin better and prevent future knob spinning.

It’s a pretty straightforward repair if a bit fussy, but the result is knobs that perfectly match the radio and still have the patina of 60-plus years of use. We’ll keep this technique in mind for our next restoration, or even just an everyday repair. Of course, for less demanding applications, there are always 3D printed knobs.

Whether the goal is reverse engineering, black hat exploitation, or just simple curiosity, getting inside the packages that protect integrated circuits has long been the Holy Grail of hacking. It isn’t easy, though; those inscrutable black epoxy blobs don’t give up their secrets easily, with most decapping methods being some combination of toxic and dangerous. Isn’t there something better than acid baths and spinning bits of tungsten carbide?

[Janne] over at Fraktal thinks so, and the answer he came up with is laser decapping. Specifically, this is an extension of the laser fault injection setup we recently covered, which uses a galvanometer-scanned IR laser to induce glitches in decapped microcontrollers to get past whatever security may be baked into the silicon. The current article continues that work and begins with a long and thorough review of various IC packaging technologies, including the important anatomical differences. There’s also a great review of the pros and cons of many decapping methods, covering everything from the chemical decomposition of epoxy resins to thermal methods. That’s followed by specific instructions on using the LFI rig to gradually ablate the epoxy and expose the die, which is then ready to reveal its secrets.

The benefit of leveraging the LFI rig for decapping is obvious — it’s an all-in-one tool for gaining access and executing fault injection. The usual caveats apply, of course, especially concerning safety; you’ll obviously want to avoid breathing the vaporized epoxy and remember that lasers and retinas don’t mix. But with due diligence, having a single low-cost tool to explore the innards of chips seems like a big win to us.

To the extent that one has strong feelings about insects, they tend toward the extremes of a spectrum that runs from a complete fascination with their diversity and the specializations they’ve evolved to exploit unique and ultra-narrow ecological niches, and “Eww, ick! Kill it!” It’s pretty clear that [Dr. Andy Quitmeyer] and his team tend toward the former, and while they love their bugs, spending all night watching them is a tough enough gig that they came up with Mothbox, the automated insect monitor.

Insect censuses are valuable tools for assessing the state of an ecosystem, especially insects’ vast numbers, short lifespan, and proximity to the base of the food chain. Mothbox is designed to be deployed in insect-rich environments and automatically recognize and tally the moths it sees. It uses an Arducam and Raspberry Pi for image capture, plus an array of UV and visible LEDs, all in a weatherproof enclosure. The moths are attracted to the light and fly between the camera and a plain white background, where an image is captured. YOLO v8 locates all the moths in the image, crops them out, and sends them to BioCLIP, a vision model for organismal biology that appears similar to something we’ve seen before. The model automatically sorts the moths by taxonomic features and keeps a running tally of which species it sees.

Mothbox is open source and the site has a ton of build information if you’re keen to start bug hunting, plus plenty of pictures of actual deployments, which should serve as nightmare fuel to the insectophobes out there.

Down here at the bottom of our ocean of air, it’s easy to get complacent about the hazards our universe presents. We feel safe from the dangers of the vacuum of space, where radiation sizzles and rocks whizz around. In the same way that a catfish doesn’t much care what’s going on above the surface of his pond, so too are we content that our atmosphere will deflect, absorb, or incinerate just about anything that space throws our way.

Or will it? We all know that there are things out there in the solar system that are more than capable of wiping us out, and every day holds a non-zero chance that we’ll take the same ride the dinosaurs took 65 million years ago. But if that’s not enough to get you going, now we have to worry about gamma-ray bursts, searing blasts of energy crossing half the universe to arrive here and dump unimaginable amounts of energy on us, enough to not only be measurable by sensitive instruments in space but also to effect systems here on the ground, and in some cases, to physically alter our atmosphere.

Gamma-ray bursts are equal parts fascinating physics and terrifying science fiction. Here’s a look at the science behind them and the engineering that goes into detecting and studying them.

Collapsars and Neutron Stars

Although we now know that gamma-ray bursts are relatively common, it wasn’t all that long ago that we were ignorant of their existence, thanks in part to our thick, protective atmosphere. The discovery of GRBs had to wait for the Space Race to couple with Cold War paranoia, which resulted in Project Vela, a series of early US Air Force satellites designed in part to watch for Soviet compliance with the Partial Test Ban Treaty, which forbade everything except underground nuclear tests. In 1967, gamma ray detectors on satellites Vela 3 and Vela 4 saw a flash of gamma radiation that didn’t match the signature of any known nuclear weapon. Analysis of the data from these and subsequent flashes revealed that they came from space, and the race to understand these energetic cosmic outbursts was on.

Gamma-ray bursts are the most energetic phenomena known, with energies that are almost unfathomable. Their extreme brightness, primarily as gamma rays but across the spectrum and including visible light, makes them some of the most distant objects ever observed. To put their energetic nature into perspective, a GRB in 2008, dubbed GRB 080319B, was bright enough in the visible part of the spectrum to just be visible to the naked eye even though it was 7.5 billion light years away. That’s more than halfway across the observable universe, 3,000 times farther away than the Andromeda galaxy, normally the farthest naked-eye visible object.

For all their energy, GRBs tend to be very short-lived. GRBs break down into two rough groups. Short GRBs last for less than about two seconds, with everything else falling into the long GRB category. About 70% of GRBs we see fall into the long category, but that might be due to the fact that the short bursts are harder to see. It could also be that the events that precipitate the long variety, hypernovae, or the collapse of extremely massive stars and the subsequent formation of rapidly spinning black holes, greatly outnumber the progenitor event for the short category of GRBs, which is the merging of binary neutron stars locked in a terminal death spiral.

The trouble is, the math doesn’t work out; neither of these mind-bogglingly energetic events could create a burst of gamma rays bright enough to be observed across half the universe. The light from such a collapse would spread out evenly in all directions, and the tyranny of the inverse square law would attenuate the signal into the background long before it reached us. Unless, of course, the gamma rays were somehow collimated. The current thinking is that a disk of rapidly spinning material called an accretion disk develops outside the hypernova or the neutron star merger. The magnetic field of this matter is tortured and twisted by its rapid rotation, with magnetic lines of flux getting tangled and torn until they break. This releases all the energy of the hypernova or neutron star merger in the form of gamma rays in two tightly focused jets aligned with the pole of rotation of the accretion disk. And if one of those two jets happens to be pointed our way, we’ll see the resulting GRB.

Crystals and Shadows

But how exactly do we detect gamma-ray bursts? The first trick is to get to space, or at least above the bulk of the atmosphere. Our atmosphere does a fantastic job shielding us from all forms of cosmic radiation, which is why the field of gamma-ray astronomy in general and the discovery of GRBs in particular had to wait until the 1960s. A substantial number of GRBs have been detected by gamma-ray detectors carried aloft on high-altitude balloons, especially in the early days, but most dedicated GRB observatories are now satellite-borne

Gamma-ray detection technology has advanced considerably since the days of Vela, but a lot of the tried and true technology is still used today. Scintillation detectors, for example, use crystals that release photons of visible light when gamma rays of a specific energy pass through them. The photons can then be amplified by photomultiplier tubes, resulting in a pulse of current proportional to the energy of the incident gamma ray. This is the technology used by the Gamma-ray Burst Monitor (GBM) aboard the Fermi Gamma-Ray Space Telescope, a satellite that was launched in 2008. Sensors with the GBT are mounted around the main chassis of Fermi, giving it a complete very of the sky. It consists of twelve sodium iodide detectors, each of which is directly coupled to a 12.7-cm diameter photomultiplier tube. Two additional sensors are made from cylindrical bismuth germanate scintillators, each of which is sandwiched between two photomultipliers. Together, the fourteen sensors cover from 8 keV to 30 MeV,  and used in concert they can tell where in the sky a gamma-ray burst has occurred.

Ionization methods are also used as gamma-ray detectors. The Niel Gehrels Swift Observatory, a dedicated GRB hunting satellite that was launched in 2004, has an instrument known as the Burst Alert Telescope, or BAT. This instrument has a very large field of view and is intended to monitor a huge swath of sky. It uses 32,768 cadmium-zinc-telluride (CZT) detector elements, each 4 x 4 x 2 mm, to directly detect the passage of gamma rays. CZT is a direct-bandgap semiconductor in which electron-hole pairs are formed across an electric field when hit by ionizing radiation, producing a current pulse. The CZT array sits behind a fan-shaped coded aperture, which has thousands of thin lead tiles arranged in an array that looks a little like a QR code. Gamma rays hit the coded aperture first, casting a pattern on the CZT array below. The pattern is used to reconstruct the original properties of the radiation beam mathematically, since conventional mirrors and lenses don’t work with gamma radiation. The BAT is used to rapidly detect the location of a GRB and to determine if it’s something worth looking at. If it is, it rapidly slews the spacecraft to look at the burst with its other instruments and instantly informs other gamma observatories about the source so they can take a look too.

The B.O.A.T.

On October 9, 2022, both Swift and Fermi, along with dozens of other spacecraft and even some ground observatories, would get to witness a cataclysmically powerful gamma-ray burst. Bloodlessly named GRB 221009A but later dubbed “The BOAT,” for “brightest of all time,” the initial GRB lasted for an incredible ten minutes with a signal that remained detectable for hours. Coming from the direction of the constellation Sagittarius from a distance of 2.4 billion light years, the burst was powerful enough to saturate Fermi’s sensors and was ten times more powerful than any signal yet received by Swift.

Almost everything about the BOAT is fascinating, and the superlatives are too many to list. The gamma-ray burst was so powerful that it showed up in the scientific data of spacecraft that aren’t even equipped with gamma-ray detectors, including orbiters at Mars and Voyager 1. Ground-based observatories noted the burst, too, with observatories in Russia and China noting very high-energy photons in the range of tens to hundreds of TeV arriving at their detectors.

The total energy released by GRB 221009A is hard to gauge with precision, mainly because it swamped the very instruments designed to measure it. Estimates range from 10⁴⁸ to 10⁵⁰ joules, either of which dwarfs the total output of the Sun over its entire 10 billion-year lifespan. So much energy was thrown in our direction in such a short timespan that even our own atmosphere was impacted. Lightning detectors in India and Germany were triggered by the burst, and the ionosphere suddenly started behaving as if a small solar flare had just occurred. Most surprising was that the ionospheric effects showed up on the daylight side of the Earth, swamping the usual dampening effect of the Sun.

When the dust had settled from the initial detection of GRB 221009A, the question remained: What happened to cause such an outburst? To answer that, the James Webb Space Telescope was tasked with peering into space, off in the direction of Sagittarius, where it found pretty much what was expected — the remains of a massive supernova. In fact, the supernova that spawned this GRB doesn’t appear to have been particularly special when compared to other supernovae from similarly massive stars, which leaves the question of how the BOAT got to be so powerful.

Does any of this mean that a gamma-ray burst is going to ablate our atmosphere and wipe us out next week? Probably not, and given that this recent outburst was estimated to be a one-in-10,000-year event, we’re probably good for a while. It seems likely that there’s plenty that we don’t yet understand about GRBs, and that the data from GRB 221009A will be pored over for decades to come. It could be that we just got lucky this time, both in that we were in the right place at the right time to see the BOAT, and that it didn’t incinerate us in the process. But given that on average we see one GRB per day somewhere in the sky, chances are good that we’ll have plenty of opportunities to study these remarkable events.

For as useful as computers are in the modern ham shack, they also tend to be a strong source of unwanted radio frequency interference. Common wisdom says applying a few ferrite beads to things like Ethernet cables will help, but does that really work?

It surely appears to, for the most part at least, according to experiments done by [Ham Radio DX]. With a particular interest in lowering the noise floor for operations in the 2-meter band, his test setup consisted of a NanoVNA and a simple chunk of wire standing in for the twisted-pair conductors inside an Ethernet cable. The NanoVNA was set to sweep across the entire HF band and up into the VHF; various styles of ferrite were then added to the conductor and the frequency response observed. Simply clamping a single ferrite on the wire helped a little, with marginal improvement seen by adding one or two more ferrites. A much more dramatic improvement was seen by looping the conductor back through the ferrite for an additional turn, with diminishing returns at higher frequencies as more turns were added. The best performance seemed to come from two ferrites with two turns each, which gave 17 dB of suppression across the tested bandwidth.

The question then becomes: How do the ferrites affect Ethernet performance? [Ham Radio DX] tested that too, and it looks like good news there. Using a 30-meter-long Cat 5 cable and testing file transfer speed with iPerf, he found no measurable effect on throughput no matter what ferrites he added to the cable. In fact, some ferrites actually seemed to boost the file transfer speed slightly.

Ferrite beads for RFI suppression are nothing new, of course, but it’s nice to see a real-world test that tells you both how and where to apply them. The fact that you won’t be borking your connection is nice to know, too. Then again, maybe it’s not your Ethernet that’s causing the problem, in which case maybe you’ll need a little help from a thunderstorm to track down the issue.

As a test artifact, 3DBenchy does a pretty good job of making sure your 3D printer is up to scratch. As an exemplar of naval architecture, though — well, let’s just say that if it weren’t for the trapped air in the infilled areas, most Benchy prints wouldn’t float at all. About the only way to make Benchy less seaworthy would be to make it out of cast iron. Challenge accepted.

We’ve grown accustomed to seeing [Denny] over at “Shake the Future” on YouTube using his microwave-powered kilns to cast all sorts of metal, but this time he puts his skill and experience to melting iron. For those not in the know, he uses standard consumer-grade microwave ovens to heat kilns made from ceramic fiber and lots of Kapton tape, which hold silicon carbide crucibles that get really, really hot under the RF onslaught. It works surprisingly well, especially considering he does it all on an apartment balcony.

For this casting job, he printed a Benchy model from PLA and made a casting mold from finely ground silicon carbide blasting medium mixed with a little sodium silicate, or water glass. His raw material was a busted-up barbell weight, which melted remarkably well in the kiln. The first pour appeared to go well, but the metal didn’t quite make it all the way to the tip of Benchy’s funnel. Round two was a little more exciting, with a cracked crucible and spilled molten metal. The third time was a charm, though, with a nice pour and complete mold filling thanks to the vibrations of a reciprocating saw.

After a little fettling and a saltwater bath to achieve the appropriate patina, [Denny] built a neat little Benchy tableau using microwave-melted blue glass as a stand-in for water. It highlights the versatility of his method, which really seems like a game-changer for anyone who wants to get into home forging without the overhead of a proper propane or oil-fired furnace.

A quick look around at any coffee shop, city sidewalk, or sadly, even at a traffic light will tell you that people are on their phones a lot. But exactly how much is that? For Americans in 2023, it was a mind-boggling 100 trillion megabytes, according to the wireless industry lobbying association CTIA. The group doesn’t discuss their methodology in the press release, so it’s a little hard to make judgments on that number’s veracity, or the other numbers they bandy about, such as the 80% increase in data usage since 2021, or the fact that 40% of data is now going over 5G connections. Some of the numbers are more than a little questionable, too, such as the claim that 330 million Americans (out of a current estimate of 345.8 million people) are covered by one or more 5G networks. Even if you figure that most 5G installations are in densely populated urban areas, 95% coverage seems implausible given that in 2020, 57.5 million people lived in rural areas of the USA. Regardless of the details, it remains that our networks are positively humming with data, and keeping things running is no mean feat.

If you’ve ever wondered what one does with a degree in wildlife biology, look no further than a study that looks into “avian-caused ignitions” of wildfires. The study was led by Taylor Barnes, a wildlife biologist and GIS specialist who works for a civil engineering firm, and concludes that some utility poles are 5 to 8 times more likely to spark a wildfire than the average pole due to “thermal events” following electrocution of a bird, squirrel, bear, or idiot. Unfortunately, the paper is paywalled, so there’s no information on methodology, but we’re guessing a grad student or intern spent a summer collecting animal carcasses from beneath power poles. It’s actually very valuable work since it informs decisions on where to direct wildlife mitigation efforts that potentially reduce the number of service outages and wildfires, but it’s still kinda funny.

From the “How to get rid of a lot of money in a hurry” files comes a story of a bad GPU made into an incredibly unattractive purse. About the only thing good about the offering, which consists of a GeForce GT 730 video card stuffed into a clear plastic box with a gold(ish) chain attached, is the price of $1,024. The completely un-dodgy GPUStore Shopify site also lists a purse fashioned from an NVIDIA H100 Tensor Core GPU for a cool $65,536. At least somebody knows about base two.

And finally, if you’ve struggled with the question of what humanoid robots bring to the table, chances are pretty good that adding the ability to fly with four jet engines isn’t going to make things much clearer. But for some reason, a group from the Italian Institute of Technology is working on the problem of “aerial humanoid robotics” with a cherub-faced bot dubbed iRonCub. The diminutive robot is only about 70 kilograms, which includes the four jet engines generating a total of 1,000 newtons of thrust. Applications for the flying baby robot are mostly left to the imagination, although there is a vague reference to “search and rescue” applications; we’re not sure about you, but if we’re lost in the woods and half-crazed from hunger and exposure, a baby descending from the sky on a 600° plume of exhaust might not be the most comforting sight.

With all the recent attention on Mars and the search for evidence of ancient life there, it’s easy to forget that not only has the Red Planet been under the figurative microscope since the early days of the Space Race, but we went to tremendous effort to send a pair of miniaturized biochemical laboratories there back in 1976. While the results were equivocal, it was still an amazing piece of engineering and spacefaring, one that [Marb] has recreated with this Earth-based version of the famed Viking “Labeled Release” experiment.

The Labeled Release experimental design was based on the fact that many metabolic processes result in the evolution of carbon dioxide gas, which should be detectable by inoculating a soil sample with a nutrient broth laced with radioactive carbon-14. For this homage to the LR experiment, [Marb] eschewed the radioactive tracer, instead looking for a relative increase in the much lower CO₂ concentration here on Earth. The test chamber is an electrical enclosure with a gasketed lid that holds a petri dish and a simple CO₂ sensor module. Glands in the lid allow an analog for Martian regolith — red terrarium sand — and a nutrient broth to be added to the petri dish. Once the chamber was sterilized, or at least sanitized, [Marb] established a baseline CO₂ level with a homebrew data logger and added his sample. Adding the nutrient broth — a solution of trypsinized milk protein, yeast extract, sugar, and salt — gives the bacteria in the “regolith” all the food they need, which increases the CO₂ level in the chamber.

More after the break…

[Marb]’s results are not surprising by any means, but that’s hardly the point. This is just a demonstration of the concept of the LR experiment, one that underscores the difficulties of doing biochemistry on another planet and the engineering it took to make it happen. Compared to some of the instruments rolling around Mars today, the Viking experiments seem downright primitive, and the fact that they delivered even the questionable data they did is pretty impressive.

A word of warning before watching this very cool video on soldering: it may make you greatly desire what appears to be a very, very expensive microscope. You’ve been warned.

Granted, most people don’t really need to get this up close and personal with their soldering, but as [Robert Feranec] points out, a close look at what’s going on when the solder melts and the flux flows can be a real eye-opener. The video starts with what might be the most esoteric soldering situation — a ball-grid array (BGA) chip. It also happens to be one of the hardest techniques to assess visually, both during reflow and afterward to check the quality of your work. While the microscope [Robert] uses, a Keyence VHX-7000 series digital scope, allows the objective to swivel around and over the subject in multiple axes and keep track of where it is while doing it, it falls short of being the X-ray vision you’d need to see much beyond the outermost rows of balls. But, being able to look in at an angle is a huge benefit, one that allows us a glimpse of the reflow process.

More after the break

[Robert] also takes a look at other SMD packages, such as a TSSOP chip and a QFN package, as well as some through-hole terminals. He also forces a few errors, like misaligning leads or using way too much solder, just to show how fault-tolerant SMD soldering can be. The real eye-opener here was the excess tinning on the central pad of the QFN, which clearly caused problems by preventing capillary action from pulling the outer contacts down onto the pads. We’ve had that same problem ourselves, and seeing this makes us want to give that repair another go.

Kudos to [Roboert] for sharing these delicious views of what’s really going on when the solder starts to flow.

It was probably a reasonable assumption that the “Tiny” in our recently concluded Tiny Games Contest mostly referred to the physical footprint of the game. And indeed, that’s the way most of the entries broke, which resulted in some pretty amazing efforts. [Anders Nielsen], however, took the challenge another way and managed to stuff a seagull-centric side-scroller into just 500 bytes of code.

That’s not to say that the size of [Anders]’s game is physically huge either. Flappy Larus, as he calls his game, runs on his popular 65uino platform, a 6502 microcontroller in the familiar Arduino Uno form factor. So it’s pretty small to begin with, and doesn’t even need any additional components other than the tiny OLED screen which has become more or less standard for the 65uino at this point. The only real add-on is a piezo speaker module, which when hooked up to the I2C data line happens to make reasonable approximations of a squawking seagull, all without adding a single byte of code. Check out a little game play in the video below.

Flappy Larus may be pretty simplistic, but as we recall, the game it’s based on was similarly minimalist and still managed to get people hooked. The 2024 Tiny Games contest is closed now, but if you’ve got an idea for a tiny game, we’d still love to feature it. Hit the tip line and we’ll take a look!

[Joe Barnard] made a solid propellant rocket motor, and as one does in such situations, he put it through its paces on the test stand. The video below is not about the test, nor is it about the motor’s construction. Rather, it’s a deconstruction of the remains of the motor in order to better understand its design, and it’s pretty interesting stuff.

Somewhere along the way, [Joe], aka “BPS.Space” on YouTube, transitioned from enthusiastic model rocketeer to full-fledged missile-man, and in the process stepped up his motor game considerably. The motor that goes under the knife — or rather, the bandsaw — in this video is his “Simplex V2,” a completely DIY build of [Joe]’s design. For scale, the casing is made from a 6″ (15 cm) diameter piece of aluminum tubing over a meter in length, with a machined aluminum forward closure and a composite nozzle assembly. This is a pretty serious piece of engineering.

The closure and the nozzle are the focus of the video, which makes sense since that’s where most of the action takes place. To understand what happened during the test, [Joe] lopped them off and cut them roughly in half longitudinally. The nozzle throat, which was machined from a slug of graphite, fared remarkably well during the test, accumulating only a little slag from the propellant, a combination of powdered aluminum, ammonium perchlorate, and HTBP resin. The lower part of the nozzle, made from phenolic-impregnated linen, did pretty well too, building up a pyrolyzed layer that acted much like a space capsule’s ablative heat shield would. The forward closure, whose sole job is to contain the inferno and direct the exhaust anywhere but up, took more of a beating but stood up to the challenge. Especially interesting was the state of the O-rings and the way that the igniter interfaced with the closure.

Post mortems like these are valuable teaching tools, and while it must be heartbreaking to destroy something you put so much work into, you can’t improve what you can’t measure. Hats off to [Joe] for the peek inside his world.

For vintage calculator fans, nothing strikes more fear than knowing that someday their precious and irreplaceable daily driver will become a museum piece to be looked at and admired — but never touched again. More often than not, the failure mode will be the keypad.

In an effort to recover from the inevitable, at least for 70s vintage TI calculators, [George] has come up with these nice replacement keypad PCBs. The original membrane switches on these calculators have a limited life, but luckily there are ultra-slim SMD tactile switches these days make a dandy substitute. [George] specifies a 0.8 mm thick switch that when mounted on a 1.6 mm thick PCB comes in just a hair over the original keypad’s 2.2 mm thickness. He has layouts for a TI-45, which should also fit a TI-30, and one for the larger keypads on TI-58s and TI-59s.

While these particular calculators might not in your collection, [George]’s goal is to create an open source collection of replacement keypads for all the vintage calculators sitting in desk drawers out there. And not just keypads, but battery packs, too.

When your steam engine build requires multiple microscopes, including those of the scanning electron variety, you know you’re building something really, really tiny.

All of the usual tiny superlatives and comparisons apply to [Chronova Engineering]’s latest effort — fits on a pencil eraser, don’t sneeze while you’re working on it or you’ll never find it. If we were to put the footprint of this engine into SMD context, we’d say it’s around a 2010 or so. As one would expect, the design is minimalistic, with no room for traditional bearings or valves. The piston and connecting rod are one piece, meaning the cylinder must pivot, which provides a clever way of switching between intake and exhaust. Tiny crankshaft, tiny flywheel. Everything you’d associate with a steam engine is there, but just barely.

The tooling needed to accomplish this feat is pretty impressive too. [Chronova] are no strangers to precision work, but this is a step beyond. Almost everything was done on a watchmaker’s lathe with a milling attachment and a microscope assist. For the main body of the engine, a pantograph engraving machine was enlisted to scale a 3D printed template down tenfold. Drill bits in the 0.3 mm range didn’t fare too well against annealed tool steel, which is where the scanning electron microscope came into play. It revealed brittle fractures in the carbide tool, which prompted a dive down the rabbit hole of micro-machining and a switch to high-speed steel tooling.

It all worked in the end, enough so that the engine managed 42,000 RPM on a test with compressed air. We eagerly await the equally tiny boiler for a live steam test.

OK, sit down, everyone — we don’t want you falling over and hurting yourself when you learn the news that actually yes, your phone has been listening to your conversations all along. Shocking, we know, but that certainly seems to be what an outfit called Cox Media Group (CMG) does with its “Active Listening” software, according to a leaked slide deck that was used to pitch potential investors. The gist is that the software uses a smartphone’s microphone to listen to conversations and pick out keywords that it feeds to its partners, namely Google, Facebook, and Amazon so that they can target you with directed advertisements. Ever have an IRL conversation about something totally random only to start seeing references to that subject pop up where they never did before? We sure have, and while “relationship mining” seemed like a more parsimonious explanation back in 2017, the state of tech makes eavesdropping far more plausible today. Then there’s the whole thing of basically being caught red-handed. The Big Three all huffed and puffed about how they were shocked, SHOCKED to learn that this was going on, with reactions ranging from outright denial of ever partnering with CMG to quietly severing their relationship with the company. So much for years of gaslighting on this.

In other dystopian news, the American Radio Relay League just wrote a $1 million check to end a ransomware attack. According to an ARRL statement, unidentified “threat actors” found their way into computer systems at the group’s Newington, Connecticut headquarters and related cloud-based systems, which allowed them to install encryption packages on laptops, desktops, and servers running a variety of operating systems. The ARRL’s crisis team managed to talk the cyberattackers down from their original demand of several million dollars to just a million, which all things considered was probably the path of least resistance and lowest cost. It’s a shame that things have come to that, but here we are.

The long saga of Starliner’s first crewed test flight is finally over, as the beleaguered spacecraft pushed back from the International Space Station and headed back to a midnight landing in New Mexico on Saturday. The return was sans crew, of course, with NASA being unwilling to risk the lives of astronauts Suni Williams and Butch Wilmore in a spacecraft that hadn’t really performed up to snuff on the way up to the ISS. As if the leaky thrusters weren’t enough, just before the hatches were closed Wilmore reported weird noises coming from a speaker in Starliner. He managed to capture the sounds on his mic for Mission Control, which for all the world sounded like someone repeatedly banging on a pipe in the distance. The weird thing about the sound is the regularity, which sounded a little faster than one per second. We’re keen to see if NASA shares any in-depth engineering information on this and all the other Starliner anomalies now that the craft is back on the ground.

If you’ve ever had to do extensive overhead work, such as sanding or painting ceilings, or working under a car on a lift, you know the burn that starts to set in after just a short while of holding your arms over your head. Up to now, the only way to fix that was either hit the gym and work on upper body strength, or find another way to make a living. But now that we’re living in the future, you can just strap on your own exoskeleton backpack and take a load off the robotic way. Perhaps unsurprisingly, the ExoActive exoskeleton comes from Festool, best known for its wonderfully well-engineered premium tools that often command a premium price. The ExoActive is battery-powered and straps on like a backpack with extensions that support the upper arms. It can be set to different work heights and provides a boost in lifting power, taking some of the weight off your shoulder girdle and transmitting it to your lower back. Unlike other exoskeletons we’ve seen breathless press releases for, this one seems like something you can buy right now. Sure, it’s expensive, but it’s a fraction of the cost of shoulder surgery.

And finally, Animagraffs is back with an incredibly detailed look inside the inner workings of a 16th-century sailing vessel. The video really captures what it took to build vessels that could (just barely) sail around the world for the first time. We loved the explanation of the rigging, especially the differences between the standing rigging and the running rigging. If you don’t know your clewline from your backstay, this Blender tour de force will set you straight.

What can you do with a cheap Linux machine with limited flash and only a single free GPIO line? Probably not much, but sometimes, just getting root to prove you can is the main goal of a project. If that happens to lead somewhere useful, well, that’s just icing on the cake.

Like many interesting stories, this one starts on AliExpress, where [Easton] spied some low-cost WiFi repeaters, the ones that plug directly into the wall and extend your wireless network another few meters or so. Unable to resist the siren song, a few of these dongles showed up in the mailbox, ripe for the hacking. Spoiler alert: although the attempt on the first device had some success by getting a console session through the UART port and resetting the root password, [Easton] ended up bricking the repeater while trying to install an OpenWRT image.

The second attempt, this time on a different but similar device, proved more fruitful. The rudimentary web UI provided no easy path in, although it did a pretty good job enumerating the hardware [Easton] was working with. With the UART route only likely to provide temptation to brick this one too, [Easton] turned to a security advisory about a vulnerability that allows remote code execution through a specially crafted SSID. That means getting root on these dongles is as simple as a curl command — no hardware hacks needed!

As for what to do with a bunch of little plug-in Linux boxes with WiFi, we’ll leave that up to your imagination. We like [Easton]’s idea of running something like Pi-Hole on them; maybe Home Assistant would be possible, but these are pretty resource-constrained machines. Still, the lessons learned here are valuable, and at this price point, let the games begin.

Why is it always a helium leak? It seems whenever there’s a scrubbed launch or a narrowly averted disaster, space exploration just can’t get past the problems of helium plumbing. We’ve had a bunch of helium problems lately, most famously with the leaks in Starliner’s thruster system that have prevented astronauts Butch Wilmore and Suni Williams from returning to Earth in the spacecraft, leaving them on an extended mission to the ISS. Ironically, the launch itself was troubled by a helium leak before the rocket ever left the ground. More recently, the Polaris Dawn mission, which is supposed to feature the first spacewalk by a private crew, was scrubbed by SpaceX due to a helium leak on the launch tower. And to round out the helium woes, we now have news that the Peregrine mission, which was supposed to carry the first commercial lander to the lunar surface but instead ended up burning up in the atmosphere and crashing into the Pacific, failed due to — you guessed it — a helium leak.

Thankfully, there’s a bit more technical detail on that last one; it seems that a helium pressure control valve, designated PCV2 and controlling helium to pressurize an oxidizer tank, got stuck open thanks to “vibration-induced relaxation” in threaded components within the valve. So, launch vibrations shook a screw loose inside the valve, which kept it from sealing and over-pressurized an oxidizer tank with helium to the point of tank failure — kablooie, end of mission. All of these failures are just another way of saying that space travel is really, really hard, of course. But still, with helium woes figuring so prominently in so many failures, we’re left wondering if there might not be an upside to finding something else to pressurize tanks.

Back on terra firma, we got a tip from a reader going by the name of [Walrus] who is alarmed by an apparent trend in the electronics testing market toward a subscription model for the software needed to run modern test gear. Specifically, the tip included a link to a reseller offering a deal on an “Ultimate Software Bundle” for Tektronix 4 Series Mixed-Signal Oscilloscopes. The offer expired at the end of 2023 and prices aren’t mentioned, but given that a discount of up to $5,670 with purchase of a scope was advertised, we’d imagine the Ultimate Software Bundle comes at a pretty steep price. The chief concern [Walrus] expressed was about the possibility that used instruments whose software is tied to a subscription may have little to no value in the secondary market, where many up-and-coming engineers shop for affordable gear. We haven’t had any personal experience with subscription models for test equipment software, and a quick read of the Tektronix site seems to suggest that subscriptions are only one of the models available for licensing instrument software. Still, the world seems to be moving to one where everything costs something forever, and that the days of a “one and done” purchase are going away. We’d love to hear your thoughts on subscription software for test gear, especially if we’ve misread the situation with Tek. Sound off in the comments below.

In this week’s edition of “Dystopia Watch,” we’re alarmed by a story about how police departments are experimenting with generative AI to assist officers in report writing. The product, called Draft One, is from Axon, a public safety technology concern best known for its body-worn cameras and tasers. Using Azure OpenAI, Draft One transcribes the audio from body cam footage and generates a “draft narrative” of an officer’s interaction with the public. The draft is then reviewed by the officer, presumably corrected if needed, and sent on to a second reviewer before becoming the official report. Axon reports that it had to adjust the LLM’s settings to keep AI hallucinations from becoming part of the narrative. While we can see how this would be a huge benefit to officers, who generally loathe everything about report writing, and would get them back out on patrol rather than sitting in a parking lot tapping at a keyboard, we can also see how this could go completely sideways in a hurry. All it will take is one moderately competent defense attorney getting an officer to admit under oath that the words of the report were not written by him or her, and this whole thing goes away.

And finally, getting three (or more) monitors to all agree on what white is can be quite a chore, and not just a little enraging for the slightly obsessive-compulsive — it’s one of the reasons we favor dark mode so much, to be honest. Luckily, if you need a screen full of nothing but #FFFFFF pixels so you can adjust color balance in your multi-monitor setup, it’s as easy as calling up a web page. The White Screen Tool does one thing — paints all the pixels on the screen whatever color you want. If you need all white, it’s just a click away — no need to start up MS Paint or GIMP and futz around with making it bezel-to-bezel. There are plenty of other presets, if white isn’t your thing, plus a couple of fun animated screens that imitate Windows update screens — let the office hijinks begin! You can also set custom colors, which is nice; might we suggest #1A1A1A and #F3BF10?