From: David Lang <david@lang.hm>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Starship's 4th flight test was magnificent
Date: Mon, 10 Jun 2024 02:49:56 -0700 (PDT) [thread overview]
Message-ID: <60578837-n22o-sr13-6512-pp7pn6p6q9p3@ynat.uz> (raw)
In-Reply-To: <7a905c03-a3b2-477c-acd1-ec05d60e3862@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1875 bytes --]
Alexandre Petrescu wrote:
> Le 10/06/2024 à 01:50, Dave Taht via Starlink a écrit :
>>
>> [...] seeing starlink maintain connectivity through nearly it all of that
>> plasma was amazing, too.
>
> I dont understand: the rocket body and head ('starship') where connected to
> starlink sats during flight? Wouldnt be enough to transmit straight to
> ground? Or maybe the entire trajectory is too long too distanced from ground
> receivers?
Yes, unlike other rockets, Starship has multiple starlink dishes on it and has a
high bandwidth connection through them during it's flight. There are only so
many ground stations around the world for rockets to talk to directly (and
especially over the large oceans and Africa there are substantial gaps in
coverage)
the Starliner flight for example, only had telemetry and audio, no video during
it's flight. The first Starliner test flight had the capsule misbehaving furing
one of it's gaps in coverage, which prevented controllers on the ground from
fixing the problem fast enough to salvage the flight.
Also, during reentry, the plasma tha builds up blocks any radio down to the
ground, and with anything other than a starlink, it even blocks radios up to
satellites. A combination of the large size of the Starship, and the Starlink
capabilities makes it the first rocket that is able to provide live feeds
throughout the entire reentry.
For this mission, there were some gaps in the coverage, Elon has said they will
be repositioning the starlink antennas on future flights to eliminate the blind
spots and get continuous coverage.
The Polaris Dawn private flights are doing experimentation with laser tie-ins to
the starlink constellations. NASA has the TDRS system to provide near global
coverage, see this video from Scott Manley on the topic
https://www.youtube.com/watch?v=42GpWBSwjZM
David Lang
[-- Attachment #2: Type: text/plain, Size: 149 bytes --]
_______________________________________________
Starlink mailing list
Starlink@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/starlink
next prev parent reply other threads:[~2024-06-10 9:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-09 23:50 Dave Taht
2024-06-10 0:15 ` Ulrich Speidel
2024-06-10 2:22 ` Michael Richardson
2024-06-10 10:51 ` Ulrich Speidel
2024-06-10 12:04 ` David Lang
2024-06-10 12:15 ` Ulrich Speidel
2024-06-10 2:38 ` David Lang
2024-06-10 11:04 ` Ulrich Speidel
2024-06-10 12:06 ` David Lang
2024-06-10 12:21 ` Ulrich Speidel
2024-06-10 8:57 ` Alexandre Petrescu
2024-06-10 9:49 ` David Lang [this message]
2024-06-10 13:22 ` Alexandre Petrescu
2024-06-10 13:37 ` David Lang
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=60578837-n22o-sr13-6512-pp7pn6p6q9p3@ynat.uz \
--to=david@lang.hm \
--cc=alexandre.petrescu@gmail.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