开云体育

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

What am I missing?

 

Hi group,
?
Regarding N3FJP AC Log and uploading to LOTW. I've eliminated any QSO's which were before LOTW so I would not get an error for "outside of date range"
?
Now, when I select ALL CONTACTS NOT UPLOADED, I inevitably get a pop up box as I have attached. I'm asking the program to upload any contacts not already uploaded yet I get this popup.
?
Someone in the group I'm sure can tell me where I am in error.
?
Also, is it possible to take another users formatting and apply it to my logbook. I know there are guys who have customized the layout very nicely and I'm just looking for a shortcut.?
?
Thanks in advance.
?
Alan W4ANT

Already uploaded.PNG

 

n3fjp does not mark as sent, until lotw confirms the upload. so, it may be already uploaded, but not marked yet, so I just tell it to ignore, and move on.? ?it will correct itself, on the next download


Dave Garber
VE3WEJ / VE3IE


On Fri, Mar 28, 2025 at 8:40?PM Alan W4ANT via <Alan.W4ANT=[email protected]> wrote:
Hi group,
?
Regarding N3FJP AC Log and uploading to LOTW. I've eliminated any QSO's which were before LOTW so I would not get an error for "outside of date range"
?
Now, when I select ALL CONTACTS NOT UPLOADED, I inevitably get a pop up box as I have attached. I'm asking the program to upload any contacts not already uploaded yet I get this popup.
?
Someone in the group I'm sure can tell me where I am in error.
?
Also, is it possible to take another users formatting and apply it to my logbook. I know there are guys who have customized the layout very nicely and I'm just looking for a shortcut.?
?
Thanks in advance.
?
Alan W4ANT
 

I looked into that, the QSO is marked Y in the sent column although it's not a LOTW user so it's not confirmed. I deleted all the QSO's from that callsign and tried again. Again I got the same "line 38" has already been uploaded but it's a different callsign. When checking that callsign, I'm finding them marked as sent YES but again not confirmed by LOTW.
?
If it makes any difference they all seem to be QSO party contacts where I have multiple contacts on the same day with the same callsign. However, they are not true duplicates as the time and county information has changeed.
?
Alan W4ANT
 

Hi Alan,

Thanks for your e-mail.? That error message is being returned from ARRL's TQSL software, not AC Log.? This FAQ will get you going:





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 Friday, March 28, 2025 at 09:35:42 PM EDT, Alan W4ANT via groups.io <alan.w4ant@...> wrote:


I looked into that, the QSO is marked Y in the sent column although it's not a LOTW user so it's not confirmed. I deleted all the QSO's from that callsign and tried again. Again I got the same "line 38" has already been uploaded but it's a different callsign. When checking that callsign, I'm finding them marked as sent YES but again not confirmed by LOTW.
?
If it makes any difference they all seem to be QSO party contacts where I have multiple contacts on the same day with the same callsign. However, they are not true duplicates as the time and county information has changeed.
?
Alan W4ANT
 

Alan,
Since you said it was a QSO party and you had multiple qso's with the same station could it be you worked him on a County Line? If you log a qso and all info is the same, including date and time LOTW will reject as a dupe. You have to change the time of one of the qso's by at least a minute to make LOTW happy.
I don't believe LOTW looks at the County name so that could be the problem. I have worked 3 and 4 county lines in the past and have to fudge the time of the qso to make it go through.

--
73
Fred
K2DFC
 

Thanks Scott and others for the input. Understanding now where this comes from in the sequence of things I understand. I combed through the log and found several Q's which had been uploaded to LOTW but for some reason had not returned an "L" in the Sent Conf By column.?
?
I also found a few QSO's which had invalid callsigns but had been accepted as a valid QSO by eQSL. I DO NOT use eQSL any longer for reasons most DX'ers will understand.
?
Some of the duplicate QSO's I found were State QSO parties and as Fred suspected were county line operations. I edited those so they would be accepted by LOTW.
?
I did not go as far as doing a bulk edit but that was an option.
?
Thanks all,
?
73,
Alan W4ANT
 

I have the same problem and does not go away?
--
Stephen Cullen
Maple Grove Radio Club
Vice President
KF0AED
"Keep your eyes on the sky, but your head out of the clouds."
 

Hi Stephen,

Thanks for your e-mail.? I'm sorry that you have run into trouble.? Your records must have an S added to the Sent Confirmed By field, so that AC Log does not hand them to TQSL again for signing and upload, which prompts the TQSL duplicate detected error message.

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:





And additional helpful details are here:





Enjoy!


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 Tuesday, April 1, 2025 at 01:41:09 PM EDT, Stephen KF0AED via groups.io <kf0aed9@...> wrote:


I have the same problem and does not go away?
--
Stephen Cullen
Maple Grove Radio Club
Vice President
KF0AED
"Keep your eyes on the sky, but your head out of the clouds."

1 - 8 of 8