Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Ulrich Speidel <u.speidel@auckland.ac.nz>
To: David Lang <david@lang.hm>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Starship's 4th flight test was magnificent
Date: Tue, 11 Jun 2024 00:15:09 +1200	[thread overview]
Message-ID: <bac7aecc-a5dd-4d0c-9d24-3a5df19e325b@auckland.ac.nz> (raw)
In-Reply-To: <n4p78557-s44s-0oqr-3r15-1po5rp64487q@ynat.uz>

On 11/06/2024 12:04 am, David Lang wrote:
> As I understand it, Starlink does not have ground stations transmit 
> towards the geostationary satellites, they only target the starlinks 
> when they are not in line to avoid exactly this problem)
Correct.
>
>> Conventionally, if you had to communicate your re-entry video or 
>> audio feed to a ground station, you had to communicate *through* that 
>> cone's wall. Similarly, if you wanted to go "up", you had to go to a 
>> TDRSS satellite, of which there were only a small number in orbit - 
>> and the one visible to you would have been on the other side of the 
>> plasma cone wall with high probability. With Starlink, you have 
>> potentially a few dozen satellites within field of view, and the 
>> chances of having one within view out the back of the cone are 
>> relatively good (but not guaranteed). The other day, they got lucky 
>> that the star(link)s lined up ;-)
>
> As I underand it, it's not just luck, the Starship is so much larger 
> than anything else that the plasma does not just wrap around the craft 
> and close up behind it, the sheer size of the craft gives the plasma a 
> chance to cool a bit (and you can see that in the videos)
That'll probably help, yes.
>
> Also, if it was 'luck' then they were lucky on both Starship reentry 
> flights (and since the ship was tumbling during flight 3, that would 
> be saying a lot)

I guess the problem is hard to quantify - essentially you have to have a 
Starlink satellite that's within the steering cone of one of the phased 
arrays on Starship AND the path to which doesn't lead through a cone 
wall AND that's been assigned to serve that particular phased array AND 
that needs to work out through handovers to other satellites for your 
entire flight. That's probably possible a large percentage of the time 
given the number of sats about now, but perhaps not 100% (yet), 
especially around tropical latitudes where satellite density is about 
half of what you get in the 30's to mid-50's. And yes I guess they were 
probably lucky in that sense, yes.


-- 
****************************************************************
Dr. Ulrich Speidel

School of Computer Science

Room 303S.594 (City Campus)
Ph: (+64-9)-373-7599 ext. 85282

The University of Auckland
ulrich@cs.auckland.ac.nz
http://www.cs.auckland.ac.nz/~ulrich/
****************************************************************


  reply	other threads:[~2024-06-10 12:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-09 23:50 Dave Taht
2024-06-10  0:15 ` Ulrich Speidel
2024-06-10  2:22 ` Michael Richardson
2024-06-10 10:51   ` Ulrich Speidel
2024-06-10 12:04     ` David Lang
2024-06-10 12:15       ` Ulrich Speidel [this message]
2024-06-10  2:38 ` David Lang
2024-06-10 11:04   ` Ulrich Speidel
2024-06-10 12:06     ` David Lang
2024-06-10 12:21       ` Ulrich Speidel
2024-06-10  8:57 ` Alexandre Petrescu
2024-06-10  9:49   ` David Lang
2024-06-10 13:22     ` Alexandre Petrescu
2024-06-10 13:37       ` David Lang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/starlink.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bac7aecc-a5dd-4d0c-9d24-3a5df19e325b@auckland.ac.nz \
    --to=u.speidel@auckland.ac.nz \
    --cc=david@lang.hm \
    --cc=starlink@lists.bufferbloat.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox