Skip to main content

Wireless device monitoring with wavemon

Wireless device monitoring with wavemon

wavemon is a wireless device monitoring software that allows you to watch signal and noise levels, packet statistics, device configuration, and network parameters of your wireless network hardware. It was written by Jan Morgenstern and is regularly maintained.

It allows you to display your WiFi signal strength in realtime.

Installation and start

You install wavemon with

sudo apt install wavemon -y

And start it with

wavemon

and a dashboard appears.
Check the wifi signal strength of your Raspberry Pi digital picture frame before you hang it up on the wall 3

If you can’t see the function keys at the bottom, you need to make your Terminal window larger.

What the information means

Let’s quickly run through the data points that you want to look at to understand better the WiFi quality that your digital picture frame enjoys.

Signal strength

Basically, the higher the signal strength, the more reliable the connection and higher speeds are possible. The signal strength is specified as -dBm (decibels related to one milliwatt).

Values between 0 and -100 are possible, with more being better. So -51 dBm is a better signal strength than -60 dBm.

However, the value 0 is not realistic. Even -30 dBm is hard to reach, and you have to stand almost directly next to the access point.

Here is some guidance on how to read the results:
  • 50 dBm is considered an excellent signal strength.
  • 67 dBm is said to be the minimum signal strength for reliable and relatively fast packet delivery.
  • 70 dBm is the minimum signal strength for reliable packet delivery.
  • The minimum value for a basic connection is -80 dBm. However, packet delivery is no longer necessarily reliable.
  • 90 dBm is already very close to the basic noise. Here a connection probably does not work anymore.

Link quality

A network can be received with a very good signal strength but not so good link quality.

In simple terms, it means how much of the data you send and receive will make it to the destination in good condition.

The quality indicator includes data like Bit Error Rate (BER), i.e., the number of bit errors in received bits that have been altered due to noise, interference, distortion, or bit synchronization errors. Others are Signal-to-Noise and Distortion Ratio (SINAD).

It is measured in percentage or on a scale of up to 70. So you will see a value like “60/70”.

Unlike signal strength, it is somewhat harder to say which values are still considered to be ok.

But if the value is low and your signal strength is high, you may get interference from, e.g., kitchen appliances or other electronic devices. Moving them further away may improve the link quality.

Frequency

Another interesting indicator is the WiFi frequency.

This shows if your Raspberry Pi connects to the slower 2.4 GHz network, or the faster 5 GHz version, provided, of course, that your router offers both networks.

freq: 5220 MHz, ctr1: 5230 MHz, channel: 44 (width: 40 MHz)

Alternatives

An equally good tool to measure WiFi performance is
iwconfig
which gives you a snapshot of the Wifi quality as compared to the live data of wavemon.

wlan0     IEEE 802.11  ESSID:"Hundertwasserhaus"  
          Mode:Managed  Frequency:5.22 GHz  Access Point: 78:8A:20:D5:5A:48   
          Bit Rate=180 Mb/s   Tx-Power=31 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:on
          Link Quality=61/70  Signal level=-49 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:49  Invalid misc:0   Missed beacon:0

Comments

Popular posts from this blog

"Blinky" TDOA RDF Detector

Our local Amateur Radio club is building a Radio Direction Finding TDOA (Time Difference of Arrival) detector that has LED's to indicate the direction (Left or right) of the fox.  Here are the build instructions.   (Note: this project was originally presented by NZ1J.  See his video:   https://www.youtube.com/watch?v=mNqUKYkifOo&t=68s   ) Here is the completed project: We start with the schematic:   Note that you either install PIN Diode pairs s D3 and D2, or Diodes pair D1 and D4.   The difference between these is the packaging.  If you are ok with Surface mount, then install D1/D4.  If you want discrete components use D3/D2. Next is the PCB.   The PCB can be ordered using the GRBR files available from the author.  The BOM for the electronic parts is as such: Doppler Direction Finder Bill of Materials   11/12/2021        Qty Part Digi-key Part Number References 1 PIC Pocessor PIC16F18324-I/P-ND U1 1 14 Pin Socket ED3114-ND U1 1 78L05 497-7268-ND U2

Radio Direction Finding - TDOA

This article describes a few projects that I built from plans for Amateur Radio Fox Hunting. Basically, the hobby/sport is for someone to hide a few low power "Foxes", which are small transmitters that beep or send Morse Code, and then have a bunch of HAM's try to find them. The first project that I built was a Yagi Antenna (Directional receiver) and a 4MHZ Offset Attenuator.  The attenuator is needed when you get close to the fox and you need to reduce the power of the received signal.  I struggled with this setup because, on my first 2 fox hunts, there was too much reflection and multi-path interference.  This causes false direction detection and if you are not mentally prepared for this, you want to throw all of your equipment into a garbage can and take up a different hobby.   There are some truly strange individuals who find this frustration fun and enjoy making other people suffer, but I will leave that discussion for another day.  Anyway, in one particularly frustr

Internet Explorer 11 (Windows 8.1) "Google Bug". Back Button hangs IE

I discovered this week that there is a bug in Google's web page that causes Internet Explorer 11 to hang when you click the back button. The specific scenario is that when you start on Google's web page, and go to a link of some sort, it can trigger this bug when you click back to return to google.  This is fairly well documented on some forums, in that it has been like this for a while, and Google seems unwilling, or unable, to modify their code to not trigger this bug. I do not consider it a IE11 bug as much as I consider it a problem with Google.  Microsoft should of course fix their issue, but also you would think that Google might take this seriously.  To trigger the issue, Go to google.com and search for something that takes you to a Microsoft page.  Example: "Exchange edge server".  Click on the first link and then click on any link on that Microsoft page.  Then click back twice.  The first "back" will work fine because it takes you to the original Mi