From: "Dick Roy" <dickroy@alum.mit.edu>
To: "'David Lang'" <david@lang.hm>, "'Mike Puchol'" <mike@starlink.sx>
Cc: "'Larry Press'" <lpress@csudh.edu>, <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] Starlink Roaming
Date: Mon, 21 Feb 2022 13:17:22 -0800 [thread overview]
Message-ID: <C0CF133BC44548BF9DD26C41B4665CA5@SRA6> (raw)
In-Reply-To: <866405-s043-n12n-6pqs-46o38r189218@ynat.uz>
What is involved in "setting the service address"??
Do dishy's have IMUs (aka some means for determining attitude w.r.t. the
local gravitational vector and true or magnetic north) or GPS modules (or
both)???
I am somewhat skeptical that the system would be able to locate a UT just
based on zero tilt transmissions from the UT. I am guessing something a bit
more complex is transpiring, like some rudimentary form of SDMA (aka
spatio-temporal resource allocation).
RR
-----Original Message-----
From: David Lang [mailto:david@lang.hm]
Sent: Monday, February 21, 2022 12:53 PM
To: Mike Puchol
Cc: 'David Lang'; 'Larry Press'; dickroy@alum.mit.edu;
starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Starlink Roaming
that's what happened when I tried to use it ~60 miles away, but when I tried
to
use it ~25 miles away I got the attached error very quickly.
I've used it at a couple locations 5-10 miles away without a problem
I asked starlink support about roaming and it's currently not supported, you
can
change the registered location, and if a slot is available, they'll approve
it
and guarantee service (view of the sky permitting). But when you do that you
give up the slot at your home location and are not guaranteed to be able to
move
it back.
They told me that I could try it, and it may work, may be degraded a bit, or
may
not work at all. They do plan to add roaming capabilities in the future (my
guess is that the laser satellites will enable a lot more flexibility)
David Lang
On Mon, 21 Feb 2022, Mike Puchol wrote:
> From what I have observed, there is a new "roaming" flag in terminal
properties that determines roaming capability. Mine is false, and I could
not get service if I set the service address too far.
>
> The way the UT does it is, after startup, it moves to zero tilt, then
searches and registers with any passing satellite, likely using a low-rate,
omnidireccional beacon. The backend then informs the terminal if it is out
of its service address, and if so, it will just sit there doing nothing
(although it does periodically send stuff).
>
> Best,
>
> Mike
> On Feb 21, 2022, 23:31 +0300, Dick Roy <dickroy@alum.mit.edu>, wrote:
>> What does your contract say about the "where" you can expect service from
>> your dishy? I suspect the system is capable of tracking all users at all
>> times they're in coverage which is how they could/would enforce a
>> contractual limitation/constraint.
>>
>> RR
>>
>> -----Original Message-----
>> From: Starlink [mailto:starlink-bounces@lists.bufferbloat.net] On Behalf
Of
>> David Lang
>> Sent: Sunday, February 20, 2022 11:30 PM
>> To: Larry Press
>> Cc: starlink@lists.bufferbloat.net
>> Subject: Re: [Starlink] Starlink Roaming
>>
>> tonight I took it to a friends house about 25 miles away and within a
couple
>> min
>> it gave me an error message saying that I wasn't at my assigned location.
>>
>> David Lang
>>
>> On Mon, 21 Feb 2022, Larry Press wrote:
>>
>>> Date: Mon, 21 Feb 2022 07:22:44 +0000
>>> From: Larry Press <lpress@csudh.edu>
>>> To: David Lang <david@lang.hm>,
>>> Jonathan Bennett <jonathanbennett@hackaday.com>
>>> Cc: "starlink@lists.bufferbloat.net" <starlink@lists.bufferbloat.net>
>>> Subject: Re: [Starlink] Starlink Roaming
>>>
>>> David brought his dish to my location -- about fifty miles from his
>> service loacation and in a different cell and it could not connect. We
had a
>> clear view of the entire sky. He speculated that that was because it was
>> registered to use a specific ground station that was out of range at my
>> place. Does that seem reasonable?
>>>
>>> Larry Press
>>> ________________________________
>>> From: Starlink <starlink-bounces@lists.bufferbloat.net> on behalf of
David
>> Lang <david@lang.hm>
>>> Sent: Monday, February 14, 2022 12:29 PM
>>> To: Jonathan Bennett <jonathanbennett@hackaday.com>
>>> Cc: starlink@lists.bufferbloat.net <starlink@lists.bufferbloat.net>
>>> Subject: Re: [Starlink] Starlink Roaming
>>>
>>> I asked starlink about temp service away from my registered location,
they
>> said
>>> I have two options
>>>
>>> 1. formally change the service location (if approved, guaranteed to
work,
>> but
>>> you aren't guaranteed to be able to change the service location back)
>>>
>>> 2. best effort, set it up and try it. Service may perfect, or may be
worse
>> (all
>>> the way to non-existant) depending on how many other dishes are in use
in
>> the
>>> area.
>>>
>>> I've done some limited testing with my dish within about 15 miles of my
>>> registered location (in both cases with less than optimal sky views) and
>> it's
>>> worked without a hitch. I plan to do a test further away this weekend
(but
>> in a
>>> less populated area, so I have high hopes)
>>>
>>> David Lang
>>>
>>> On Mon, 14 Feb 2022, Jonathan Bennett wrote:
>>>
>>>> It appears that there is now a system in place for Starlink to
re-connect
>>>> even if you are outside your official service cell. For those of us who
>>>> want to use Starlink on vacations or other trips, this is quite the
>>>> development.
>>>>
>>>> --Jonathan Bennett
>>>>
>>> _______________________________________________
>>> Starlink mailing list
>>> Starlink@lists.bufferbloat.net
>>>
>>
https://urldefense.com/v3/__https://lists.bufferbloat.net/listinfo/starlink_
>>
_;!!P7nkOOY!txPxU76SxJ4JvYe2kDjl5OcuAgSIb7mkHWuCMgt3eSH3Tec--6vePH_RCs0NVt6n
>> 2TE6_9HsG20fOA$
>>>
>> _______________________________________________
>> Starlink mailing list
>> Starlink@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/starlink
>>
>> _______________________________________________
>> Starlink mailing list
>> Starlink@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/starlink
>
next prev parent reply other threads:[~2022-02-21 21:17 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 [this message]
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
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=C0CF133BC44548BF9DD26C41B4665CA5@SRA6 \
--to=dickroy@alum.mit.edu \
--cc=david@lang.hm \
--cc=lpress@csudh.edu \
--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