From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Speaking of retirements...
Date: Mon, 25 Sep 2023 10:06:10 +0200 [thread overview]
Message-ID: <af464305-485d-40d3-b093-3c61f4aa2e25@gmail.com> (raw)
In-Reply-To: <d80e820fe49dab599d26f3edbaef0507@ausics.net>
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.
These 12V-220V/110V adapters are relatively big, necessitate fans. 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.
Alex
Le 25/09/2023 à 08:05, Noel Butler via Starlink a écrit :
>
> When the heck are starlink going to release a true "RV unit" that is 12v?
>
> Sure we can hack it to do what starlink should have been doing all
> along, but that's ugly, it voids our warranties, and is only of use to
> those who have some understanding electronics.
>
> Surely they can design a 12v RV modem that has the boost converters
> internally so its plug and play in campers or cars/vans, rather than
> saying "this is RV - but you need inefficient mains inverters to use
> it", they charge a premium for sub standard service (low priority
> data), surely they can add an extra, well at my singular buy price $15
> in components, to them in mass production it would be more like $5.
>
> --
>
> 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.
>
>
>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
next prev parent reply other threads:[~2023-09-25 8:06 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 [this message]
2023-09-25 10:32 ` Noel Butler
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=af464305-485d-40d3-b093-3c61f4aa2e25@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