If you were lucky enough to be near the path of totality, and didn’t have your view obscured by clouds, yesterday’s eclipse provided some very memorable views. But you know what’s even better than making memories? Having cold hard data to back it up.
Hackaday contributor [Bob Baddeley] was in Madison, Wisconsin for the big event, which NASA’s Eclipse Explorer website predicted would see about 87% coverage. Watching the eclipse through the appropriate gear at the local hackerspace was fun, but the real nerding out happened when he got home and could pull the data from his solar system.
A graph of the system’s generated power shows a very clear dip during the duration of the eclipse, which let him determine exactly when the occlusion started, peaked, and ended.
After more than forty-six years all of us are likely to feel the wear of time, and Voyager 1 is no different. Following months of harrowing troubleshooting as the far-flung spacecraft stopped returning sensible data, NASA engineers now feel confident that they have tracked down the cause for the problem: a single defective memory chip. Why this particular chip failed is unknown, but possibilities range from wear and tear to an energetic particle hitting it and disrupting its operation.
We’ve covered the Voyager 1 troubleshooting saga so far, with the initial garbled responses attributed to a range of systems, but narrowed down to the Flight Data Subsystem (FDS), which prepares data for transmission by the telemetry modulation unit (TMU). Based on a recent ‘poke’ command that returned a memory dump engineers concluded that the approximately 3% of corrupted data fit with this one memory chip, opening the possibility of a workaround.
Recently NASA engineers have also been working on patching up the firmware in both Voyager spacecraft, against the background of the dwindling energy produced by the radioisotope generators that have kept both spacecraft powered and warm, even in the cold, dark depths of Deep Space far beyond the light of our Sun.
When all else fails, blame it on the cloud? It seems like that’s the script for just about every outage that makes the news lately, like the Wyze camera outage this week that kept people from seeing feeds from their cameras for several hours. The outage went so far that some users’ cameras weren’t even showing up in the Wyze app, and there were even reports that some people were seeing thumbnails for cameras they don’t own. That’s troubling, of course, and Wyze seems to have taken action on that quickly by disabling a tab on the app that would potentially have let people tap into camera feeds they had no business seeing. Still, it looks like curiosity got the better of some users, with 1,500 tapping through when notified of motion events and seeing other people walking around inside unknown houses. The problem was resolved quickly, with blame laid on an “AWS partner” even though there were no known AWS issues at the time of the outage. We’ve said it before and we’ll say it again: security cameras, especially mission-critical ones, have no business being connected with anything but Ethernet or coax, and exposing them to the cloud is a really, really bad idea.
Intuitive Machines’ first mission (IM-1) featuring the Nova-C Odysseus lunar lander was launched on top of a SpaceX Falcon 9 on February 15th, 2024, as part of NASA’s Commercial Lunar Payload Services (CLPS). Targeting a landing site near the lunar south pole, it was supposed to use its onboard laser range finders to help it navigate safely for a soft touchdown on the lunar surface. Unfortunately, it was this component that was found to have malfunctioned as the spacecraft was already in lunar orbit. Fortunately, there was a workaround. By using one of the NASA payloads on the lander, the Navigation Doppler Lidar (NDL), the mission could continue.
Perhaps unsurprisingly, the use of the NDL as a fallback option was considered before launch, and since its functionality overlaps with that of the primary laser range finders of Nova-C, it was pressed into service with a new configuration uploaded by IM operators back on Earth before Nova-C committed to a landing burn. Then, on February 22nd, the spacecraft began its descent to the surface, which also involved the Eaglecam payload that was designed to be released before snapping a self-portrait of the lander as it descended.
Figuring out what the Earth’s climate is going to do at any given point is a difficult task. To know how it will react to given events, you need to know what you’re working with. This requires an accurate model of everything from ocean currents to atmospheric heat absorption and the chemical and literal behavior of everything from cattle to humans to trees.
In the latter regard, scientists need to know how many trees we have to properly model the climate. This is key, as trees play a major role in the carbon cycle by turning carbon dioxide into oxygen plus wood. But how do you count trees at a continental scale? You’ll probably want to get yourself a nice satellite to do the job.
When we first developed telescopes, we started using them on the ground. Humanity was yet to master powered flight, you see, to say nothing of going beyond into space. As technology developed, we realized that putting a telescope up on a satellite might be useful, since it would get rid of all that horrible distortion from that pesky old atmosphere. We also developed radio telescopes, when we realized there were electromagnetic signals beyond visible light that were of great interest to us.
Now, NASA’s dreaming even bigger. What if it could build a big radio telescope up on the Moon?
Recently, a prototype inflatable space station module built by Sierra Space exploded violently on a test stand at NASA’s Marshall Space Flight Center in Alabama. Under normal circumstances, this would be a bad thing. But in this case, Sierra was looking forward to blowing up their handiwork. In fact, there was some disappointment when it failed to explode during a previous test run.
LIFE Module Burst Test
That’s because the team at Sierra was looking to find the ultimate bust pressure of their 8.2 meter (26.9 foot) diameter Large Integrated Flexible Environment (LIFE) module — a real-world demonstration of just how much air could be pumped into the expanding structure before it buckled. NASA recommended they shoot for just under 61 PSI, which would be four times the expected operational pressure for a crewed habitat module.
By the time the full-scale LIFE prototype ripped itself apart, it had an internal pressure of 77 PSI. The results so far seem extremely promising, but Sierra will need to repeat the test at least two more times to be sure their materials and construction techniques can withstand the rigors of spaceflight.
Sierra is a targeting no earlier than 2026 for an in-space test, but even if they nail the date (always a dubious prospect for cutting edge aerospace projects), they’ll still be about 20 years late to the party. Despite how futuristic the idea of inflatable space stations may seem, NASA first started experimenting with the concept of expandable habitat modules back in the 1990s, and there were practical examples being launched into orbit by the early 2000s.
Hackaday contributor [Bob Baddeley] was in Madison, Wisconsin for the big event, which NASA’s Eclipse Explorer website predicted would see about 87% coverage. Watching the eclipse through the appropriate gear at the local hackerspace was fun, but the real nerding out happened when he got home and could pull the data from his solar system.
