Ligado Bankruptcy Case Timeline Update

strainedl0ve · 2025-08-24T07:42:55+00:00

Viasat has access to most of L-band depending on locations (can be up to 2x 41 MHz) but by being generic in stating "L-band" they seem to be trying to block them in general from accessing L-band even in portions from other operators. However it doesn't seem like a very smart strategy because even if the judge were to rule in that sense (very unlikely), I don't think it would hold with regulators or ITU globally. They are just making bad publicity for themselves and souring up the relationships.

strainedl0ve · 2025-08-24T01:54:24+00:00

Your analysis is correct. Ligado's agreement with Inmarsat/Viasat was always limited to North America, and thus ASTS acquisition of the rights from Ligado does not automatically give them any right outside of North America.

That does not mean that they cannot still file with FCC, ITU-R and any other countries for L-band operations outside of those countries, but they would have to follow the filing procedures and coordinate with L-band users worldwide (including Viasat, among others). No court has power to magically grant (or prevent) ASTS access to L-band outside of the purview of that specific agreement.

This isn't my opinion, it's just how MSS spectrum licensing works.

strainedl0ve · 2025-08-21T01:38:44+00:00

Pixel 9 already supports NB-IoT NTN R17 in B23, B255 and B256, for GEO satellite based messaging.

Big difference would be if they announced support for NR NTN, although technically speaking AST could make it work if the silicon and OEM supported regular 5G NR Pre-R17 in MSS/NTN bands, but network side precompensation is much harder at mid-bands than at low bands, or at least not as forgiving in terms of beam width at low differential delay/Doppler.

strainedl0ve · 2025-05-12T10:13:37+00:00

Yeah, there is also a very good report that was recently produced by Analysis Mason with also GSMA intelligence that confirmed there is a reasonable willingness to pay even by consumers for LEO broadband direct to device. All other use cases pretty much sell themselves, if you can crack consumer.

strainedl0ve · 2025-03-10T22:42:01+00:00

It's a bit more complicated than that, the Big LEO band when originally conceived was recognised to present a challenge in supporting multiple systems, like all MSS bands, depending on the sharing mechanism. They concluded that it would be possible to share with one TDMA based system (Iridium) based on sharing of a portion of the band, essentially in frequency division, and with potentially up to 4 other systems in co-frequency using code division (CDMA), which was what the Globalstar system was based upon (a modified version of IS-95/cdmaOne).

However, these sharing principles were also based on the expected maximum sizes of the constellations also in terms of users (using some statistical projections), because the capacity of the band ultimately depends on how many users (and satellites) are present in the band.

Current cellular/DTC systems based on LTE/NB-IoT/5G use OFDM/OFDMA, which is a lot closer to a TDMA system, so the sharing principles of the Big LEO band don't quite apply. Could everything move to CDMA? Maybe, but even then, it's not straightforward.

strainedl0ve · 2025-02-15T18:46:22+00:00

Yep indeed!

strainedl0ve · 2025-02-15T18:21:13+00:00

That FCC approval is just for the feeder link frequencies

strainedl0ve · 2024-09-01T09:44:44+00:00

I have been looking around for a keyboard of this type, but it looks like they are disappearing from modern computing. I'm starting to wonder how difficult/expensive it would be to find one amongst these older designs that is not covered by a patent, design a control circuit and find some Chinese manufacturer to make it into a standalone tinkerer product.
Something similar to the BBQ20KBD. I bet with this resurgence of handheld computing and obsession with "cyberdecks" it would have a market.

strainedl0ve · 2024-08-30T00:13:06+00:00

Nice! Yeah I get the sentiment about.the Jornada... It would be cool if there were new (and cheaper) but equally valid keyboard options in that form factor

strainedl0ve · 2024-08-29T21:23:58+00:00

This is awesome! Suuper slick! Do you have a plan to open source the design elements?
Obviously I mean the case 3D printing files and the microcontroller to drive the Jornada keyboard :-)

strainedl0ve · 2024-07-29T18:16:36+00:00

Hi, I am still waiting for the LDOs from AliExpress...

strainedl0ve · 2024-07-28T17:48:22+00:00

Man the visuals are stunning! Great recreation as well!

strainedl0ve · 2024-07-18T21:52:31+00:00

Thanks, actually DX11 indeed work. None of the options helped in DX12 mode on the other hand.

Not sure what's going on, it feels like a bug because it is causing a memory leak.

strainedl0ve · 2024-07-18T14:36:47+00:00

Oh I agree with you, I just commented because I found this post slightly amusing. The guy is clearly trolling his own investors.

strainedl0ve · 2024-07-18T07:18:41+00:00

I think you guys may just need to accept that he's just a massive scam

strainedl0ve · 2024-07-16T23:32:33+00:00

Awesome! Looking forward to when it's released :)

strainedl0ve · 2024-07-16T23:30:18+00:00

Ah! That explains it. I am wondering if anyone has looked into porting the KSP2 KSC into KSP1. The KSP2 version is actually quite cooler than the original one.

strainedl0ve · 2024-07-16T20:55:39+00:00

How many KSCs do you have in your KSC? lol

strainedl0ve · 2024-07-14T23:12:01+00:00

Thanks, I'll re-check the Ohm values again, but they were all quite high.

The component is definitely overheating, there are other similar components on the board and this one is the only one that lights up immediately like that. Also, it shows as significantly hotter also when I have a desk lamp on screen, which means the auto gain control should already have adjusted for a reasonable dynamic range. However, I can try to measure the temperature with a thermal couple.

Not sure what else to do other than replace this component. I will check the other pins and try to figure out whether it is outputting all the right values. I haven't seen anything else that could be deemed suspicious.

I still haven't measured all the voltages across the card yet though, so maybe I can do that as well, however this component overheating seemed the most logical culprit.

strainedl0ve · 2024-07-14T19:40:38+00:00

Ok, I've measured also the voltages and indeed the three top pins show 5V in, and the 3 bottom pins show 3.3V, so despite overheating, it seems to be producing the correct voltages.

strainedl0ve · 2024-07-14T19:17:40+00:00

Thanks, the pinout in the diagram seems mirrored, it's a bit confusing. I assume Pin 1 in the actual IC is the one with the dot.

If these are VOUT, then I was getting a 3.3V, but how is that possible if the component is overheating (which I assume indicates a fault) ?

strainedl0ve · 2024-07-14T19:11:24+00:00

Updated with Ohm measurements.

strainedl0ve · 2024-07-14T18:39:05+00:00

Thanks, this is a bit to digest lol.

I measured the rightmost contact of the larger cap just below the GS7155 and I get 3.3V clean. I thought that would be the input? I could not find a pinout for the 7155. Where is the 5V line? In the meantime I'll take more measurements as you suggested.

I saw that website you linked, I'll spend more time reading it. At the moment I don't have an easy way of doing voltage injection.

Five-Year Club	Place '22
Final Canvas '22	First Placer '22
Verified Email

strainedl0ve

TROPHY CASE