From: Jim Forster <jim@connectivitycap.com>
To: Mark Steckel <mjs@phillywisper.net>
Cc: herberticus <herberticus@gmail.com>,
libreqos <libreqos@lists.bufferbloat.net>
Subject: Re: [LibreQoS] solar powered internet
Date: Fri, 14 Apr 2023 21:59:05 -0700 [thread overview]
Message-ID: <232EC5F9-CB88-427F-8FDB-FCD79BFF18FC@connectivitycap.com> (raw)
In-Reply-To: <1877cf3132b.102c3799a191947.1618777140509011187@phillywisper.net>
[-- Attachment #1: Type: text/plain, Size: 1223 bytes --]
Right. The WISPs and ISPs that I know of in Africa & India have this pretty much this dialed in. Some solar-only sites, lots of DC sites.. Loads range from ~10w - 100+w. Various suppliers for the pieces-parts, various time on battery deisgns, various engineering standards.,
Jim
> On Apr 13, 2023, at 4:28 PM, Mark Steckel via LibreQoS <libreqos@lists.bufferbloat.net> wrote:
>
> I don't follow WispTalk so can't speak to those discussions. And agree, the Ubnt stuff sort of does the job, but it's under powered for what we do.
>
> We have yet to build a solar powered site, and in Philly it is probably unlikely we ever will. However, all of our high-sites use a DC power plant.
>
> The attached photos are from a small site, and the others are (almost certainly overbuilt*) for what is a large site that I expect will grow over time. (We've also switched to LiFePo4 batteries of AGM lead acid.)
>
> * I've found upgrading network gear is much easier than power systems... and have been hampered when we have outgrown our power system at a couple of sites in the past. And granted, a good portion of the over built system in 3 of the photos is a by product of load sharing and redundancy.
>
[-- Attachment #2: Type: text/html, Size: 5669 bytes --]
next prev parent reply other threads:[~2023-04-15 4:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 23:28 Mark Steckel
2023-04-15 4:59 ` Jim Forster [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-13 22:07 Dave Taht
2023-04-13 23:02 ` Herbert Wolverson
2023-04-15 11:57 ` Brian Munyao Longwe
2023-04-15 16:56 ` dan
2023-04-16 0:21 ` Dave Taht
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/libreqos.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=232EC5F9-CB88-427F-8FDB-FCD79BFF18FC@connectivitycap.com \
--to=jim@connectivitycap.com \
--cc=herberticus@gmail.com \
--cc=libreqos@lists.bufferbloat.net \
--cc=mjs@phillywisper.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