GridTracker

General discussions V2
Post Reply
k0guz
Novice Class
Posts: 7
Joined: 22 Jan 2018, 20:06

GridTracker

Post by k0guz » 29 Jan 2020, 17:20

FT8/FT4 users might be interested in trying Grid Tracker, https://tagloomis.com/grid-tracker/, which is a graphic interface for WSJT-X, and has most of the same features as JTAlert, and a lot more. It works seamlessly with Log4OM with if you add the first line below to configuration | connections:
Capture.PNG
Capture.PNG (20.71 KiB) Viewed 1891 times
Unlike JTAlert, however, GridTracker simply rebroadcasts the QSO information but does not check to make sure it was received; thus, if you forget to start Log4OM first, the QSO won't be entered in your Log4OM log.

User avatar
IK0TIX
Advanced Class
Posts: 69
Joined: 26 Mar 2016, 06:41

Re: GridTracker

Post by IK0TIX » 29 Jan 2020, 19:02

Hi Stephen
I discovered gridtracker on this forum.
I absolutely agree with you: it is truly a well-made program.
I am not a fan of digital modes (I prefer phone) but I am using FT8 to try to work those North American States that I cannot reach (generally they are your innermost States such as Wyouming, Idahao, Montana etc. guys help me!) and complete my 50USA.
Gridtracker is helping me to find these areas without continuous CQUSA CQUSA.
73
Max IK0TIX

va3vf
Advanced Class
Posts: 67
Joined: 19 Jan 2020, 03:10

Re: GridTracker

Post by va3vf » 29 Jan 2020, 21:28

The only problem was that GridTracker would not run side by side with JTAlert, until today.

See the settings for GridTracker-JTAlert-JTDX (not WSJT-X) here:

https://hamapps.groups.io/g/Support/message/27544

73 de Vince

k0guz
Novice Class
Posts: 7
Joined: 22 Jan 2018, 20:06

Re: GridTracker

Post by k0guz » 30 Jan 2020, 01:01

Ha! I live in western Colorado and have WAS on 30M for every state but Wyoming...and that's less than 200 km north of my QTH. So don't feel badly.

Now that GridTracker has evolved, I find that I don't need to use JTAlert any more, so trying to get them both to work at the same time is not an issue. I was very, very pleasantly surprised at how well the new version of Log4OM works with that program. Good job!

User avatar
DF5WW
Log4OM Alpha Team
Posts: 1559
Joined: 02 May 2013, 09:49
Location: Kraam, Rhineland Palatinate, Germany

Re: GridTracker

Post by DF5WW » 30 Jan 2020, 06:23

k0guz wrote:
30 Jan 2020, 01:01
I find that I don't need to use JTAlert any more
It´s like using WSJT-X or JTDX, for each of us one or the other doing better
what we want. Laurie (VK3AMA) is doing a great Job with JTalert and integrating
it to new loggers and it has the best "Worked B4" stats. It´s simple, easy and if
you have set alarms you can let it run in the background....

Just my 2 cts ... ;) ;)
73´s .. Juergen ... ALT-512 SDR (10W) , 50 m random wire at CG-3000 autotuner, Ailunce HS2 (20W and 5W VHF/UHF) to LPDA´s and different vertical´s ...

PA0AER
Advanced Class
Posts: 62
Joined: 30 Oct 2017, 12:09
Contact:

Re: GridTracker

Post by PA0AER » 30 Jan 2020, 13:34

k0guz wrote:
29 Jan 2020, 17:20
FT8/FT4 users might be interested in trying Grid Tracker, https://tagloomis.com/grid-tracker/, which is a graphic interface for WSJT-X, and has most of the same features as JTAlert, and a lot more. It works seamlessly with Log4OM with if you add the first line below to configuration | connections:

Capture.PNG

Unlike JTAlert, however, GridTracker simply rebroadcasts the QSO information but does not check to make sure it was received; thus, if you forget to start Log4OM first, the QSO won't be entered in your Log4OM log.
I'm a gridtracker user too. But can't use it in V2. See here my settings in V1 and V2, please advice me what am i'm doing wrong:
Log4OMV1


WSJT-X UDP 2333 Gridtracker 2333 .....> log4 OM 2236
WSJT-X ADIF 2237

k0guz
Novice Class
Posts: 7
Joined: 22 Jan 2018, 20:06

Re: GridTracker

Post by k0guz » 30 Jan 2020, 13:45

This is from the author of GridTracker on a Facebook forum:
In Log4OM V2 Configuration->Software integration->Connections create a new entry "Port" 2236 "Connection Name" GRID TRACKER "Service Type" UDP_INBOUND ADIF_MESSAGE and be sure it's enabled [X]
Image

PA0AER
Advanced Class
Posts: 62
Joined: 30 Oct 2017, 12:09
Contact:

Re: GridTracker

Post by PA0AER » 30 Jan 2020, 15:24

Thanks, I did. This is how it works with V1. Gridtracker is now in V2 working perfectly, but not together with log4omV2. No qso information, no logging into log4om.

k0guz
Novice Class
Posts: 7
Joined: 22 Jan 2018, 20:06

Re: GridTracker

Post by k0guz » 30 Jan 2020, 15:40

PA0AER wrote:
30 Jan 2020, 15:24
Thanks, I did. This is how it works with V1. Gridtracker is now in V2 working perfectly, but not together with log4omV2. No qso information, no logging into log4om.
Hmmm. You are running all 3 programs (WSJT-X, GridTracker and Log4OM) at the same time, right? I found that if I start Log4OM first, then WSJT-X then GridTracker it works.

NI4TG
Novice Class
Posts: 3
Joined: 29 Apr 2020, 20:37

Re: GridTracker

Post by NI4TG » 15 Sep 2020, 19:24

Log4OM 2, WSJT X, and Gridtracker (night view). The instructions on the Gridtracker site under media are great.
IMG_0766.jpg
IMG_0766.jpg (87.27 KiB) Viewed 482 times

Post Reply