Lets make wifi fast again!
 help / color / mirror / Atom feed
From: moeller0 <moeller0@gmx.de>
To: David Lang <david@lang.hm>
Cc: Bob McMahon <bob.mcmahon@broadcom.com>,
	make-wifi-fast@lists.bufferbloat.net,
	"cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] [Cerowrt-devel] more well funded attempts showing market demandfor better wifi
Date: Mon, 27 Jun 2016 11:43:55 +0200	[thread overview]
Message-ID: <69058459-83F9-4FFB-871A-B83A2194DB4F@gmx.de> (raw)
In-Reply-To: <alpine.DEB.2.02.1606270017030.5129@nftneq.ynat.uz>

Hi David,

> On Jun 27, 2016, at 09:44 , David Lang <david@lang.hm> wrote:
> 
> On Mon, 27 Jun 2016, Sebastian Moeller wrote:
> 
>>> On a wireless network, with 'normal' omnidirctional antennas, the signal drops off with the square of the distance. So if you want to service clients from 1 ft to 100 ft away, your signal strength varies by 1000 (4 orders of magnatude), this is before you include effects of shielding, bounces, bad antenna alignment, etc (which can add several more orders of magnatude of variation)
>>> 
>>> The receiver first normalized the strongest part of the signal to a constant value, and then digitizes the result, (usually with a 12-14 bit AD converter). Since 1000x is ~10 bits, the result of overlapping tranmissions can be one signal at 14 bits, and another at <4 bits. This is why digital processing isn't able to receive multiple stations at the same time.
>> 
>>     But, I you add 10 Bits to your AD converter you basically solved this. Now, most likely this also needs to be of higher quality and of low internal noise, so probably expensive... Add to this the wide-band requirement of the sample the full band approach and we are looking at a price ad converter. On the bright side, mass-producing that might lower the price for nice oscilloscopes...
> 
> well, TI only manufactures AD converters up to 16 bit at these speeds, so 24 bit converters are hardly something to just buy. They do make 24 and 32 bit ADCs, but only ones that could be used for signals <5MHz wide (and we are pushing to 160 MHz wide channels on wifi)

	But David’s idea was to sample the full 5GHz band simultaneously, so we would need something like a down-mixer and an ADC system with around 2GHz bandwidth (due to Nyquist), I believe multiplexing multiple slower ADC’s as done in better oscilloscopes might work, but that will not help reduce the price not solve the bit resolution question.

> 
> also note my comment about walls/etc providing shielding that can add a few more orders of magnatude on the signals.

	Well, yes, but in the end the normalizing amplifier really can be considered a range adjustor that makes up for the ADC’s lack of dynamik resolution. I would venture the guess not having to normalize might allow speed up the “wifi pre-amble” since one amplifier less to stabilize…

> 
> And then when you start being able to detect signals at that level, the first ones you are going to hit are bounces from your strongest signal off of all sorts of things.

	But that is independent of whether you sample to whole 5GHz range in one go or not? I would guess as long as the ADC/amplifier does not go into saturation both should perform similarly.

> 
> You will also find that noise and distortion in the legitimate strong signal is going to be at strengths close to the strength of the weak signal you are trying to hear.

	But if that noise and distortion appear in the weak signals frequency band we have issues already today?

> 
> As I said, I see things getting better, but it’s going to be a very hard thing to do, and I'd expect to see reverse mu-mimo (similarly strong signals from several directions) long before the ability to detect wildly weaker signals.

	You are probably right.

> 
> I also expect that as the ability to more accurately digitize the signal grows, we will first take advantage of it for higher speeds.

	Yes, but higher speed currently means mostly wider bands, and the full 4-5GHz range is sort of the logical end-point ;).

Best Regards
	Sebastian

> 
> David Lang


  reply	other threads:[~2016-06-27  9:44 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-24 21:24 [Make-wifi-fast] " dpreed
2016-06-26 22:54 ` Bob McMahon
2016-06-27  0:00   ` David Lang
2016-06-27  2:23     ` Bob McMahon
2016-06-27  3:01       ` David Lang
2016-06-27 17:55         ` Dave Taht
2016-06-27 18:22           ` Bob McMahon
2016-06-27 19:40             ` David Lang
2016-06-27 20:05               ` Bob McMahon
2016-06-27 20:09                 ` David Lang
2016-06-27 20:34                   ` Bob McMahon
2016-06-27 21:09                     ` David Lang
2016-06-27 22:12                       ` Bob McMahon
2016-06-27 22:18                         ` David Lang
2016-06-28  1:09                           ` Bob McMahon
2016-06-27  6:34     ` [Make-wifi-fast] [Cerowrt-devel] " Sebastian Moeller
2016-06-27  7:44       ` David Lang
2016-06-27  9:43         ` moeller0 [this message]
2016-06-27 17:39           ` Jason Abele
2016-06-27 19:27             ` David Lang
2016-06-27 19:22           ` 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=69058459-83F9-4FFB-871A-B83A2194DB4F@gmx.de \
    --to=moeller0@gmx.de \
    --cc=bob.mcmahon@broadcom.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=david@lang.hm \
    --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