From: Ulrich Speidel <u.speidel@auckland.ac.nz>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Main hurdles against the Integration of Satellites and Terrestial Networks
Date: Sat, 16 Sep 2023 03:18:22 +1200 [thread overview]
Message-ID: <a2fea86b-58b2-89c6-beab-a7bfc0fa1d47@auckland.ac.nz> (raw)
In-Reply-To: <2012b68c-2e15-4b5c-b36b-3b1d7eff12b4@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2085 bytes --]
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.
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.
--
****************************************************************
Dr. Ulrich Speidel
School of Computer Science
Room 303S.594 (City Campus)
The University of Auckland
u.speidel@auckland.ac.nz
http://www.cs.auckland.ac.nz/~ulrich/
****************************************************************
[-- Attachment #2: Type: text/html, Size: 2845 bytes --]
next prev parent reply other threads:[~2023-09-15 15:18 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 [this message]
2023-09-15 17:52 ` David Lang
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=a2fea86b-58b2-89c6-beab-a7bfc0fa1d47@auckland.ac.nz \
--to=u.speidel@auckland.ac.nz \
--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