GridTracker gets overlays and more…

We’re now a full featured Grid tracker and Log viewer with the addition of CQ/ITU/WAC/WAS overlays.  A lot of improvements to message handling and DXCC detection make for a more useful tool.

Henry(N2VFL) is working his tail off trying to get the documentation up to date (I have been moving too fast for him to keep up). We are  anxiously waiting for him to go take his General exam as well!

We have put our house up for sale here in the Denver area and looking forward to our move to Oregon.  I am putting development on hold until we get out there.  If there are any pressing issues they will be addressed, just no new features for a couple months.

Thank you all for the kind messages and sharing your status online, it’s been fascinating to see all the new GT Flags show up on the map.

We’re a little over 4 months into the project and I think we’ve made some serious progress.

As always we welcome new ideas and suggestions for improvements.

Meet us on our Discord server!


-Stephen ‘Tag’ Loomis  / N0TTL


14 thoughts on “GridTracker gets overlays and more…”

  1. Just downloaded the new version. When I open it, all I get is the map, no side bar. I have not be able to figure out how to get the side bar. What to I need to do?

    1. Richard,

      Try uninstalling it with the MS Windows ‘uninstaller’.
      Reinstall as administrator in default directory.
      Launch the application.

      73, Rich, K3VAT

  2. Great software!
    I just download and try to start.
    UDP messages is “red”
    No message
    I checked “multicast” IP address is
    Port 2237
    What should I change?

    1. Check in WSJT-X and make sure that reporting over UDP is turned on and you have the same ip address and port set there as in GridTracker.

  3. I have been using GridTracker on my Mac for a few weeks. Great program. Just last week I opened it and it just shows the regular window with nothing but black. Any input on this? Thanks.

  4. Tnx so much for this great software. I would like to see lines time decaying by color. And a way to show 2nd party QSOs (those you only receive the locator of one side).

    This could be done by having a user file with callsigns plus locator.

    These features would be especially helpful on higher HF frequencies and 6m, since propagation there is most selective and changing.

    KO1DX has some really good ideas here:

  5. I just found GridTracker and started to play with it. First impression is very good. Since I cannot add the second monitor to my PC, I wonder if there exist a way to make GridTracker run on one PC and listen to WSJT-X on the other PC? I thought that the multicast setting can do that, but unfortunately even that the manual promises a section about multicast – there is no such section to be found.
    Kind regards,Vladimir

    1. Not sure but if you change the IP address from the default to the IP of the machine that you want to run GridTracker on it should cast the data to that machine. is an internal IP address and normally (assuming no Trojan or virus on your machine) nothing will leave the computer that it is running on. You would I believe also have to set GridTracker to ‘listen’ to the IP address (not of the source machine, the one running WSJT-X and/or JTAlertX.

  6. I have been using GridTracker 1.18 with wsjt-x and jtalert for some time now. I have two problems, at the top of the screen I see a black box with the text “downloading log (s)”. What is gridtracker trying to download? The other problem is that GT always forgets my QTH locator. I start as an administrator in W10.

  7. I want to run GridTracker with WSJT-X and JTAlertX. Although UDP rebroadcasting is turned on in JTAlertX on UDP Port 2334, GridTracker does not receive anything from WSJT-X.
    If I run WSJT-X without JTAlertX, GridTracker gets all data from WSJT-X and runs fine.
    Is there a workaround or setting, which makes it possible to run both JTAlertX and GridTracker?
    Must be an UDP problem, but as I wrote above, UDP rebroadcasting seems not to work, either.
    My firewall lets all UDP packets trough and I run the programs as admin.
    Vy 73, Alex – DH2ID

  8. I run WSJT-X, JTAlertX, and GridTracker, here are my settings.
    Settings –>> Network Services
    UDP Server: Port: 2237

    Settings –>> Logging
    Last QSO API to port 2334

    Settings –>> General
    Receive UDP Port: 2234

    So for me GridTracker gets its data from JTAlertX. I had problems getting it working in the beginning too, this configuration has worked for me for months. I also have rebroadcast turned on, but JTAlertX is rebroadcasting on a different port (and GridTracker is listening) than it is receiving data from WSJT-X on.

    Try and see if it works for you.

    1. Sorry, in my previous post I said I had the RX UDP port for GridTracker set to 2234, it should be set to the UDP broadcast port used in JTAlertX which in my case is 2334. If you are not using JTAlertX then set it to the UDP port in WSJT-X.

      For my setup GridTracker is set as follows: Receive UDP Port: 2334

      This is the only way I could get it to work, which makes me think that multicasting (one to many) does not work. If it did work then broadcasts from WSJT-X could be received directly by more than one app.

      I could never get that to work for me so I have them set up in a relay as follows:

      WSJT-X –2237–>> JTAlertX –2334–>> GridTracker

Leave a Reply

Your email address will not be published. Required fields are marked *