From: Nathan Owens <nathan@nathan.io>
To: Dave Taht <davet@teklibre.net>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] ordered my dishy!!
Date: Thu, 24 Jun 2021 19:11:03 -0700 [thread overview]
Message-ID: <CALjsLJu=kO=Q1ht97ZheZywMmkaphVyktpkasQ=OC_8fJBhmNQ@mail.gmail.com> (raw)
In-Reply-To: <FC9D62D5-71CD-4964-B15C-C2CFE26D3D0B@teklibre.net>
[-- Attachment #1: Type: text/plain, Size: 5863 bytes --]
Cutting the data rate probably has implications on the transmit side, i
imagine that may complicate things.
Given it’s possible to make a long battery life short-burst-data iridium
device, it certainly seems in the realm of possibility, but no phased array
or high bandwidth there.
The dish takes about 20-30min on first boot, that may have included a
software update. If it’s not moved, reboots seem fairly quick, software
update took it down for under 5min. The OS boot is probably not the slow
part - I assume a lot of RF magic to find and track the sats.
On Thu, Jun 24, 2021 at 8:04 PM Dave Taht <davet@teklibre.net> wrote:
>
>
> On Jun 24, 2021, at 6:36 PM, Nathan Owens <nathan@nathan.io> wrote:
>
> *pre-ordered (so much confusion about this on Reddit)
>
> The newer dish model pulls closer to 65-70W, fwiw.
>
>
> One of the things we worked on in the make-wifi-fast project was combined
> power and rate control.
>
> My guess is that if all you want is 2Mbit service you can cut the power
> requirements enormously.
>
> Might pull more in snow melt mode
>
>
> One of my unanswered questions is how long does it take to power up and
> start transferring data?
>
> I’ve worked on linux fast boot (sub second boot times) - in the past. Most
> seem to have forgotten how to do that (sigh) and have boot times measured
> in minutes. One reason why I like openwrt so much is it boots in seconds -
> totally bound by the pathetically slow NAND or NOR chips other people
> insist on using still. With some work you can also get rid of the friggin
> bootloader, also.
>
> My initial model for the marine market and for one of my clients is very
> different from how most use the internet today as an always on service.
>
> In this case I just need to get on a couple times a day, download my
> email, grab a few new music files, get the weather report, and get off. So
> I really don’t need all that much power for very long, except to surf the
> web briefly and make a ton of videoconference calls. An hour or two a day,
> tops.
>
> I’ve written a lot about “designing for the disconnect” in the past 4
> decades and I really kind of hate the idea of the internet being an
> always-on drug. Here’s one old talk I gave in australia quite some time
> back about it.
>
> http://the-edge.blogspot.com/2019/12/designing-for-disconnect.html
>
>
> There’s another always-on marine sub-project we’re on, though, that I
> *long* to talk about but can’t, unless somehow we can get the starlink folk
> to do an apollo 13 and fix their !@#!! bufferbloat with something like
> cake, or we can figure out how to optimize dynamically for it via another
> router hanging off of the dishy.
>
> tidbit - one time recently I was 10 miles out at sea, in a 25 knot gale
> and 15+ seas trying to write something down important, and I hit the wrong
> key and the !@#!@@ new apple M1 laptop asked me:
>
> “do you want to install siri”
>
> "No, damn it, I just want to write stuff. If there’s no friggin internet
> why on earth do I want to use siri?”
>
> (apologies I’m grumpy today)
>
>
> —Nathan
>
>
> On Thu, Jun 24, 2021 at 7:01 PM Dave Taht <davet@teklibre.net> wrote:
>
>> I ordered my dishy today. It looks like a couple months or more before I
>> can get one… :(
>>
>> I have all sorts of cool stuff for rock steady movement compensation and
>> so forth on my sailboat here. I hope, that at least at anchor in pillar
>> point harbor or nearby, that it will “just work”. It’s been a useful place
>> to debug and improve LTE and 5G behaviors for the past couple years.
>>
>> When starlink gets movement truly mastered it will be *awesome*.
>>
>> My LTE up on the mast is pretty amazing (I get 5+ miles and pretty good
>> behavior from the cake instance and monitoring tools there) but there are
>> many spots along the california coast (and obviously further out) that are
>> dead zones.
>>
>> The 100+W power requirements are going to hurt though! I just ordered
>> another solar panel and some hefty lithium batteries.
>>
>> Begin forwarded message:
>>
>> *From: *"Starlink" <no-reply@starlink.com>
>> *Subject: **Starlink Order Confirmed*
>> *Date: *June 24, 2021 at 5:44:17 PM PDT
>> *To: *davet@teklibre.net
>>
>> [image: Starlink Logo]
>>
>> Order Confirmed
>> Order Number:
>> *ORD-972149-36038-99*
>> Service Address:
>> *80 Cabrillo Hwy N, Half Moon Bay, CA 94019, USA
>> <https://www.google.com/maps/search/80+Cabrillo+Hwy+N,+Half+Moon+Bay,+CA+94019,+USA?entry=gmail&source=g>*
>> Shipping Address:
>> *80 CABRILLO HWY N STE Q
>> <https://www.google.com/maps/search/80+CABRILLO+HWY+N+STE+Q?entry=gmail&source=g>,
>> PMB 404, HALF MOON BAY, CA, 94019-1650, US*
>>
>> Starlink is targeting coverage in your area in mid to late 2021. Orders
>> will be fulfilled on a first-come, first-served basis. You will be notified
>> via email prior to shipment, and you will be charged the remainder of your
>> balance 3 days after you receive your order notification email.
>>
>> Your Starlink Kit will arrive with your Starlink, wifi router, power
>> supply, cables and mounting tripod. For more information or to cancel your
>> order, sign in to your account.
>> SIGN IN TO MY ACCOUNT
>> <https://auth.starlink.com/set-password?code=0e9b9715-febd-4078-a1d6-80b5090ca182>
>>
>> Space Exploration Technologies Corp | 1 Rocket Road, Hawthorne, CA 90250
>> <https://www.google.com/maps/search/1+Rocket+Road,+Hawthorne,+CA+90250?entry=gmail&source=g>
>>
>> Questions? See Starlink FAQs <https://www.starlink.com/faq>
>>
>>
>> _______________________________________________
>> Starlink mailing list
>> Starlink@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/starlink
>>
>
>
[-- Attachment #2: Type: text/html, Size: 25060 bytes --]
next prev parent reply other threads:[~2021-06-25 2:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4XxOdTE7SSKV1PSkdhm_Ng@geopod-ismtpd-3-0>
2021-06-25 1:00 ` Dave Taht
2021-06-25 1:36 ` Nathan Owens
2021-06-25 2:04 ` Dave Taht
2021-06-25 2:11 ` Nathan Owens [this message]
2021-06-25 14:56 ` Michael Richardson
2021-06-25 2:07 ` Nathan Owens
2021-06-25 2:16 ` Daniel AJ Sokolov
2021-06-25 2:32 ` Nathan Owens
2021-06-25 6:23 ` Mike Puchol
2021-06-27 20:07 ` Darrell Budic
2021-06-27 21:28 ` Michael Richardson
2021-06-27 22:41 ` Jared Mauch
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='CALjsLJu=kO=Q1ht97ZheZywMmkaphVyktpkasQ=OC_8fJBhmNQ@mail.gmail.com' \
--to=nathan@nathan.io \
--cc=davet@teklibre.net \
--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