From: J Pan <Pan@uvic.ca>
To: Jim Forster <jim@connectivitycap.com>
Cc: Inemesit Affia <inemesitaffia@gmail.com>,
Starlink <Starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] Question on Startlink density
Date: Wed, 15 Nov 2023 06:38:35 -0800 [thread overview]
Message-ID: <CAHn=e4hGd3UKv=tW1qqnsUxPYtMkn3ZUzkkiHvaHP4Ca=zNZ+g@mail.gmail.com> (raw)
In-Reply-To: <5250C178-F909-4A4C-9724-5862B67D6CE1@connectivitycap.com>
it's not only about the power density. it's more about the satellite
(and ground station) capacity, and interference among these dishes and
with other devices in the same frequency band
only starlink knows for sure its current capacity. we can do some
inference and envelope estimation. if you have 100 households nearby,
a (mini) "community gateway" might be better
--
J Pan, UVic CSc, ECS566, 250-472-5796 (NO VM), Pan@UVic.CA, Web.UVic.CA/~pan
On Wed, Nov 15, 2023 at 12:05 AM Jim Forster <jim@connectivitycap.com> wrote:
>
> Thanks, that’s helpful.
>
> Would is also be the case that “100 dishes in 3km^2” is ok? That’s 100x the power density…
>
> — Jim
>
> On Nov 15, 2023, at 9:07 AM, J Pan <Pan@uvic.ca> wrote:
>
> an old starlink capacity rule of thumb is "100 dishes in a 300 km^2
> cell". not sure about the latest as there are more satellites now, and
> starlink can shuffle beam among nearby cells too
>
>
next prev parent reply other threads:[~2023-11-15 14:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 21:01 [Starlink] run a few scripts behind your starlink dish? J Pan
2023-11-15 6:12 ` [Starlink] Question on Startlink density Jim Forster
2023-11-15 6:55 ` Inemesit Affia
2023-11-15 6:56 ` Inemesit Affia
2023-11-15 7:01 ` Jim Forster
2023-11-15 7:04 ` David Lang
2023-11-15 7:07 ` J Pan
2023-11-15 8:05 ` Jim Forster
2023-11-15 14:38 ` J Pan [this message]
2023-11-15 7:03 ` 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='CAHn=e4hGd3UKv=tW1qqnsUxPYtMkn3ZUzkkiHvaHP4Ca=zNZ+g@mail.gmail.com' \
--to=pan@uvic.ca \
--cc=Starlink@lists.bufferbloat.net \
--cc=inemesitaffia@gmail.com \
--cc=jim@connectivitycap.com \
/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