Questions from a new user

[jtostenr]

Just started using QLog this week and already impressed. Coming from an older, popular tool it is nice to see something with a much more user friendly and modern interface. I've imported a few ADIF files, read the wiki and played around a bit, but still have a few questions/comments. For background, I primarily use digital modes and use Gridtracker to log to LotW and forward packets to my local logging program. I also operate in other states/countries and so getting everything to play nice together has been tricky in the past.

• I've added a few rigs and antennas, but I don't see any way to specify which I am using. For example, at my "Home" QTH, I use a 7610 with separate HF and 6m antennas and it seems like QLog should know to select the proper antenna based on the current band. For now, all of my logged QSOs are getting set to my 705, which I use for POTA.

• Is there a way to set the callbook lookup to automatic each time a QSO is logged?

• I tested the export feature and noticed that the address field is malformed. Looks like maybe a broken field tag or something.

• I don't see a way to add lat/long to the station profile. Is it specified elsewhere?

• Are there plans to upgrade the Groups.io site eventually so more people can join?

[aa5sh]

Welcome to the group.

For the rigs and antennas look at the 'My Station' also take a look at the 'Activities' Menu in the bottom status bar and I've mentioned examples here you may find it good.

For the callback lookup do you have the 'Primary' set?

Address:
Can you send an example of what you are seeing?

Lat/Lon:
Right now you can only add your Gridsquare

Groups.io
We've talking about it but just the pricing is a little concerning since this is opensource/volunteer driven.

[jtostenr]

• Ok, I see where to set the rig and antenna now, but do I need to manually change the antenna setting whenever I switch bands? I'll look into the Activities options.
• Callbook settings are correct and it does work if I right click on an entry and select "Update from Callbook". Just wondering if there is an option to automate this.
• Here is an example of a malformed address (they are all like this):
  <tx_pwr:3>100
  address:62Richard E Pack4666 E Gettysburg AveFresno, CA 93726-1702USA <P
  <arrl_sect:3>SJV
• Hopefully lat/long can be added in the future
• Totally understand about the costs. Happy to donate a bit to help if there is a decision to upgrade.

[foldynl]

Callbook settings are correct and it does work if I right click on an entry and select "Update from Callbook". Just wondering if there is an option to automate this.

I don't know what automation you're talking about, but when you fill in the callsign in New contact, it's automatically searched for.

Here is an example of a malformed address (they are all like this):
<tx_pwr:3>100
address:62Richard E Pack4666 E Gettysburg AveFresno, CA 93726-1702USA <P
<arrl_sect:3>SJV

please, send the ADI record for the QSO. If this fragment is from input file then your previous application incorrectly formatted the export file.

Hopefully lat/long can be added in the future

Simply hoping for it is not enough. There needs to be some justification for why it should be included in QLog. What advantage does it have over a gridsquare?

Totally understand about the costs. Happy to donate a bit to help if there is a decision to upgrade.

Details: https://groups.io/g/qlog/message/1051

However, not many people responded here. My preference is GitHub, because I can track everything there and nothing gets lost among emails in my inbox.

[jtostenr]

• Regarding callbook lookup, I am referring to when WSJTX or Gridtracker populates a log entry in Qlog. It seems that the callbook lookup must be done manually for each QSO.
• ADIF files attached (had to change to .txt to upload here)
  qlog_export.txt
  dxkeeper_export.txt
• A gridsquare is not precise. Granted for many use cases it is good enough, but lat/long is preferred for POTA, FFMA, etc
• Thank you for the background on the forum platform.

[aa5sh]

For Callbook lookup turn off QSY Wiping in the Rig Control and you may have to in WSJT disable the Clear DX Call after QSO so it will linger for a second until it is logged. QLog uses the New Log panel even for WSJT to add details in case you want to add comments, park numbers etc. If WSJT clears the call before it is logged those changes could get lost.

For a GridSquare you can go to a 6 or 8 digit grid square to get more precise.

[jtostenr]

I turned off QSY Wiping and disabled Clear DX Call and still not working. It may have something to do with how packets are being forwarded between the applications. Since it is pretty easy to select all rows and manually update from the callbook, I won't worry about this too much for now.

[aa5sh]

I'm not familiar really with GridTracker I typically just use WSJT and QLog. I know you mentioned that you use Gridtracker to upload to LoTW - QLog does that pretty seamlessly with one click. It isn't real time but I typically upload to all the things when I get done each day or session of operating.

[jtostenr]

Gridtracker forwards the packets from WSJTX to my logging application, which I suspect may have something to do with the automatic callbook lookup not working, but I will have to confirm. One alternative would be to setup WSJTX to use multicast, but I haven't tried that yet. Gridtracker is also a zero-click solution for logging directly to LotW. The only time I ever manually upload QSOs to LotW is for POTA logs.

[foldynl]

ADIF files attached (had to change to .txt to upload here)

It is a QLog issue...will be fixed.

A gridsquare is not precise. Granted for many use cases it is good enough, but lat/long is preferred for POTA, FFMA, etc

For US, the 8-characters grid, supported by QLog, is 700–850 m × 460 m. For Middle Europe 600 × 460 m. Isn't that enough? Does this require any service to have Lat/Long?

[jtostenr]

It is a QLog issue...will be fixed.
Thank you!

For US, the 8-characters grid, supported by QLog, is 700–850 m × 460 m. For Middle Europe 600 × 460 m. Isn't that enough? Does this require any service to have Lat/Long?
I don't think it's required for any service, but very useful to have when you activate from multiple locations within a large POTA entity or rare FFMA grid. If there is a text box available, that would be fine as well or perhaps I can just append it to the station profile name.

Overall, Qlog seems like a great tool so far and I see these as relatively minor issues. Going to play around with it a bit more and hope to import 70k+ QSOs soon and make the switch for good.

[aa5sh]

One other option is you could have WSJT talk to QLog then QLog has the option on the network tab to forward WSJT messages so you could have QLog send them to GridTracker. But like you say it is fairly easy to add the missing callback information in batches.

…

On May 27, 2026, at 11:40 AM, jtostenr ***@***.***> wrote: Gridtracker forwards the packets from WSJTX to my logging application, which I suspect may have something to do with the automatic callbook lookup not working, but I will have to confirm. One alternative would be to setup WSJTX to use multicast, but I haven't tried that yet. Gridtracker is also a zero-click solution for logging directly to LotW. The only time I ever manually upload QSOs to LotW is for POTA logs. — Reply to this email directly, view it on GitHub <#1044?email_source=notifications&email_token=AUEEMXSMFSHCUIOH4ZPUM43444LAZA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZQG44DAMZQUZZGKYLTN5XKOY3PNVWWK3TUUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-17078030>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUEEMXT6FJ7KR4RGTU44DEL444LAZAVCNFSM6AAAAACZOQHN7KVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTOMBXHAYDGMA>. Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/AUEEMXXJRIE4ZX33SXTE7BL444LAZA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZQG44DAMZQUZZGKYLTN5XKOY3PNVWWK3TUUVSXMZLOOSVGM33PORSXEX3JN5ZQ> and Android <https://github.com/notifications/mobile/android/AUEEMXRPPJCWNLACOSMPIHL444LAZA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZQG44DAMZQUZZGKYLTN5XKOY3PNVWWK3TUUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ>. Download it today! You are receiving this because you commented.