From: Oleg Kutkov <contact@olegkutkov.me>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Satellites Beamforming
Date: Mon, 2 Dec 2024 22:04:03 +0200 [thread overview]
Message-ID: <3e8dd962-26ff-4917-9210-5f19176bb713@olegkutkov.me> (raw)
In-Reply-To: <CAFvDQ9rdG96x=-5A7D47i1QmqRitkO5JQ3KQbFVgnrbYd2p2Jg@mail.gmail.com>
Beamforming implies multiple antennas to form the beam.
A typical GNSS CRPA antenna uses 4-6 antennas to form the "vector" and
discard all interfering and false signals from non-sky directions.
On 12/2/24 21:43, Hesham ElBakoury via Starlink wrote:
> Has anyone worked with multi antenna GNSS systems that specifically
> utilize beamforming and other directional techniques?
>
> Can beamforming eliminate the need for more antennas to handle jammer?
>
> Thanks
> Hesham
>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
--
Best regards,
Oleg Kutkov
prev parent reply other threads:[~2024-12-02 20:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 19:43 Hesham ElBakoury
2024-12-02 20:04 ` Oleg Kutkov [this message]
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=3e8dd962-26ff-4917-9210-5f19176bb713@olegkutkov.me \
--to=contact@olegkutkov.me \
--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