Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: "Gary E. Miller" <gem@rellim.com>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Microstate Accounting and the Nyquist problem
Date: Sat, 12 Jun 2021 12:20:14 -0700	[thread overview]
Message-ID: <20210612122014.5338f636@spidey.rellim.com> (raw)
In-Reply-To: <7759ff5d-9d0e-4dd5-8b05-5ea5646b7b5c@Spark>

[-- Attachment #1: Type: text/plain, Size: 1621 bytes --]

Yo Mike!

On Sat, 12 Jun 2021 21:05:19 +0200
Mike Puchol <mike@starlink.sx> wrote:

> Duh… you are correct, I was still on the desktop-sizes ones… but
> would you need one? What I can find is not cheap. It would be
> interesting to work the math eg for Doppler shift compensation which
> could require better accuracy than a “normal” GPS synced timing
> source.

GNSS satellites have many atomic clocks.  Usually three, to start
with.  Some Ceasium, some Rubidium.  They know what time it is, but not
where they are.  Solar winds psuh them around by several meters.  So
ground stations bounce lasers off the sats to reduce the positiion
uncertainty.

After that, the Ionosphere and Troposphere uncertainty dominates.

The doppler can be +/- 10Khz, but the receiver bandwidth is about 250
hz.  So you need to know the doppler before you can lock on the signal
from the bird.

Starlink must have even greater doppler, compensated by a wider receiver
bandwidth.

No way you are improving on what the GNSS folks do.  A lot of black
magic invovled.

For well under $100 you can get a receiver solution that will asily
surpass the clock resolution in a Linux host (<50 ns).  The actual
PPS will be around 15ns.  That can be improved with a bit of external
hardware.

RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
	gem@rellim.com  Tel:+1 541 382 8588

	    Veritas liberabit vos. -- Quid est veritas?
    "If you can't measure it, you can't improve it." - Lord Kelvin

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 851 bytes --]

  reply	other threads:[~2021-06-12 19:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <baa8ff7a-0bde-9d6e-5984-ef5fcbae5ccd@rogers.com>
2021-06-09 13:15 ` [Starlink] Fwd: " Dave Taht
2021-06-11 22:14   ` David Collier-Brown
2021-06-11 22:34     ` Mike Puchol
2021-06-11 22:39       ` [Starlink] " Dave Taht
2021-06-11 22:59         ` Nathan Owens
2021-06-11 23:00         ` Dave Taht
2021-06-11 23:09           ` Mike Puchol
2021-06-18 18:17           ` [Starlink] NTP implementations [was: Microstate Accounting and the Nyquist problem] Juliusz Chroboczek
2021-06-12 14:00         ` [Starlink] Microstate Accounting and the Nyquist problem Michael Richardson
2021-06-12 16:13           ` Mike Puchol
2021-06-12 16:42             ` Nathan Owens
2021-06-12 19:05               ` Mike Puchol
2021-06-12 19:20                 ` Gary E. Miller [this message]
2021-06-12  1:40       ` [Starlink] Fwd: " Karl Auerbach

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=20210612122014.5338f636@spidey.rellim.com \
    --to=gem@rellim.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