OH6BG Elevation-Angle Analyzer for VOACAP

VOACAP Home | Antennas


The EAA User's Manual

Updated: 13 November 2011

The OH6BG Elevation-Angle Analyzer (or EAA for short) reads VOACAP output files and generates a statistical elevation-angle data format, which can directly be used in the HFTA (HF Terrain Assessment) program, developed by Dean Straw N6BV. HFTA is available on the latest ARRL Antenna Book CD-ROM. HFTA shows visually how the elevation angles of a horizontal dipole or Yagi or stacked Yagis cover the statistical distribution of elevation angles that are necessary for communication via the ionosphere from one location to another.

We must always remember this simple truth: The ionosphere controls the elevation angles, not our transmitting antenna!

And thus:

EAA (v1.0, 13 Nov 2011) is available for free downloading for non-commercial personal use. This software is still in beta which means that there can be bugs, and unexpected things can happen. There is no warranty whatsoever. So be warned that you use it at your own risk! Nevertheless, I have used it extensively under Windows XP, and so far, without any major problems.

How does EAA work?

The EAA basically reads VOACAP's textual output files and assumes that the calculations have been made using either Method 25 or Method 30, or both. Other Methods are not supported at the moment. I strongly urge that if you choose to try this software for serious analysis, please use the 081227 (Dec 27, 2008) version of VOACAP.

Please note that EAA does not care which input values you have chosen for creating the VOACAP output file. So it is your responsibility to make a good model of your case in VOACAP if you want to get some sensible predictions. However, there are some restrictions on the use of frequencies and the SSN values if you want to make full use of EAA:

The slow part: Creating the database with REL values > 0

When EAA processes the VOACAP output and builds its database, it only picks those propagation modes (and frequencies) from the output where the predicted REL value is greater than zero. The REL value is in direct relation to the Required Signal-to-Noise ratio (SNR) which is a user-settable value in VOACAP. Typically, I set the REQ.SNR value to 24 dB/Hz which can be considered as the lowest value for the CW mode.

Reading an output file can take a lot of time, I mean - a lot. While reading a huge output file (say, tens of millions of lines), the user interface of EAA may seem unresponsive for minutes. Please wait patiently, though. Processing such files can take up to 10-15 minutes, depending on your CPU.

The user interface

So, this is EAA:

Let's start by examining the column headings in the upper part of the user interface. These are the bread and butter of your EAA database:

Column headingExplanation
#the record number in the EAA database
TXthe name of the transmitter location
RXthe name of the receiver location
FREQthe frequency
SSNthe Smoothed Sunspot Number (use 5, 25, 50, 75, 100 and 150 only, for filtering purposes)
MONTHthe month of the year (please note that the year itself is irrelevant in VOACAP)
HOURthe UTC time (e.g. "1" = 01 UTC, provided UTC was used in VOACAP...)
SDBWthe Signal Power at the receive antenna (can be translated to S-Meter values)
TANGLEthe predicted take-off angle of the transmit antenna (in degrees) for the predicted MODE, see below.
RELthe reliability value i.e. the probability of achieving the user-defined Required SNR (REQ.SNR in VOACAP).
"0.1" = 10%; "1" = 100%
MODEthe predicted propagation mode for the given hour, month, SSN, and frequency.
E.g. "2.F2" means two hops via the F2 layer, "3. E" means three hops via the E layer.
TOthe minimum take-off angle of the antenna (in degrees, a system parameter in VOACAP).
Also in this cell, the VOACAP Method, either "25" or "30". Not visible in the screenshot.

All columns can be sorted in ascending or descending order, just click on the column heading. This feature makes it easy for you to view the database e.g. by frequency or by Signal Power (SDBW). However, if there are more than, say, 50,000 records in your database, sorting the data takes a lot of time, and there is the freezing effect as described above.

The HFTA Elevation-Angle Data

The lower part of the user interface, named "Elevation angles by band", consists of a textual data window, some special filters (REL, SSN and Month) and a plotting function. The data in the window is in the format that is directly understood by HFTA. With the special filters you can fine-tune your HFTA data file, and there is also an option to graphically view the elevation-angle distribution data by band. The "Plot chart" button and the Band and Scale selector (defaults to "35", the number of elevation-angle markers in the plot) go together.

Let's start with the interesting stuff first by plotting an elevation-angle chart for one band. For instance, when the textual elevation-angle data is visible and you are interested in viewing the elevation-angle data for the circuit on 10M (28.4 MHz), select "10m" on the Band selector, leave Scale selector to "35", and then click on the "Plot chart" button. The following chart will appear in a separate window:

This chart demonstrates the predicted percentage - or statistical distribution - of the elevation angles that the ionosphere can support for the circuit on the 10M band. We can see in the header section of the chart that the solar minimum and maximum (SSN 5-150) on all months of the year have been considered. The REL value used in this chart was 0.1 (10%) which means that all database records where the REL was greater than or equal to 0.1 was taken into consideration.

The Y-axis of the chart show the predicted percentage of the elevation angles. The figures in the bars have been rounded. The X-axis shows the elevation-angle markers from 1 to 34 (degrees). For instance, the elevation-angle marker "1" covers the predicted angles from 1.00 to 1.99 degrees, the marker "2" covers the angles from 2.00 to 2.99 degrees, and so forth.

Solar minimum vs. the total solar cycle

By default, the total solar cycle, or all sunspot numbers from 5 to 150 are considered while the HFTA elevation-angle data is being run. This may give you an overall picture of the elevation-angle distribution in general but it is of little help when you happen to be in the sunspot minimum, as we are at the time of writing. Therefore, the SSN pop-up menu offers some helpful preset values to choose from:

You can select an individual SSN number such as "25" which is close to the current predicted SSN value. You can also select a group of SSN values such as "Low" which then considers the SSN values of 5 and 25 in the final analysis.

Specific month(s) vs. all months

By default, all months of the year are taken into the analysis. If your database does not cover all months, EAA will nevertheless consider all available months. For the sake of comparison, it can be useful to run the analysis against just a specific month, or a group of months.

Saving the elevation data

As soon as you launch EAA for the first time, a small 2KB database, named "ElevationAngleDatabase.rbd", will be created into the directory where EAA is located. This is your elevation-angle database, and if you, after a long EAA run, want to back up your data, just make a copy of that database file, and give it a more meaningful name. Remember to keep the extension of ".rbd".

Saving your data as an HFTA elevation-statistics file

The main purpose of EAA is to create elevation-statistic files for use with HFTA. Choose the option "Save elevation data..." from the File menu, and give your file a meaningful name. Remember that all HFTA statistic files ends with the extension of ".prn". So, don't forget to add it!

Exporting your elevation data into a spreadsheet

The elevation-angle data you have created is not the sole monopoly of EAA. You can export this data into a tab-separated file format which can then later be opened e.g. in Microsoft Excel or OpenOffice Calc. Of course, you can open the file with your favorite text editor as well.

Thank you

I wish to thank Dean Straw N6BV for our discussions during the development of this software. He was a great inspiration.

Also a special thank-you to Greg Hand, the maintainer of the VOACAP code, who made changes to VOACAP even on his birthday!

© 2003-2011 Jari Perkiömäki, OH6BG/OG6G.