Skip to main content

Rescue Mission Is Called Off For NASA's Aging Swift Space Telescope

1 week ago
NASA has called off a $30 million mission to rescue its aging Swift space telescope after Katalyst Space's Link spacecraft developed persistent control and positioning problems. The Associated Press reports: Katalyst said Link will not attempt to capture Swift and boost it to a higher orbit because of problems with controlling the spacecraft. NASA said this means the telescope will plunge through the atmosphere after more than 20 years of tracking some of the biggest explosions in the universe like gamma ray bursts and exploding stars. Its demise is not expected before October. NASA paid $30 million to Katalyst in an attempt to raise the telescope to a safer, longer-lasting orbit. Intense solar activity caused it to lose altitude faster than expected. The rescue spacecraft went into an uncontrollable spin a few weeks after its liftoff in early July. While flight controllers managed to slow Link's tumble, issues continued to plague its pointing and positioning in orbit. "This is not the outcome we were working toward, but it does not change why this mission was worth attempting," NASA Administrator Jared Isaacman said in a statement. As a consolation prize, Katalyst will continue to operate Link in proximity with the telescope to demonstrate capabilities for future rescue operations. Katalyst CEO Ghonhee Lee said it was an ambitious mission on an aggressive timeline that was thrown together in under a year. "We took on this high-risk, high-reward challenge and are proud of the milestones we reached along the way," Lee said in a statement. "We have already learned a tremendous amount."

Read more of this story at Slashdot.

BeauHD

Representative Line: We All Register This

1 week ago

Today's maybe more of a "representative data sheet entry" than anything else.

Every developer has the experience of reading the documentation. If you've been at this for some time, you've probably read bad documentation. Documentation that is incomplete, inaccurate, or otherwise flawed. Or, my personal favorite, the brief time where Oracle tried to put all of its documentation into an Adobe Flex site (aka, a Flash application, not a real web app). That one had fun bonus features, like "breaking copy and paste" and "preventing you from deep linking to a piece of the documentation".

But software documentation has got nothing on bad data sheets. When you buy an integrated chip from a vendor, whether it's a microcontroller that'll run your code, a sensor you're trying to get data from, you're at the mercy of the datasheet for understanding how it works. Sometimes, even finding an English language datasheet can be a challenge. The more complex the chip you're trying to interact with, the more complex the datasheet needs to be, and at a certain point, a lot of vendors say, "meh, you'll figure it out." I've had chips where the datasheet and reality disagreed about what registers were available, which often means that core functions of the chip require twiddling undocumented registers. For more fun, they sometimes lie about which pins on the chip do which thing, including mislabeling which pins handle power. There's nothing more fun than the tiny little "pop" of a chip dying when you throw 5V power onto a pin that's actually ground.

Now, there are some vendors, and some products, where the datasheets are pretty solid. This isn't a universal problem, but when you're working in an embedded space, "cheapest" is frequently the main criteria for picking components, and "cheapest" means "worst documented".

Which brings us to Jarek's recent experience going through a data sheet. The chip in question had a "fantastic feature" that would change how debugging worked, which was for "super users" to enable by setting a register.

3.2.4 Super User Fantastic Feature Enable Register The Super User Fantastic Feature Enable Register allows the user to modify the behavior of the mEDBG. Name: SUFFER Offset:  0x0120 Reset: 0xFF

Sometimes, doing embedded work definitely feels like the SUFFER register is set.

[Advertisement] Picking up NuGet is easy. Getting good at it takes time. Download our guide to learn the best practice of NuGet for the Enterprise.
Remy Porter