From: Ulrich Speidel <u.speidel@auckland.ac.nz>
To: David Lang <david@lang.hm>
Cc: Michael Richardson <mcr@sandelman.ca>,
"starlink@lists.bufferbloat.net" <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] Starlink power use & satellite tracking
Date: Sun, 19 Feb 2023 01:36:42 +1300 [thread overview]
Message-ID: <c4f11dc3-7da9-dfc1-54da-936dc56fcb59@auckland.ac.nz> (raw)
In-Reply-To: <9o926n83-59qp-2p27-459r-q66n48s58n1n@ynat.uz>
On 18/02/2023 11:52 pm, David Lang wrote:
> On Sat, 18 Feb 2023, Ulrich Speidel via Starlink wrote:
>
>> This requires the satellite to be in view of both terminal and
>> gateway. There is, however, no reason why a user's packets could not
>> travel via a diversity of satellites.
>
> In theory you are correct, but I don't think they are doing that yet.
> We had a discussion of the signaling protocol and someone posted that
> they had done research and found that there was only one satellite
> illuminating a cell at a time. IIRC this was when the paper came out
> on using starlink signals for positioning.
Given that the number of satellites has effectively doubled over the
last year, does this still hold? For handover purposes, dishy must be
tracking multiple satellites anyway, and exchanging successive packets
with different satellites shouldn't be all that difficult then.
I've just run a series of 20 speedtest.net test and tried to spy the
upload / download power usage half-way through each test. The result
shows a significantly stronger correlation between power use and
download final rate than between power use and upload final rate. Of
course, it's a small sample, and I'll try to do a few more tomorrow.
Of course, if it receives from multiple birds at the same time, then
that would keep its signal processor a little busier than if it only
received from one. So maybe it's that. Or maybe we're looking at one
bird with multiple channels/bursts, also imposing a higher compute load?
Also intriguing: In the past, we used to see typical power usage in the
80-100 W range with the thing, maybe as low as 60 W if I caught it
lucky. But now it's within the official specs of 40-75 W most of the
time, and it's changed this week.
>
> As they launch more satellites and get the in-space routing up and
> running, I expect that they will change that at some point.
>
> it is an interesting question.
>
> David Lang
>
> _______________________________________________
> 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-02-18 12:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 23:08 Ulrich Speidel
2023-02-16 23:12 ` Nathan Owens
2023-02-16 23:14 ` Nathan Owens
2023-02-16 23:25 ` Jonathan Bennett
2023-02-16 23:23 ` David Lang
2023-02-16 23:36 ` David Lang
2023-02-17 1:24 ` Bruce Perens
2023-02-17 5:27 ` Ulrich Speidel
2023-02-17 5:31 ` Nathan Owens
2023-02-17 15:43 ` Michael Richardson
2023-02-17 19:13 ` Bruce Perens
2023-02-18 10:25 ` Ulrich Speidel
2023-02-18 10:52 ` David Lang
2023-02-18 12:36 ` Ulrich Speidel [this message]
2023-02-18 20:13 ` Bruce Perens
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=c4f11dc3-7da9-dfc1-54da-936dc56fcb59@auckland.ac.nz \
--to=u.speidel@auckland.ac.nz \
--cc=david@lang.hm \
--cc=mcr@sandelman.ca \
--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