From: Oleg Kutkov <contact@olegkutkov.me>
To: BufferBloat List <starlink@lists.bufferbloat.net>
Subject: [Starlink] Starlink rev 3 power architecture, implementation and repairs
Date: Tue, 31 Dec 2024 03:57:58 +0200 [thread overview]
Message-ID: <09508d5f-a71a-432e-9cb7-723c918ed8a8@olegkutkov.me> (raw)
[-- Attachment #1: Type: text/plain, Size: 431 bytes --]
Hello,
I have published a new article on my blog: Starlink REV3 power architecture:
https://olegkutkov.me/2024/12/31/starlink-rev-3-v2-power-architecture/
<https://olegkutkov.me/2024/12/31/starlink-rev-3-v2-power-architecture/>
Some details about the implementation, diagrams, most common problems,
and solutions.
I hope this article will help everyone involved in repairing Starlink
terminals.
--
Best regards,
Oleg Kutkov
[-- Attachment #2: Type: text/html, Size: 857 bytes --]
reply other threads:[~2024-12-31 1:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=09508d5f-a71a-432e-9cb7-723c918ed8a8@olegkutkov.me \
--to=contact@olegkutkov.me \
--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