Skip to content
Real-time statistics viewer for N1MM+ on Field Day
Branch: master
Clone or download
n1kdo Merge pull request #17 from ke0pci/patch-1
Update of rpi installation
Latest commit 8442010 May 24, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
examples
init
shapes directories cleanup/rearrange, fix up doc a bit, add init stuff May 6, 2017
.gitignore
Configure_Apache.md gid and uid for the tmp space May 24, 2019
INSTALL_RASPI.md Update of rpi installation May 23, 2019
INSTALL_WINDOWS.md fix typo in dashboard.py, update INSTALL_WINDOWS.md Jun 21, 2017
LICENSE.txt Rename LICENSE to LICENSE.txt Jan 28, 2018
README.md
VeraMoBd.ttf directories cleanup/rearrange, fix up doc a bit, add init stuff May 6, 2017
collector.py
config.py
constants.py Update constants.py Jan 6, 2019
dashboard.py Fix an issue where the section map is blank Jan 25, 2018
dataaccess.py made code more modular Jul 8, 2017
graphics.py
headless.py
logo-old.png
logo.png
one_chart.py
replayer.py

README.md

n1mm_view

n1mm_view is a set of python scripts to display real-time contest QSO statistics for N4N ARRL Field Day.

It listens to N1MM+ or TR4W "Contact Info" UDP broadcasts (see the N1MM+ documentation) and collects the contact info into a database. The contact info data is used to create useful data screens that are continuously rotated.

The contactchange and contactdelete UDP messages are also handled for changes made to the data in the logging program.

It was built to run on a Raspberry Pi and to display the statistics on a large television screen. It should run anywhere its dependencies can be installed on, meaning it should work on Linux, Windows, and OS X. It is known to run on the Raspberry Pi and also on Windows 7/10.

Currently, it supports the following displays:

  • QSOs by Operator pie chart
  • QSO by Band Pie chart
  • QSOs by Mode Pie chart
  • QSOs by Station Pie chart
  • QSOs Summary Table
  • QSO/Hour Rate Table
  • Top 5 Operators by QSO Count Table
  • QSOs/Hour/Band stacked chart
  • Sections Worked Choropleth Map, shows all US and Canada sections.

Example Images:

QSOs by Section:

QSOs by Section

QSO Rate Chart:

QSO Rates Chart

QSOs by Operator Chart:

QSOs by Operator Chart

Summary Table:

QSO Summary Table

QSOs by Operator Table:

QSOs by Operator Table

QSO Rates Table:

QSO Rates Table

Dependencies:

  • python 2.7
  • python matplotlib library
  • python pygame library
  • python sqlite3 library

Components:

  • collector.py -- collect contact data from n1mm+ broadcasts
  • config.py -- configuration data. edit this to change configuration.
    In theory, the only part you should need to edit to configure n1mm_view for your environment.
  • constants.py -- constant values shared by collector and dashboard. Bands and Modes are defined here.
  • dashboard.py -- display collected statistics on screen
  • dataaccess.py -- module contains data access code
  • graphics.py -- module contains code to create and manipulate the graphs, charts, and map.
  • headless.py -- application to create graphs, charts, and maps non-interactively, producing image files. Useful if you want to serve the images by http.
  • one_chart.py -- application that will display one chart only. Use this when debugging charts.
  • replayer.py -- test application, "replays" an old N1MM+ log to test collector and dashboard.
  • init/n1mm_view_collector.service -- systemd control file, starts collector at boot
  • init/n1mm_view_dashboard.service -- systemd control file, starts dashboard at boot
  • shapes/* -- map shapes for every US section. Thank you, Charles.

Installation

See INSTALL_RASPI.md for information to install n1mm_view on a Raspberry Pi.

N1MM+ Setup

N1MM+ needs to be configured to send the UDP messages.

Use the "Config->Configure Ports, Mode Control..." menu option to open the "Configurer".

From the "Configurer" window, select the "Broadcast Data" tab.

In the "Broadcast Data" tab, check the box in front of the word "content". Set the IP address on that same line to be either the single, specific IP of the Raspberry Pi running collector.py, or set it to the proper broadcast address for your subnet.

(I believe the proper broadcast address can be calculated from the machines's IP address ORed with the NOT of the machine's subnet mask. I could be wrong. But for your garden variety 192.168.1.n IP address, the broadcast address is 192.168.1.255. That's a good place to start from.)

Usage:

Log in to your raspberry pi. You don't need X-window system, the dashboard can create the graphics window without X. Open at least two login sessions. (Alt-F1, Alt-F2, etc. to switch between virtual consoles if not running X is good.)

Change to the directory where the code is installed.

You may wish to edit the n1mm_view_config.py file to adjust the start and stop dates of field day, for instance.

You may wish to delete the n1mm_view.db database file to reset the counts to zero. The collector.py program will re-create the database.

In one login session, start the collector: $ ./collector.py

The collector should display output for every QSO message it receives. This is a good thing.

Control-C will stop the collector.

in the other login session, start the dashboard: $ ./dashboard.py

The dashboard should start up. Eventually, graphs and tables will be displayed. The dashboard supports the following keys:

  • Q: quit
  • left and right arrows: change displayed page
  • scroll lock button: stop automatic page changing

If HTML_DIR is set, the dashboard will create PNG files of all the images.

If HTML_ONLY is selected, then no screen interface is displayed. (Use CTRL-\ to stop dashboard).

License:

This software is licensed under the terms of the "Simplified BSD license", see LICENSE.

Copyright 2016, 2017 Jeffrey B. Otterson, N1KDO
All Rights Reserved

To Do

There's always more to do. This project is still in late-prototype stage.

  • add command-line options
  • somebody might want to support other contests besides field day
    • multipliers table
  • the qso_log table could be exported to ADIF.
  • A help option ("?" key?) for the dashboard to display what keys do what.

GitHub pull requests will be happily looked at, and the odds are good that they will be merged.

You can’t perform that action at this time.