From: Ulrich Speidel <u.speidel@auckland.ac.nz>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Quick questions about Starlink user terminal
Date: Fri, 12 May 2023 12:43:46 +1200 [thread overview]
Message-ID: <0262654c-382d-6925-0f31-a187d907c1e8@auckland.ac.nz> (raw)
In-Reply-To: <75e8f43a-5ac2-6ddf-4fb6-da2f6366e7c8@olegkutkov.me>
[-- Attachment #1: Type: text/plain, Size: 2140 bytes --]
On a side note (TX vs RX):
When people look at the "speed" of Internet connections, there's often a
focus on "down" as opposed to "up".
For folk working from home using cloud storage for audio or video
content that they edit, not having a lot of "up" is an issue.
Here's what to expect around our neck of the woods:
https://comcom.govt.nz/__data/assets/pdf_file/0023/314816/MBNZ-Summer-Report-2-May-2023.pdf
(page 7 and 9)
Now one of the interesting bits about Starlink is that its uplink
performance is really not that great in comparison to downlink here in
NZ - pretty much the worst of the current technologies:
This agrees with what I've seen here personally. ADSL in non-fibre areas
generally now means "miles from the DSLAM", as does VDSL. DSLAM-side
crosstalk tends to be the limiting factor there.
Non-fibre areas also generally mean "far from the base station". HFC is
available in only a few select areas here as NZ does not have large
cable networks.
On 12/05/2023 10:18 am, Oleg Kutkov via Starlink wrote:
> On 5/12/23 01:12, Sirapop Theeranantachai wrote:
>
> > Just a confirmation, HP terminal can work with two satellites at the
> > same time, one for only TX, and the other for only RX. Is this
> > statement still correct?
>
>
> Correct. It's a hardware limitation. A switch inside connects antenna
> elements to transmitter or receiver chains.
> Plus, each Dishy can do TX only in specified time slots. TX slots depend
> on the allowed duty cycle and are defined by a global scheduler.
>
> --
> Best regards,
> Oleg Kutkov
>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
> <https://lists.bufferbloat.net/listinfo/starlink>
--
****************************************************************
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.1: Type: text/html, Size: 3418 bytes --]
[-- Attachment #2.2: e0OmsNLmR6O2npRy.png --]
[-- Type: image/png, Size: 39248 bytes --]
next prev parent reply other threads:[~2023-05-12 0:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 21:48 Sirapop Theeranantachai
2023-05-11 21:58 ` Ulrich Speidel
2023-05-11 23:47 ` David Lang
2023-05-11 22:05 ` Oleg Kutkov
2023-05-11 22:12 ` Sirapop Theeranantachai
2023-05-11 22:18 ` Oleg Kutkov
2023-05-11 22:22 ` Sirapop Theeranantachai
2023-05-12 0:43 ` Ulrich Speidel [this message]
2023-05-12 4:22 ` Eugene Y Chang
2023-05-12 4:28 ` David Lang
2023-05-12 4:39 ` Eugene Y Chang
2023-06-05 19:03 ` Sirapop Theeranantachai
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=0262654c-382d-6925-0f31-a187d907c1e8@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