From: David Lang <david@lang.hm>
To: Ulrich Speidel <u.speidel@auckland.ac.nz>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Quick questions about Starlink user terminal
Date: Thu, 11 May 2023 16:47:42 -0700 (PDT) [thread overview]
Message-ID: <8p6ooqq3-5rnp-3p70-7oq2-2090p20porpo@ynat.uz> (raw)
In-Reply-To: <3a526869-c718-6e25-e84b-e973427acdbc@auckland.ac.nz>
On Fri, 12 May 2023, Ulrich Speidel via Starlink wrote:
> 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.
We don't know if this is a hardware limitation or a software limitation, what we
can observe is that currently it doesn't appear to do multiple connections.
David Lang
next prev parent reply other threads:[~2023-05-11 23:47 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 [this message]
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=8p6ooqq3-5rnp-3p70-7oq2-2090p20porpo@ynat.uz \
--to=david@lang.hm \
--cc=starlink@lists.bufferbloat.net \
--cc=u.speidel@auckland.ac.nz \
/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