public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Thijs van Veen <dicht@operamail.com>
To: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@lists.open-mesh.org>,
	Battle of the Mesh Mailing List <battlemesh@ml.ninux.org>
Subject: Re: [B.A.T.M.A.N.] [Battlemesh] Batman-adv high TQ and Low throughput
Date: Thu, 24 Apr 2014 15:38:26 +0200	[thread overview]
Message-ID: <1398346706.1416.109931001.56F7753F@webmail.messagingengine.com> (raw)
In-Reply-To: <20140424125820.GR26376@medion.lan>

It depends a bit on the receiver's quality, I've had experiences where
the SNR could drop to about 8 and the link would still somewhat work.

The thermal noise is mostly intrinsic to how energy relates at a
particle level, this is denoted by the Boltzmann constant (k). 
Further, it depends on the bandwidth (B) used and temperature (T).
Nthermal = B * k * T = 20*10^6 Hz (802.11 channel) * 1.38065*10^-23 J/K 
* 300 K (27 Celsius) ~= 8.28 * 10^-11
This gives the noise in Watts, to change it to dBm (which references
miliWatts), you take 10*log10( N * 1000 ) ~= -100.
[1] Has a nice table with examples of this noise.

In reality, there's more interference than just from the temperature.
It's quite probable your receiver adds another 5 dBm to its reported
noise to account for this.
I also recall from my time working on my thesis that receivers/drivers
tend to return a static value for noise, rather than actually measure
it.

[1]:http://en.wikipedia.org/wiki/Thermal_noise#Noise_power_in_decibels

-- 
  Thijs van Veen
  dicht@operamail.com


On Thu, Apr 24, 2014, at 14:58, Bastian Bittorf wrote:
> * Thijs van Veen <dicht@operamail.com> [24.04.2014 14:45]:
> > N is usually somewhere around -100 dBm, meaning that a Prx of about -85
> 
> unsure about that: it depends on the WiFi-receiver's quality, isn't it?
> 
> when i use 'iwinfo' the noise is always '-95', no matter on which
> location.
> it seems to come from nl80211_get_noise() but i dont understand it fully.
> 
> or do i mix something up? bye, bastian

-- 
http://www.fastmail.fm - Or how I learned to stop worrying and
                          love email again


  reply	other threads:[~2014-04-24 13:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-24  8:34 [B.A.T.M.A.N.] Batman-adv high TQ and Low throughput cmsv
2014-04-24  9:48 ` Simon Wunderlich
2014-04-24 11:57   ` Thijs van Veen
2014-04-24 12:58     ` [B.A.T.M.A.N.] [Battlemesh] " Bastian Bittorf
2014-04-24 13:38       ` Thijs van Veen [this message]
2014-04-30 14:24   ` [B.A.T.M.A.N.] " cmsv
     [not found] ` <5358D919.3010700@altermundi.net>
     [not found]   ` <53618E04.2010404@wirelesspt.net>
     [not found]     ` <CADSh-SOhXxvhV1_mMPcfQJAPxaRMpsTqCgnP7k4P0firBH4ZiA@mail.gmail.com>
2014-05-02 14:30       ` [B.A.T.M.A.N.] [OpenWrt-Users] [Battlemesh] " cmsv

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=1398346706.1416.109931001.56F7753F@webmail.messagingengine.com \
    --to=dicht@operamail.com \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=battlemesh@ml.ninux.org \
    /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