From: Jim Gettys <gettysjim@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: "bloat-devel@lists.bufferbloat.net" <bloat-devel@lists.bufferbloat.net>
Subject: Re: Temp range for wndr3700
Date: Fri, 26 Aug 2011 18:09:17 -0400 [thread overview]
Message-ID: <2152403F-F74C-4177-A42C-1CA7A5C29F9D@gmail.com> (raw)
In-Reply-To: <CAA93jw7jMyR7qk1PA+g5U+kdLL9u6fzKGULJqD_qKp+JSYmEzg@mail.gmail.com>
Remember: you were near the ocean in high humidity in Nicaragua; failing due to warm, humid salt air is always a headache.... Temperature by itself is far from the whole story.
Maybe sminthbone can throw a few in olpc's environmental chamber as a quick test....
Jim
On 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)
>
> I will gladly try to come up with some way to bake the wndrs...
>
> On Thu, Aug 25, 2011 at 2:24 PM, Rick <graham.rick@gmail.com> wrote:
>> I couldn't say anything regarding 50C, but in a warm room, the heat
>> mine generates is barely noticeable.
>>
>> On Thu, Aug 25, 2011 at 5:13 PM, Richard Smith <richard@laptop.org> wrote:
>>> Resend via the account I'm actually subscribed from...
>>>
>>> On Thu, Aug 25, 2011 at 4:13 PM, Richard Smith <smithbone@gmail.com> wrote:
>>>> This is more of a hardware question but the hardware specifications
>>>> for the router don't tell me whats actually known to work.
>>>>
>>>> What temperature range has the wndr3700 been used in while
>>>> testing/operating cerowrt or openwrt? Has anyone tried to use one
>>>> fully loaded at say 50C ambient.
>>>>
>>>> --
>>>> Richard A. Smith
>>>>
>>>
>>>
>>>
>>> --
>>> Richard A. Smith
>>> One Laptop per Child
>>> _______________________________________________
>>> Bloat-devel mailing list
>>> Bloat-devel@lists.bufferbloat.net
>>> https://lists.bufferbloat.net/listinfo/bloat-devel
>>>
>>
>>
>>
>> --
>> They must find it difficult...
>> Those who have taken authority as the truth,
>> Rather than truth as the authority.
>> G. Massey, Egyptologist
>> _______________________________________________
>> Bloat-devel mailing list
>> Bloat-devel@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/bloat-devel
>>
>
>
>
> --
> Dave Täht
> SKYPE: davetaht
> US Tel: 1-239-829-5608
> http://the-edge.blogspot.com
> _______________________________________________
> Bloat-devel mailing list
> Bloat-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat-devel
next prev parent reply other threads:[~2011-08-26 21:11 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 [this message]
2011-08-31 17:27 ` Richard Smith
2011-08-29 17:28 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2152403F-F74C-4177-A42C-1CA7A5C29F9D@gmail.com \
--to=gettysjim@gmail.com \
--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