From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] one dish per household is silly.
Date: Tue, 14 Nov 2023 10:04:30 +0100 [thread overview]
Message-ID: <2e8dba27-542c-45b7-91c2-b877cc227430@gmail.com> (raw)
In-Reply-To: <fdcc3ae9-3fb0-4a18-95bc-3a6bf71a8290@auckland.ac.nz>
Le 14/11/2023 à 06:13, Ulrich Speidel via Starlink a écrit :
>
> So that's just over 6 kW if phase and voltage align, which in an
> application like this, they're most likely not going to do most of the
> time.
>
> The interesting bit in the photo are the large air intakes / outlets,
> which point at the presence of some sort of cooler / aircon unit at
> the base of the radome. Transmitter heat removal and/or receiver
> cooling (to keep the noise floor down)?
>
Ah, I see what you people mean by consumption: that of teleports, not
that of end users. Sorry for my earlier post about the dishy
electricity consumption.
Alex
> On 14/11/2023 5:57 pm, J Pan via Starlink wrote:
>> rated power consumption for all components at peak
>> https://files.tecnoblog.net/wp-content/uploads/2021/05/starlink-gateway-v3-selo-anatel-700x898.png
>> --
>> J Pan, UVic CSc, ECS566, 250-472-5796 (NO VM), Pan@UVic.CA,
>> Web.UVic.CA/~pan <http://Web.UVic.CA/~pan>
>>
>> On Mon, Nov 13, 2023 at 12:42 PM Inemesit Affia via Starlink
>> <starlink@lists.bufferbloat.net> wrote:
>> >
>> > I don't know why that number didn't trip my antenna.
>> > _______________________________________________
>> > 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
> --
> ****************************************************************
> Dr. Ulrich Speidel
>
> School of Computer Science
>
> Room 303S.594 (City Campus)
>
> The University of Auckland
> u.speidel@auckland.ac.nz
> http://www.cs.auckland.ac.nz/~ulrich/
> ****************************************************************
>
>
>
>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
next prev parent reply other threads:[~2023-11-14 9:04 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-10 11:44 Dave Taht
2023-11-10 12:21 ` Inemesit Affia
2023-11-11 4:42 ` Alexandre Petrescu
2023-11-10 12:33 ` [Starlink] [NNagain] " Bill Woodcock
2023-11-10 12:55 ` Dave Taht
2023-11-10 13:17 ` Alexandre Petrescu
2023-11-10 13:44 ` David Lang
2023-11-10 15:10 ` Dave Taht
2023-11-10 16:09 ` Alexandre Petrescu
2023-11-10 16:40 ` David Lang
2023-11-10 16:58 ` Alexandre Petrescu
2023-11-10 18:16 ` Alexandre Petrescu
2023-11-10 13:53 ` Dave Taht
2023-11-11 4:50 ` Alexandre Petrescu
2023-11-10 16:11 ` Alexandre Petrescu
2023-11-10 13:51 ` [Starlink] " David Lang
2023-11-13 6:37 ` J Pan
2023-11-13 6:40 ` Inemesit Affia
2023-11-13 16:10 ` J Pan
2023-11-13 16:22 ` Inemesit Affia
2023-11-13 20:34 ` Ulrich Speidel
2023-11-13 20:38 ` Inemesit Affia
2023-11-13 20:42 ` Inemesit Affia
2023-11-14 4:57 ` J Pan
2023-11-14 5:13 ` Ulrich Speidel
2023-11-14 5:18 ` J Pan
2023-11-14 9:04 ` Alexandre Petrescu [this message]
2023-11-14 8:50 ` Alexandre Petrescu
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=2e8dba27-542c-45b7-91c2-b877cc227430@gmail.com \
--to=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