Lets make wifi fast again!
 help / color / mirror / Atom feed
From: Bob McMahon <bob.mcmahon@broadcom.com>
To: Aaron Wood <woody77@gmail.com>
Cc: Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] 2.4Ghz hybrid wiring for nest protects
Date: Tue, 18 May 2021 13:27:13 -0700	[thread overview]
Message-ID: <CAHb6LvpV8=1BdVXASwJajUAAF3e0Y2NOByBXp12wqeaYQBhpOQ@mail.gmail.com> (raw)
In-Reply-To: <CALQXh-OUMb6qyx01QhUhjDD1eZr2-csGZz7ivS8HY1r5Ar_6Nw@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 4625 bytes --]

yeah, thanks for this. I have access to such RF enclosures at work. I'll
likely build it out first here in CA before shipping. I purchased a HackRF
one as well for on premise measurements.

I was also hoping to get API access into the fire alarms for cloud based
remote monitoring, basic things like batteries need replacement or an
unexpected device removal from the mesh. I haven't found a way to do that
yet.

Bob

On Tue, May 18, 2021 at 9:02 AM Aaron Wood <woody77@gmail.com> wrote:

> I've seen similar techniques used for creating isolated wifi device test
> labs.  Each device is locked into a small RF isolation box, with bulkhead
> fittings for power and coax.  A 2.4GHz (or 5GHz antenna, or both) is placed
> inside the box, and then the boxes are wired to one another in any topology
> that is desired.  splitters of course dropping the signal in the coax, but
> really not much more than in the air.
>
> You might want to do some test setups with cheap isolation boxes of wire,
> to see how much signal you'll get through your antennas and coax.
>
> On Mon, May 17, 2021 at 11:09 AM Bob McMahon via Make-wifi-fast <
> make-wifi-fast@lists.bufferbloat.net> wrote:
>
>> Hi All,
>>
>> There is a historic building that has 5 floors and no fire alerting
>> associated with the rear fire escape ladder. I'm considering installing
>> nest protects in each unit near the rear egress to alert of the fire escape
>> is compromised by fire. My guess is floor to floor wireless communications
>> may not work too well.
>>
>> I'm thinking about cleaning up the communications runs in the rear of the
>> building. The cable company did a shoddy job of hanging cable for TV
>> services in the 80s. It seems a good time to add communications conduit and
>> run more modern cabling.
>>
>> As part of this, I'm considering running LMR 600 cabling on the exterior
>> brick wall to act as 2.4Ghz communications wave guides. I was thinking make
>> a loop but break the loop at each floor with a 2.4Ghz wilkinson power
>> divider
>> <https://www.pasternack.com/2-way-n-wilkinson-power-divider-690-mhz-2.7-ghz-10-watts-pe2092-p.aspx?utm_source=google&utm_medium=cpc&adpos=&scid=scplpP74039&sc_intid=P74039&gclid=CjwKCAjwqIiFBhAHEiwANg9szk1JG2oJufz2G2Hylc6oOgOSl-tBN5O39Kn2T1pHV4g8_r8AnkFA7xoCFhUQAvD_BwE>.
>> Then bore a hole into each unit and install a 2.4Ghz patch antenna
>> <https://www.l-com.com/wireless-antenna-24-ghz-8-dbi-round-patch-antennas>
>> pm each rear interior wall. Each unit would then install a Nest protect on
>> the ceiling from the patch antenna. The ring or loop topology I think gives
>> a bit of redundancy.
>>
>> Thoughts on if this would achieve the goals of supporting nest protect
>> communications for such a building?
>>
>> Bob
>>
>>
>>
>>
>> This electronic communication and the information and any files
>> transmitted with it, or attached to it, are confidential and are intended
>> solely for the use of the individual or entity to whom it is addressed and
>> may contain information that is confidential, legally privileged, protected
>> by privacy laws, or otherwise restricted from disclosure to anyone else. If
>> you are not the intended recipient or the person responsible for delivering
>> the e-mail to the intended recipient, you are hereby notified that any use,
>> copying, distributing, dissemination, forwarding, printing, or copying of
>> this e-mail is strictly prohibited. If you received this e-mail in error,
>> please return the e-mail to the sender, delete it from your computer, and
>> destroy any printed copy of it.
>> _______________________________________________
>> Make-wifi-fast mailing list
>> Make-wifi-fast@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/make-wifi-fast
>
>

-- 
This electronic communication and the information and any files transmitted 
with it, or attached to it, are confidential and are intended solely for 
the use of the individual or entity to whom it is addressed and may contain 
information that is confidential, legally privileged, protected by privacy 
laws, or otherwise restricted from disclosure to anyone else. If you are 
not the intended recipient or the person responsible for delivering the 
e-mail to the intended recipient, you are hereby notified that any use, 
copying, distributing, dissemination, forwarding, printing, or copying of 
this e-mail is strictly prohibited. If you received this e-mail in error, 
please return the e-mail to the sender, delete it from your computer, and 
destroy any printed copy of it.

[-- Attachment #1.2: Type: text/html, Size: 5562 bytes --]

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4206 bytes --]

  reply	other threads:[~2021-05-18 20:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-17 18:09 Bob McMahon
2021-05-18 16:02 ` Aaron Wood
2021-05-18 20:27   ` Bob McMahon [this message]
2021-05-18 21:57 ` Jannie Hanekom
2021-05-18 23:32   ` Bob McMahon
2021-05-18 23:52     ` Bob McMahon
2021-05-19  0:09       ` David Lang
2021-05-19  4:47         ` Bob McMahon
2021-05-19  5:27           ` David Lang

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/make-wifi-fast.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAHb6LvpV8=1BdVXASwJajUAAF3e0Y2NOByBXp12wqeaYQBhpOQ@mail.gmail.com' \
    --to=bob.mcmahon@broadcom.com \
    --cc=make-wifi-fast@lists.bufferbloat.net \
    --cc=woody77@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