From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
To: David Lang <david@lang.hm>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] "Interesting set of developments with Starlink. Musk says they will support "international aid orgs" in Gaza, Israel now says they will use "all available means" to stop SpaceX from doing so.
Date: Tue, 14 Nov 2023 09:48:45 +0100 [thread overview]
Message-ID: <bb8767c3-7a57-42f2-8769-5c126f489f42@gmail.com> (raw)
In-Reply-To: <6s24rnq6-n37o-7q75-n0o8-6n12o2qo555o@ynat.uz>
Le 13/11/2023 à 17:03, David Lang a écrit :
> On Mon, 13 Nov 2023, Alexandre Petrescu via Starlink wrote:
>
>> It has a Donate button, which seems to make it a site built by an
>> independent end user. It is a great tool already! With respect to
>> the starlink sats positions: celestrak might simply reflect an
>> original data which is made by space-track.org which is a US
>> authority. Or maybe not, they dont say it. I dont know.
>>
>> My question is how is the original data on space-track.org (or other
>> original source of sat position data) created: do they range the sats
>> (i.e. point lasers at them and wait for replies, radar, or similar)
>> or do the sats transmit their positions on a voluntary and
>> cooperative basis?
>
> It is in the interests of every country to avoid having satellties hit
> each other, which requires that everyone have accurate information on
> where existing satellites are. The US space command (or whatever their
> name is under the USSF now) tracks everything in orbit that they can
> (I thinkit's everything above ~10cm)
Fair enough, I agree with both statements. But certainly they're not
the only ones to track for the benefit of all, it is not the only
publicly available original tracking data. Ideally, one would have a
single trackign authority and the tracking method - not only the
tracking data - would be documented publicly.
>
> companies coordinate with each other when they need to move satellites
> so that you don't have two satellites trying to avoid a collision both
> move in a way that make the collision more likely to happen.
>
> There's even an International agreement (going back to the cold war
> between the US and USSR) that requires satellite launcher telemetry to
> be unencrypted so that everyone can monitor it.
Thanks, I'll have to look that up. I think I've seen publicly
available tracking data of launchers of all sorts, but I'll have to dig
it up again from the Internet.
>
> so the orbits of everything (including spy satellites) is well known
> and not some deep secret.
Sure. But plans are one thing and the implementation might be different.
>
>> Another question is about which starlink sats are 'in-service' and
>> deliver service, and which not? It is not only a matter of
>> altitude. The current websites telling 'in-service' or similar
>> attributes, do not seem to be related to starlink, and do not seem to
>> take that data from DISHYs. They seem to be simply telling that if
>> it is at a 550km altitude then they're in service.
>
> What would be the value in having a satellite in the proper orbit,
> using a orbital slot, but not in use? unless the satellite electronics
> have failed, they would use it (electronics do not wear out from use)
I agree with the question. It makes sense.
But what is a 'proper' orbit, what altitude? Is one sure that a
starlink sat at 350km altitude for several weeks, if not months, is
_not_ in service? Maybe I'll have to go look at the ITU and FCC orbit
altitude reservations for starlink, because probably that is the only
data available.
Alex
>
> David Lang
next prev parent reply other threads:[~2023-11-14 8:48 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-29 16:06 the keyboard of geoff goodfellow
2023-10-29 16:26 ` Dave Taht
2023-10-29 19:10 ` Frantisek Borsik
2023-10-29 19:38 ` Dave Taht
2023-10-30 4:32 ` Joe Hamelin
2023-10-30 5:56 ` Ulrich Speidel
2023-10-30 12:03 ` Alexandre Petrescu
2023-10-30 12:47 ` Ulrich Speidel
2023-10-30 13:30 ` Alexandre Petrescu
2023-10-30 16:49 ` David Lang
2023-10-31 12:57 ` Ulrich Speidel
2023-10-31 14:26 ` Alexandre Petrescu
2023-11-11 5:09 ` Alexandre Petrescu
2023-11-11 23:47 ` Ulrich Speidel
2023-11-13 10:15 ` Alexandre Petrescu
2023-11-13 16:03 ` David Lang
2023-11-14 8:48 ` Alexandre Petrescu [this message]
2023-10-30 12:54 ` Alexandre Petrescu
2023-10-30 13:10 ` Ulrich Speidel
2023-10-30 13:39 ` Alexandre Petrescu
2023-10-30 6:02 ` Dave Taht
2023-10-30 17:46 ` Daniel AJ Sokolov
2023-10-30 18:47 ` [Starlink] [off-topic] " Dave Collier-Brown
2023-10-30 18:47 ` [Starlink] " Alexandre Petrescu
2023-10-30 19:58 ` Frantisek Borsik
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=bb8767c3-7a57-42f2-8769-5c126f489f42@gmail.com \
--to=alexandre.petrescu@gmail.com \
--cc=david@lang.hm \
--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