Lets make wifi fast again!
 help / color / mirror / Atom feed
From: Bob McMahon <bob.mcmahon@broadcom.com>
To: David Lang <david@lang.hm>
Cc: Jannie Hanekom <jannie@hanekom.net>,
	 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 21:47:06 -0700	[thread overview]
Message-ID: <CAHb6LvrHWHEzhMdNmUE3Yj+W0Jh4j_3Pr22AxvLVr9ZrOSDfJg@mail.gmail.com> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.2105181705040.16154@qynat-yncgbc>


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

Thanks, this helps. Yeah, looking for "better than nothing" here for sure.
I also gotta watch out for taking on liabilities myself. Disclaimers of no
responsibility will need to be clear.

I'm not understanding the connecting pairs together in your response.

I was thinking of a single directional antenna per floor connected into a
2.4Ghz Wilkinson power divider with 22 dB isolation for the splits going to
adjacent floors. This way each floor would reach one floor up and one floor
down and no further. (I haven't yet measured the power outputs of the
devices and of a heavily trafficked 2.4Ghz noise floor to make sure 22dB is
sufficient.) I'd connect the bottom floor to the top floor the same way so
basically each floor has one peer up and one peer down.

|--> (3dB less per power split) to floor above
Fire alarm (free space)  Ant--->PD (0.5dB loss) |
                                         -- 22dB isolation between

|--> (3dB less per power split) to floor below

where PD is a Wilkinson power divider, 5 floors for 5 PDs.

Then the LMR connects the Wilkinson's splits to each other. The LMR is
external to the building (along the rear ladder) and the antennas internal.

The floor logical topology becomes 5<-1<->2<->3<->4<->5->1 such that any
single hop failure only impacts that floor. Passive materials will be
military grade, hermetically sealed and inside conduit. The building has
two sets of egress stairs so alerting per one set being compromised can
direct to the other. The internal stairwell is connected floor to floor -
that was required by the fire department (and was costly to the owners.)

I was hoping to be able monitor the devices' topology and detect
any changes using remote servers in the cloud. So far no luck in getting
that information via an API that I can find. I think this is a critical
piece, i.e. having always on servers bugging someone to pay attention to an
unexpected topology change or a need for battery replacements.

I don't think there'd be fire marshal approval for this but, even without
that, I think this meets the "better than nothing" goal and isn't
prohibitively expensive.

Bob

On Tue, May 18, 2021 at 5:09 PM David Lang <david@lang.hm> wrote:

> passive repeaters (two antennas connected together with no electronics)
> work
> much better than most people realize.
>
> I would do floor-by-floor antenna pairs, and if each device going off
> should
> trigger the one on the next floor, I'd consider spacing them out so that
> you
> don't have one antenna pair feeding a strong signal to the next pair.
>
> If the only purpose of this is to relay the fire alarm signals, use
> high-gain,
> narrow beamwidth antennas pointed at the alarms, this will do wonders at
> overcoming the general noise on 2.4GHz
>
> I have too much radio experience to be happy trusting anything wireless
> for
> critical things, but where the alternative is no connectivity, it's better
> than
> nothing.
>
> David Lang
>

-- 
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: 4600 bytes --]

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

  reply	other threads:[~2021-05-19  4:47 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
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 [this message]
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=CAHb6LvrHWHEzhMdNmUE3Yj+W0Jh4j_3Pr22AxvLVr9ZrOSDfJg@mail.gmail.com \
    --to=bob.mcmahon@broadcom.com \
    --cc=david@lang.hm \
    --cc=jannie@hanekom.net \
    --cc=make-wifi-fast@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