From: Noel Butler <noel.butler@ausics.net>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Speaking of retirements...
Date: Mon, 25 Sep 2023 20:32:21 +1000 [thread overview]
Message-ID: <34eb69c849fc441c0184e7768ec768d9@ausics.net> (raw)
In-Reply-To: <af464305-485d-40d3-b093-3c61f4aa2e25@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2456 bytes --]
On 25/09/2023 18:06, Alexandre Petrescu via Starlink wrote:
> ah, sorry, probably we speak of the same thing.
>
> I dont know whether or not the current in-car starlink devices require
> an extra 12v-to-220V/110V adapter, or whether it's included, or
> integrated.
Here, the "RV" is identical to a household service, the same stuff,
except your allowed to move around - not locked to the beam covering
your home location.
> These 12V-220V/110V adapters are relatively big, necessitate fans.
If you're getting the "RV/camping/portable" equipment you'd want to use
your 12volt system that nearly all campers and RV's I've seen with
factory electrics come with (A couple RV models are 24v) so the DC
supply woud need to accept 12 to 48 input, slightly less heat is
generated if you use 24v and even less again if 48v since it only bucks
it for the 12v parts of the circuitry in modem. You would not want to
use an AC supply, defeats the purpose of the design of that service, the
12 to 48v boost converters for the dish to work have decent heat sinks,
a little better ventilation in the modems for that little bit of extra
heat would be beneficial.
> If they are still needed for starlink in-car devices is probably
> because of higher transmit power that is necessary to reach to 360km
> altitude. They could reduce that in-car power need by bringing the sats
> even lower, or other non-sat objects like HAPs. Or by augmenting the
> starlink sat antennas sizes.
They are identical hardware, no extra power is needed, since there is
350 odd km's to the satellite, do you really think the 2 or so metres
AGL for campers, would really need more power compared to the standard
unit at 10 metres AGL, at say a house mounted dish :) In early days I
remember quite a few youtubers using the stand on the ground in their
back yard, and they probably still do.
--
Regards,
Noel Butler
This Email, including attachments, may contain legally privileged
information, therefore at all times remains confidential and subject to
copyright protected under international law. You may not disseminate
this message without the authors express written authority to do so.
If you are not the intended recipient, please notify the sender then
delete all copies of this message including attachments immediately.
Confidentiality, copyright, and legal privilege are not waived or lost
by reason of the mistaken delivery of this message.
[-- Attachment #2: Type: text/html, Size: 4193 bytes --]
next prev parent reply other threads:[~2023-09-25 10:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 6:05 Noel Butler
2023-09-25 7:56 ` Alexandre Petrescu
2023-09-25 8:06 ` Alexandre Petrescu
2023-09-25 10:32 ` Noel Butler [this message]
2023-09-25 11:45 ` Ulrich Speidel
2023-09-26 1:28 ` David Lang
2023-09-26 10:46 ` Noel Butler
2023-09-26 11:02 ` Ulrich Speidel
2023-09-30 1:56 ` Noel Butler
2023-09-25 9:01 ` 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=34eb69c849fc441c0184e7768ec768d9@ausics.net \
--to=noel.butler@ausics.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