开云体育

ctrl + shift + ? for shortcuts
© 2025 开云体育
  1. N3FJPSoftwareUsers
  2. Topics

Log entry uploaded to LoTW ok but LoTW download does not mark it

 

I have one log entry from the other day that uploaded fine from ACLog to LoTW (I logged into lotw.arrl.org and checked it), but when I download LoTW to ACLog it does not get marked as LoTW QSL. I.e. the line stays black in my log instead of turning green. It was uploaded and signed with a N7DZ/7 certificate (that's the call I used when I made the contact), but I've done that plenty in the past without problem. Now I'm back home and uploading with my home certificate, N7DZ (no /7), and that line causes an upload problem since it's logged with N7DZ/7 and I'm now uploading with N7DZ certificate. If I select the new lines in the log and upload "selected contacts from main log" that works fine.
?
Yes, I know I could just edit the offending line and manually mark it with a check in the QSO Sent, and L in the Sent Conf By. But I'd like to understand what went wrong and avoid it in the future if possible.?
?
How to diagnose?
?
Thanks - Bill N7DZ
?
?
 

Hi Bill,

Thanks for your e-mail. I'm sorry that you ran into trouble. Colors are based on your Y/N values in the S/R columns, so look for those values, rather than the colors. For your records to be marked as Sent to LoTW in AC Log (L in the Sent Confirmed By field), the following criteria must be met:

1. Your records must be successfully uploaded to LoTW.
2. Your records must be successfully downloaded from LoTW
3. The callsign must match the call of the station worked.
4. The band must match the band of the station worked.
5. The date and time in AC Log must match the date and time on the LoTW record.

Note that to speed processing, once AC Log finds a match, it doesn't continue searching your log for more matches, so if you have two or more contacts with the same station on the same band at the same time (such as working county line stations in a state QSO party), only one of the QSOs will be automatically marked.? When that occurs, just edit the unmarked contact and mark it manually.

If you continue to have trouble, click the option to display raw data on AC Log's LoTW form when you do the download.? If the QSOs are not included in the download, the LoTW server is not providing them.? If they are, but they are not updating in AC Log, see the data for the specific QSOs that the server provided and determine which of the above criteria is not matching.? More details on this trouble shooting method are here:




Having only ever had one call here, I can't speak to any nuances you may be encountering regarding the multiple call signs, though we don't typically hear of folks having trouble, as long as settings on the LoTW form are correct for the applicable call.? Someone else on the group may have more insights for you there.


Enjoy!

73, Scott
N3FJP


Serving the Amateur Radio community with contesting and general logging software since 1997.

1 Peter 3 vs 15: Always be prepared to give an answer to everyone who asks you to give . But do this with gentleness and respect...


On Wednesday, January 22, 2025 at 09:26:33 AM EST, Bill via groups.io <bill@...> wrote:


I have one log entry from the other day that uploaded fine from ACLog to LoTW (I logged into lotw.arrl.org and checked it), but when I download LoTW to ACLog it does not get marked as LoTW QSL. I.e. the line stays black in my log instead of turning green. It was uploaded and signed with a N7DZ/7 certificate (that's the call I used when I made the contact), but I've done that plenty in the past without problem. Now I'm back home and uploading with my home certificate, N7DZ (no /7), and that line causes an upload problem since it's logged with N7DZ/7 and I'm now uploading with N7DZ certificate. If I select the new lines in the log and upload "selected contacts from main log" that works fine.
?
Yes, I know I could just edit the offending line and manually mark it with a check in the QSO Sent, and L in the Sent Conf By. But I'd like to understand what went wrong and avoid it in the future if possible.?
?
How to diagnose?
?
Thanks - Bill N7DZ
?
?
 

The "fix" was to change "Own Call" to N7DZ/7 in the LoTW download dialog, to pick up that one log entry when I was signing with the portable suffix. It also works if I leave this field blank.?
?
I didn't previously understand what this field does, but I started filling it in when I started managing our club station log in addition to mine, since the field says "only needed if managing multiple calls". Now I see that what it does is request only lines from my LoTW log that match that callsign. Good to know.?
?
It's implicit I guess that "only needed if managing multiple calls" means "only needed if managing multiple calls under a single LoTW account". I didn't think it through enough. When I'm dealing with the club call, it's a different log book, and a different LoTW account, so this guidance doesn't really apply to me.?
?
I DO manage multiple of my own calls, all portable variations on my own call, but I don't see how using this field helps at all with that. I'm going back to always blank.?
?
Just curious, when is the "Own Call" ever useful?
?
Bill - N7DZ

1 - 3 of 3