Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Aaron Wood <woody77@gmail.com>
To: Dave Taht <dave.taht@gmail.com>,
	 "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] solar wifi ap designs?
Date: Mon, 05 Jun 2017 01:54:42 +0000	[thread overview]
Message-ID: <CALQXh-PPn6xt7KBs552BVv4vHW9oDbCRgEq9Dr-POvakRSMrBQ@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw40qwv-8JV9K-t3kDq4mPcHc8B81HzKRw-7w3cTN5-=HQ@mail.gmail.com>

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

I'd pick an AP that works off of a 12vdc supply, and then try to setup a
12vdc solar supply (which should get you lots of stuff for automotive/rv
use).

Are you planning on deep cycle lead acid or lithium ion for storage?

-Aaron
On Sun, Jun 4, 2017 at 17:49 Dave Taht <dave.taht@gmail.com> wrote:

> I keep finding nicely integrated solar/battery/camera/wifi designs
>
>
> https://www.amazon.com/s/ref=nb_sb_noss_2?url=search-alias%3Delectronics&field-keywords=solar+wifi&rh=n%3A172282%2Ck%3Asolar+wifi
>
> But what I want is merely an solar/battery/AP design well supported by
> lede... and either the ath9k or ath10k chipset - or mt72 - that I can
> hang off a couple trees. I've not worked with solar much in the past
> years, and picking the right inverter/panel/etc seems like a pita, but
> perhaps there are ideas out there?
>
>
> --
>
> Dave Täh
> Let's go make home routers and wifi faster! With better software!
> http://blog.cerowrt.org
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>

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

  reply	other threads:[~2017-06-05  1:54 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 [this message]
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
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=CALQXh-PPn6xt7KBs552BVv4vHW9oDbCRgEq9Dr-POvakRSMrBQ@mail.gmail.com \
    --to=woody77@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@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