SpinLaunch And The History Of Hurling Stuff Into Space

June 24, 2022 by Tom Nardi 156 Comments

It’s fair to say that there’s really no phase of spaceflight that could be considered easy. But the case could be made that the most difficult part of a spacecraft’s journey is right at the very beginning, within the first few minutes of flight. At this point the vehicle’s booster rocket will be fighting with all its might against its own immense propellant-laden mass, a battle that it’s been engineered to win by the smallest of margins. Assuming the balance was struck properly and the vehicle makes its way off of the launch pad, it will still need to contend with the thick sea-level atmosphere as it accelerates, a building dynamic pressure that culminates with a point known as “Max q” — the moment where the air density imposes the maximum structural load on the rocket before quickly dropping off as the vehicle continues to ascend and the atmosphere thins.

Air-launched rockets avoid flying through dense sea level air.

While the vast majority of rocket launches have to contend with the realities of flying through the lower atmosphere, there are some exceptions. By launching a rocket from an aircraft, it can avoid having to power itself up from sea level. This allows the rocket to be smaller and lighter, as it doesn’t require as much propellant nor do its engines need to be as powerful.

The downside of this approach however is that even a relatively small rocket needs a very large aircraft to carry it. For example, Virgin Orbit’s LauncherOne rocket must be carried to launch altitude by a Boeing 747-400 airliner in order to place a 500 kg (1,100 lb) payload into orbit.

But what if there was another way? What if you could get all the benefits of starting your rocket from a higher altitude, without the cost and logistical issues involved in carrying it with a massive airplane? It might sound impossible, but the answer is actually quite simple…all you have to do it throw it hard enough.

Continue reading “SpinLaunch And The History Of Hurling Stuff Into Space” →

Pinning Tails On Satellites To Help Prevent Space Junk

September 13, 2021 by Tom Nardi 32 Comments

Low Earth orbit was already relatively crowded when only the big players were launching satellites, but as access to space has gotten cheaper, more and more pieces of hardware have started whizzing around overhead. SpaceX alone has launched nearly 1,800 individual satellites as part of its Starlink network since 2019, and could loft as many as 40,000 more in the coming decades. They aren’t alone, either. While their ambitions might not be nearly as grand, companies such as Amazon and Samsung have announced plans to create satellite “mega-constellations” of their own in the near future.

At least on paper, there’s plenty of room for everyone. But what about when things go wrong? Should a satellite fail and become unresponsive, it’s no longer able to maneuver its way out of close calls with other objects in orbit. This is an especially troubling scenario as not everything in orbit around the Earth has the ability to move itself in the first place. Should two of these uncontrollable objects find themselves on a collision course, there’s nothing we can do on the ground but watch and hope for the best. The resulting hypervelocity impact can send shrapnel and debris flying for hundreds or even thousands of kilometers in all three dimensions, creating an extremely hazardous situation for other vehicles.

One way to mitigate the problem is to design satellites in such a way that they will quickly reenter the Earth’s atmosphere and burn up at the end of their mission. Ideally, the deorbit procedure could even activate automatically if the vehicle became unresponsive or suffered some serious malfunction. Naturally, to foster as wide adoption as possible, such a system would have to be cheap, lightweight, simple to integrate into arbitrary spacecraft designs, and as reliable as possible. A tall order, to be sure.

But perhaps not an impossible one. Boeing subsidiary Millennium Space Systems recently announced it had successfully deployed a promising deorbiting device developed by Tethers Unlimited. Known as the Terminator Tape, the compact unit is designed to rapidly slow down an orbiting satellite by increasing the amount of drag it experiences in the wispy upper atmosphere.

Continue reading “Pinning Tails On Satellites To Help Prevent Space Junk” →

CubeSat For Under $1000?

April 28, 2021 by Chris Lott 19 Comments

Want to build your own CubeSat but have been put off by the price? There may be a solution in the works — [RG Sat] has challenged himself to design and build one for less than $1,000. (Video, embedded below.)

He begins by doing a survey of available low-cost options in the first video, and finds there isn’t a complete package for less than $10,000. By the time you added all necessary “options”, the final tally would probably be well over $20,000.

His idea isn’t just a pipe dream, either. In the the fifteen months since he began the project, [RG Sat] has designed and built the avionics and electrical power system circuit boards, and is currently testing his sun tracker design. Software is written in Rust, just because he wants to learn something new. You can check out the hardware and software design files on the project’s GitHub repositories, if you are inclined to build one yourself.

[RG Sat] lays out a compelling case, but we wonder if there’s a major gotcha lurking in the dark somewhere. In fact, [RG Sat] himself asks the question, “where do these high costs come from?” Our first instinct is to point the finger at qualifying parts for space and/or testing. But if you don’t care about satellite longevity or failure rates, then maybe [RG Sat] is onto something here.

Stepping back and looking at the big picture, however, the price of a CubeSat can be a drop in the bucket when compared to the launch costs, unless you’ve got a free ride. Is hardware the best place to focus cost reduction efforts? Regardless, [RG Sat]’s project is bound to provide interesting and useful results whether he succeeds in his goal or confirms that indeed you need $10,000 to build a CubeSat. We’ll be following his progress with interest.

We’ve written about open source CubeSats before, and also a port-mortem analysis of a failed mission that contains some good lessons. Thanks to [Jeremy Grosser] for the tip.

Hello From The NearSpace

November 9, 2020 by Matthew Carlson 6 Comments

A key challenge for any system headed up into the upper-atmosphere region sometimes called near space is communicating back down to the ground. The sensors and cameras onboard many high altitude balloons and satellites aren’t useful if the data they collect can’t be retrieved. Often times, custom antennas or beacons are added to help. Looking at the cost and difficulty of the problem, [arko] and [upaut] teamed up to try and make a turn-key solution for any near-space enthusiast by building CUBEX, a wonderful little module with sensors and clever radio that can be easily reused and repurposed.

CUBEX is meant as a payload for a high-altitude balloon with a camera, GPS, small battery, solar cell, and the accompanying power management circuits. The clever bit comes in the radio back down. By using the 434.460 Mhz band, it can broadcast around a hundred miles at 10mW. The only hardware to receive is a radio listener (a cheap RTL USB stick works nicely). Pictures and GPS coordinates stream down at 300 baud.

Their launch was quite successful and while they didn’t catch a solar eclipse, their balloon reached an impressive 33698m (110,560ft) while taking pictures. Even though it did eventually splashdown in the Pacific Ocean, they were able to enjoy a plethora of gorgeous photos thanks to their easy and cost-effective data link.

Continue reading “Hello From The NearSpace” →

Lessons Learned From A CubeSat Postmortem

January 24, 2020 by Tom Nardi 35 Comments

On the 3rd of June 2019, a 1U CubeSat developed by students of the AGH University of Science and Technology in Kraków was released from the International Space Station. Within a few hours it was clear something was wrong, and by July 30th, the satellite was barely functional. A number of problems contributed to the gradual degradation of the KRAKsat spacecraft, which the team has thoroughly documented in a recently released paper.

We all know, at least in a general sense, that building and operating a spacecraft is an exceptionally difficult task on a technical level. But reading through the 20-pages of “KRAKsat Lessons Learned” gives you practical examples of just how many things can go wrong.

It all started with a steadily decreasing battery voltage. The voltage was dropping slowly enough that the team knew the solar panels were doing something, but unfortunately the KRAKsat didn’t have a way of reporting their output. This made it difficult to diagnose the energy deficit, but the team believes the issue may have been that the tumbling of the spacecraft meant the panels weren’t exposed to the amount of direct sunlight they had anticipated.

This slow energy drain continued until the voltage dropped to the point that the power supply shut down, and that’s were things really started going south. Once the satellite shut down the batteries were able to start charging back up, which normally would have been a good thing. But unfortunately the KRAKsat had no mechanism to remain powered down once the voltage climbed back above the shutoff threshold. This caused the satellite to enter into and loop where it would reboot itself as many as 150 times per orbit (approximately 90 minutes).

The paper then goes into a laundry list of other problems that contributed to KRAKsat’s failure. For example, the satellite had redundant radios onboard, but the software on them wasn’t identical. When they needed to switch over to the secondary radio, they found that a glitch in its software meant it was unable to access some portions of the onboard flash storage. The team also identified the lack of a filesystem on the flash storage as another stumbling block; having to pull things out using a pointer and the specific memory address was a cumbersome and time consuming task made all the more difficult by the spacecraft’s deteriorating condition.

Of course, building a satellite that was able to operate for a couple weeks is still an impressive achievement for a student team. As we’ve seen recently, even the pros can run into some serious technical issues once the spacecraft leaves the lab and is operating on its own.

[Thanks to ppkt for the tip.]

Open-Source Satellite Propulsion Hack Chat

December 9, 2019 by Dan Maloney 10 Comments

Join us on Wednesday, December 11 at noon Pacific for the Open-Source Satellite Propulsion Hack Chat with Michael Bretti!

When you look back on the development history of any technology, it’s clear that the successful products eventually reach an inflection point, the boundary between when it was a niche product and when it seems everyone has one. Take 3D-printers, for instance; for years you needed to build one if you wanted one, but now you can buy them in the grocery store.

It seems like we might be getting closer to the day when satellites reach a similar inflection point. What was once the province of nations with deep pockets and military muscles to flex has become far more approachable to those of more modest means. While launching satellites is still prohibitive and will probably remain so for years to come, building them has come way, way down the curve lately, such that amateur radio operators have constellations of satellites at their disposal, small companies are looking seriously at what satellites can offer, and even STEM programs are starting to get students involved in satellite engineering.

Michael Bretti is on the leading edge of the trend toward making satellites more DIY friendly. He formed Applied Ion Systems to address one of the main problems nano-satellites face: propulsion. He is currently working on a range of open-source plasma thrusters for PocketQube satellites, a format that’s an eighth the size of the popular CubeSat format. His solid-fuel electric thrusters are intended to help these diminutive satellites keep station and stay in orbit longer than their propulsion-less cousins. And if all goes well, someday you’ll be able to buy them off-the-shelf.

Join us for the Hack Chat as Michael discusses the design of plasma thrusters, the details of his latest testing, and the challenges of creating something that needs to work in space.

Our Hack Chats are live community events in the Hackaday.io Hack Chat group messaging. This week we’ll be sitting down on Wednesday, December 11 at 12:00 PM Pacific time. If time zones have got you down, we have a handy time zone converter.

Click that speech bubble to the right, and you’ll be taken directly to the Hack Chat group on Hackaday.io. You don’t have to wait until Wednesday; join whenever you want and you can see what the community is talking about.

Hackaday Links: December 8, 2019

December 8, 2019 by Dan Maloney 14 Comments

Now that November of 2019 has passed, it’s a shame that some of the predictions made in Blade Runner for this future haven’t yet come true. Oh sure, 109 million people living in Los Angeles would be fun and all, but until we get our flying cars, we’ll just have to console ourselves with the ability to “Enhance!” photographs. While the new service, AI Image Enlarger, can’t tease out three-dimensional information, the app is intended to sharpen enlargements of low-resolution images, improving the focus and bringing up details in the darker parts of the image. The marketing material claims that the app uses machine learning, and is looking for volunteers to upload high-resolution images to improve its training set.

We’ve been on a bit of a nano-satellite bender around here lately, with last week’s Hack Chat discussing simulators for CubeSats, and next week’s focusing on open-source thrusters for PocketQube satellites. So we appreciated the timing of a video announcing the launch of the first public LoRa relay satellite. The PocketCube-format satellite, dubbed FossaSat-1, went for a ride to space along with six other small payloads on a Rocket Lab Electron rocket launched from New Zealand. Andreas Spiess has a short video preview of the FossaSat-1 mission, which was designed to test the capabilities of a space-based IoT link that almost anyone can access with cheap and readily available parts; a ground station should only cost a couple of bucks, but you will need an amateur radio license to uplink.

We know GitHub has become the de facto standard for source control and has morphed into a collaboration and project management platform used by everybody who’s anybody in the hacking community. But have you ever wished for a collaboration platform that was a little more in tune with the needs of hardware designers? Then InventHub might be of interest to you. Currently in a limited beta – we tried to sign up for the early access program but seem to have been put on a waiting list – it seems like this will be a platform that brings versioning directly to the ECAD package of your choice. Through plugins to KiCad, Eagle, and all the major ECAD players you’ll be able to collaborate with other designers and see their changes marked up on the schematic — sort of a visual diff. It seems interesting, and we’ll be keeping an eye on developments.

Amazon is now offering a stripped-down version of their Echo smart speaker called Input, which teams up with speakers that you already own to satisfy all your privacy invasion needs on the super cheap — only $10. At that price, it’s hard to resist buying one just to pop it open, which is what Brian Dorey did with his. The teardown is pretty standard, and the innards are pretty much what you’d expect from a modern piece of surveillance apparatus, but the neat trick here involved the flash memory chip on the main board. Brian accidentally overheated it while trying to free up the metal shield over it, and the BGA chip came loose. So naturally, he looked up the pinout and soldered it to a micro-SD card adapter with fine magnet wire. He was able to slip it into a USB SD card reader and see the whole file system for the Input. It was a nice hack, and a good teardown.