Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Christopher Robin <pheoni@gmail.com>
To: Richard Smith <smithbone@gmail.com>, cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] solar wifi ap designs?
Date: Tue, 13 Jun 2017 13:03:01 +0000	[thread overview]
Message-ID: <CAPjrEw-C4odYv31i-uaHgSCAzz+htJMNG9DUGgQj43iXy34udw@mail.gmail.com> (raw)
In-Reply-To: <CAPjrEw9FY9GU3XXMXDTi254nUUDdyVw22+9G-MKuT08ABtTJ9Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1258 bytes --]

On Tue, Jun 13, 2017 at 8:24 AM Christopher Robin <pheoni@gmail.com> wrote:

>
> On Tue, Jun 13, 2017 at 7:52 AM Richard Smith <smithbone@gmail.com> wrote:
>
>> On 06/09/2017 10:02 AM, Dave Taht wrote:
>>
>> > My use case used to be covering hundreds of km in the Nicaraguan
>> > jungle. The prototype for that covers a mere 110 acres in the los
>> > gatos hills, trying to get stuff deep into ravines and so on.
>>
>> Accounting for wost case is always what amplifies the requirements of an
>> off-grid system.
>>
>> NASA Surface meteorology and Solar Energy claims that for Los Gatos
>> December is the lowest output.  Given a split-the-middle tilt alignment
>> of 37 degrees it will receive average full-sun net of 3.5 hours.
>
>
Dave: With these being tree mounted, how likely is full-sun? I'm not
familiar with the tree type/density. Are you're looking to avoid having
separated solar panels?

Richard: I would presume these calculations are all for "open field"
conditions?

If the panels are under a tree canopy, a lower attack angle may be better
to better utilize morning/evening sun. A higher one may be necessary to get
a useful charge during peak daylight. I've seen some pretty impressive
calculators to work out best guesses for field testing.

[-- Attachment #2: Type: text/html, Size: 1836 bytes --]

  parent reply	other threads:[~2017-06-13 13:03 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 [this message]
2017-06-13 16:25               ` Richard Smith
2017-06-13 17:25                 ` Dave Taht
2017-06-13 21:09                   ` Richard Smith
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=CAPjrEw-C4odYv31i-uaHgSCAzz+htJMNG9DUGgQj43iXy34udw@mail.gmail.com \
    --to=pheoni@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=smithbone@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