From: Mike Puchol <mike@starlink.sx>
To: starlink@lists.bufferbloat.net, Dave Taht <dave.taht@gmail.com>
Subject: Re: [Starlink] not that I consider the dailymail credible but
Date: Sun, 20 Mar 2022 15:25:13 +0100 [thread overview]
Message-ID: <f1d17950-dba4-485e-ad48-32fed16819a3@Spark> (raw)
In-Reply-To: <CAA93jw668r9frGEbPzX0S=9ZpUOOYsfTxyGGE1nNUxjgq-2xtQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1197 bytes --]
There seems to be some confusion on this one - the drones are not capable of directly using Starlink. The drone’s short to medium range air-to-ground data & video link can be relayed by the drone’s local controller to a command post over a Starlink internet connection. The command post could also be using Starlink, but the scenario looks like this:
The drone is presumed to be remote and only having Starlink as the uplink towards the command post. The command post could be in a position to be served by fiber, and use Starlink as a backup (or vice-versa). I have assumed the drone’s data link works at 5 GHz, but it could be on any band.
Best,
Mike
On Mar 20, 2022, 12:15 +0100, Dave Taht <dave.taht@gmail.com>, wrote:
> https://www.dailymail.co.uk/news/article-10630625/Elon-Musks-internet-allowing-Ukrainian-drones-pound-Putins-helpless-tanks.html
>
> --
> I tried to build a better future, a few times:
> https://wayforward.archive.org/?site=https%3A%2F%2Fwww.icei.org
>
> Dave Täht CEO, TekLibre, LLC
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
[-- Attachment #2.1: Type: text/html, Size: 1818 bytes --]
[-- Attachment #2.2: Drone served over Starlink.png --]
[-- Type: image/png, Size: 48283 bytes --]
next prev parent reply other threads:[~2022-03-20 14:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-20 11:15 Dave Taht
2022-03-20 14:25 ` Mike Puchol [this message]
2022-03-21 21:29 ` Dave Täht
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=f1d17950-dba4-485e-ad48-32fed16819a3@Spark \
--to=mike@starlink.sx \
--cc=dave.taht@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