CETUS-RF · Operational Manual
GRID PATH
Mobile Edition
Complete operational reference for the Grid Path Mobile web application — path calculator, terrain profiler, ARRL contest QSO logger, microwave beacon map, and ADIF export.
CETUS-RF · cetus-rf.com
Document Version 1.0 · 2026
ARRL 10 GHz & Up Contest Rules Compliant

Table of Contents

1 Overview 3
1.1  Purpose & Key Features 3
1.2  Getting Started 3
2 Interface Layout 3
3 Path Calculator 4
3.1  Point A — My Location 4
3.2  Point B — Remote Station 4
3.3  Antenna Heights 4
3.4  Band Selection 5
3.5  Earth Model & Units 5
4 Path Results 5
4.1  Compass Rose 5
4.2  Path Statistics 6
5 Terrain Profile 6
6 QSO Log 7
6.1  Logging a QSO 7
6.2  ARRL Contest Scoring Rules 8
6.3  Dupe Detection 8
6.4  Log Display & Full Log View 9
6.5  Contest Score Bar 9
7 Microwave Beacon Map 10
8 ADIF Export 11
9 Data Storage & Privacy 11
10 Display Settings 12
11 Quick Reference 12

1   Overview

1.1   Purpose & Key Features

Grid Path Mobile is a browser-based tool designed for microwave rover operators to quickly compute great-circle headings, evaluate terrain line-of-sight, and log QSOs in the field during the ARRL 10 GHz & Up Contest — all from a smartphone, with no app installation required.

Path & Terrain

  • Great-circle heading A → B and reverse B → A
  • Distance in km or miles
  • Animated compass rose with kite-needle
  • Terrain elevation profile (Open-Meteo API)
  • First Fresnel zone visualization
  • LOS obstruction detection with verdict
  • Earth-curvature correction (k = 4/3 or k = 1)

Contest Operations

  • Inline QSO logger with ARRL scoring
  • All 8 contest bands (10 GHz – >241 GHz)
  • Automatic dupe detection per band
  • Real-time total score display
  • ADIF export for submission
  • Microwave beacon map with headings
  • GPS location support

1.2   Getting Started

  1. Open grid-path-mobile.html in any modern smartphone or desktop browser.
  2. Enter your current grid square (or tap ⌖ GPS) into Point A.
  3. Enter the remote station's grid square into Point B.
  4. Tap CALCULATE PATH to compute heading and terrain.
  5. Log each QSO using the QSO Log section below the results.
Note The terrain profile requires an active internet connection to fetch elevation data. All other features (heading, compass, QSO logging, scoring) work fully offline.

2   Interface Layout

The page is organized top-to-bottom in a single scrolling column optimized for portrait smartphone use:

SectionLocationDescription
Header barTop, stickyApp title, font-size buttons (A− / A+), theme toggle (☀/☾)
Endpoints card§3Point A, Point B, antenna heights, band, earth model, units
Terrain spinnerBelow inputsVisible while fetching elevation data
Path Results§4Compass rose, heading values, path statistics (hidden until first calculation)
Terrain Profile§5Elevation cross-section with LOS and Fresnel zone (hidden until calculation)
QSO Log card§6Contest score bar, callsign entry, band/mode, LOG button, QSO list

3   Path Calculator

3.1   Point A — My Location

Point A represents your transmit location. It is used for heading calculations, terrain profiling, and as the source grid for logged QSOs. Enter one of the following formats:

FormatExampleNotes
2-char gridDMField-level, center of 20° × 10° square
4-char gridDM43Square-level, center of 2° × 1° square
6-char gridDM43CGSubsquare — standard for contest exchange
8-char gridDM43CG44Extended precision
Lat, Lon33.27,-111.79Decimal degrees, comma-separated
GPS Tip Tap ⌖ GPS to automatically fill Point A with your current location as a 10-character Maidenhead grid (highest available precision). Requires browser location permission. On iPhone, use Safari for best GPS accuracy.

3.2   Point B — Remote Station

Point B is the remote station or target location. Accepts the same formats as Point A. For contest use, enter the 6-character grid square received in the exchange. You can also tap any row in the beacon map to auto-fill Point B with a beacon's grid.

Rover Note As a rover you will update Point A for each new grid square you operate from. Point B remains your intended contact until you need a different heading. The QSO log captures the Point A grid at the moment of logging, so changing Point A later does not affect previously logged QSOs.

3.3   Antenna Heights

Ant A and Ant B set the effective antenna height above ground at each end of the path. These values affect only the terrain profile and Fresnel zone calculation — they have no effect on heading or QSO scoring.

SettingTypical Use
1.0 mDish or horn on a car roof rack (default)
1.5 mElevated tripod or portable mast
2.0 – 3.0 mFixed tower or elevated installation

3.4   Band Selection

The Band selector determines which frequency is used for Fresnel zone calculation in the terrain profile and which contest multiplier is applied to QSO scores. All eight ARRL 10 GHz & Up contest bands are available:

SelectionFrequency (MHz)WavelengthScore Multiplier
10 GHz ×110,368.13 cm×1
24 GHz ×224,048.11.2 cm×2
47 GHz ×447,088.16 mm×4
76 GHz ×876,0324 mm×8
119 GHz ×16119,0002.5 mm×16
142 GHz ×32142,0002.1 mm×32
241 GHz ×64241,0001.2 mm×64
>241 GHz ×128300,000<1 mm×128
Important The selected band is used for both terrain analysis and QSO scoring. Make sure to select the correct band before tapping LOG — changing the band after logging does not retroactively update existing entries.

3.5   Earth Model & Units

Earth Model

  • RADIO k=4/3 (default) — Standard radio propagation model. Applies an effective Earth radius of 4/3 × 6371 km, accounting for typical atmospheric refraction. Recommended for all practical path analysis.
  • TRUE k=1 — Geometric Earth radius, no refraction correction. Use for academic comparison only.

Units

  • KM / M (default) — Distance in kilometres, elevation in metres.
  • MI / FT — Distance in miles, elevation in feet. Switching units instantly redraws all results without recalculating.

4   Path Results

After tapping CALCULATE PATH, results appear automatically below the calculator card. Scroll down to view them.

4.1   Compass Rose

The compass rose displays the great-circle bearing between Point A and Point B using a classic kite-needle design:

  • Green half — forward bearing (A → B). The tip points in the direction you need to aim.
  • Red half — reverse bearing (B → A, the tail). This is the heading the remote station aims toward you.
  • N is highlighted in cyan at the top of the rose.
  • Degree labels appear at every 30°.
  • Minor tick marks at every 10°.
Field Tip The large green number above the compass is the forward bearing in degrees, with compass direction (e.g., 247.3° WSW). The red number below is the reverse bearing — read it out to the remote station so they can aim back at you.
N E S W 247° ⇄ 67° REV
Example: A→B = 247° WSW / B→A = 67° ENE

4.2   Path Statistics

Below the compass, a statistics grid shows:

StatisticDescription
DISTANCEGreat-circle distance between Point A and Point B
AZIMUTH A→BForward bearing in degrees with compass direction abbreviation
REVERSE B→ABearing back from Point B to Point A
MIDPOINT6-character grid square at the geographic midpoint of the path
GRID AResolved grid and decimal lat/lon for Point A
GRID BResolved grid and decimal lat/lon for Point B
ELEV MINMinimum terrain elevation along the path (requires elevation data)
ELEV MAXMaximum terrain elevation along the path (requires elevation data)

5   Terrain Profile

The terrain profile is a cross-sectional elevation chart drawn along the great-circle path from A to B. Elevation data is fetched in real time from the Open-Meteo Elevation API using up to 200 sample points spaced along the path.

5.1   Chart Elements

ElementColorMeaning
Terrain fillBlue-grey gradientEarth surface elevation corrected for atmospheric curvature using the selected k-factor
LOS lineGreenStraight line-of-sight between the two antenna tips (A and B at their specified heights)
Fresnel zoneCyan dashed bandFirst Fresnel zone (F1) radius around the LOS line at the selected frequency. Microwave links perform best when this zone is 60% clear.
ObstructionRed highlightAny terrain segment rising above the LOS line — link is blocked here
Antenna markersCyan dotsA and B antenna positions with mast height above terrain

5.2   Path Verdict

Below the profile chart, a single-line verdict summarises the path quality:

VerdictMeaning
✓ PATH CLEAR LOS is unobstructed and at least 60% of the F1 Fresnel zone is clear. Link should be solid.
△ LOS CLEAR, F1 INTRUDED Direct LOS is clear but terrain intrudes into the Fresnel zone. Expect some diffraction loss but the link should still work.
✕ PATH OBSTRUCTED Terrain is above the LOS line. The link is blocked at the reported distance from A. A higher vantage point or different route is needed.

The verdict also reports the worst-case clearance margin and location, frequency used, and k-factor applied.

5.3   Offline Behaviour

If the elevation API is unreachable (offline, poor signal), the terrain profile is skipped and a ⚠ ELEVATION UNAVAILABLE message is shown in its place. Heading calculation and QSO logging are not affected — they work completely offline.

Redraw without Refetch Changing Antenna Height, Band, Earth Model, or Units after a calculation instantly redraws the profile using cached elevation data — no new API call is needed.

6   QSO Log

The built-in QSO log is designed for field use during the ARRL 10 GHz & Up Contest. It stores all contacts locally on the device, computes ARRL contest scores automatically, detects duplicates, and exports to ADIF for submission.

6.1   Logging a QSO

Step-by-step procedure

  1. Set Point A to your current grid square. The My Grid display box auto-fills from Point A.
  2. Set Point B to the worked station's grid square (received in the exchange).
  3. Select the correct Band (including multiplier) for this QSO.
  4. Enter My Call (your callsign; use K6VHF/R format for rover operation). Saved automatically after first entry.
  5. Enter the Worked Station callsign in the QSO entry field.
  6. Select the Mode (CW, SSB, FT8, or Q65).
  7. Tap LOG. The QSO is scored and added instantly to the top of the list.
Before Logging Both Point A and Point B must contain valid grid squares before tapping LOG. If either is empty or invalid, an error message will appear and the QSO will not be saved.

Fields stored for each QSO

FieldDescription
Date / TimeUTC date and time at moment of logging (auto-captured)
My CallYour callsign as entered in the My Call field
Worked CallThe remote station's callsign
My Grid6-character grid from Point A at time of logging
Their Grid6-character grid from Point B at time of logging
DistanceComputed haversine distance between the two 6-char grid centers (km)
BandSelected band label (e.g., 10G, 24G, 47G…)
MultiplierARRL band multiplier (1, 2, 4, 8… 128)
ScorePoints awarded: distance × multiplier (0 for dupes)
Dupe flagTrue if same callsign + same band was already logged
ModeCW / SSB / FT8 / Q65

6.2   ARRL Contest Scoring Rules

Scoring follows the official ARRL 10 GHz & Up Contest rules:

Scoring Formula Score = Round( Distance_km × Band_Multiplier )
Duplicate contacts on the same band score zero points.
BandMultiplierExample: 250 km QSO
10 GHz×1250 pts
24 GHz×2500 pts
47 GHz×41,000 pts
76 GHz×82,000 pts
119 GHz×164,000 pts
142 GHz×328,000 pts
241 GHz×6416,000 pts
>241 GHz×12832,000 pts

The same contact on multiple bands counts as a separate valid QSO on each band, provided the exchange is genuinely made on that band. Only true dupes (same call, same band, logged more than once) are zeroed.

6.3   Dupe Detection

Every time you tap LOG, the app checks whether the same callsign has already been logged on the same band in the current session. If it has:

Tip Working the same station on a different band is not a dupe — each band is tracked independently. K6VHF on 10G and K6VHF on 24G are two separate scored contacts.

6.4   Log Display & Full Log View

The compact log list shows the most recent QSOs directly below the entry form. Each row contains:

ElementDescription
Date / TimeUTC in MM/DD HH:MMz format
CallsignWorked station's callsign in cyan
Grid pathMyGrid → TheirGrid (6-char)
ScorePoints in large bold green (1,234) or DUPE in red
Band × MultBand label with multiplier (e.g., 10G ×1, 24G ×2)
Delete button✕ — removes the QSO from the log immediately

The log header shows a running summary: N QSOs · TOTAL PTS · ND dupes

Full Log View

Tap ⛶ FULL LOG to open a full-screen overlay showing all QSOs with expanded details. On Android, the device Back button closes this view. On iOS, use the ← BACK button. From within the full log view you can also access Map and ADIF Export.

Deleting a QSO

Tap the button at the right of any log row to permanently delete that entry. Deletion is immediate — there is no undo. If you accidentally delete a QSO, you must re-enter it manually.

Clearing All QSOs

Tap ✕ CLEAR LOG at the bottom of the log card (or in the full log footer). A confirmation dialog appears stating the number of QSOs to be deleted. This action is irreversible — export ADIF first if you need to preserve the data.

Warning Clearing the log or deleting the browser site data removes all QSOs permanently. Export ADIF before clearing, especially at the end of a contest.

6.5   Contest Score Bar

At the top of the QSO Log card, a Contest Score Bar displays a real-time summary of your overall performance. It reads from the shared contest log key and updates automatically when you switch back to this browser tab or when the log is updated in another tab.

CellShows
Total ScoreSum of all valid (non-dupe) QSO scores
QSOs / DupesValid QSO count, with dupe count in red if any
Active BandsNumber of different bands with at least one valid QSO
Best ODXLongest single QSO distance in km
Open Contest LogLink to the dedicated 10ghz-log.html contest logger
Note — Two Separate Logs Grid Path Mobile keeps its own local log (gp_qsolog) for path-calculation purposes. The Contest Score Bar reads from the shared contest log key (crf_10ghz_log_v1) written by the dedicated 10ghz-log.html page. If you log only in Grid Path Mobile, the score bar will show "No contest QSOs" until you also use the contest logger.

7   Microwave Beacon Map

The 🗺 MAP button opens an interactive Leaflet map in a new browser tab showing all known SoCal / NorCal / AZ microwave beacons plus your logged QSO paths. The map can be opened even when the QSO log is empty — it will still show all beacons.

Popup Permission Required The map opens in a new tab. If your browser blocks popups, you will see a prompt to allow them. Allow popups for this site and tap MAP again.

7.1   Map Elements

SymbolColorMeaning
● Large circle Green My station — one marker per unique My Grid / callsign combination. Popup shows callsign, grid, QSO count, and total points from that site.
● Small circle Red Worked station — one marker per QSO. Popup shows callsign, grid, band × multiplier, mode, UTC time, distance, and score.
◇ Diamond Orange Microwave beacon — all 10 known regional beacons. Popup shows name, location, grid, frequencies, and heading/distance from Point A (or from each logged op site).
─── Line Cyan solid Valid QSO path (great-circle line A → B)
- - - Line Faint red dashed Duplicate QSO path

7.2   Beacon Popups

Tapping an orange beacon diamond opens a popup containing:

7.3   Known Beacons

NameGridLocationCallsign(s)Frequencies (MHz)
Palos VerdesDM03trSoCalWA6MEM/B10368.300
Mt FrazierDM04msSoCalN6CA/B10368.310
Heaps Pk ⚠DM14kfSoCalAF6HP/B10368.330
San DiegoDM12jvSoCalK6QPV/B10368.360
Mt. LeesonCM97aeNorCalKF6KVG10367.990 / 24191.975 / 47087.990 / 79919.920
Mt VacaCM88wjNorCalW6ASL10368.325
Mt AllisonCM97blNorCalK6MG / N6NU / KF6KVG / AD6IW10369 / 24192 / 47088 / 80832
Bear Mtn ⚠DM06irNorCalW6BY/B24191.990
StanfordCM87wjNorCalK6ML122400
White TanksDM33rnAZW7ATN10368.375

⚠ = beacon reported down at time of writing. Verify current status before operating.

7.4   Map Tile Mode

When the app is in dark mode (default), the map uses CartoDB dark tiles for readability in low-light conditions. In light mode, it switches to standard OpenStreetMap tiles. The map auto-fits all markers and beacons into view on opening.

8   ADIF Export

Tap ⬇ EXPORT ADIF (in the log card or full log view) to download your QSO log as an ADIF 3.1.4 file (.adi) for submission to the ARRL or import into logging software such as WSJT-X, N1MM+, or Log4OM.

8.1   ADIF Fields Exported

ADIF FieldContent
STATION_CALLSIGNYour callsign (My Call)
OPERATORBase callsign without /R suffix
CALLWorked station callsign
QSO_DATEUTC date (YYYYMMDD)
TIME_ONUTC time (HHMMSS)
BANDBand label (e.g., 10G)
FREQFrequency in MHz (e.g., 10368.1000)
MODECW / SSB / FT8 / Q65
GRIDSQUAREWorked station's 6-char grid
MY_GRIDSQUAREYour 6-char grid at time of QSO
DISTANCEDistance in km between grid centers
File Name The exported file is automatically named gridpath_YYYY-MM-DD.adi using the current local date. Save it immediately after export — the download link expires when the page is refreshed.

8.2   ARRL Submission

For ARRL 10 GHz & Up Contest submission, export the ADIF file after the contest period ends and upload it through the ARRL contest submission portal. Verify that your callsign, grid squares, and operating times are correct before submitting. Dupe QSOs are included in the ADIF export for completeness — the ARRL adjudication software handles dupe removal on their end.

9   Data Storage & Privacy

9.1   How Data is Stored

All QSO log data is stored exclusively in your browser's localStorage on your own device. No data is transmitted to any server. The application itself is served as a static HTML file — after the page loads, it operates completely independently of the server.

KeyContentWhere Used
gp_qsologFull QSO log array (JSON)Grid Path Mobile only
gp_mycallYour saved callsignAuto-fills My Call on next visit
gp_fontFont size index (0–3)Display preference
gp_theme"dark" or "light"Display preference

9.2   Per-Device Isolation

Each physical device and each browser app maintains a completely separate localStorage. Multiple operators using the same URL from their own smartphones will each have their own independent log. There is no synchronization, no shared database, and no way for one device to see another device's data. This is the correct behavior for rover contest operation where each operator maintains their own log.

9.3   Data Persistence

ActionEffect on Log
Close the browser tabData preserved
Restart the browserData preserved
Restart the phoneData preserved
Use Private / Incognito modeData lost when tab closes
Browser "Clear Site Data"Data permanently deleted
Uninstall the browserData permanently deleted
Best Practice Export ADIF at the end of each operating session, even if you plan to continue later. This protects against accidental browser data clearing or device failure.

10   Display Settings

Three display controls appear in the sticky header bar:

ControlFunction
A− Decrease base font size. Cycles through 4 steps: 100% → 112% → 125% → 140%
A+ Increase base font size. Useful when operating in bright sunlight or gloves.
/ Toggle between dark mode (default, blue-black theme) and light mode (white theme). Light mode is better for outdoor use in direct sunlight.

All three settings are saved to localStorage and restored automatically on next visit.

Field Tip — Sunlight Readability In direct sunlight, switch to light mode (☀ button) and increase font size to A+ or A++ for maximum screen readability. The compass and terrain profile automatically redraw in light-mode colors.

11   Quick Reference

11.1   ARRL 10 GHz & Up Band Multiplier Table

BandMultFreq (MHz)Score for 100 kmScore for 500 km
10 GHz×110,368.1100 pts500 pts
24 GHz×224,048.1200 pts1,000 pts
47 GHz×447,088.1400 pts2,000 pts
76 GHz×876,032800 pts4,000 pts
119 GHz×16119,0001,600 pts8,000 pts
142 GHz×32142,0003,200 pts16,000 pts
241 GHz×64241,0006,400 pts32,000 pts
>241 GHz×128300,00012,800 pts64,000 pts

11.2   Grid Input Formats

FormatLengthExamplePrecision (center)
Field2 charsDM~1,100 km × 550 km
Square4 charsDM43~110 km × 55 km
Subsquare (contest standard)6 charsDM43CG~4.6 km × 2.3 km
Extended subsquare8 charsDM43CG44~460 m × 230 m
GPS / decimallat,lon33.27,-111.79Limited by input precision

11.3   Common Workflow — Rover Operation

  1. Arrive at grid square → tap ⌖ GPS to set Point A.
  2. Enter remote station grid in Point B → tap CALCULATE PATH.
  3. Point antenna to the displayed green heading.
  4. Read the reverse heading to the remote station.
  5. After contact, enter their callsign, select band, tap LOG.
  6. Repeat steps 2–5 for additional contacts on different bands or to different grids.
  7. When moving to a new grid: update Point A (GPS or manual) → continue.
  8. At end of session: tap ⬇ EXPORT ADIF to save your log.

11.4   Troubleshooting

IssueCauseSolution
LOG button shows errorMissing callsign, or Point A/B not setEnsure My Call, Point A, and Point B all have valid entries
Terrain not loadingNo internet connectionHeading and log still work offline; reconnect for terrain
Map popup blockedBrowser popup blockerAllow popups for this site and tap MAP again
GPS not workingLocation permission deniedGrant location permission in browser/phone settings; use Safari on iOS
Score bar shows "No QSOs"Score bar reads 10ghz-log.html key, not Grid Path Mobile's own logUse 10ghz-log.html to log contest QSOs, or ignore the score bar
Log lost after clearCLEAR LOG was used or browser data clearedNo recovery — export ADIF regularly as backup
CETUS-RF · Grid Path Mobile · cetus-rf.com · Operational Manual v1.0 · 2026
ARRL 10 GHz & Up Contest Rules · Open-Meteo Elevation API · Leaflet.js Maps