SimpleCalc

SimpleCalc

SimpleCalc is an application that can help you calculate the cascaded noise figure of your EME receiving chain, predict the amount of sun noise your system should be able to detect and the SNR expected when receiving your own echoes or those from another station. It can also measure the HPBW (-3 dB), -10 dB points, the gain and more of your antenna.

SimpleCalc can be used to measure the level of noise received, it uses filtering on the audio signal from the radio (via soundcard) and presents the filtered data (RMS value) in a separate window as a graph.


During installation and debugging of my 70cm EME system (and later on my 4.8m dish for 23cm EME), I developed SimpleCalc to help me understand and calculate the noise figure of my system, the effects of changing LNA's, cable losses etc. I also needed a quick and easy tool to help me calculate the expected sun noise I should be able to measure and at the same time, provide an easy way of recording notes taken during measurements and experimentation.


For many years, the "EMECalc" program by Doug VK3UM (sadly now a Silent Key) has been "The Tool" to use for doing this and much more (and still very much is!).


In my case, I needed something a little more "light" with only a fraction of the features of EMECalc. I also wanted to learn something!

This was how SimpleCalc was born.


Acknowledgments.

Many thanks to Paul W1GHZ for his reviews, suggestions and inputs on this webpage and SimpleCalc and its features.

During the development and testing of SimpleCalc, I got valuable input and suggestions from members of the Moon-Net email reflector, in particular Vladimir UR5EAZ, Peter G3LTF and Charlie G3WDG. 

Dave KG0D has done a lot of practical tests with the tool, also many thanks to Ingebrigt LB6B for brainstorm, suggestions and ideas in the process.


Quick jump to sections:


DISCLAIMER:  

I'm NOT an mathematician !!


I have tried to make SimpleCalc correct. However, I do not by any means, claim to have the full overview of all the aspects of the math going into making the calculations "super precise". SimpleCalc calculates NF, predicts sun noise, and calculates echo strengths but leaves out a few of the finer details, details that might get you 0.1 or 0.2 dB closer to "the real truth".

One of those "finer details" that IS handled: when you measure antenna beamwidth by scanning across the sun, the sun's own size slightly widens what you see. SimpleCalc corrects for this before computing gain, so the numbers reflect your antenna's real beamwidth, not a sun-broadened one.


That being said, I think (and hope) that the application makes up for this by being simple and easy(er) to use.


One thing you can be absolutely sure about, is that there are errors in the program :) When you find some, please send me an email of what you see and have done. My email address is on the CV/Contact page.



Below is a video of SimpleCalc when I made the first version, a lot has changed since, but it shows some of the features.

The main window

The main window of SimpleCalc is shown below.

This is where you enter most of the data for your system.

All the results in the "Results" box to the right are re-calculated every time you change one of the parameters on this (and other) screens of SimpleCalc. 


In order to calculate the "Expected sun noise" the program needs a "band specific SFU" value. The program fetches todays and yesterdays measured Solar Flux data from NOAA and uses these to calculate the SFU value for the (Ham) band you select. The selection of which site to use for SFU data is done on another screen (see below).

The used SFU value is VERY important as even a slight change in that will have a great impact on the "Expected sun noise" value.


You can find much more information on the SFU values, their usage and what to be aware of by studying the many articles, posts and documents about VK3UM's EMECalc.


The main window also enables you to calculate the expected noise increase if the LNA input is terminated in a 50 ohm resistor. Enabling the "terminator" feature also makes it possible to use "crosscheck", this will basically calculate the Ta value IF, and ONLY IF, all other values have been entered correctly!


Each of the controls have "tooltip" help texts. If you let the mouser hover over a control, the tooltip help text will popup.


In the menu of the main window, you will find functions that allows you to save and load setups from files.

You can also save/load the current settings using the two buttons in the lower left corner.


The "Edit comments" button is explained below.

"Get SFU data.." - Update SFU Data window

This window handles all the updating and interpolation of SFU data. As the 5 sites that measure SFU data, only measure these on some specific "non ham" frequencies, we need to do some interpolation of the actual measured values in order to get the SFU value for the ham bands we are interested in.


Currently, I have implemented two different ways of doing this interpolation, "Spline" and "Lines". The Spline method uses a "spline" that goes thru all the measured SFU values to derive the ham band SFU values. The "Lines" method interpolates the SFU values by "drawing" a line between the two "neighboring" measured SFU values and calculating the needed SFU value.


The "Lines" method is what usually are used by observatories, it is regarded as the recommended and "standard" way of doing interpolation/extrapolation of SFU values to other frequencies.

I made both options available for now, as there are some different opinions on which gives the most correct answer!


Whichever of the two methods you use, be careful that they don't generate "out of the ordinary" results, watch the graph at the bottom of the window!


Remember a Sun that is not stable/quiet can change the expected Y-Sun level a lot. Sometimes when the Sun is (very) active, the results can change from one moment to the other!


The "Lines" (standard) interpolation method is described here:

Determination of Earth Station Antenna G-T Using the Sun....




The SFU update window looks a bit busy at first.

The upper part with the table, lists the measured SFU values from around the world and different times. Red colored columns are data from "yesterday" and orange colored columns are data from "today". Use the column that is closest in time and location to your location and time.


In the yellow column, you can manually enter measured SFU values (for example historic data) and use these as the basis of the band specific SFU values.


To the extreme right, there is a list of the ham bands and their calculated SFU values (derived from the measured SFU values). The band specific value(s) shown there is the value that is used on the main window for the "Expected sun noise" calculation. 

If you change the data on this page, the SFU value on the main window are automatically updated.


The graph on the bottom half of the window shows both the physical measured SFU values and also the derived "ham specific bands" SFU values. The blue data is the measured SFU values and the orange data is the derived/interpolated ham band SFU values.


It can sometimes happen that a measurement site does not have data for one or more of the frequencies, this will be shown as "-1" in the data. Depending on the interpolation method used (Spline/Lines), you can get into a situation where there is no valid data for a specific ham band.


Using the "Fetch newest data" button will download the newest data from NOAA, these data are downloaded using FTP from: ftp://ftp.swpc.noaa.gov/pub/lists/radio/rad.txt


When downloading data, a copy of these are saved in the "Documents" folder on your PC in "...Documents/LastSFUData.txt".


Page 3 in this document explains some of the theory behind interpolation of the measured SFU values to a specific frequency: Determination of Earth Station Antenna G/T Using the Sun or the Moon as an RF Source


SimpleCalc can use either "linear interpolation" or "Spline interpolation". There is some discussion about which one gives the "most correct" answer.


The "Linear interpolation" is also what is used by for example Learmonth Observatory:

Australian Space Weather Forecasting Centre - Quiet Solar (IFLUX)


If you enter the measured flux values from the table on their website:


After entering the measured Flux values in the "Your data" in the "Get SFU data", you can enter any of the frequencies used in the Learmonth IFLUX screendump in the main window of SimpleCalc, f.ex 6000 MHz, and you will see that the interpolated value matches (313.4) exactly the calculations done by Learmonth.

This is when using "Linear interpolation" in the "Get SFU data" window.


As previously noted, some believe that a "Spline interpolation" is more correct. The choice is yours :)


Two station and own echo window

The "Two stations performance and echo's" window lets you calculate the possible SNR (Signal to Noise Ratio) between two stations. It will also tell you the SNR of your own (and the DX stations) own echo's. You can copy the values from the main screen to either the "Home" or the "DX" half of the window, you can also save and load the settings for Home and/or DX.

Let the mouse hover above each control and you will get some help for each field.


I found excellent inspiration here: KA1GT - EME Echoes


Got some good results comparing my strongest echoes detected on my 70cm EME 4-Yagi system.


Noise Measurement window

The application has a window that will allow you to measure the noise level currently received. The application uses a soundcard interface to sample the audio, filters this and calculates the RMS value from this. It is VERY important that you DISABLE AGC completely when doing this, only by disabling the AGC the measurements will make any sense.


It is also VERY important that the receive chain is linear in the range of the noise measured, clipping/limiting by the receiver will make the measurements invalid!

A good test is to use a good step attenuator before the receiver, check that the attenuation selected matches the difference shown on the noise window measurements, this is equally important when pointing towards cold sky as it is when pointing towards the sun!


As a general rule, the receive chain needs to be linear from about 6 dB below cold sky level to more than 10 dB above the maximum sun noise you will experience! Gaussian noise has peak power levels that are more than 10 dB above average so you need the extra 10 dB (minimum) of headroom!


The noise window will collect current antenna position if you are using a URC rotor controller. You need to enable "UDP Broadcast" in the "Setup" window of the URC, and set the "UDP BC port" to 30201 on the URC rotor controller for this to work.


Using the control to the left, you can select which input to use, the dB per division and the width of the graph in seconds.


The "Average" field sets the number of samples that are averaged (2 updates/second), usually a value of 20 (10 seconds long filter) is fine, if you want "super nice" traces, for example for sun drift measurements (see "HPBW section" below), you can set this to 50 (or even more).


Pressing the "Set Cold" button will take a snapshot of the current measured noise level and place a blue line with the text "(Cold Sky=-xx.xx dB" at that level. You can also right click with the mouse on the signal and select the "Set Cold Sky value to point" menu item to set the "Cold Sky" value. The  "Delta(dB)" number just below the "Set Cold" button, will show the delta between the current "Cold Sky" value and the current noise level (The "Cold Sky" value will also be saved in settings, so the next time the application is started, this stored value will be used as the basis for the delta value).


Pressing "Pause" will pause the update of the graf, the data collected will be inserted once the button is pressed again. Right click with the mouse inside the graph area to bring up the submenu shown.


Various markers are available by right-clicking with the mouse over the trace. Reference markers, delta markers (both referenced to "reference marker" or to "Cold Sky" level) and "user comment markers".

Cold sky can be set, either manually or automatically and HPBW can be calculated.


It is also possible to save and load the contents from the noise window (including any markers).


Explanation of marker functions in Measure noise window.

Automatic cold sky feature

On the Noise Measurement window, you can set the "cold sky" reading either manually or automatic (automatic since version 1.0.0.20). If selecting the automatic mode, SimpleCalc will search and try to find the proper cold sky reading. This will be from the data currently visible on the Noise Measure window, if the window is zoomed, only the visible data will be used for the search.



To use it, right-click the graph and choose Find Cold Sky value automatically from scan to have SimpleCalc determine the cold-sky reference from the recorded data instead of picking a point by hand.


Two situations, handled differently


The function first checks whether there is a Sun in the data at all, by comparing the quietest and busiest parts of the trace. Empty sky varies by a few tenths of a dB; even a weak, narrow Sun spans several dB, so the two cases separate cleanly.


With a Sun present, it looks for the lowest sustained plateau. A window is slid across the data, each window averaged in linear power, and the lowest one sets the reference; other windows within a small tolerance are treated as the same level and included. Because contamination is one-sided — the Sun, RFI and ground pickup only ever add power — the lowest sustained level is the best estimate of empty sky.


With no Sun present, there is no plateau to search for: the whole record is empty sky, so all of it is averaged. This is the normal way to set the reference before the Sun arrives — point at blank sky, record for a minute, and run the function. Searching for a lowest section here would simply track the low side of the slow baseline wander and read slightly low.


Two approaches it deliberately avoids in both modes:


  • Averaging the lowest N samples.That selects the downward noise excursions and always reads low, with the error growing as the trace gets noisier.
  • Averaging everything below a threshold.The stretch just after the Sun leaves the main lobe is not empty sky — it still carries far-sidelobe and ground pickup decaying away. Including it biases the result high by several tenths of a dB.


All averaging is done in linear power. Averaging dB values would form a geometric mean and read low.


Zoom is respected


Only the samples currently visible are used, and the Sun-present check is re-evaluated on that range. If part of a recording is spoiled by interference, a slew or a second source, zoom to the section you trust and run the function on that alone. Zooming to a clean, flat stretch of sky gives an exact result.


One case needs a little care: if you zoom to a region that still contains part of the Sun's decaying skirt, that range can look flat enough to be taken for empty sky, and the result will read slightly high. A gentle skirt and a slow baseline wander cannot be told apart reliably from the data, so rather than guess, the function warns when the visible range is not flat and suggests zooming to a flatter section. In practice, either leave the view unzoomed — the plateau search handles the skirt correctly on its own — or zoom to a stretch that looks visibly level.


What it reports


Before anything is applied, a dialog shows the level found, how many samples were averaged, the sample noise, and the difference from the cold-sky value currently set. With a Sun present it also shows which samples the plateau was taken from, the peak level and the implied Y-factor; with no Sun it reports the level spread across the range instead. You then choose whether to accept it.


It warns when:


  • the visible range is not flat, and may still contain part of the Sun's skirt;
  • the quiet stretch is short — barely enough data to average;
  • the level differs by more than 0.1 dB before and after the Sun (or, on a Sun-free recording, between the start and end), indicating gain or atmospheric drift;
  • the Y-factor is below 3 dB, suggesting the Sun was not properly in the beam. This is only raised when a Sun was actually found, so recording empty sky on its own is never flagged as a failed measurement.


Accuracy


Tested against simulated scans with a known baseline, the value returned is typically within 0.01–0.05 dB of the true level, including on heavily averaged traces where sample-to-sample noise is only a few thousandths of a dB, and on records with slow baseline undulation. The manual Set Cold Sky value to point option remains available if you prefer to choose the level yourself.



Below are a couple of examples of the "automatic cold sky" feature.


First example finds cold sky automatically from the full dataset currently recorded, the second example shows the search done on a zoomed part of the dataset.

The third example the data are zoomed and the peak from the measurement of 50 ohm termination on LNA is visible. In this case, SimpleCalc warns you about this, but still manages to find a plausible cold sky reference.


Measuring HPBW and antenna gain using the Sun

(Remember, ALWAYS disable the AGC of your radio and make sure you are within the linear range of your receive chain (see this also), these two things are VERY important!)


Datafile that can be loaded and experimented with in the "Noise measure window", NDAT file


SimpleCalc can measure (among other things) an antenna's half-power beam width (HPBW) and estimate its gain directly from a sun transit. The procedure is non-invasive — the antenna passes through the sun (or vice versa) while the noise level is recorded — and the analysis is done with a single right-click once the transit is complete.

HPBW explanation: https://www.everythingrf.com/community/what-is-half-power-beam-width.


It's worth noting that once the antenna's beamwidth approaches the sun's diameter (~0.5°), the raw drift-scan width is no longer the antenna's true HPBW — the sun's own size gets convolved into the measurement. SimpleCalc corrects for this automatically. As the measured beamwidth gets close to the sun's diameter, though, that correction becomes increasingly sensitive to measurement noise: below about twice the sun's diameter, SimpleCalc still computes a result but flags it as low-confidence; below roughly 1.4 × the sun's diameter, the correction is mathematically undefined and SimpleCalc reports no result rather than an unreliable one. For the large majority of amateur EME dishes — where beamwidths are comfortably wider than this — the method is accurate and this isn't a practical concern.


Two scan geometries are supported:

  • Azimuth drift— dish azimuth parked, sun drifts through the beam in azimuth as Earth rotates. Suitable when the sun's elevation barely changes during the scan, or when you let the elevation axis track the sun. This is the classic geometry.
  • Elevation drift— dish elevation parked, dish azimuth tracking the sun. The sun moves through the beam in elevation as it climbs or descends through the parked elevation. Useful when you want to characterize the antenna pattern in the perpendicular plane, or when local terrain makes the azimuth-drift geometry inconvenient.


Both modes are accessed from the chart's right-click context menu (Find HPBW (Sun) — Azimuth drift and Find HPBW (Sun) — Elevation drift).


Preparation

Set the operating frequency in the band selector on the left of the screen. This determines both the predicted sun noise and the apparent solar diameter used in later corrections.

Also set the "Average" input field to a high number, I usually use a value of 50 for sun drift scans in my systems.


Establish the cold-sky reference by pointing the antenna at a clean patch of sky away from the sun, the moon, the galactic plane, and any local terrain features, and pressing "Set Cold" button. The stored cold-sky level is used as the reference for both the live Δ-dB readout and the (S+N)/N correction inside the HPBW measurement (you can also set the "cold sky" level later on by right clicking on the graph and select "Set cold sky to point"). You can either find and set the "cold sky" manually, or you can use the automatic cold sky function.


For an azimuth-drift scan, move the antenna so that it sits a few degrees ahead of the sun in azimuth — typically 5–10° offset, but always more than half the expected HPBW so the sun fully crosses the beam on both flanks. Keep the azimuth axis stationary and let the elevation axis track the sun.


For an elevation-drift scan, choose a target elevation a few degrees ahead of where the sun will be (above its current position if you want to scan as it rises through your parked elevation, below it if you want to scan as it descends). Set the dish to that fixed elevation and let the azimuth axis track the sun. As the sun climbs or falls through the parked elevation, it will drift through the beam in elevation, producing a clear hump in the noise graph.


A typical transit takes 30–60 minutes for an azimuth-drift scan; an elevation-drift scan can take longer (1–3 hours) depending on the time of day, since the sun moves more slowly in elevation than in azimuth except near the horizon (and the beam width of the antenna!). While the scan is running, the Delta (dB)field shows the live Y-factor between the current noise level and the stored cold-sky reference.


Running the measurement


Once the sun has fully crossed the beam and both flanks have dropped well below the peak, right-click anywhere on or near the hump and select the appropriate entry from the context menu:

  • Find HPBW (Sun) — Azimuth drift— for a fixed-Az (El-tracking) scan
  • Find HPBW (Sun) — Elevation drift— for a fixed-El (Az-tracking) scan


The two modes share the same numerical machinery; they differ only in how the sky-degree offset is computed from each flank crossing.


SimpleCalc will:


  1. Locate the peak of the hump nearest to your right-click position. The peak is then refined by least-squares parabolic fit to all samples within 0.5 dB of the rough integer-index maximum — this gives sub-sample precision and is robust against noise on flat-topped main lobes.
  2. Determine the −3 dB threshold using the (S+N)/N correction. The receiver measures total power (sun + system noise), but the −3 dB point of the antenna pattern is where the sun's contribution alone halves. For a peak Y-factor Y, the corrected threshold is at 10·log₁₀((Y−1)/2 + 1) dB above the cold sky. For strong signals this is nearly identical to peak−3 dB, but for weak ones it makes a measurable difference.
  3. Walk outward from the peak on both sides and interpolate the exact crossing where the noise level falls through the −3 dB threshold.
  4. Convert each crossing to a sky-degree offset, according to the scan geometry:

    • Azimuth-drift mode: at each flank crossing, the sun's elevation is read at that specific moment and the local cos(El) is used to convert the rotor-azimuth span into a true sky-plane angle. This per-sample cos(El) treatment matters for long transits where the elevation can change significantly between the rising and falling flanks.
    • Elevation-drift mode: the sky-degree offset is simply the difference between the sun's elevation at the crossing and the sun's elevation at the peak. No cos(El) correction is needed — a degree of elevation is a degree on the sky everywhere.
  5. Deconvolve the sun's apparent diameter from the measured HPBW using Gaussian quadrature: HPBW_true = √(HPBW_measured² − FWHM_sun²). The apparent sun diameter is frequency-dependent; at 1296 MHz it is ≈0.60°, but at lower frequencies the radio sun grows considerably (≈1.1° at 144 MHz).
  6. Estimate the antenna gain from the corrected HPBW using two formulas:
    • G = 41253/HPBW²— the upper bound for a lossless, 100% efficient beam
    • G = 27000/HPBW²— Stutzman & Thiele's typical-dish approximation (≈65% efficiency)
    • G = 20600/HPBW²— Stutzman & Thiele's typical-dish approximation (≈50% efficiency)
  7. If the peak Y-factor exceeds 12 dB, also locate the −10 dB crossings (with the same (S+N)/N correction) and compute the BW10/HPBW ratio. This ratio is a sensitive illumination diagnostic — see "Beam-shape verdict" below.
  8. Place markers on the curve: pink stars at the peak and the two −3 dB crossings, light-blue stars at the −10 dB crossings if measured. Each marker carries a label with the role, level, sun position, and timestamp. The peak marker is tagged [Az drift] or [El drift] so the geometry used is always visible at a glance.

  9. Display the full result in a summary pop-up, with the title indicating which mode was used.


If there are multiple humps on the graph from earlier measurements, simply right-click on the one you want — the algorithm confines its peak search to a 6 dB window around the click and ignores the others.


Once the HPBW measurement are completed and the result box is shown, you can also optionally save most of the results as a one page PDF file. The filename will be suggested as "HPBW-Report-2026-06-25_114418.pdf", the date and time is taken from the actual peak value. Optionally, you have the report include the major values from the main window in SimpleCalc (different NF/Gains, losses, SFU value etc).


Example of a report file: PDF report file.

The HPBW result message box shows everything in one compact view:

Below is a video showing a drift scan in azimuth of the sun. The data collected can be downloaded below, you can load these in the Noise Window of SimpleCalc by right-clicking with mouse and select "Load data from file".

The file is here.


Header & mode

  • Window title indicates the scan mode used ("Sun drifting in azimuth")
  • First line confirms the geometry: "Sun transit – Az plane (dish Az parked, sun drifts by dish in azimuth, elevation tracks)"


Reference levels

  • Cold sky level — the stored cold-sky power level from the "Set Cold" button (−60.79 dB in this example)
  • Peak level — the sample-card power at beam center, with the sun's azimuth and elevation at that moment (−43.45 dB at Az 140.19° El 52.8°)
  • Sun noise — the Y-factor between cold sky and peak (17.33 dB), i.e. the strength of the sun signal above the system noise floor


−3 dB crossings

  • The azimuth and elevation of the left and right −3 dB crossings, with the sky-degree offset from peak shown in brackets
  • Offsets are computed with per-sample cos(El) — the elevation at each individual crossing is used, not just the elevation at peak, so long scans where the sun's elevation drifts noticeably between flanks are handled correctly


Beam width and gain

  • True HPBW — the sun-size-deconvolved half-power beam width, with the sun's apparent diameter at the current frequency shown for reference (3.25°, sun FWHM 0.60° at 1296 MHz). The "true" value is what you compare to dish geometry / theoretical expectations
  • Gain (theoretical) — upper bound assuming 100% efficiency, computed as 10·log₁₀(41253/HPBW²) (35.93 dBi)
  • Gain (~65% eff.) — typical real-dish estimate using Stutzman & Thiele's 27000/HPBW² formula (34.09 dBi). For most well-built EME dishes the typical value is the one to trust
  • Gain (~50% eff.)— typical real-dish estimate for small dishes (~1.5m at 23cm with large blocking of feedhorn for example) using Stutzman & Thiele's 20600/HPBW² formula (32.93 dBi). For most well-built EME dishes the 65% value is the one to trust


−10 dB beam width (beam-shape diagnostic)

  • Reported only when the Y-factor is large enough (≥12 dB) for the −10 dB threshold to sit comfortably above the noise floor
  • −10 dB level — the absolute power level corresponding to the −10 dB-on-pattern point, computed with the same (S+N)/N correction as the −3 dB threshold (−52.79 dB)
  • Azimuths and sky offsets for both flanks
  • BW10 (measured) — the full −10 dB width, shown in both rotor-azimuth degrees and sky degrees (9.37° → 5.67°)
  • Ratio BW10/HPBW — the key illumination diagnostic (1.72 in this example)
  • Verdict tag — interpretation of the illumination state (here "EME-optimal low-noise")
  • Reference line at the bottom: ratios in 1.55–1.65 mean max-gain illumination (good for TX but hot for RX), 1.65–1.85 mean EME-optimal low-noise (best G/T)


Beam-shape verdict (BW10/HPBW ratio)

The ratio of the −10 dB beam width to the HPBW is a sensitive indicator of how the dish is illuminated by the feed. For an EME station the relevant categories are:


Ratio Interpretation:

  • < 1.40 Sharper than physically reasonable — check the measurement
  • 1.40 – 1.55 Severe over-illumination — high spillover, hot system
  • 1.55 – 1.65 Max-gain illumination (−8 to −10 dB edge taper) — good for TX, hot for EME RX
  • 1.65 – 1.85 EME-optimal low-noise(−12 to −15 dB edge taper, lowest T_sys)
  • 1.85 – 2.00 Soft taper — low sidelobes, slightly under-illuminated
  • > 2.00 Severe under-illumination — wasted aperture, broad beam



Do two scans of the same dish, both azimuth and elevation drift

If your rotator system supports it, running both an azimuth-drift and an elevation-drift scan on the same dish on the same day gives you two independent measurements of the antenna pattern in perpendicular planes. The two HPBW values should agree to within ~1% for a well-built prime-focus dish, since the main lobe is normally close to circularly symmetric. Disagreements larger than that point to feed-pattern asymmetry (common with septum polarizers), feed defocus, or surface irregularities. Differences in the sidelobe structure between the two planes can directly reveal which way the feed's E-plane and H-plane axes are oriented relative to the antenna's mechanical axes.

Remember a square feed (Septum feeds) can have artifacts in 45° planes also, you will not necessarily see these form a Az/El drift scan of the system.

(Note: An offset dish will have its sidelobes in 45° planes, so to see these you would need to do a 45° scan of the sun!)


Notes and best practice

  • The cos(El) correction is essential: at high elevations, a degree of azimuth on the rotor covers less than a degree on the sky. At 54° elevation, cos(54°) ≈ 0.59, so a measured rotor-azimuth span of 9.6° corresponds to a true sky-plane HPBW of only 5.6°. SimpleCalc applies this correction per-sample so long scans where the elevation varies between flanks are handled correctly.
  • Get both flanks well below −3 dBbefore triggering the measurement — ideally 5–6 dB below peak — so the crossings are unambiguous. A warning is shown if a flank cannot reach the threshold.
  • For −10 dB measurement, peak sun noise needs to be ≥12 dB above cold sky. Below that, the −10 dB threshold sits within a few dB of the cold-sky baseline and noise variations dominate the result.
  • Cold-sky stability matters more than absolute accuracy. A small offset in the cold-sky reference shifts both the Y-factor and the (S+N)/N-corrected threshold together, mostly cancelling out. Drift during the scan is a bigger problem than a 1–2 dB offset.
  • For sun transits through south (azimuth ~180° at northern-hemisphere mid-latitudes), the elevation barely changes during the transit, so parking the dish entirely is a perfectly acceptable alternative if the rotor controller does not support disabling azimuth tracking while elevation continues to track. Otherwise the elevation axis can be nudged manually during the transit.
  • Pick the right mode for your scan geometry. Running the elevation-drift algorithm on an azimuth-drift scan (or vice versa) will produce a sensible-looking but incorrect number, since the angular axes will be confused. The peak-marker tag ([Az drift]or [El drift]) is your reminder of which mode you used.


Two example scans


Below are two complementary scans of the same 4.8 m dishat 1296 MHz, performed on the same day.


Azimuth drift (azimuth parked, elevation tracking). Azimuth tracking was disabled and the dish parked 40° east of the sun's current azimuth. With elevation still tracking, the sun drifted west through the beam, and the scan was stopped when it had passed 40° west of the dish. Only the central ±10° around the peak is needed to locate the −3 dB and −10 dB points, but the wider ±40° sweep also captured the sidelobe and far-field structure outside the main lobe — features that a narrower scan would have missed.


Elevation drift (elevation parked, azimuth tracking). The complementary case: elevation tracking was disabled and the dish parked 13° below the sun's current elevation, with azimuth still tracking. The sun descended through the beam from above to below, and the scan was stopped once it sat ~13° below the dish.


The two independent measurements agree very closely: HPBW to 0.02°, BW10 to 0.06°, and BW10/HPBW to 0.03 between the azimuth-plane and elevation-plane scans. The dish's main lobe is therefore circularly symmetric to better than 1%.


Azimuth drift.Below are three pictures where you can see the shadow of the feedhorn from when the scan started, peak reached and when the scan ended:

Below is a screenshot of the result window that is displayed once the "Find HPBW, (antenna Az parked, antenna El tracks. Sun passes in Az)"  feature is used:

Elevation drift

Below is another example, this time for an elevation drift scan. For this test, I disabled tracking on the elevation axis so only the azimuth axis tracked the sun. The dish was parked at the suns current elevation minus 13°, azimuth was still being tracked. The sun passed by the antenna (from "above to "below"), and measurement was stopped when the sun was approximately 13° below the antenna in elevation.

The three pictures below shows when sun was aligned with the dish, when it was a bit lower in elevation and when the scan was finished (13° below the dish elevation).


If you look carefully on the drift scans of the azimuth and the elevation, you can see the two small secondary "bumps" just besides the sidelobe "bumps" are not present in the elevation drift scan, but only on the azimuth drift scan above. This is probably due to the fact that the septum transformer in the feedhorn is placed horizontal in the feedhorn, this was done to have the RX and TX connectors at the "top" and "bottom" of the feedhorn in normal operation. The "extra" bumps are probably due to to this. 


Below is a screenshot of the result window that is displayed once the "Find HPBW, (antenna El parked, antenna Az tracks. Sun passes in El)" feature is used:

Yet another azimuth drift measurement of my 4.8m dish on 23cm. Also included the SimpleCalc windows from the test, the gain calculated by the HPBW measurement are used in SimpleCalc, the noise measured from the termination resistor is used to "reverse calculate" the Tant, this is then used as basis for the Sun noise prediction. All numbers matches up with this very nicely.

When I do tests like these, I park my dish minimum 10 degrees "ahead" of the suns current azimuth, disables azimuth or elevation tracking in my URC rotor controller (so rotor controller only tracks elevation or azimuth) and then enable sun tracking. This makes sure the antennas elevation or azimuth follows the sun while the sun passes by the stationary (in azimuth or elevation) antenna. For some of the drift scans above, I let the sun drift +/- 40° to get all possible sidelobes etc to show up (if any).


HPBW measurement on 1.5m "Cooker dish" on 23cm

Below is a drift scan in the elevation plane on 23cm of the popular "Cooker dish". This is a very affordable 1.5m solid dish, originally sold as a "cooker dish" for heating food using concentrated solar power. By removing the reflective material from the dish, it works perfect as a parabolic dish for 23cm and all the way to 10 GHz.

The results below are from an older test that Dave KG0D have done during his many tests and experiments with SimpleCalc.


The resulting PDF HPBW report from the above drift scan:

Comment window

SimpleCalc has a built-in "documentation window". The "Comment" window allows you to keep a log of what you measure, the conditions when you did the measurement etc. Basically you can enter whatever text you want. The contents of the comment window will be saved along the entered data on the main window and SFU window if you do a "save config" from the menu on the main window.


The comment window lets your enter text, change font, add colors, add screendumps etc., pretty much like "Wordpad" or other (simple) text editors. You can also import and export the contents (including any graphics, copied cells from Excel etc) using the "Import from file" and "Export to file" buttons.


Theory behind calculations

SimpleCalc uses a number of generally used formulas and constants. I have tried to make the calculations as correct as possible (when I started SimpleCalc, I had no idea of how pretty much any of the values were calculated!)


Below is a number of screenshots from the main window and the echo window. On each screenshot, a green thick square identifies a calculated value, the red circles/squares around other numbers shows the input to the calculation.

Receiver noise figure

First the receiver noise figure is calculated. This is basically the "cascaded gain and noise figure" of the "receive chain from the feeding element to and including the receiver.


This calculation includes the "Line 1 cable loss" which starts at the "feeder element" of the antenna. The Line 1 cable loss must include losses in a balun if such a thing exists in your antenna and everything else to the input of the first LNA, including cables, connectors and relays.

Overall noise figure

The "overall noise figure" is then calculated.

This is the calculated receiver noise figure including "ohmic losses" in the antenna and the "effective antenna temperature due to external noise" (Ta).


Ta:

"The antenna temperature, Ta, is the convolution of the antenna pattern and the brightness temperature of the sky and ground. Ta is the "pure" external noise temperature. It does not include the antenna noise temperature due to the antenna's ohmic losses."


The noise temperature due to losses in the ground and surrounding objects is related to the brightness temperature of the antenna, Ta.

The losses in the ground and surrounding objects are not related to the ohmic losses of the antenna.

 

In other words, losses in the ground and surrounding objects are not related to losses in the antenna and, in general, do not reduce the radiation efficiency of the antenna.

 

Figure of merit, M (G/T)

G/T is the "Gain to noise Temperature" of the receiving system.


More: Measuring G/T 


"Figure of merit, M

Figure of merit, M is a measure of the performance of the radio receiving system including the receiving antenna, any transmission lines to the receiver, and the receiver itself.

M = G/T, 

where

M = figure of merit, ratio

M, dB = 10*log(M)

G = antenna gain relative to isotropic radiator, ratio

T = Top = system operating noise temperature relative to 1 K, ratio"


Some more on G/T:

ITU - S.733-2 - Determination of the g/t ratio for earth stations operating in the fixed-satellite service


Expected sun noise

SimpleCalc will also calculate the expected sun noise/Y-sun level.


The amount of sun noise we are expected to measure relies on the current SFU (Solar Flux Index) for the frequency we operate on (important!) and the calculated G/T of the receiving system.


The SFU value (for the frequency we calculate on) is an interpolated value (calculated on the "SFU window" in SimpleCalc). As it is an interpolated value, it is not a "scientific truth". There can also be wild fluctuations of the SFU values, even from one hour to the next. When comparing "expected sun noise" values it is extremely important to use the correct SFU value, even a small change in SFU value (for the frequency in use) can change the calculated expected sun noise by quite a lot! On the "Get SFU data" window you can see how the band specific SFU value is inter- and/or extrapolated (extrapolated below 245 MHz and above 15400 MHz).


The calculated value is also dependent on the frequency selected. Using the "Band" group of buttons, you can quickly select one of the usual Ham radio bands, you can also enter your own specific frequency in the entry field at the bottom.


Using the "crosscheck feature" described below, it is also possible to enter the actual Y-Sun (amount of sun noise you measured) and have the program calculate what the Ta value would have to be in order for the program to "predict" that level of Y-Sun level (this requires all other parameters to be correct!).


One additional (usually tiny) correction: the formula above assumes the sun is a point source. On systems with a very narrow beam relative to the sun's apparent size — a large dish at 5.7/10 GHz and above, for example — this slightly over-predicts the expected sun noise. SimpleCalc corrects for this using the same frequency-dependent sun diameter described in the HPBW section below. For most stations (beamwidth of several degrees or more) it's well under a tenth of a dB and safe to ignore.


Crosscheck feature for sun noise

It is possible to enable a "crosscheck feature" for the sun noise on the main window:

If you enable the "crosscheck feature", a new section will be shown on the main window:

In the crosscheck section, when enabled, you can enter the actual measured Y-Sun value (in the example above, 12.80 dB). The Ta value was initially entered as 40.00 K, and that gave an expected Y-Sun value of 13.34 dB.

When you enter the true measured Y-Sun value in the crosscheck section and press the "Ta from Y-Sun" button, SimpleCalc will calculate (crosscheck) the Ta value that would result in the measured Y-Sun value. 

This requires that all other values are correct, the cascaded noise figure of the receiver, the antenna gain, the ohmic losses etc.

(The same sun-size correction mentioned above also applies here, so on narrow-beam systems the Ta value calculated by crosscheck already accounts for it.)

If you press "Yes" on the pop-up window, the screen will look like this:

You can now see that the "Overall NF/temperature", the "Figure of merit, M (G/T)" and the "Y-Sun level" have been recalculated with the new calculated Ta value. If you then disable the "crosscheck section", the window will now look like this:

The Ta value is now set to the calculated value, and the expected Y-Sun level is now the same as the one we just measured and entered in the crosscheck section.

Termination noise prediction

If you enable the "Enable terminator" checkbox, the application will show the expected noise if the LNA is terminated into 50 Ohm. The calculated value is what difference in noise you should expect between cold sky and connecting a resistor (termination) instead of the antenna (termination MUST be connected right at the connector that normally connects to the feedpoint of the antenna system. Be very careful to examine the losses before/after the connection point!


The predicted noise shown is calculated based on the current Tsys (system noise), this includes the noise figure of the receive chain (from the input of the "Line 1" coax cable to the receiver, both included) together with the Ta value entered. The predicted value is basically the difference in noise you should see between cold sky (which takes the Ta into account) and terminating the LNA input.


Using the "crosscheck feature" for the termination noise described below, it is also possible to enter the actual Y-Term (amount of noise you measured with the LNA input terminated in 50 Ohm) and have the program calculate what the Ta value would have to be in order for the program to "predict" that level of Y-Term level (this requires all other parameters to be correct!).


Remember to use the correct Tres value (termination resistor temperature), often the termination resistor mounts directly on a SMA relay which is energized in RX mode, and because of that, the relay will get pretty hot. This heat will then transfer to the termination resistor. One more thing to take into consideration if you are chasing "that last 0.1 dB"!


On my 4.8m 23cm EME dish, I have the ability in my LNA box to switch the input of the LNA between the RX port of the feed and a 50 ohm termination resistor:

Video explaining the "termination resistor noise" feature.

Crosscheck feature for termination noise

It is possible to enable a "crosscheck feature" for the termination noise the same way as for the expected sun noise:

In the crosscheck section, when enabled, you can enter the actual measured Y-Term value (in the example above, 6.20 dB). The Ta value was initially entered as 25.00 K, and that gave an expected Y-Term value of 7.72 dB.

When you enter the true measured Y-Term value in the crosscheck section and press the "Ta from Y-Term" button, SimpleCalc will calculate (crosscheck) the Ta value that would result in the measured Y-Term value. 

This requires that all other values are correct for the cascaded noise figure of the receiver.

If you press "Yes" on the pop-up window, the screen will look like this:

The Ta value have now been changed to the new calculated value (47.55K), the expected noise level for a termination resistor is now shown to be exactly the value you just entered:

Two station performance and echoes

The "Two station performance and echoes" window calculates the expected SNR of your stations own echoes and what SNR you will hear another station with (and vice versa).


The strength of your own (and another stations) echoes depends on the antennas, the power, the frequency, the system sensitivity, the bandwidth of the receiver and the current degradation ("extra" galactic noise and distance to the moon).


If degradation is set to 0.00 dB the calculations assumes the moon is at a distance of 384000 km (which is the

average distance between the moon and the earth).

The current degradation value can be seen in WSJT (Astronomical data) and other applications. Currently SimpleCalc does not calculate the current degradation by itself but relies on valid numbers from other programs.

System sensitivity

First the "system sensitivity" (receiver noise floor) of both the Home and DX stations are calculated.


This uses the calculated "Overall NF" and the selected bandwidth as input.

Calculation of own echoes strength

Own echoes is the SNR that each station (Home and DX) can (under optimum conditions!) hear their own echoes.

In this calculation, the "Antenna ohmic losses" are subtracted from the transmission power then the antenna gain is added. This gives the radiated power from each station.

The degradation value is subtracted from the received SNR value.


This calculation does NOT take any polarisation offsets into account (or Faraday rotation), it assumes perfect alignment and polarisation.

Calculation of other stations strength

The "other" stations echo strength is done in principle like calculating ones own echo strength.

The difference is that the TX power is taken from the other stations definitions, and where the combined antenna gain in the "own echo" calculation is two times your own antenna gain, it is now the gain of your own antenna plus the gain of the other stations antenna.


Cascaded noise figure and overall system NF

Often the question about "How much gain is needed" is brought up. There is a lot of opinions out there, but the math behind this is pretty simple and easy. There are other factors than only the gain/NF that comes into play (you don't want to overdrive your receive chain etc.) but the math behind cascaded noise figure is already built into SimpleCalc. Below you will see some hard facts about system noise figure, the effect different first-stage LNA gains have on the overall noise figure.

The example is directly taken with a ICOM IC-9700 radio, this has a noise figure of 4 dB with the internal preamp on, and 15 dB with the internal preamp off, this is for 70cm.

I also assume the coax loss between the mast mounted LNA and radio is 3 dB.


Please also have a look at my PDF file linked below, I made this during tuning of my 70cm EME system.

Measurements OZ9AAR 70cm EME system.pdf

Data for system noise figure with internal preamp in IC-9700 ON (for 70cm).

Data for system noise figure with internal preamp in IC-9700 OFF (for 70cm).

Download

The program is free, but if you like the program and want to support further developments from me, you are more than welcome to make a donation via Paypal to me :) Email address is on my Contact/CV page.

SimpleCalc runs under Windows operating system. There are no installation to be done. The program consists of a single .exe file, simply download this, copy it to a folder and execute it from there.


SimpleCalc will create a configuration file (with the name "SimpleCalc.cfg") in the folder it is located in, this file contains all settings from the program. If you supply the application with a filename when you start it, it will use this file as configuration file. This enables you to start the program with different setups, depending on what you want to achieve.


Please note, you might get "false positive" virus alerts from Microsoft Defender. This is quite normal, and nothing to worry about.


If you notice "funny things" with saving settings, storing data, please make sure that the program has write access to the folder where you try and write to (for settings problems, the folder where the application is located). Alternatively you might try and start the application in "Administrator mode".



2026-09-11 SimpleCalc - Version 1.0.0.20


Datafile that can be loaded and experimented with in the "Noise measure window", NDAT file


For the Station files below, right click and "Save to" and save them in a folder. Use "Load file to Home station" and "Load file to DX Station" to load the settings into "Two station performance and echoes" window in SimpleCalc. 


Station (.STA) file for NC1I: NC1I 70 cm system

Station (.STA) file for OZ9AAR 70cm system: STA file for OZ9AAR 70cm system

Station (.STA) file for OZ9AAR 23cm system: STA file for OZ9AAR 23cm system


Previous versions:

2026-07-09 SimpleCalc - Version 1.0.0.19

2026-06-23 SimpleCalc - Version 1.0.0.18

2026-06-22 SimpleCalc - Version 1.0.0.17

2026-05-18 SimpleCalc - Version 1.0.0.16

2026-04-26 SimpleCalc - Version 1.0.0.15

2026-04-16 SimpleCalc - Version 1.0.0.14

2026-04-06 SimpleCalc - Version 1.0.0.13

2025-10-28 SimpleCalc - Version 1.0.0.12

2025-09-02 SimpleCalc - Version 1.0.0.11

2025-08-19 SimpleCalc - Version 1.0.0.10

2024-09-27 SimpleCalc - Version 1.0.0.0 




Release notes

2026-09-11 1.0.0.20

  • On "Measure noise" window you can set the "Cold sky" reading to a manually selected point or, SimpleCalc can also find this automatically for you. This new function finds the average over linear power (not dB), avoids selecting minima of noisy data which will be biased (too) low. If the window is zoomed, the cold sky is found within the zoomed area only.
  • Added "URC serial number" to settings window. If you use the URC Rotor controller to control your antenna  then the "Measure Noise" window will collect the true antenna position and add that to markers etc (and in HPBW calculations) as well as any saved data (.NDAT files). On the URC, enable "UDP Broadcast" in "Setup" and set the "UDP BC port" to 30201.
  • New HPBW option: fixed-dish drift scan support
  • The HPBW measurement now offers a third scan geometry: fixed dish, where both antenna axes are parked and the Sun's own motion carries it through the beam. This is the classic drift-scan procedure and is now the first entry in the Find HPBW menu.
    • Previously only two geometries were available — azimuth drift(Az parked, El tracking) and elevation drift(El parked, Az tracking).Both assume that one axis follows the Sun, so the Sun crosses the beam along a single axis.A parked dish behaves differently: the Sun moves in azimuth and elevation at the same time, crossing the beam diagonally.Measuring only the azimuth component of that diagonal path understates the true angular width.
      The size of the error depends on how far the scan is from the Sun's transit. It vanishes at transit, but reaches roughly −15% two to four hours either side, which translates into an over-optimistic gain figure. Anyone who parked both axes and chose the azimuth-drift option was affected, with nothing in the results to indicate it.
      How offsets are now calculated
      Where the URC Rotor controller is connected, the recorded antenna position is used directly, and the offset from boresight is the true angular(great - circle) separation between the Sun and where the dish was actually pointing at each sample.This needs no assumption about the scan geometry at all, and it absorbs real rotor pointing error rather than ignoring it.
      Without a URC Rotor controller, the Sun's ephemeris is used instead. For a fixed-dish scan this gives the same answer, because the parked boresight is simply the Sun's position at the peak.The two tracking geometries continue to use their original formulas, which remain correct when an axis genuinely tracks.
      Automatic cross - check
      When antenna telemetry (using a URC Rotor controller) is present, the recorded dish movement is compared against the scan type selected in the menu.If they disagree — for example a fully parked scan analysed as azimuth drift — a warning appears showing both, with the option to use the detected geometry instead.
      Reporting
      The result window and PDF report now state the actual scan geometry, and record whether the beam offsets came from antenna telemetry or from the Sun's ephemeris. This makes an archived report self-documenting: a future reader can tell how the measurement was derived rather than having to assume.
  • Actual Sun distance is taken into account in the G/T prediction on the main page of SimpleCalc (and for the HPBW calculations).
    • Seasonal spread of Sun noise on 24 GHz from midwinter to midsummer can vary:
      Dish size: Seasonal spread:
      0.6 m        0.014 dB
      0.9 m        0.031 dB
      1.2 m        0.054 dB
      1.8 m        0.110 dB
      2.4 m        0.172 dB


2026-07-09 1.0.0.19

  • Added BW10 (-10 dB points) to the HPBW function as well as BW10/HPBW factor (shows general illumination status)
  • HPBW/BW10 corrects for the Sun's diameter at the frequency selected (as long as the beamwidth are >> Sun's diameter (approx 0.5°).
  • Expected sun noise (and the Ta crosscheck) now also corrects for the sun's finite angular size on narrow-beam systems, using the same frequency-dependent sun diameter as the HPBW function.
  • HPBW function calculates gain (both theoretical and at 65% efficiency)
  • HPBW can measure for both azimuth and elevation drift scans (for azimuth scans corrects for cos(el), for elevation drift scans no correction needed).
  • Better zoom functionality using the mouse wheel on the noise window (data under the mouse stays in place)
  • The "Delta = 0" button is now "Set cold". Added a dedicated blue line that shows the "cold sky" value set with that button (cold sky value is also saved with the data if "file save" is used)
  • Better handling of "minimize" button in Noise Window.
  • General optimization in the noise window (speed/memory)
  • When loading a file in Noise window, the vertical scrollbar will place the view so the cold sky measurement is at the bottom of the view
  • When doing HPBW measurement, an optional report PDF file can be created
  • In noise measure window: Added "user comment marker" function, user can enter a multiline text and place that as a marker


2026-06-23 1.0.0.18

  • (Sill experimental) Changed the HPBW function so it can correct for (S+N)/N for system where sun noise is lower than 13 dB. (Thanks Peter G3LTF)


2026-06-22 1.0.0.17

  • In Noise Measure window, new function added, find "HPBW". This will find peaks and search for -3dB points from there and try to calculate the HPBW based on that.


2026-05-18 1.0.0.16

  • Band at 3456 MHz changed to 3400 MHz (Thanks Andreas, DJ3JJ)
  • In noise window, limited the number of labels on X axis (would get crowded on large span measurements) (Thanks Dave KG0D)
  • Error in "Fetch current distance" for moon in Echo window (minimum distance allowed for moon was exceeded) (Thanks Robert DC1RDB)


2026-04-26 1.0.0.15

  • Fixed error, at very high Ta values (when Y-Term goes negative), enabling crosscheck will cause an error in the program (Thanks Michael W9IP)

  • Improved calculation of sun position. Before used the "Astronomy" library, now changed to my own calculation code (from 1993).


2026-04-16 1.0.0.14

  • Updated marker functionality in noise window.
  • Noise window, hovering the mouse over the trace shows level and sun/moon position for the timestamp for the specific datapoint
  • Possible to save and load the data shown in Noise window (markers are also saved/loaded)


2026-04-06 1.0.0.13

  • Added the ability to calculate expected noise if LNA is terminated on its input with 50 ohm resistor. Also included "crosscheck" feature for this (see here).
  • Added "Delta marker" on noise window. This creates a marker that shows the offset to the last placed marker/delta marker.
  • Markers on noise window does now contain sun and moon position for the timestamp of the marker


2025-10-28 1.0.0.12

  • Added "Export to file" and "Import from file" on comment window. Exports and imports comments (including graphics, colors etc.) to/from a RTF file (can be opened and edited in Wordpad, Microsoft Word etc.)


2025-09-02 1.0.0.11

  • Added better handling when NOAA has missing SFU data (-1 in all SFU values for all stations) (Thanks Bryn GW4ZHI)


2025-08-19 1.0.0.10

  • Added possibility to start directly in "measure noise" window on program startup, IF the noise window was visible when program was last shut down. A new setting enables this feature (Thanks Jonathan G4KLX)


2025-05-25 - Version 1.0.0.9

  • Added more resilience to SFU data (Thanks Dean VK3NFI and Ralph VK3WRE)


2024-12-23 - Version 1.0.0.8

  • Added noise temperature (at 290K) for all NF values on main window
  • Added current sun position on main window (based on the configured observer position in Settings)


2024-11-26 - Version 1.0.0.7

  • Minor changes in texts/functionality for crosscheck function (Thanks UR5EAZ)
  • Fixed bug in "two station" window, EIRP for DX station was not calculated.
  • In "two station" window you can change the moon distance. Both Home and DX uses the same pathloss/distance
  • New menu item, "Settings", for now only observer location (needed for calculating the moon distance on "two station" window)
  • Moon distance can be set in "two station" window, used in calculationg pathloss (distance to home location)


2024-11-14 - Version 1.0.0.6

  • Fixed a small error in one of the used constants in the program (Thanks UR5EAZ)
  • Added (calculated) noise temperatures for the losses in the 3 lines and for antenna ohmic losses, both main window and two station window (Thanks UR5EAZ)
  • Updated various tooltip texts in the program
  • Added temperature display for all losses
  • The "power at the feed" on "two station" window is shown in dBW and EIRP also


2024-11-06 - Version 1.0.0.5

  • On Noise measure window, you can select between Left and Right channel from soundcard
  • Crosscheck was miscalculating a little under certain conditions (Thanks UR5EAZ)

 

2024-11-05 - Version 1.0.0.4

  • Error in SFU window if NOAA FTP server was not reachable. Now fixed (Thanks Jos PA0JOZ)

  • Changed suffix names of settings files on main window if using "Actions -> Save settings to file" menu item

  • Added and corrected tooltip texts for all controls on all windows

  • Added "Crosscheck" feature on main window (please see website for explanation: Crosscheck)

  • Added "Two station echoes" menu item/feature

  • Changed menu items and their functionality (hide/show) 


2024-10-02 - Version 1.0.0.3

  • Small bug fixes.
  • Added Noise window


2024-10-02 - Version 1.0.0.2

  • Small bug fixes.
  • Downloaded SFU data will now be placed in the root of the "Documents" folder (if you want to save them for some reason).
  • Easier to resize images if pasted into the "Comments" window.

2024-10-02 - Version 1.0.0.1

  • The antenna gain was limited to only 40 dBi by mistake. Changed to 60 dBi. (Thanks Roger W3SZ)
  • Added a "user defined frequency" entry field on the main page. User can enter a frequency in MHz and have the program calculate (interpolate) a SFU value for that (thanks Bob K6ZZ)


2024-09-27 - Version 1.0.0.0 

  • This is the initial release