From: David Lang <david@lang.hm>
To: Mike Puchol <mike@starlink.sx>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Starlink "beam spread"
Date: Wed, 31 Aug 2022 03:06:41 -0700 (PDT) [thread overview]
Message-ID: <s98q46ss-9pnn-n3o0-22q7-38r263n927n5@ynat.uz> (raw)
In-Reply-To: <be8f4d46-f310-4bf4-ade5-2744f301b4ca@Spark>
[-- Attachment #1: Type: text/plain, Size: 1851 bytes --]
I was actually referring to the possibility that the home dishy could point at
different satellites, so you could have multiple satellites pointing at a given
cell on the same frequency, and the dishy can aim it's beam to pick which one to
hear as well as which one to transmit to.
David Lang
On Wed, 31 Aug 2022, Mike Puchol via Starlink wrote:
> On this particular one, the gateway beams are extremely narrow, around 1.5º to 2.5º. SpaceX is working on “mega-gateways” where 32 antennas will co-exist. They are also deploying a new gateway design with a larger antenna, and thus narrower beamwidth and more gain, allowing for a considerable reduction in TX power.
>
> Best,
>
> Mike
> On Aug 31, 2022, 09:33 +0200, David Lang via Starlink <starlink@lists.bufferbloat.net>, wrote:
>> On Wed, 31 Aug 2022, Ulrich Speidel via Starlink wrote:
>>
>>> This combines with the uncomfortable truth
>>> that an RF "beam" from a satellite isn't as selective as a laser beam,
>>> so the options for frequency re-use from orbit aren't anywhere near as
>>> good as from a mobile base station across the road: Any beam pointed at
>>> you can be heard for many miles around and therefore no other user can
>>> re-use that frequency (with the same burst slot etc.).
>>
>> not quite, you are forgetting that the antennas on the ground are also steerable
>> arrays and so they can focus their 'receiving beam' at different satellites.
>> This is less efficient than a transmitting beam as the satellites you aren't
>> 'pointed' at will increase your noise floor, but it does allow the same
>> frequency to be used for multiple satellites into the same area at the same
>> time.
>>
>> David Lang
>> _______________________________________________
>> Starlink mailing list
>> Starlink@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/starlink
>
[-- Attachment #2: Type: text/plain, Size: 149 bytes --]
_______________________________________________
Starlink mailing list
Starlink@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/starlink
next prev parent reply other threads:[~2022-08-31 10:06 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.3.1661875202.32670.starlink@lists.bufferbloat.net>
2022-08-30 16:53 ` David P. Reed
2022-08-30 17:32 ` Doc Searls
2022-08-30 20:09 ` Mike Puchol
2022-08-30 20:35 ` Daniel AJ Sokolov
2022-08-30 20:40 ` Mike Puchol
2022-08-30 21:09 ` David Lang
2022-08-30 21:01 ` David Lang
2022-08-30 22:07 ` Brandon Butterworth
2022-08-30 22:21 ` David Lang
2022-08-30 22:37 ` Brandon Butterworth
2022-08-30 23:07 ` David Lang
2022-08-30 23:45 ` Brandon Butterworth
2022-08-30 23:28 ` David P. Reed
2022-08-31 0:12 ` David Lang
2022-08-31 0:31 ` Dave Taht
2022-08-31 0:32 ` David P. Reed
2022-08-31 10:29 ` Dave Collier-Brown
2022-08-31 18:51 ` David Lang
2022-08-31 19:04 ` Dave Taht
2022-08-30 22:50 ` Ulrich Speidel
2022-08-30 23:13 ` David Lang
2022-08-31 0:46 ` tom
2022-08-31 0:58 ` Dave Taht
2022-08-31 7:36 ` Mike Puchol
2022-08-31 6:26 ` Sebastian Moeller
2022-08-31 7:25 ` Ulrich Speidel
2022-08-31 7:31 ` Hayden Simon
2022-08-31 7:33 ` David Lang
2022-08-31 9:59 ` Mike Puchol
2022-08-31 10:06 ` David Lang [this message]
2022-08-31 10:12 ` Mike Puchol
2022-08-31 17:52 ` Dick Roy
2022-08-31 13:41 ` Ulrich Speidel
2022-08-31 14:30 ` Mike Puchol
2022-08-31 21:44 ` Ulrich Speidel
2022-09-01 7:58 ` Sebastian Moeller
2022-09-01 11:38 ` Ulrich Speidel
2022-09-01 19:54 ` Michael Richardson
2022-09-01 21:08 ` tom
2022-09-02 7:52 ` Sebastian Moeller
2022-09-02 12:29 ` tom
2022-08-31 7:49 ` Sebastian Moeller
2022-08-31 9:25 ` Brandon Butterworth
2022-08-31 9:34 ` David Lang
2022-09-01 9:12 ` Brandon Butterworth
2022-08-31 14:52 ` Dave Taht
2022-08-31 15:22 ` [Starlink] starlink upload behavior Dave Taht
2022-09-01 19:24 ` Luis A. Cornejo
2022-09-01 19:50 ` Dave Taht
2022-08-31 8:15 [Starlink] Starlink "beam spread" David Fernández
2022-08-31 14:51 David Fernández
2022-08-31 18:09 ` Michael Richardson
2022-08-31 21:46 ` Ulrich Speidel
2022-08-31 23:44 ` Lin Han
2022-09-01 19:26 ` Dave Taht
[not found] <mailman.800.1661972667.1281.starlink@lists.bufferbloat.net>
2022-08-31 19:51 ` David P. Reed
2022-08-31 20:28 ` David Lang
2022-08-31 21:17 ` David P. Reed
2022-08-31 21:33 ` David Lang
2022-09-01 7:05 ` Mike Puchol
2022-09-01 11:43 ` Ulrich Speidel
2022-09-01 8:09 ` David Lang
2022-09-01 15:19 David Fernández
2022-09-01 16:33 ` Darrell Budic
2022-09-02 9:32 ` David Fernández
2022-09-01 19:56 ` Michael Richardson
2022-09-02 12:27 ` Sebastian Moeller
2022-09-02 18:34 ` Michael Richardson
2022-09-02 20:11 ` Sebastian Moeller
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=s98q46ss-9pnn-n3o0-22q7-38r263n927n5@ynat.uz \
--to=david@lang.hm \
--cc=mike@starlink.sx \
--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