The story of why I built Beam Navigator is over on the Projects page. This one is the tour.
Every screen in version 1.5.0, what it does, and what the user guide has to say about it. The guide quotes are in the boxes. The rest is me.
Grab a cup of coffee.
Start with your station
Everything in Beam Navigator is worked out from where you are. So that’s the first thing it asks.

Enter your callsign (optional), home grid, units (km or mi) and time zone (for net times, for example America/New_York).
The callsign is optional. The grid is not. If you know your exact latitude and longitude, there’s a spot for those too.
The time zone matters more than it looks. Since 1.5.0, a new station starts with your computer’s own time zone. Upgrading from an older version? Check Settings → Station. A station set up earlier may still say UTC, and evening nets can land on the wrong day.
Bands
Each band remembers whether you care about long path.

On bands set to long path (10 m and 6 m by default; Settings → Bands), the long-path bearing and distance are shown too.
On 2 meters and up, long path doesn’t matter for me. On 6 meters during a good opening, it might.
The dashboard: type anything
This is the screen I leave open. One big box. Type something, press Enter, and you get a bearing.
Type a target in the big Target box and press Enter. You see what it resolved to and where that came from, its grid when it has one, the true bearing (one decimal place), the 16-point compass name, and the distance in your units.
It takes almost anything. A grid square:

A plain compass point, when net control says “southwest” and that’s all you’ve got:

NE means Northeast; Nebraska is offered as a one-click alternative.
A shortcode you set up yourself:

Or a callsign. If you have a QRZ login, a call it doesn’t know yet gets looked up on the spot:

Beam Navigator never guesses a location.
That one line matters more to me than most of the features. No grid, no bearing.
The Rotate button always says exactly what’s going to happen, down to the tenth of a degree. Nothing turns until you press it.
Aliases
Shortcodes for the places you point all the time.

I set one up for every beacon I use to check my antennas. An alias can point at a grid or at a station, so when a station’s grid changes, the alias follows.
Rotators
This is the part I was most careful about. The app talks to PstRotator or PstRotatorAz on Windows, or to Hamlib’s rotctld on anything.

A new rotator always starts in simulation: Rotate moves a pretend rotor so you can try everything safely.
To go live, press Test connection. Only after it passes can you turn on the Simulation switch; it then reads Live: Rotate turns the real antenna.
There’s also an offset. If your beam points at true north when the rotor says 5°, you enter 5 and every heading gets corrected. Check yours against a beacon before you trust it.
If the rotator reports no position, Beam Navigator says “Command sent — position unverified” rather than claiming the beam got there.
QRZ lookups
Optional, and only if you have a QRZ XML Data subscription.

Your login is kept in your computer’s credential store (Windows Credential Manager, macOS Keychain or the Linux keyring), never in Beam Navigator’s files or backups.
QRZ only fills blanks: it never overwrites a grid from a roster or one you typed.
Since 1.5.0, a saved station with no name, or only a rough four-character grid, gets checked on QRZ by itself for the full details.
Everything else works without it.
Nets
The nets list is where your Monday and Friday nights live. It reads like a week: today’s nets first, favourites on top, then the rest of the week in order.
Nets lists your nets in week order from today: today’s nets first (favourites, then by start time), then the rest of the week, then nets with no schedule.
The first time you run it, Beam Navigator offers a set of example nets.
Beam Navigator offers example nets from a published Pack Rats schedule. They are marked Example — unverified until you check them.
Adding your own net takes one dialog. The controller’s grid is the important field. That’s what lets the net screen work out where net control has to point to hear you.

Open a net and you see the next session, who’s running it, past sessions and who usually checks in. A closed session shows the first line of its notes.

Start session begins tonight’s session; each session has Open (the live net screen) and Net control.
Importing the roster
After the net, the roster goes up on the reflector. Paste it in.

The review table shows each station with its bearing and distance from you. A bearing printed in the roster is shown as Published for reference only.
Anything Beam Navigator can’t read is kept as an “Unparsed text” row, never thrown away.
Rosters don’t always carry grids. Since 1.4.0, the review fills them in.

A station the roster gives no grid for is filled in from your saved records, then from QRZ (when automatic QRZ lookup is on, one call at a time), and the row says from saved record or from QRZ; such a grid goes with this session but is never saved as if the roster had said it.
That last part matters. A guess from QRZ never gets passed off as something the roster said.
And if a roster doesn’t say who ran the net, it still imports. Beam Navigator uses the net’s saved net control, and that call shows up in the Import screen’s dropdown.
Do this every week and the regulars stop being strangers.
Following a net
This is the screen I built the whole thing for. Version 1.3.0 rebuilt it around one idea, 1.4.0 made logging faster, and 1.5.0 boiled the typing down to one box.

One idea: there is one Target. Whatever you picked last is the Target, and Rotate turns the antenna to it.
The Beam panel on the left holds the Target, Rotate, Rotate to net control, the rotator and the compass. It stays put. Everything you pick from is on the right, with one entry box, I hear, at the top, so it doesn’t scroll away when the net gets busy. On a narrow window or a small screen, the Target and the Rotate button stay in view.
Clicking, typing and pressing Enter never move the antenna; only Rotate (Ctrl+Enter) and Rotate to net control (Home) do. If Rotate is greyed out, the sentence under it says why.
Net control is pointing
When the controller announces a direction (“anyone to the northeast?”), press its number-pad key (8 N, 9 NE, 6 E, 3 SE, 2 S, 1 SW, 4 W, 7 NW) or click it. When the controller just calls a station, type the call in I hear (or click the station in a list): the compass lights the way net control points to reach them and reads, say, Net control is pointing SW.

If it is your sector, a large YOUR SECTOR IS UP banner appears. It is worked out from net control’s location directly, not by adding 180°, and it never claims the controller can hear you.
This one came out of a Friday night 6-meter net. Net control calls a station, and I want to know right away whether his beam is anywhere near me. Now the compass just shows me.
When net control isn’t who you expected
The Net control line at the top is never a dead end. It says Change… when net control is known, Add grid… when only the call is known, and Set net control… when the net has none.

Use for tonight changes this session only, for when someone else is running the net. Save for this net also makes it the net’s net control, so every future session starts with it.
No roster? No problem
Version 1.5.0 folded Find and I hear into one box.

I hear: one box for everything. Type the callsign of a station you hear and pause: its details fill in from what Beam Navigator knows (then QRZ, when the saved record has no name or only a 4-character grid), with no need to step through the boxes. As soon as the call is whole it becomes the Target, so Ctrl+Enter turns the antenna to it straight from the box; Enter logs it.
Type a grid, alias or direction (FN20, 270, W) instead and Enter points at it (“Typed”) without logging anything. Typing never hides anyone in the lists below.
That last line is a fix I wanted badly. The old Find box narrowed the lists while you typed, and on a busy net people would vanish right when you were looking for them.
A new callsign clears the line, so the last station’s grid or report never sticks to the next one.
Direction shows which way they are as soon as there’s a grid. Aim to makes them the Target. Nothing turns until you press Rotate or Ctrl+Enter.
Regulars not heard yet lists everyone who has checked in to this net before, with bearing, distance, attendance and last check-in.
You can still mark each station Heard, Weak, Not heard or Via relay. Those marks are private. They never show up in an export.
Notes for next time
When the net ends, close your session and leave yourself a note.

Add Notes for next time (“K3WGR weak from 40°, try 30°”) and they appear as Last time at the top of the next session of this net, on both screens.

Closing notes are private, too. They’re never exported.
Running a net
For the net controllers, the entry line works like a contest logger.

In Callsign, the first Enter fills in Name, Grid and QTH from history (or from QRZ, marked “Filled from QRZ.”) and moves to Name; the next Enter logs the check-in.
While you type a callsign, matching stations are listed, the most regular first; the arrow keys choose one.
Try to log someone twice and it offers to update the first entry instead.
Publishing the roll call
When the net’s done, export it.

Export the roll call as Text, CSV or JSON. Bearings are labelled “from net control”; if net control’s location isn’t known, they are from your own station and say so.
Names and QTHs get tidied into proper case on the way out. The text version is ready to paste right into the reflector.
Keys
Every shortcut can be changed.

Keys that move the rotator (Rotate and Rotate to net control) need Ctrl or Alt, or a key that never types, such as F9, Home or a number-pad key.
That rule is on purpose. A stray keystroke while you’re typing someone’s name should never swing the tower.
Backup and sharing between PCs
Everything lives in one file, and one button backs it all up.

After a restore, every rotator is in simulation. Run Test connection and switch Live back on.
Same idea as before. A fresh restore never turns the antenna until you’ve tested it.
One set of data for the whole shack
New in 1.5.0. I’ve got two computers upstairs in the shack, and I want the same nets, stations and logs on both. Now that’s one setting.
In Settings → Data → Data folder, type a folder every PC can reach, for example \\SHACK\BeamNavigator, and press Use this folder. If the folder is empty your data is copied there; if it already has Beam Navigator data (from your other PC), that data is used as it is and nothing is overwritten.
Only one PC can have the data open at a time: two at once could damage it. While one PC has it, the other shows Beam Navigator’s data is in use, naming that PC and when it opened it.

If the other PC was left running or crashed, press Take over.
If the shared folder can’t be reached when Beam Navigator starts, it says so and stops rather than quietly using another folder.
That’s the same rule as everywhere else in the app. It tells you what’s wrong instead of guessing.
About
Settings has an About tab now.

Settings → About shows the version, the copyright, the licence, and links to the screen-by-screen walkthrough and the story behind Beam Navigator.
Installing on Windows
Version 1.2.0 brought a real installer, BeamNavigatorSetup.exe. No Python needed, and no administrator password.

Because the installer is not signed, Windows may say Windows protected your PC. Choose More info, then Run anyway.
Beam Navigator runs quietly in the background and shows itself in your browser; there is no other window. To stop it, press Quit at the top right of any page.
To update, run the new installer. Your stations, nets and history stay put. Rather not install anything? BeamNavigator.exe is still on the release page and runs on its own.
On macOS, Linux or a Raspberry Pi, the install goes through uv. The user guide on GitHub has the steps.
What’s new
1.5.0 (November 22). Straight from a Friday night 6-meter net. One box, I hear, replaces Find and I hear: a callsign fills in and becomes the Target, so Ctrl+Enter turns the beam and Enter logs it, and typing never hides anyone in the lists. The compass shows where net control is pointing. The Target and Rotate button stay in view on small screens. Saved stations with no name or a rough grid get checked on QRZ. Rosters import even when they don’t name net control. New stations use your computer’s time zone instead of UTC. And your data can live in one shared folder for every PC in the shack.
1.4.0 (November 18). Faster logging and smarter imports. I hear fills itself in when you pause, and a new callsign clears the line. Find or point at and I hear sit at the top of the net screen, above the lists. Imported rosters get their missing grids, labelled with where they came from. The Dashboard shows the grid. Nets are listed by the day of the week, today first.
1.3.0 (November 1). A clearer net screen. One Target, two columns, and a net control line that’s never just “unknown.” Snap back became Rotate to net control, and Aim at became Find or point at. A greyed-out Rotate tells you why.
1.2.0 (October 31). A proper Windows installer, no console window, and a Quit button. I hear got the same boxes as the net control screen, plus Direction and Aim to.
1.1.0 (October 30). The participant net screen: tonight’s check-ins, regulars not heard yet, I hear, sorting, and closing notes for next time.
Always true: Beam Navigator never turns your antenna unless you press Rotate, or its key.
Get it
Version 1.5.0 is a free public beta, and I want to hear what breaks. Email beam-navigator@n2lqh.com or open an issue on GitHub.
Point where it says. Then listen.
73 de N2LQH · Terry Rossi · South Jersey
