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 09:58:58 +1200 [thread overview]
Message-ID: <3a526869-c718-6e25-e84b-e973427acdbc@auckland.ac.nz> (raw)
In-Reply-To: <CAPcR1WqL++WbAqee36+8j1GAV+MiJRpk=z9Z7Gc6+2RxTieACQ@mail.gmail.com>
On 12/05/2023 9:48 am, Sirapop Theeranantachai via Starlink wrote:
> Hi, I'm currently working on packet simulation analysis over large LEO
> constellations such as Starlink, and I do have a few questions on the
> Starlink commodity terminals and ISL.
>
> 1) Is the commodity hardware capable of forming multiple GSL channels
> to multiple satellites? If it's not possible, is it possible that the
> hardware allows multiple downlink but only one uplink?
Based on our observations, no to both questions - one sat at a time.
We've noticed that power use goes up with observed downlink rate,
though. Mike Puchol might be able to comment a bit more here as he's
tried to get between Dishy and the birds.
>
> 2) Does Starlink currently use laser ISL or is it planning in the
> future? If so, how is the link performance due to laser accuracy?
Laser links are in use, and most likely also between different orbital
planes, but use is a bit weird. Traffic from Tarawa (Kiribati) emerges
onto the Internet in Auckland, NZ, 4200 km away and not near a common
orbital plane in Starlink's dominant 53.2 deg constellation. Link
performance - how long is a piece of string? We've seen significant
transient outages from Tarawa, but when there is no outage, rates are
comparable to what you'd get elsewhere (anecdotally - we haven't seen
any actual test results from there yet, the owner of the only unit there
has reported regulatory issues).
>
> Best,
> Mark
>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> 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/
****************************************************************
next prev parent reply other threads:[~2023-05-11 21:59 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 [this message]
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
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=3a526869-c718-6e25-e84b-e973427acdbc@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