From: Eugene Y Chang <eugene.chang@ieee.org>
To: Oleg Kutkov <contact@olegkutkov.me>,
Sirapop Theeranantachai <sirapop741@gmail.com>,
Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] Quick questions about Starlink user terminal
Date: Thu, 11 May 2023 18:22:41 -1000 [thread overview]
Message-ID: <CBC7E0E5-ED3D-4D1E-BB74-DC2C52440F58@ieee.org> (raw)
In-Reply-To: <75e8f43a-5ac2-6ddf-4fb6-da2f6366e7c8@olegkutkov.me>
[-- Attachment #1.1: Type: text/plain, Size: 1393 bytes --]
Usually it is deliberate that equipment does not transmit while receiving. This is to prevent the transmit power from overloading the receiver. This problem can be avoided if the TX and RX are on widely separated freaquencies and antenna configurations to keep the TX signal out of the RX signal path.
What do we know about Starlink’s use of laser links for satellite-to-satellite communications? I am most curious about the challenges of pointing the laser at a moving target.
Gene
----------------------------------------------
Eugene Chang
eugene.chang@ieee.org
o 781-799-0233
> On May 11, 2023, at 12:18 PM, Oleg Kutkov via Starlink <starlink@lists.bufferbloat.net> wrote:
>
> On 5/12/23 01:12, Sirapop Theeranantachai wrote:
>
>> Just a confirmation, HP terminal can work with two satellites at the same time, one for only TX, and the other for only RX. Is this statement still correct?
>
>
> Correct. It's a hardware limitation. A switch inside connects antenna elements to transmitter or receiver chains.
> Plus, each Dishy can do TX only in specified time slots. TX slots depend on the allowed duty cycle and are defined by a global scheduler.
>
> --
> Best regards,
> Oleg Kutkov
>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
[-- Attachment #1.2: Type: text/html, Size: 8185 bytes --]
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-05-12 4:22 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
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 [this message]
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=CBC7E0E5-ED3D-4D1E-BB74-DC2C52440F58@ieee.org \
--to=eugene.chang@ieee.org \
--cc=contact@olegkutkov.me \
--cc=sirapop741@gmail.com \
--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