From: Richard Smith <richard@laptop.org>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat-devel@lists.bufferbloat.net
Subject: Re: Temp range for wndr3700
Date: Mon, 29 Aug 2011 13:28:52 -0400 [thread overview]
Message-ID: <CA+vq8rf8qJ3WMYObhvDzPqRjysQy97AN=v_7aEcbQVsm=HGw4g@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw7jMyR7qk1PA+g5U+kdLL9u6fzKGULJqD_qKp+JSYmEzg@mail.gmail.com>
On Fri, Aug 26, 2011 at 3:11 PM, Dave Taht <dave.taht@gmail.com> wrote:
> The nanostation M5 radios were rated to 70C, and use almost the same
> chipset as in the WNDR3700.
>
> That said, most consumer gear (e.g the wndr3700s) I've played with
> rarely survives for very long at temps higher than 40C, and I have a
> long string of failed gear from other manufacturers in Nicaragua to
> prove that, where the ambient temp is often well above 36C.
>
> The nanostations were the only thing that survived for a long time in
> that environment - (well, they got taken out by rain and lightning)
Thanks. I'll add those to my list of hardware to suggest to people to
lookat. I think we may have a site in Jamaica that is using
nanostations.
> I will gladly try to come up with some way to bake the wndrs...
I ask because I'd like to start recommending the wndr (or perhaps
another cerowrt compatible device) to OLPC folk in response to
questions about whats good choice for an AP. The big deployments seem
to have their own methods of choosing and testing but lots of the
smaller sites (say like with 500 or 1000 XO's) spread out over several
sites don't have the ability to do good long term environmental
testing prior to deployment. We spec the XO to operate fine up to
50C so I wanted to try and find a AP that would match. (even if its
official ratings are not that high).
Ambient at 35C is pretty common for mid-day in the summers for places
that don't have any sort of air conditioning (which is 95% of them) so
if the AP is closed up in a room or stuck up in some sort of attic it
will easily reach >40C.
The test would need more than just a short term baking. Although some
sort of test in 50C ambient running heavily loaded and looking at the
rise inside the case would be a good start.
--
Richard A. Smith
One Laptop per Child
prev parent reply other threads:[~2011-08-29 16:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+vq8rdoO3jBR890EU05p9bnu2FDSC-+Ycq2oObK8XMum3USMQ@mail.gmail.com>
2011-08-25 21:13 ` Richard Smith
2011-08-25 21:24 ` Rick
2011-08-26 19:11 ` Dave Taht
2011-08-26 22:09 ` Jim Gettys
2011-08-31 17:27 ` Richard Smith
2011-08-29 17:28 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+vq8rf8qJ3WMYObhvDzPqRjysQy97AN=v_7aEcbQVsm=HGw4g@mail.gmail.com' \
--to=richard@laptop.org \
--cc=bloat-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