From: Richard Smith <smithbone@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Christopher Robin <pheoni@gmail.com>,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] solar wifi ap designs?
Date: Tue, 13 Jun 2017 17:09:30 -0400 [thread overview]
Message-ID: <0477ece1-2253-b6bc-aba7-91ddca3cafa5@gmail.com> (raw)
In-Reply-To: <CAA93jw4xff9H09L+-4qzbgE3o+00Kdh3e3D+s+EGVLNOq=V6Lg@mail.gmail.com>
On 06/13/2017 01:25 PM, Dave Taht wrote:
> If you run the numbers for Nicaragua, you'll find that the solar
> coverage is WAY better year round. (share the spreadsheet?) The
> problem is the rainy season from late august through november, and I
> was aiming for 3 days of battery life, with only 20% sun over those
> days.
In general is better but I would not call it WAY better. I looked up
Harmonia and used Cárdenas, Nicaragua as my data point.
The average is a pretty solid 5-6 hours across the year but the rainy
season has a large effect. 20% matches the 3-day in Oct which looks
like it's the weakest month overall, but the 3-day minimum is in Aug @
13%. When you do the math it actually ends up being worse that the
minimum in Los Gatos. Los Gatos had a minimum of 2.4 hours where as
Cárdenas nets out at 2 hours.
Here's the spreadsheet. 'Lowest' and 'Highest' are Los Gatos and
'Nicaragua' is Cárdenas.
https://docs.google.com/spreadsheets/d/1p6PYBgcTtLR9cwWlVpzRiIt4t2RcjoYVC4_K6WxLmso/edit?usp=sharing
> I might give wind a try, also.
Wind and solar are great complements to each other. In general one is
good when the other is bad.
> I am heading down there next week or the one following to explore the
> possibilities (and get some surfing in!).
Nice. Can't go wrong with some good beach time.
> Now that my new office space is coming along, I have space and tools
> (cnc machine, etc), to try and build something that would work. I'd
> always intended local manufacture of the edison batteries.....
Cool. I'm interested in seeing what you come up with. Maybe you can do
a kickstarter to build a larger quantity of them. :)
--
Richard A. Smith
next prev parent reply other threads:[~2017-06-13 21:09 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-05 0:49 Dave Taht
2017-06-05 1:54 ` Aaron Wood
2017-06-05 2:03 ` Dave Taht
2017-06-05 3:53 ` Aaron Wood
[not found] ` <148921.1496635376@turing-police.cc.vt.edu>
2017-06-05 4:27 ` Dave Taht
2017-06-05 13:12 ` Michael Richardson
2017-06-05 16:01 ` Richard Smith
2017-06-05 17:52 ` dpreed
2017-06-05 18:01 ` dpreed
2017-06-05 18:21 ` Jim Gettys
2017-06-05 18:53 ` Aaron Wood
2017-06-06 23:59 ` Christopher Robin
2017-06-09 14:02 ` Dave Taht
2017-06-13 11:52 ` Richard Smith
[not found] ` <CAPjrEw9FY9GU3XXMXDTi254nUUDdyVw22+9G-MKuT08ABtTJ9Q@mail.gmail.com>
2017-06-13 13:03 ` Christopher Robin
2017-06-13 16:25 ` Richard Smith
2017-06-13 17:25 ` Dave Taht
2017-06-13 21:09 ` Richard Smith [this message]
2017-06-05 20:20 ` David Lang
2017-06-05 20:26 ` Jim Gettys
2017-06-06 12:04 ` Richard Smith
2017-06-06 18:40 ` Richard Smith
2017-06-07 20:15 ` Michael Richardson
2017-06-05 21:51 ` Michael Richardson
2017-06-05 22:49 ` Joel Wirāmu Pauling
2017-06-06 2:00 ` Michael Richardson
2017-06-06 2:03 ` Jim Gettys
2017-06-06 12:04 ` Richard Smith
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0477ece1-2253-b6bc-aba7-91ddca3cafa5@gmail.com \
--to=smithbone@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=pheoni@gmail.com \
/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