Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: "Dick Roy" <dickroy@alum.mit.edu>
To: "'Nathan Owens'" <nathan@nathan.io>,
	"'Steve Golson'" <sgolson@trilobyte.com>
Cc: <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] Starlink Roaming
Date: Mon, 21 Feb 2022 17:19:13 -0800	[thread overview]
Message-ID: <7AF3C232602E4C33917C55A746F54460@SRA6> (raw)
In-Reply-To: <CALjsLJtxV7djoyxpuV5gva-t4Xnok5CykisKONg5iRvD6aZjLw@mail.gmail.com>

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

 

 

  _____  

From: Starlink [mailto:starlink-bounces@lists.bufferbloat.net] On Behalf Of
Nathan Owens
Sent: Monday, February 21, 2022 3:16 PM
To: Steve Golson
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Starlink Roaming

 

Oh duh, yes, reading the wrong bit. It definitely has GPS, but beyond that,
not sure. 

 

On Mon, Feb 21, 2022 at 3:08 PM Steve Golson <sgolson@trilobyte.com> wrote:

On 2/21/22 4:58 PM, Nathan Owens wrote:
> Per the debug data, the dish has GPS, a Gyroscope, a Magnetometer, and an
Accelerometer.

Actually, the app is reporting the sensors that your phone has, not what the
dish has.

The dish has GPS and accelerometer at least. Perhaps a magnetometer as well,
but it can find north just using GPS.

[RR] I'd be interested in knowing how the dishy gets orientation from GPS.
Does it have three spatially diverse GPS antennas and receivers so it can
determine its orientation?  I suspect not. Also, a single accelerometer and
magnetometer are generally insufficient to uniquely determine orientation in
3-D space.  There's clearly a bit more to this to uncover:-)))  

 

RR



-Steve

-- 
Steve Golson / Trilobyte Systems / +1.978.369.9669 / sgolson@trilobyte.com
Consulting in: Verilog, synthesis, patent analysis, reverse engineering
_______________________________________________
Starlink mailing list
Starlink@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/starlink


[-- Attachment #2: Type: text/html, Size: 6229 bytes --]

  reply	other threads:[~2022-02-22  1:19 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-14 19:53 Jonathan Bennett
2022-02-14 20:29 ` David Lang
2022-02-14 21:43   ` Mike Puchol
2022-02-14 21:53     ` Jonathan Bennett
2022-02-14 21:59       ` Mike Puchol
2022-02-21  7:22   ` Larry Press
2022-02-21  7:29     ` David Lang
2022-02-21 20:31       ` Dick Roy
2022-02-21 20:43         ` Mike Puchol
2022-02-21 20:52           ` David Lang
2022-02-21 21:17             ` Dick Roy
2022-02-21 21:32               ` David Lang
2022-02-21 21:58                 ` Nathan Owens
2022-02-21 22:26                   ` Dick Roy
2022-02-21 23:08                   ` Steve Golson
2022-02-21 23:15                     ` Nathan Owens
2022-02-22  1:19                       ` Dick Roy [this message]
2022-02-21 22:02             ` Daniel AJ Sokolov
2022-02-22  2:17               ` David Lang
2022-02-22  5:34                 ` Mike Puchol
2022-02-22  7:20                   ` Dick Roy
2022-02-22  7:42                     ` Mike Puchol
2022-02-22  7:51                       ` Dick Roy
2022-02-22  9:03                       ` Sebastian Moeller
2022-02-22  9:40                         ` Mike Puchol
2022-02-22  9:46                           ` Sebastian Moeller
2022-02-22 10:01                             ` Mike Puchol
2022-02-22 10:37                               ` Vint Cerf
2022-02-22 11:14                                 ` Mike Puchol
2022-02-22  7:58                     ` Ulrich Speidel
2022-02-22  8:51                   ` David Lang
2022-02-22  7:47                 ` Dick Roy
2022-02-22  8:55                   ` David Lang
2022-02-22 23:14                     ` Dick Roy

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=7AF3C232602E4C33917C55A746F54460@SRA6 \
    --to=dickroy@alum.mit.edu \
    --cc=nathan@nathan.io \
    --cc=sgolson@trilobyte.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