Details

Written by: NØTTL

Welcome Matt HB9HWI! Thank you for your contributions to GridTracker2, including the new SOTA support!

Proudly presenting "The Kitchen Sink, Hail Mary, Pre-CABG Release"

Call Roster / Feed Roster

• New Settings -> "Columns" tab in each roster: every column in one place, in the roster's column order
  • Change any column's color (Callsign, Grid, DXCC, State, Spotter, DE DXCC, Freq, Age, ...), with "Reset Colors" to return to the defaults
  • Drag a column onto another to move it, like the column headers; tick it to show or hide it
  • "Reset Column Order" moved here from the General tab
  • The Call Roster and Feed Roster keep their own colors; the hunting colors
    • (Callsign, Grid, DXCC, State, County, Cont, POTA, CQz, ITUz, PX, DXM, Calling) also color a wanted entry's background
  • Band and Mode keep using the band and mode colors from the main window: click Band to open Settings -> Colors there
• The column headers stick at the top of the window while the roster scrolls; returning long lost behavior
• Faster with long rosters
• The SOTA column marks what a summit is worth to you with dots beside its reference
  • Two dots before it: you haven't chased a summit in that association yet; one dot: you've chased one there
  • A dot after it: you haven't chased a summit in that region yet
• The DXCC column marks new ones, whatever the Logbook choice: ★ either side of an ATNO
  • (an entity you've never worked); after the name, ◆ a band you haven't worked it on, ● a mode you haven't worked it in; its hover says which
• In the Feed Roster, click a park or summit in the POTA / SOTA column to log the QSO by hand (CW, SSB), while no logger such as AC Log is connected and no WSJT-X / JTDX is on its band and mode
  • A park QSO is spotted to POTA, as for a logged decode

Call Roster

• With SOTA Chasing on, a decoded station that DX Feeds spots on a summit gets that summit
  • A new "SOTA" column (off by default; turn it on in Settings -> Columns) and a "SOTA" Wanted, like the Feed Roster's
  • A QSO logged with them gets the summit's SOTA_REF
  • The station's grid stays the one it transmits; with none sent, the summit's square is shown, not qualified (◇)

Feed Roster

• New Settings -> Features -> Online -> "SOTA Chasing" (shown while DX Feeds is on): Summits on the Air activators from DX Feeds spots
  • A "SOTA" column (off by default, like POTA), right of POTA, shows the summit named in the spot; its hover gives the summit's name, height and points
  • A "SOTA" Wanted highlights summits you haven't chased today (from SOTA_REF in your logs), also in Settings -> Audio Alerts -> Feed Roster ("Wanted Feed Summit" / "Many Feed Summits")
  • A spot on a summit is placed there: its grid becomes the summit's (Feed Roster, distance, and a logged QSO that has no grid)
  • On the map, on their own layer with a new SOTA button in the button panel (shown while SOTA Chasing is on): one snow-capped double-peak marker per summit, black with an orange outline, or orange, for the same three states as the DX Feeds markers; its tooltip lists every spot on it
  • Like POTA Hunting, it turns on the GT backup log, and a QSO logged with a spotted activator gets the summit's SOTA_REF
  • A spot saying "QRT" ends that activation: the activator's spots on the summit leave the Feed Roster and the map until they're spotted again
  • So does a spot with no frequency
  • An activator spotted on another summit leaves the old one at once
  • An activator still being decoded keeps their summit, even after the last spot of them ages out
  • A spot of an activator that doesn't name the summit (a skimmer's, say) gets the summit they're on
  • An activator you decode is shown on their summit's marker as a spot from you, like POTA's
• New "Auto Band" and "Auto Mode" exceptions (in the Feed Roster and Settings -> Audio Alerts -> Feed Roster): only spots on a band / in a mode one of your rigs is on (WSJT-X, JTDX, AC Log or Log4OM); with both, a rig on the spot's band and mode
  • With no rig connected they show everything
• The roster's Feeds settings tab (Modes, Bands, "Allow Alert Script", "Allow Notifications") moved to the main window's Settings -> Feeds, under Feed Spots Max Age and Clear All Feeds
  • The map's DX Feeds and SOTA markers now follow the same Modes and Bands as the Feed Roster
• Logbook choices say "Spots" instead of "Live" (e.g. "Spots Band & Mode"), in the Feed Roster and Settings -> Audio Alerts -> Feed Roster
• New Logbook choices for Phone and CW, beside the Digi ones: "Spots Band, Phone Modes", "Spots Band, CW Mode", "Mix Band & Phone Modes" and "Mix Band & CW Mode" (Feed Roster and Settings -> Audio Alerts -> Feed Roster)
• "DE DXCC" and "DE Cont" columns are now shown by default
• Clicking a callsign works the spot from the right place
  • A rig already on the spot's band and mode (WSJT-X, JTDX, AC Log or Log4OM) gets it, as before
  • Otherwise a connected AC Log gets it, on any band and mode: its entry tab is cleared and filled with the spot's frequency, band, mode, call and grid
  • With "Enable Rig Control" (Settings -> Logging -> N3FJP Loggers), AC Log tunes the rig to the spot's frequency and mode instead
  • Without AC Log, it goes to Gen Msgs on the active WSJT-X / JTDX
• The ▲ before a callsign now only marks spots on the band and mode one of your rigs is on
• A callsign in a rig's DX Call (WSJT-X, JTDX, or AC Log's entry tab) is highlighted green, like in the Call Roster
• "Hide Self-Spotters" is now "Hide Self-Spot"

Map / UI

• Overlapping POTA, SOTA and DX Feeds markers in the same DXCC entity are grouped into one marker, at their averaged position
  • A grouped tooltip is a compact table ("POTA Spot × 3", "SOTA Spot × 2") with the park / summit reference after the grid
  • New Settings -> Map -> "Group Overlapping Spots" (on by default): turn it off to show every marker on its own
• The POTA tooltip has a new header, like SOTA's: the park reference and name, its location, and distance / bearing
• Callsigns in a popped-out tooltip can be clicked to look them up
• Right-click a POTA park to pop out its tooltip
• POTA parks are drawn above DX Feeds spots, and SOTA summits above both
• Left-click a POTA, SOTA or DX Feeds marker to work the spot, like a Feed Roster callsign: a rig on its band and mode, else a connected AC Log (and its rig, with "Enable Rig Control")
  • A marker for several spots works the first one its tooltip lists
  • Where markers are stacked, only the top one is worked
• A POTA, SOTA or DX Feeds marker of a callsign in a rig's [DX Call] is ringed for easy finding on the map
• DX Feeds and SOTA markers leave the map once their spots expire, even while no new spots arrive
• The GridTracker Spotters button's hover shows how many spotters are on the map, with the map's band and mode filters applied ("Spotters: 42")
• Settings -> Map is regrouped into Base Map, Paths, Grayline, Overlays and Display boxes: day and night side by side, each path's width and colors on one row, and the colors shown as swatches
  • The Night column shows while "Auto Night Map" is on
  • More options have hover help
  • "Merge Award Overlay" is now "Keep Other Layers With Award View", and "'CQ' Highlighting" is now "Outline Directed CQ Areas"
• The Grids tab is now a Grids box in Settings -> Map: its three sliders with their values, Split QSL Grids and Auto Mouseover Grids
• So does Settings -> Audio: an Audio box (Device, notification sound, volume) and a Text-To-Speech box (Voice, rate, pitch, volume, phonetics)
• And Settings -> Lookups: Callsign Lookup Service, Lookups and Callsign Databases boxes
• And Settings -> Features: Operational, Service and Online boxes, with options indented under the one they depend on; the Simplepush and Pushover boxes show while each is on
  • "Clear on CQ" is now "Clear WSJT-X / JTDX On CQ"
• And Settings -> Logging: Logbooks On This Computer beside Logging Programs, above Online Logbooks, each with only the columns its services use; PSK-Reporter 24 Hour History has its own box at the bottom; no more scrolling to reach HRD Logbook
  • The columns are now "Connect", "Menu Button", "Load At Startup" and "Log QSO"
• And Settings -> Logbook: a QSL Location Authority box and a Logbook Filters box (Working Callsign(s), Grid(s) and Date, each with its Enable tick, and Apply Changes)
  • An empty Working Callsign(s) / Grid(s) field shows the callsigns / grids found in your logs, faintly, until you type there
  • A new QSL Location Authority is applied with its own Apply Changes button (it reloads your logbooks), no longer at once
• And Settings -> Colors: Gridsquare Colors and Band Colors boxes, each with its Reset Colors button in the title, and smaller swatches beside their names
• And Settings -> Feeds: a DX Feeds box (Max Age, Clear All Feeds, the Allow options) above Modes and Bands boxes side by side
• And Settings -> General: the three UDP boxes, Station, Display and Settings boxes, and an On QSO Reply box shown while more than one WSJT-X / JTDX instance is open (it now hides again when you're back to one)

Logbook

• The whole logbook is one scrolling list instead of pages, and even very large logs scroll smoothly
• The search boxes and column headers stay at the top while the list scrolls
• The sorted column shows an arrow with the sort direction, like the rosters
  • Sorting by another column keeps the current direction; click the same column again to reverse it
• New "SOTA" column with the summit of each QSO (SOTA_REF), with its own search box
• The POTA and SOTA columns are shown when your log has POTA / SOTA QSOs, whether or not POTA Hunting / SOTA Chasing is on
• New "Export SOTA Chaser Log…" button (shown when your log has SOTA QSOs): your SOTA chases as a CSV file for the SOTA database's chaser log upload
  • Pick the From and To times (local time; the file is UTC); each export starts where the last one ended
  • The QSOs are listed first: edit any field or leave a QSO out (possible duplicates are flagged); this only changes the file, never your logbook

Logging / AC Log

• Settings -> Logging -> N3FJP Loggers: a green / red dot right of "Connect" shows whether AC Log is connected
• New "Enable Rig Control" under the N3FJP Loggers details (shown while Connect is on): clicking a Feed Roster callsign tunes the rig through AC Log
• AC Log's band and mode follow its entry tab when it has no rig frequency, and a rig frequency is shown in the main panel when it has one
• The call and grid in AC Log's entry tab show in GridTracker even before tabbing out of the call, and clear with the entry tab
• The status bar shows "CONNECTED" instead of "RECEIVE" while AC Log is the active rig
• Clicking a spot also fills AC Log's Other fields titled POTA_REF / SOTA_REF with the spot's park / summit
• QSOs logged in AC Log reach GridTracker more reliably: even several logged in quick succession
• A QSO logged in AC Log with a park (its Other field titled POTA_REF) is spotted to POTA, like one logged from WSJT-X (with POTA Hunting on)
• A QSO a logger broadcasts back is no longer logged and sent out a second time

Logging / Log4OM

• New "Connect" in Settings -> Logging -> Log4OM, through Log4OM's UDP remote control, with a green / red dot showing whether Log4OM is connected
  • Log4OM's rig frequency, band and mode show in the main panel, and the status bar shows "CONNECTED" while Log4OM is the active rig
  • With Log4OM on the same PC, its station callsign and locator are read from its settings when connecting
• Clicking a Feed Roster callsign, or a POTA, SOTA or DX Feeds marker, sends the spot's call to Log4OM's QSO entry (not over a call you typed there yourself)
  • The main panel shows the call and grid sent
• New "Enable Rig Control" (shown while Connect is on): clicking a spot also tunes the rig through Log4OM to the spot's frequency and mode

App

• New Settings -> General -> Station -> "Callsign": your callsign while no WSJT-X, JTDX, AC Log or Log4OM is connected; a callsign they report is always used for them
  • While it's blank, it takes the callsign WSJT-X / JTDX gives; you can change it, and it's never replaced
• Settings -> General -> Forward UDP Messages accepts hostnames (e.g. ft8battle.com) as well as IP addresses, several comma separated: "IP(s)/Hostname(s)"
  • A hostname that can't be found (a typo, or no internet) is reported under the field