Is it on anyone’s roadmap to work with the team at GridTracker to get native logging? If I had that, I might stop using QRZ entirely! As it is, I mainly use QRZ as the Grand Central for logging, and integrate logbook transfers from there.
4 Likes
@KB0RB I’m with you on hoping for direct integration–in the meantime, I have GridTracker forwarding UDP messages and WRL’s Cat Control App listening on that forward port.
And since I have my WRL syncing with QRZ and my QRZ integrated into GridTracker just for log display purposes, I think it kind of simulates the same? But you’re right, if GT could interface directly with WRL, QRZ could get cut out of the chain.
That said, QRZ is probably permanent in my workflow since I like to post logs on the other popular platforms for confirmations and awards.
3 Likes
I guess I’d also take a scheduled job for QRZ sync as a substitute for this. If I was PMing WRL (I am a career software PM) I’d be trying to capture the QRZ logging market directly, but at the end of the day all I care about is that the data is replicated. I haven’t logged into the godawful LoTW since I got my eQSL, but I synchronize to it regularly. If I didn’t have to go manually sync WRL and QRZ, that would fill my requirements too.
4 Likes
@KB0RB Currently you can auto export QSO’s from WRL to QRZ via the QRZ import/export integrations, as well as use QRZ for callsign look up (which is recommended) since you have a QRZ subscription. Additionally you can use the WRL cat control app to work with WSJTX/JTDX and Gridtracker to send qso logging data to your WRL logbook.
Here are instructions that I use (and many others have used) to make this work:
WRL Cat Control / WSJTX / GridTracker / QRZ Integration Steps:
-
Start by going to the integrations page in WRL and downloading the cat control app (World Radio League)
-
Start the following apps in the following order (this seems to be important). Start WRL Cat Control first (then connect to your radio and make sure its connected then start WSJTX listening after making sure the port is set like in the screenshot labeled “WORKING-WSJTX-WRL-catControl-SETTINGS”), then start Grid Tracker, Then start WSJTX or JTDX (whichever you prefer).
-
Then go into the settings for GridTracker and under ‘General’ set the ports to match the screenshot i’ve attached labeled “WORKING-GRIDTRACKER-SETTINGS-1”. Then goto the “Logging” tab and set two things that are highlighted red in the screenshot labeled “WORKING-GRIDTRACKER-SETTINGS-2”. NOTE: since there is no WRL option in GridTracker i enabled the last option that says “HRD Logbook” and tied it to the same port. Again, this may or may not be necessary but this is what I did.
-
Then go to your WSJTX / JTDX settings and go to the “Radio” tab and make sure its set to hamlib as well as click the “Update Hamlib” button at the bottom of the screen (this is highlighted red in the screenshot “WORKING-WSTJX-rigSETTINGS”) NOTE: after clicking the ‘update hamlib’ button you’ll need to close and reopen WSTJX)
-
Then reopen the WSTJX Settings and goto the “Reporting” tab in WSJTX/JTDX and make sure everything is setup the same way it shows in the screenshot “WORKING-WSJTX-reportingSETTINGS”
At this point everything should be setup to correctly talk to one another. I would close everything out and open each app in the order I mention in #2. Then make a contact, once the logging window pops up in WSJTX add your power and comment (if you add this information) and click the ok button to log the QSO. After about a second or so the contact will show up in your WRL logbook as well as in your QRZ logbook .I’ve also added a screenshot of the JTDX settings if you prefer to use that instead of WSJTX, if not you can ignore that screenshot.
I hope this helps, somewhat!
Thanks & 73
Brad K4AZE
2 Likes
Wow, super detailed and helpful. Thanks! Sorry for the delayed reply here. The forum doesn’t seem to be sending me notification emails even though I’m subscribed to these threads. Need to check that out.
4 Likes