Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Richard Smith <smithbone@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] solar wifi ap designs?
Date: Tue, 6 Jun 2017 08:04:24 -0400	[thread overview]
Message-ID: <6ea25924-f10b-1dfc-4747-46f430073bd8@gmail.com> (raw)
In-Reply-To: <6143.1496699488@obiwan.sandelman.ca>

On 06/05/2017 05:51 PM, Michael Richardson wrote:
> Such an interesting thread.
> But, is the 3800 tolerant of spikes of 13.6V?  Has anyone tried?
> I haven't many left :-)

OpenWRT has some hardware info here:

https://wiki.openwrt.org/toh/netgear/wndr3700#tab__hardware_details

Which has a pointer to the data sheet for the onboard regulators.

http://www.st.com/stonline/stappl/st/com/TECHNICAL_RESOURCES/TECHNICAL_LITERATURE/DATASHEET/CD00169322.pdf

The datasheet says those are good up to 18V input so that's promising. 
It will depend on what they did with protection circuitry (if any) and 
the thermal design.

I'd be surprised if it 13.8V made it smoke but depending on the thermal 
design it might be a problem at higher temperatures.

That said, an automotive electrical system is a _very_ harsh place. 
13.8-14.2V is just the nominal output of the voltage regulator for 
charging the battery.  It's by no means the limit of the spikes that can 
occur.

I would not recommend any electronics not designed to work in a car be 
used without some sort of external protection.  Load dump can cause very 
large voltage swings for extended periods.

Here's an app note that talks about some of the hazards.

www.st.com/resource/en/application_note/cd00181783.pdf

-- 
Richard A. Smith

      parent reply	other threads:[~2017-06-06 12:04 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
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 [this message]

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=6ea25924-f10b-1dfc-4747-46f430073bd8@gmail.com \
    --to=smithbone@gmail.com \
    --cc=cerowrt-devel@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