Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: David Lang <david@lang.hm>
To: Ulrich Speidel <u.speidel@auckland.ac.nz>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Main hurdles against the Integration of Satellites and Terrestial Networks
Date: Fri, 15 Sep 2023 10:52:56 -0700 (PDT)	[thread overview]
Message-ID: <0q3n1sp5-09r5-5pqn-3p9p-opq883305s1s@ynat.uz> (raw)
In-Reply-To: <a2fea86b-58b2-89c6-beab-a7bfc0fa1d47@auckland.ac.nz>

[-- Attachment #1: Type: text/plain, Size: 2175 bytes --]

On Sat, 16 Sep 2023, Ulrich Speidel via Starlink wrote:

> On 15/09/2023 11:29 pm, Alexandre Petrescu via Starlink wrote:
>> 
>> I must say that I dont know whether the original 'DISHY' is simply a
>> dish antenna with an analog amplifier and maybe some mechanical motor
>> steering, or whether DISHY includes a computer to execute some protocol,
>> some algorithm.

In addition to that Ulrich says, the dishy is a full computer, it's output is 
ethernet/IP and with some adapters or cable changes, you can plug it directly 
into a router.

There are numberous teardown videos on youtube now, for both the original and 
the 1st of the rectangular dishys, they will show you how complex the system is.

David Lang

  >
> It's a phased array, not a dish, even if it looks like one. It consists of 
> 100's of fingernail-sized antenna elements that:
>
> * during transmissions, have an individual phase delay added to the
>   signal transmitted from that element, in order to permit
>   transmission of the combined signal from all elements into a
>   particular direction.
> * during reception, have an individual phase delay added to the signal
>   collected by that element, before the signals are added to obtain
>   the combined received signal. This allows reception from a
>   particular direction.
>
> Dishy's main direction of transmission / reception is therefore not its 
> surface normal - this simply points to the area of the sky where Dishy 
> expects to see most satellites (a function of geographical latitude and 
> constellation design - essentially straight up in the tropics, and elsewhere 
> in the direction of the 53rd parallel, which corresponds to the predominant 
> orbital inclination in the Starlink fleet). The actual tracking is then done 
> with the phased array without mechanical movement by Dishy.
>
> From what I've seen, Dishy seems to consume more power on receive than on 
> transmit - that's if you actually download stuff. This is somewhat 
> counter-intuitive if you're used to putting link budgets together. But I'd 
> attribute that to a higher degree of digital signal processing required on 
> the receive and demodulation path.
>
>

[-- Attachment #2: Type: text/plain, Size: 149 bytes --]

_______________________________________________
Starlink mailing list
Starlink@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/starlink

  reply	other threads:[~2023-09-15 17:52 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-30 12:10 Hesham ElBakoury
2023-08-30 13:57 ` Alexandre Petrescu
2023-08-30 16:51   ` Inemesit Affia
2023-08-30 19:35     ` David Lang
2023-09-01 16:27       ` Inemesit Affia
2023-09-15 11:29         ` Alexandre Petrescu
2023-09-15 15:18           ` Ulrich Speidel
2023-09-15 17:52             ` David Lang [this message]
2023-09-15 23:32               ` Ulrich Speidel
2023-09-17 17:21                 ` Alexandre Petrescu
2023-09-17 19:58                   ` David Lang
2023-09-18 23:32                     ` Hesham ElBakoury
2023-09-19  0:31                       ` David Lang
2023-09-19  0:36                         ` Hesham ElBakoury
2023-09-19  1:01                           ` David Lang
2023-09-19  1:08                             ` [Starlink] [Sat-int] " Jorge Amodio
2023-09-19  1:25                               ` David Lang
2023-09-21  7:58                               ` emile.stephan
2023-09-21 12:37                               ` Alexandre Petrescu
2023-09-19 13:44                           ` [Starlink] " Alexandre Petrescu
2023-09-19 14:36                             ` David Lang
2023-09-19 13:35                       ` Alexandre Petrescu
2023-09-19 14:44                         ` David Lang
2023-09-17 17:12               ` Alexandre Petrescu
2023-09-17 17:09             ` Alexandre Petrescu
2023-09-17 18:06               ` Steve Stroh
2023-08-31  8:44     ` Alexandre Petrescu
2023-08-31 11:39       ` David Lang
  -- strict thread matches above, loose matches on Subject: below --
2023-10-16 13:26 David Fernández
2023-10-18 15:04 ` Alexandre Petrescu
2023-09-19 14:55 David Fernández
2023-09-19 15:15 ` David Lang
2023-09-20  8:09   ` Alexandre Petrescu
2023-09-20  8:32     ` David Lang
2023-09-03  1:03 David Fernández
2023-09-03  3:44 ` Mike Puchol
2023-09-15 11:35 ` Alexandre Petrescu
2023-08-31 16:12 David Fernández
2023-08-31 15:51 David Fernández
2023-08-30 12:02 Hesham ElBakoury

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=0q3n1sp5-09r5-5pqn-3p9p-opq883305s1s@ynat.uz \
    --to=david@lang.hm \
    --cc=starlink@lists.bufferbloat.net \
    --cc=u.speidel@auckland.ac.nz \
    /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