From: Jared Mauch <jared@puck.nether.net>
To: Nitinder Mohan <mohan@in.tum.de>
Cc: Mike Puchol <mike@starlink.sx>,
Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] starlink at sea
Date: Thu, 14 Jul 2022 08:57:14 -0400 [thread overview]
Message-ID: <858AB3A2-EDE0-4035-A4FE-EC2313CC3197@puck.nether.net> (raw)
In-Reply-To: <etPan.62d010c7.38f70598.2a3f@in.tum.de>
I haven’t poked hard, but it does seem you can get it:
currentCellId current_cell_id
Seem to be in the GRPC proto dump from the dish.
https://github.com/sparky8512/starlink-grpc-tools/blob/main/extract_protoset.py
This should pull it out, if you want from my (stationary) dish I bet I can run something to pull/dump the info.
- jared
> On Jul 14, 2022, at 8:49 AM, Nitinder Mohan via Starlink <starlink@lists.bufferbloat.net> wrote:
>
> Hi Mike,
>
> Do you happen to have a tool that can extract the current uplink channel of Starlink and (more importantly) which staellite it is connected to at any given time? I wanted to track the handovers in Starlink and try to find its impact on network performance but cannot seem to get those values.
>
> Thanks and Regards
>
> Nitinder Mohan
> Technical University Munich (TUM)
> https://www.nitindermohan.com/
>
> From: Sebastian Moeller via Starlink <starlink@lists.bufferbloat.net>
> Reply: Sebastian Moeller <moeller0@gmx.de>
> Date: 14. July 2022 at 14:35:16
> To: Mike Puchol <mike@starlink.sx>
> Cc: Dave Taht via Starlink <starlink@lists.bufferbloat.net>
> Subject: Re: [Starlink] starlink at sea
>
>> Hi Mike.
>>
>> Thanks a lot. This is intersting.
>>
>> > On Jul 14, 2022, at 14:02, Mike Puchol <mike@starlink.sx> wrote:
>> >
>> > The uplink is an OFDM signal with 128 subcarriers, looking at the signal in the time domain reveals a frame length corresponding to 14% (from memory, 1,1 us frame vs 6.7 us pause). I have two terminals 1 meter apart and they can each achieve 30 Mbps at the same time over the same uplink channel. I would expect the satellite to assign a particular set of slots to a terminal.
>>
>> So assuming the 30 Mbps being gross rate and not measured goodput:
>>
>> 30Mbps -> 30 / (1.1/(6.7+1.1)) = 212.73 Mb/s while actively sending, and
>> 1000000µs/s / (6.7+1.1)µs = 128205.128205 slots/sec
>> (30 / (1.1/(6.7+1.1))) * 1000^2 / (1000000 / (6.7+1.1)) = 1659.27 bits/slot 1659.27/8 = 207.41 Bytes/slot
>>
>> with 128 subcarriers that would be approximately an average
>>
>> 1659.27/128 = 12.96 or ~ 13 bit/subcarrier
>>
>> if all carriers are loaded equally (which is unlikely, I expect some re-arrangement ot bits between subcarriers to account for different levels of noise and what not).
>>
>>
>> > If there are any OFDM blind analysis experts in the room, shout!
>>
>> Please do!
>> Regards
>> Sebastian
>>
>> >
>> > Best,
>> >
>> > Mike
>> > On Jul 14, 2022, 13:33 +0200, Sebastian Moeller <moeller0@gmx.de>, wrote:
>> >> Hi Mike,
>> >>
>> >>> On Jul 14, 2022, at 13:15, Mike Puchol via Starlink <starlink@lists.bufferbloat.net> wrote:
>> >>>
>> >>> On the multiple terminals, I have verified that the duty cycle of a consumer terminal is 14%, thus, you could have 7 terminals on a single uplink channel with some guard time.
>> >>
>> >> Could you elaborate how that works.how the terminals will be interleaved in that situation?
>> >>
>> >> Regards
>> >> Sebastian
>> >>
>> >>
>> >>> I have seen 30 Mbps up, so you’d be able to push 210 Mbps in uplink, or a spectral efficiency of about 3.4 bps/Hz.
>> >>
>>
>> _______________________________________________
>> Starlink mailing list
>> Starlink@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/starlink
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
next prev parent reply other threads:[~2022-07-14 12:57 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 0:20 Dave Taht
2022-07-14 0:31 ` David Lang
2022-07-14 0:36 ` Gary E. Miller
2022-07-14 0:40 ` David Lang
2022-07-14 0:59 ` Gary E. Miller
2022-07-14 1:36 ` David Lang
2022-07-14 5:46 ` Larry Press
2022-07-14 7:00 ` David Lang
2022-07-14 11:15 ` Mike Puchol
2022-07-14 11:32 ` Sebastian Moeller
2022-07-14 12:02 ` Mike Puchol
2022-07-14 12:34 ` Sebastian Moeller
2022-07-14 12:49 ` Nitinder Mohan
2022-07-14 12:57 ` Jared Mauch [this message]
2022-07-14 13:05 ` Nitinder Mohan
2022-07-14 13:33 ` Nitinder Mohan
2022-07-14 14:56 ` Mike Puchol
2022-07-14 15:28 ` Sebastian Moeller
2022-07-14 15:32 ` Nathan Owens
2022-07-27 21:17 ` Dave Taht
2024-07-02 20:40 Dave Taht
2024-07-03 3:40 ` Ulrich Speidel
2024-07-03 17:21 ` Larry Press
2024-07-03 4:21 ` Marc Blanchet
2024-07-03 4:26 ` J Pan
2024-07-03 17:06 ` Larry Press
2024-07-03 22:06 ` Michael Richardson
2024-07-14 19:32 ` J Pan
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=858AB3A2-EDE0-4035-A4FE-EC2313CC3197@puck.nether.net \
--to=jared@puck.nether.net \
--cc=mike@starlink.sx \
--cc=mohan@in.tum.de \
--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