From: Sebastian Moeller <moeller0@gmx.de>
To: Mike Puchol <mike@starlink.sx>
Cc: Larry Press <lpress@csudh.edu>, David Lang <david@lang.hm>,
Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] starlink at sea
Date: Thu, 14 Jul 2022 13:32:51 +0200 [thread overview]
Message-ID: <42D3F3C5-C1B3-48EA-8C45-2540ACD787E4@gmx.de> (raw)
In-Reply-To: <841ca6dc-d6d3-46ab-87c0-d6bcaa31533b@Spark>
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.
next prev parent reply other threads:[~2022-07-14 11:32 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 [this message]
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
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=42D3F3C5-C1B3-48EA-8C45-2540ACD787E4@gmx.de \
--to=moeller0@gmx.de \
--cc=david@lang.hm \
--cc=lpress@csudh.edu \
--cc=mike@starlink.sx \
--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