From: Michael Richardson <mcr@sandelman.ca>
To: Mike Puchol <mike@starlink.sx>,
starlink@lists.bufferbloat.net, Dave Taht <dave.taht@gmail.com>,
Mark Handley <mark@handley.org.uk>
Subject: Re: [Starlink] thinking about the laser links again
Date: Tue, 26 Oct 2021 13:51:51 -0400 [thread overview]
Message-ID: <28034.1635270711@localhost> (raw)
In-Reply-To: <e6088411-1d1f-46e6-ba08-46bfe4c6b669@Spark>
[-- Attachment #1: Type: text/plain, Size: 1936 bytes --]
Mike Puchol <mike@starlink.sx> wrote:
> I could bore you to death but here’s a quick test you can do: grab a
> laser pointer and try to keep it on a target the size of the laser dot
> on a wall 10-15 meters away. You’ll quickly see why doing that at
I fail, because the cat attacks me :-)
(our cats somehow know when we get the laser pointers out, even if the
batteries are dead...)
> The logical thing to start with would be to keep every shell
> interconnected, but not to try to cross-link shells. For this,
> ground-to-satellite links come into play.
Or they could interconnect using microwaves, couldn't they?
It's all just different parts of the EM spectrum after all :-)
> How do you make capacities in the petabits per second around your space
> segment useful? You need to deliver to the ground eventually. IMHO the
> only way this will hapen is ground-to-satellite links, with the ground
> stations either in a few, as cloudless as possible locations, or many
> stations in as geographically diverse configuration as possible, so
> that at least some will not have cloud cover.
> Once you have the ground links to each shell, they can be used to
> offload to internet backbones, or you can relay data between shells,
> without complicating your pointing & tracking on the satellites.
What about going the other way? Interconnect via GEO?
Or something resonant to the earth that is not quite so far?
> Mark Handley makes a very good job at explaining in this video (and
> others he has posted): https://www.youtube.com/watch?v=QEIUdMiColU
Thnk you for the link.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | IoT architect [
] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2021-10-26 17:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 1:26 Dave Taht
2021-10-26 13:49 ` Mike Puchol
2021-10-26 17:51 ` Michael Richardson [this message]
2021-10-27 6:20 ` Ulrich Speidel
2021-10-27 7:03 ` David Lang
2021-10-27 9:34 ` Ulrich Speidel
2021-10-27 10:49 ` David Lang
2021-10-27 18:37 ` Michael Richardson
2021-10-27 18:29 ` Michael Richardson
2021-10-28 8:00 ` Ulrich Speidel
2021-10-28 10:52 ` Mike Puchol
2021-10-29 1:12 ` Dave Taht
2021-10-29 1:50 ` David Lang
2021-10-29 2:01 ` Dave Taht
2021-10-29 3:06 ` David Lang
2021-10-29 2:38 ` Steve Crocker
2021-10-29 3:08 ` David Lang
2021-10-29 13:13 ` Michael Richardson
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=28034.1635270711@localhost \
--to=mcr@sandelman.ca \
--cc=dave.taht@gmail.com \
--cc=mark@handley.org.uk \
--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