Starlink’s Inter-Satellite Laser Links Are Setting New Record With 42 Million GB Per Day

Slide from the SpaceX Starlink presentation on mesh routing via the laser links. (Credit: PCMag/Michael Kan)
Slide from the SpaceX Starlink presentation on mesh routing via the laser links. (Credit: PCMag/Michael Kan)

Although laser communication in space is far from novel, its wide-scale deployment as seen with SpaceX’s Starlink satellite internet constellation has brought the technology to the forefront like never before. This was quite apparent during the SPIE Photonics West event on January 30th when [Michael Kan] and other journalists attended a presentation by SpaceX’s [Travis Brashears] on the inter-satellite laser communication performance that was first enabled with the Starlink v1.5 satellites.

Among currently active inter-satellite communication systems, Starlink is by far the most numerous and with the highest bandwidth, reaching over 42 PB per day across its over 9000 space lasers (yes, that is over 9000) for a 5.6 Tbps throughput. Since these satellites form a mesh network with their 100 Gbps laser transceivers, a big part of using it efficiently is to route any data with the least amount of latency while taking into account link distance (maximum of 5,400 km), link duration (up to multiple weeks) and presence of other Starlink satellites before they become within reach. With this complex mesh in LEO, this also means that a very high uptime can be accomplished, with a claimed 99.99% due to rapid route changing.

For the future, SpaceX has plans to not only keep upgrading its own Starlink satellites with better laser transceivers, but to also make them available to third-party satellites, as well as beam the lasers directly down to Earth for ground-based transceivers. The latter is still cutting edge, despite it being tested to beam cat videos to Earth from Deep Space.

The Past, Present, And Future Of Inflatable Space Habitats

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.

Continue reading “The Past, Present, And Future Of Inflatable Space Habitats”

3D Printed Axial Compressor Is On A Mission To Inflate Balloons

[Let’s Print] has been fascinated with creating a 3D printed axial compressor that can do meaningful work, and his latest iteration mixes FDM and SLA printed parts to successfully inflate (and pop) a latex glove, so that’s progress!

Originally, the unit couldn’t manage even that until he modified the number and type of fan blades on the compressor stages. There were other design challenges as well. For example, one regular issue was a coupling between the motor and the rest of the unit breaking repeatedly. At the speeds the compressor runs at, weak points tend to surface fairly quickly. That’s not stopping [Let’s Print], however. He plans to explore other compressor designs in his quest for an effective unit.

Attaching motor shafts to 3D printed devices can be tricky, and in the past we’ve seen a clever solution that is worth keeping in mind: half of a spider coupling (or jaw coupling) can be an economical and effective way to attach 3D printed things to a shaft.

While blowing up a regular party balloon is still asking too much of [Let’s Print]’s compressor as it stands, it certainly inflates (and pops) a latex glove like nobody’s business.

Continue reading “3D Printed Axial Compressor Is On A Mission To Inflate Balloons”

Hackaday Links Column Banner

Hackaday Links: January 28, 2024

From the “No good deed goes unpunished” files, this week came news of a German programmer who probably wishes he had selected better clients. According to Heise Online (English translation), a freelance programmer — referred to only as “defendant” in the article — was retained by a company to look into a database problem in their system. His investigation revealed that the customer’s database was being filled with log messages from a third-party service called Modern Solution GmbH & Co. KG. over a MySQL connection to a remote server. Assuming this connection was dedicated for his client’s use, the programmer looked at the executable used to make the connection with a text editor, which revealed a password in plain text. Upon connecting to the remote database, he found that it not only contained data for all of Modern Solution’s customers, but also data for all the end users of their customers.

Realizing he’d unintentionally wandered into verboten territory, the programmer immediately backed out and contacted Modern Solutions. They quickly fixed the issue, and then just as quickly reported him to the police. Their “investigation” revealed that the programmer had “decompiled” the executable to obtain the password, in violation of German law. The judge agreed, stating that merely looking at and using the password constituted a criminal offense, regardless of intent and despite the fact that Modern Solution had provided the password to the programmer’s client when they sold them the software. The upshot of all of this nonsense? A €3,000 fine for the programmer, if the verdict stands on appeal. It could have been worse, though; German law allows for up to three years in prison for such offenses.

Continue reading “Hackaday Links: January 28, 2024”

This Week In Security: MOAB, Microsoft, And Printers

This week, news has broken of the Mother of All Breaches, MOAB. It’s 12 terabytes and 26 billion records, averaging about 500 bytes each. Now note that a record here is likely not a discrete email address, but simply a piece of data — a row on the database.

Now before we all lose our minds over this, there’s an important detail to take note of: These aren’t new leaks. This is a compilation of leaks, and as far as researchers have checked, there aren’t any new leaks disclosed here. This was someone’s database of accumulated leak data, accidentally re-leaked via an unsecured database. [Troy Hunt] goes so far as to speculate that it could be from a breach search service, which sounds pretty plausible.

There was yet another release of credentials late last week that hasn’t attracted as much attention, but seems to represent a much bigger issue. The Naz.api data set isn’t a breach where a company was hacked, and their entire user database was stolen. Instead, this one is combination of a credential stuffing list and stealer logs.

Credential stuffing is basically a smarter brute force attack, where the credentials from one breach are tried on multiple other sites. Such a list is just the results where guesses were successful. The really interesting bit is that this dataset seems to include stealer logs. Put simply, that’s the results of malware that scrapes victim machines for credentials.

Naz.api has over 70 million unique email addresses, and it looks like about a third of them are new, at least according to the Haveibeenpwned dataset. Now that’s significant, though not really worthy of the MOAB title, either. Continue reading “This Week In Security: MOAB, Microsoft, And Printers”

Read QR Codes Without A Computer

Did you ever watch Star Wars and wondered how people understood what R2D2 was saying? Maybe [Luke Skywalker] would enjoy learning to decode QR Codes by hand, too. While it might not be very practical, it would be a good party trick — assuming, like us, you party with nerds.

You can start by scanning a code, or the site will create one according to your specifications or generate one randomly. It then takes the selected code and shows you how it is put together. Fun fact: 21×21 “modules” (QR-speak for pixels) is the size of a version 1 QR code. Each version increases the size by four modules.

Continue reading “Read QR Codes Without A Computer”

Alarm Panel Hack Defeats Encryption By Ignoring It

As frustrating as it may be for a company to lock you into its ecosystem by encrypting their protocols, you have to admit that it presents an enticing challenge. Cracking encryption can be more trouble than it’s worth, though, especially when a device gives you all the tools you need to do an end-run around their encryption.

We’ll explain. For [Valdez], the encrypted communication protocols between a DSC alarm panel and the control pads on the system were serious impediments to integration into Home Assistant. While there are integrations available for these alarm panels, they rely on third-party clouds, which means that not only is your security system potentially telling another computer all your juicy details, but there’s also the very real possibility that the cloud system can either break or be shut down; remember the Chamberlain MyQ fiasco?

With these facts in mind, [Valdez] came up with a clever workaround to DSC encryption by focusing on physically interfacing with the keypad. The device has a common 16×2 LCD and a 25-key keypad, and a little poking around with a multimeter and a $20 logic analyzer eventually showed that the LCD had an HD44780 controller, and revealed all the lines needed to decode the display with an ESP32. Next up was interfacing with the keypad, which also involved a little multimeter work to determine that the keys were hooked up in a 5×5 matrix. Ten GPIOs on the ESP32 made it possible to virtually push any key; however, the ten relays [Valdez] originally used to do the switching proved unwieldy. That led to an optocoupler design, sadly not as clicky but certainly more compact and streamlined, and enabling complete control over the alarm system from Home Assistant.

We love this solution because, as [Valdez] aptly points out, the weakest point in any system is the place where it can’t be encrypted. Information has to flow between the user and the control panel, and by providing the electronic equivalents to eyes and fingers, the underlying encryption is moot. Hats off to [Valdez] for an excellent hack, and for sharing the wealth with the HA community.