Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: David Lang <david@lang.hm>
To: Dave Taht <dave.taht@gmail.com>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] starlink at sea
Date: Wed, 13 Jul 2022 17:31:13 -0700 (PDT)	[thread overview]
Message-ID: <134p918o-rr23-q9r6-o9qq-71p0os2596p@ynat.uz> (raw)
In-Reply-To: <CAA93jw6m4_u+Cs+++2HqJrHROK-=VW8BdDYtD9CdZHoMZA_Y7Q@mail.gmail.com>

On Wed, 13 Jul 2022, Dave Taht via Starlink wrote:

> 2) They show 6 starlink terminals on one side of the ship, and 6 on
> the other side (unless it's a reversed image). While I can imagine
> that the downlink can manage that many terminals close by (but how?),
> I find it hard to conceive that the uplinks can co-exist emitting that
> much energy so few feet apart. Are modern phased arrays that good? Has
> anyone experimented with how closely placed two terminals can be?

I would assume that the uplinks are multiplexed under the control of the 
satellites (possibly time-based slots, but other options are possible). In some 
cases it may be possible to reprogram one dish to use a larger share of 
available airtime, but it is much simpler to have multiple standard devices than 
modifying some to use a larger share (not to mention the potential duty cycle 
limits)

In the scale of satellite communication, the satellite can't really tell the 
difference between a few feet apart and a few hundred feet apart, the angle to 
the satellite is too small to resolve the difference.

David Lang

  reply	other threads:[~2022-07-14  0:31 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-14  0:20 Dave Taht
2022-07-14  0:31 ` David Lang [this message]
2022-07-14  0:36 ` Gary E. Miller
2022-07-14  0:40   ` David Lang
2022-07-14  0:59     ` Gary E. Miller
2022-07-14  1:36       ` David Lang
2022-07-14  5:46     ` Larry Press
2022-07-14  7:00       ` David Lang
2022-07-14 11:15         ` Mike Puchol
2022-07-14 11:32           ` Sebastian Moeller
2022-07-14 12:02             ` Mike Puchol
2022-07-14 12:34               ` Sebastian Moeller
2022-07-14 12:49                 ` Nitinder Mohan
2022-07-14 12:57                   ` Jared Mauch
2022-07-14 13:05                     ` Nitinder Mohan
2022-07-14 13:33                       ` Nitinder Mohan
2022-07-14 14:56                         ` Mike Puchol
2022-07-14 15:28                           ` Sebastian Moeller
2022-07-14 15:32                             ` Nathan Owens
2022-07-27 21:17           ` Dave Taht
2024-07-02 20:40 Dave Taht
2024-07-03  3:40 ` Ulrich Speidel
2024-07-03 17:21   ` Larry Press
2024-07-03  4:21 ` Marc Blanchet
2024-07-03  4:26   ` J Pan
2024-07-03 17:06   ` Larry Press
2024-07-03 22:06   ` Michael Richardson
2024-07-14 19:32     ` J Pan

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=134p918o-rr23-q9r6-o9qq-71p0os2596p@ynat.uz \
    --to=david@lang.hm \
    --cc=dave.taht@gmail.com \
    --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