Date   
Re: One QSO 'Already Uploaded' - how to find it

Dave Cole
 

Why not sort on the field in question? The blank one(s) will be on the bottom or top... Just click the field name while in SHOW ALL.

73, and thanks,
Dave (NK7Z)
https://www.nk7z.net
ARRL Volunteer Examiner
ARRL Technical Specialist
ARRL Asst. Director, NW Division, Technical Resources

On 4/7/20 2:28 PM, Christopher Scibelli via groups.io wrote:
Be happy you don't have 75,000 Qs.
73,
Chris  NU1O
-----Original Message-----
From: Mark Steele <kd2nom@...>
To: N3FJPSoftwareUsers <N3FJPSoftwareUsers@groups.io>
Sent: Tue, Apr 7, 2020 2:38 pm
Subject: Re: [N3FJPSoftwareUsers] One QSO 'Already Uploaded' - how to find it
Ugh - this is brutal - I have 29,000 contacts and they all have something in the S Conf By field (I upload to EQSL and Club Log) - i'll scroll to find the one that is missing the L

Re: New TQSL

Dave Cole
 

Just getting this on your radar is all... No hurry. Little not picking things is all... Thanks for being so responsive to feature requests...

73, and thanks,
Dave (NK7Z)
https://www.nk7z.net
ARRL Volunteer Examiner
ARRL Technical Specialist
ARRL Asst. Director, NW Division, Technical Resources

On 4/7/20 2:20 PM, Scott Davis via groups.io wrote:
Hi Dave,
Thanks for your follow up.  If you can find a way for AC Log to problematically detect that message from the TQSL software, I will be glad to.  That said, since AC Log will continue to work with the new version of TQSL as is, I am not planning a new AC Log release for the near term.
Enjoy!
73, Scott
N3FJP
_http://www.n3fjp.com_ <http://www.n3fjp.com/>
/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 _the reason for <http://www.n3fjp.com/Faith.htm>the hope that you have <http://www.n3fjp.com/Faith.htm>_. But do this with gentleness and respect/...
-----Original Message-----
From: Dave Cole <dave@...>
To: N3FJPSoftwareUsers@groups.io
Sent: Tue, Apr 7, 2020 5:16 pm
Subject: Re: [N3FJPSoftwareUsers] New TQSL
If you are doing changes, can you change things so the TQSL, do you want
to update, window comes up in front of the ACL application, and not
hidden behind it, when TQSL needs an update?
73, and thanks,
Dave (NK7Z)
https://www.nk7z.net <https://www.nk7z.net/>
ARRL Volunteer Examiner
ARRL Technical Specialist
ARRL Asst. Director, NW Division, Technical Resources
On 4/7/20 2:05 PM, Scott Davis via groups.io wrote:
> Thanks for the good information Steven.  I had not seen that.
>
> Enjoy!
>
>
> 73, Scott
> N3FJP
> _http://www.n3fjp.com_ <http://www.n3fjp.com/>
>
> /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 _the reason for <http://www.n3fjp.com/Faith.htm>the
> hope that you have <http://www.n3fjp.com/Faith.htm>_. But do this with
> gentleness and respect/...
>
>
> -----Original Message-----
> From: AI3KS <AI3KS.01@... <mailto:AI3KS.01@...>>
> To: N3FJPSoftwareUsers@groups.io <mailto:N3FJPSoftwareUsers@groups.io>
> Sent: Tue, Apr 7, 2020 4:05 pm
> Subject: [N3FJPSoftwareUsers] New TQSL
>
> Scott,
>
> Don't know if you have seen this yet, or if it will take changes to the
> software:
>
> (From the ARRL Website)
>
> The latest version of /TrustedQSL/ (/TQSL/), version 2.5.2, offers
> improved Logbook of The World (*LoTW*
> <http://www.arrl.org/logbook-of-the-world>) support for operations from
> several locations, as well as the ability to detect uploads that contain
> incorrect location data. The primary new feature in /TQSL/ 2.5.2 allows
> logging programs, in conjunction with /TQSL/, to avoid incorrect contact
> uploads, while adding mechanisms to allow easy uploading of logs for
> roving stations. LoTW had required rovers to identify each location used
> as a separate location in /TQSL/. The new version of /TQSL/ allows these
> operations to be handled much more smoothly by using information from
> the station’s logging program.
> When a log is signed by /TQSL/, the station details — call Sign, DXCC
> entity, grid square, and other location details provided by the selected
> station location (and call sign certificate) — are compared with the
> details in the log. If the US state and station location in a log do not
> agree, /TQSL/ 2.5.2 will reject the contact, detecting errors in
> instances when an incorrect station location has been chosen. This
> feature will necessitate changes in many logging programs, because it
> requires that the log provide station details previously not used by
> /TQSL/. Once a logging program supplies these (MY_STATE, MY_DXCC,
> MY_CQ_ZONE, etc.), then /TQSL/ will validate them against the log.
> Currently, Cabrillo logs use the CALLSIGN field to verify that the
> contacts are for the correct call sign.
> Optionally, a station performing roaming operations (e.g., from multiple
> grid squares) can choose to have /TQSL/ assume that the log is correct.
> When call sign or home station are provided with the log, /TQSL/ will
> automatically update the details on the upload. Select “Override Station
> Location with QTH Details from your Log” on the “Log Handling”
> preference page to enable this feature.
> This release also includes an update to the most recent /TQSL/
> configuration file. /— Thanks to Rick Murphy, K1MU/
>

Re: Last Names not recording in log

Scott Davis
 

Hi Frank,

Thanks for your e-mail.  AC Log includes whatever data is returned by the lookup.  AC Log doesn't filter the data in any way.

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 the reason for the hope that you have. But do this with gentleness and respect...


-----Original Message-----
From: Frank C. D'Amato <kb2mxv@...>
To: N3FJPSoftwareUsers@groups.io
Sent: Tue, Apr 7, 2020 3:46 pm
Subject: [N3FJPSoftwareUsers] Last Names not recording in log

Using N3FJP 6.6 and connected to QRZ lookup

Why do some callsigns populate both First and Last name in the name field, while others only populate the first name in the name field?

Video of Problem
https://youtu.be/xYUJHeXz8N0

Frank - KB2MXV

Re: New TQSL

Scott Davis
 

Hi All,

Aside the the normal TQSL upgrade procedure that you perform with any TQSL upgrade, there is nothing else special you have to do.  

AC Log works fine with TQSL 2.5.2.  I have signed and uploaded records using AC Log 6.6 and TQSL 2.5.2 with no problems whatsoever.

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 the reason for the hope that you have. But do this with gentleness and respect...


-----Original Message-----
From: Lou Everett, Sr. <loueverettsr@...>
To: N3FJPSoftwareUsers@groups.io
Sent: Tue, Apr 7, 2020 6:21 pm
Subject: Re: [N3FJPSoftwareUsers] New TQSL

What would you need instructions for?  It is just an upgrade.  Click on your TQSL Icon, and the window link for the upgrade will pop up.

Lou WA5LOU

On Tue, Apr 7, 2020 at 5:08 PM Mike Olbrisch <mike-2020@...> wrote:
Have they posted instructions for this someplace?  At first read, it sounds confusing.  But then, I’m just waking up, I’m on shift the next 4 nights.
 
You-all stay SAFE and HEALTHY.
 
Mike – KD5KC -- El Paso -- Texas.
 
The canyons are calling, colorful and deep.  But I have promises to keep.
And miles to go still in my Jeep...   And miles to go still in my Jeep...
 
 
ADVENTURE:  The respectful pursuit of trouble.
 
 
 
 
From: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io> On Behalf Of AI3KS
Sent: Tuesday, April 7, 2020 14:06 PM
To: N3FJPSoftwareUsers@groups.io
Subject: [N3FJPSoftwareUsers] New TQSL
 
Scott,

Don't know if you have seen this yet, or if it will take changes to the software:

(From the ARRL Website)
The latest version of TrustedQSL (TQSL), version 2.5.2, offers improved Logbook of The World (LoTW) support for operations from several locations, as well as the ability to detect uploads that contain incorrect location data. The primary new feature in TQSL 2.5.2 allows logging programs, in conjunction with TQSL, to avoid incorrect contact uploads, while adding mechanisms to allow easy uploading of logs for roving stations. LoTW had required rovers to identify each location used as a separate location in TQSL. The new version of TQSL allows these operations to be handled much more smoothly by using information from the station’s logging program.
When a log is signed by TQSL, the station details — call Sign, DXCC entity, grid square, and other location details provided by the selected station location (and call sign certificate) — are compared with the details in the log. If the US state and station location in a log do not agree, TQSL 2.5.2 will reject the contact, detecting errors in instances when an incorrect station location has been chosen. This feature will necessitate changes in many logging programs, because it requires that the log provide station details previously not used by TQSL. Once a logging program supplies these (MY_STATE, MY_DXCC, MY_CQ_ZONE, etc.), then TQSL will validate them against the log. Currently, Cabrillo logs use the CALLSIGN field to verify that the contacts are for the correct call sign.
Optionally, a station performing roaming operations (e.g., from multiple grid squares) can choose to have TQSL assume that the log is correct. When call sign or home station are provided with the log, TQSL will automatically update the details on the upload. Select “Override Station Location with QTH Details from your Log” on the “Log Handling” preference page to enable this feature.
This release also includes an update to the most recent TQSL configuration file. — Thanks to Rick Murphy, K1MU   
--
Lou WA5LOU


Re: New TQSL

Lou Everett, Sr.
 

What would you need instructions for?  It is just an upgrade.  Click on your TQSL Icon, and the window link for the upgrade will pop up.

Lou WA5LOU

On Tue, Apr 7, 2020 at 5:08 PM Mike Olbrisch <mike-2020@...> wrote:

Have they posted instructions for this someplace?  At first read, it sounds confusing.  But then, I’m just waking up, I’m on shift the next 4 nights.

 

You-all stay SAFE and HEALTHY.

 

Mike – KD5KC -- El Paso -- Texas.

 

The canyons are calling, colorful and deep.  But I have promises to keep.

And miles to go still in my Jeep...   And miles to go still in my Jeep...

 

 

ADVENTURE:  The respectful pursuit of trouble.

 

 

 

 

From: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io> On Behalf Of AI3KS
Sent: Tuesday, April 7, 2020 14:06 PM
To: N3FJPSoftwareUsers@groups.io
Subject: [N3FJPSoftwareUsers] New TQSL

 

Scott,

Don't know if you have seen this yet, or if it will take changes to the software:

(From the ARRL Website)

The latest version of TrustedQSL (TQSL), version 2.5.2, offers improved Logbook of The World (LoTW) support for operations from several locations, as well as the ability to detect uploads that contain incorrect location data. The primary new feature in TQSL 2.5.2 allows logging programs, in conjunction with TQSL, to avoid incorrect contact uploads, while adding mechanisms to allow easy uploading of logs for roving stations. LoTW had required rovers to identify each location used as a separate location in TQSL. The new version of TQSL allows these operations to be handled much more smoothly by using information from the station’s logging program.

When a log is signed by TQSL, the station details — call Sign, DXCC entity, grid square, and other location details provided by the selected station location (and call sign certificate) — are compared with the details in the log. If the US state and station location in a log do not agree, TQSL 2.5.2 will reject the contact, detecting errors in instances when an incorrect station location has been chosen. This feature will necessitate changes in many logging programs, because it requires that the log provide station details previously not used by TQSL. Once a logging program supplies these (MY_STATE, MY_DXCC, MY_CQ_ZONE, etc.), then TQSL will validate them against the log. Currently, Cabrillo logs use the CALLSIGN field to verify that the contacts are for the correct call sign.

Optionally, a station performing roaming operations (e.g., from multiple grid squares) can choose to have TQSL assume that the log is correct. When call sign or home station are provided with the log, TQSL will automatically update the details on the upload. Select “Override Station Location with QTH Details from your Log” on the “Log Handling” preference page to enable this feature.

This release also includes an update to the most recent TQSL configuration file. — Thanks to Rick Murphy, K1MU   

--
Lou WA5LOU


Re: New TQSL

Mike Olbrisch
 

Have they posted instructions for this someplace?  At first read, it sounds confusing.  But then, I’m just waking up, I’m on shift the next 4 nights.

 

You-all stay SAFE and HEALTHY.

 

Mike – KD5KC -- El Paso -- Texas.

 

The canyons are calling, colorful and deep.  But I have promises to keep.

And miles to go still in my Jeep...   And miles to go still in my Jeep...

 

 

ADVENTURE:  The respectful pursuit of trouble.

 

 

 

 

From: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io> On Behalf Of AI3KS
Sent: Tuesday, April 7, 2020 14:06 PM
To: N3FJPSoftwareUsers@groups.io
Subject: [N3FJPSoftwareUsers] New TQSL

 

Scott,

Don't know if you have seen this yet, or if it will take changes to the software:

(From the ARRL Website)

The latest version of TrustedQSL (TQSL), version 2.5.2, offers improved Logbook of The World (LoTW) support for operations from several locations, as well as the ability to detect uploads that contain incorrect location data. The primary new feature in TQSL 2.5.2 allows logging programs, in conjunction with TQSL, to avoid incorrect contact uploads, while adding mechanisms to allow easy uploading of logs for roving stations. LoTW had required rovers to identify each location used as a separate location in TQSL. The new version of TQSL allows these operations to be handled much more smoothly by using information from the station’s logging program.

When a log is signed by TQSL, the station details — call Sign, DXCC entity, grid square, and other location details provided by the selected station location (and call sign certificate) — are compared with the details in the log. If the US state and station location in a log do not agree, TQSL 2.5.2 will reject the contact, detecting errors in instances when an incorrect station location has been chosen. This feature will necessitate changes in many logging programs, because it requires that the log provide station details previously not used by TQSL. Once a logging program supplies these (MY_STATE, MY_DXCC, MY_CQ_ZONE, etc.), then TQSL will validate them against the log. Currently, Cabrillo logs use the CALLSIGN field to verify that the contacts are for the correct call sign.

Optionally, a station performing roaming operations (e.g., from multiple grid squares) can choose to have TQSL assume that the log is correct. When call sign or home station are provided with the log, TQSL will automatically update the details on the upload. Select “Override Station Location with QTH Details from your Log” on the “Log Handling” preference page to enable this feature.

This release also includes an update to the most recent TQSL configuration file. — Thanks to Rick Murphy, K1MU   

Re: One QSO 'Already Uploaded' - how to find it

Christopher Scibelli
 

Be happy you don't have 75,000 Qs.

73,

Chris  NU1O


-----Original Message-----
From: Mark Steele <kd2nom@...>
To: N3FJPSoftwareUsers <N3FJPSoftwareUsers@groups.io>
Sent: Tue, Apr 7, 2020 2:38 pm
Subject: Re: [N3FJPSoftwareUsers] One QSO 'Already Uploaded' - how to find it

Ugh - this is brutal - I have 29,000 contacts and they all have something in the S Conf By field (I upload to EQSL and Club Log) - i'll scroll to find the one that is missing the L

Re: New TQSL

Scott Davis
 

Hi Dave,

Thanks for your follow up.  If you can find a way for AC Log to problematically detect that message from the TQSL software, I will be glad to.  That said, since AC Log will continue to work with the new version of TQSL as is, I am not planning a new AC Log release for the near term.

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 the reason for the hope that you have. But do this with gentleness and respect...


-----Original Message-----
From: Dave Cole <dave@...>
To: N3FJPSoftwareUsers@groups.io
Sent: Tue, Apr 7, 2020 5:16 pm
Subject: Re: [N3FJPSoftwareUsers] New TQSL

If you are doing changes, can you change things so the TQSL, do you want
to update, window comes up in front of the ACL application, and not
hidden behind it, when TQSL needs an update?

73, and thanks,
Dave (NK7Z)
https://www.nk7z.net
ARRL Volunteer Examiner
ARRL Technical Specialist
ARRL Asst. Director, NW Division, Technical Resources

On 4/7/20 2:05 PM, Scott Davis via groups.io wrote:
> Thanks for the good information Steven.  I had not seen that.
>
> Enjoy!
>
>
> 73, Scott
> N3FJP
> _http://www.n3fjp.com_ <http://www.n3fjp.com/>
>
> /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 _the reason for <http://www.n3fjp.com/Faith.htm>the
> hope that you have <http://www.n3fjp.com/Faith.htm>_. But do this with
> gentleness and respect/...
>
>
> -----Original Message-----
> From: AI3KS <AI3KS.01@...>
> To: N3FJPSoftwareUsers@groups.io
> Sent: Tue, Apr 7, 2020 4:05 pm
> Subject: [N3FJPSoftwareUsers] New TQSL
>
> Scott,
>
> Don't know if you have seen this yet, or if it will take changes to the
> software:
>
> (From the ARRL Website)
>
> The latest version of /TrustedQSL/ (/TQSL/), version 2.5.2, offers
> improved Logbook of The World (*LoTW*
> <http://www.arrl.org/logbook-of-the-world>) support for operations from
> several locations, as well as the ability to detect uploads that contain
> incorrect location data. The primary new feature in /TQSL/ 2.5.2 allows
> logging programs, in conjunction with /TQSL/, to avoid incorrect contact
> uploads, while adding mechanisms to allow easy uploading of logs for
> roving stations. LoTW had required rovers to identify each location used
> as a separate location in /TQSL/. The new version of /TQSL/ allows these
> operations to be handled much more smoothly by using information from
> the station’s logging program.
> When a log is signed by /TQSL/, the station details — call Sign, DXCC
> entity, grid square, and other location details provided by the selected
> station location (and call sign certificate) — are compared with the
> details in the log. If the US state and station location in a log do not
> agree, /TQSL/ 2.5.2 will reject the contact, detecting errors in
> instances when an incorrect station location has been chosen. This
> feature will necessitate changes in many logging programs, because it
> requires that the log provide station details previously not used by
> /TQSL/. Once a logging program supplies these (MY_STATE, MY_DXCC,
> MY_CQ_ZONE, etc.), then /TQSL/ will validate them against the log.
> Currently, Cabrillo logs use the CALLSIGN field to verify that the
> contacts are for the correct call sign.
> Optionally, a station performing roaming operations (e.g., from multiple
> grid squares) can choose to have /TQSL/ assume that the log is correct.
> When call sign or home station are provided with the log, /TQSL/ will
> automatically update the details on the upload. Select “Override Station
> Location with QTH Details from your Log” on the “Log Handling”
> preference page to enable this feature.
> This release also includes an update to the most recent /TQSL/
> configuration file. /— Thanks to Rick Murphy, K1MU/
>



Re: New TQSL

Dave Cole
 

If you are doing changes, can you change things so the TQSL, do you want to update, window comes up in front of the ACL application, and not hidden behind it, when TQSL needs an update?

73, and thanks,
Dave (NK7Z)
https://www.nk7z.net
ARRL Volunteer Examiner
ARRL Technical Specialist
ARRL Asst. Director, NW Division, Technical Resources

On 4/7/20 2:05 PM, Scott Davis via groups.io wrote:
Thanks for the good information Steven.  I had not seen that.
Enjoy!
73, Scott
N3FJP
_http://www.n3fjp.com_ <http://www.n3fjp.com/>
/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 _the reason for <http://www.n3fjp.com/Faith.htm>the hope that you have <http://www.n3fjp.com/Faith.htm>_. But do this with gentleness and respect/...
-----Original Message-----
From: AI3KS <AI3KS.01@...>
To: N3FJPSoftwareUsers@groups.io
Sent: Tue, Apr 7, 2020 4:05 pm
Subject: [N3FJPSoftwareUsers] New TQSL
Scott,
Don't know if you have seen this yet, or if it will take changes to the software:
(From the ARRL Website)
The latest version of /TrustedQSL/ (/TQSL/), version 2.5.2, offers improved Logbook of The World (*LoTW* <http://www.arrl.org/logbook-of-the-world>) support for operations from several locations, as well as the ability to detect uploads that contain incorrect location data. The primary new feature in /TQSL/ 2.5.2 allows logging programs, in conjunction with /TQSL/, to avoid incorrect contact uploads, while adding mechanisms to allow easy uploading of logs for roving stations. LoTW had required rovers to identify each location used as a separate location in /TQSL/. The new version of /TQSL/ allows these operations to be handled much more smoothly by using information from the station’s logging program.
When a log is signed by /TQSL/, the station details — call Sign, DXCC entity, grid square, and other location details provided by the selected station location (and call sign certificate) — are compared with the details in the log. If the US state and station location in a log do not agree, /TQSL/ 2.5.2 will reject the contact, detecting errors in instances when an incorrect station location has been chosen. This feature will necessitate changes in many logging programs, because it requires that the log provide station details previously not used by /TQSL/. Once a logging program supplies these (MY_STATE, MY_DXCC, MY_CQ_ZONE, etc.), then /TQSL/ will validate them against the log. Currently, Cabrillo logs use the CALLSIGN field to verify that the contacts are for the correct call sign.
Optionally, a station performing roaming operations (e.g., from multiple grid squares) can choose to have /TQSL/ assume that the log is correct. When call sign or home station are provided with the log, /TQSL/ will automatically update the details on the upload. Select “Override Station Location with QTH Details from your Log” on the “Log Handling” preference page to enable this feature.
This release also includes an update to the most recent /TQSL/ configuration file. /— Thanks to Rick Murphy, K1MU/

Re: New TQSL

Scott Davis
 

Thanks for the good information Steven.  I had not seen that.

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 the reason for the hope that you have. But do this with gentleness and respect...


-----Original Message-----
From: AI3KS <AI3KS.01@...>
To: N3FJPSoftwareUsers@groups.io
Sent: Tue, Apr 7, 2020 4:05 pm
Subject: [N3FJPSoftwareUsers] New TQSL

Scott,

Don't know if you have seen this yet, or if it will take changes to the software:

(From the ARRL Website)

The latest version of TrustedQSL (TQSL), version 2.5.2, offers improved Logbook of The World (LoTW) support for operations from several locations, as well as the ability to detect uploads that contain incorrect location data. The primary new feature in TQSL 2.5.2 allows logging programs, in conjunction with TQSL, to avoid incorrect contact uploads, while adding mechanisms to allow easy uploading of logs for roving stations. LoTW had required rovers to identify each location used as a separate location in TQSL. The new version of TQSL allows these operations to be handled much more smoothly by using information from the station’s logging program.
When a log is signed by TQSL, the station details — call Sign, DXCC entity, grid square, and other location details provided by the selected station location (and call sign certificate) — are compared with the details in the log. If the US state and station location in a log do not agree, TQSL 2.5.2 will reject the contact, detecting errors in instances when an incorrect station location has been chosen. This feature will necessitate changes in many logging programs, because it requires that the log provide station details previously not used by TQSL. Once a logging program supplies these (MY_STATE, MY_DXCC, MY_CQ_ZONE, etc.), then TQSL will validate them against the log. Currently, Cabrillo logs use the CALLSIGN field to verify that the contacts are for the correct call sign.
Optionally, a station performing roaming operations (e.g., from multiple grid squares) can choose to have TQSL assume that the log is correct. When call sign or home station are provided with the log, TQSL will automatically update the details on the upload. Select “Override Station Location with QTH Details from your Log” on the “Log Handling” preference page to enable this feature.
This release also includes an update to the most recent TQSL configuration file. — Thanks to Rick Murphy, K1MU   

New TQSL

AI3KS
 

Scott,

Don't know if you have seen this yet, or if it will take changes to the software:

(From the ARRL Website)

The latest version of TrustedQSL (TQSL), version 2.5.2, offers improved Logbook of The World (LoTW) support for operations from several locations, as well as the ability to detect uploads that contain incorrect location data. The primary new feature in TQSL 2.5.2 allows logging programs, in conjunction with TQSL, to avoid incorrect contact uploads, while adding mechanisms to allow easy uploading of logs for roving stations. LoTW had required rovers to identify each location used as a separate location in TQSL. The new version of TQSL allows these operations to be handled much more smoothly by using information from the station’s logging program.

When a log is signed by TQSL, the station details — call Sign, DXCC entity, grid square, and other location details provided by the selected station location (and call sign certificate) — are compared with the details in the log. If the US state and station location in a log do not agree, TQSL 2.5.2 will reject the contact, detecting errors in instances when an incorrect station location has been chosen. This feature will necessitate changes in many logging programs, because it requires that the log provide station details previously not used by TQSL. Once a logging program supplies these (MY_STATE, MY_DXCC, MY_CQ_ZONE, etc.), then TQSL will validate them against the log. Currently, Cabrillo logs use the CALLSIGN field to verify that the contacts are for the correct call sign.

Optionally, a station performing roaming operations (e.g., from multiple grid squares) can choose to have TQSL assume that the log is correct. When call sign or home station are provided with the log, TQSL will automatically update the details on the upload. Select “Override Station Location with QTH Details from your Log” on the “Log Handling” preference page to enable this feature.

This release also includes an update to the most recent TQSL configuration file. — Thanks to Rick Murphy, K1MU   

Last Names not recording in log

Frank C. D'Amato
 

Using N3FJP 6.6 and connected to QRZ lookup

Why do some callsigns populate both First and Last name in the name field, while others only populate the first name in the name field?

Video of Problem
https://youtu.be/xYUJHeXz8N0

Frank - KB2MXV

Re: One QSO 'Already Uploaded' - how to find it

Mark Steele
 

Found and fixed - thanks all!

Re: One QSO 'Already Uploaded' - how to find it

Mark Steele
 

Ugh - this is brutal - I have 29,000 contacts and they all have something in the S Conf By field (I upload to EQSL and Club Log) - i'll scroll to find the one that is missing the L

Re: One QSO 'Already Uploaded' - how to find it

Scott Davis
 

Hi Mark,

Thanks for your e-mail.  That QSO record won't be marked as Sent, so just List All and then click on the S header to sort.

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 the reason for the hope that you have. But do this with gentleness and respect...


-----Original Message-----
From: Mark Steele <kd2nom@...>
To: N3FJPSoftwareUsers@groups.io
Sent: Tue, Apr 7, 2020 1:45 pm
Subject: [N3FJPSoftwareUsers] One QSO 'Already Uploaded' - how to find it

All,

I have one QSO somewhere in my log that is tripping up my uploads to LoTW. Is there a direct way of finding it? I have already selected 're-signing' it.

Thank you

Re: One QSO 'Already Uploaded' - how to find it

Tom and Toni Hauer
 

Check the R conf by and S conf by columns on your contacts.  You need to scroll to the right on your contact screen, those columns are pretty far to the right.  There will be L in any row Sent to or Received by LOTW.  I had the same problem, The S conf by column wasn't checked for some reason on one of my contacts.

Tom, K0YA

On Tue, Apr 7, 2020 at 12:45 PM Mark Steele <kd2nom@...> wrote:
All,

I have one QSO somewhere in my log that is tripping up my uploads to LoTW. Is there a direct way of finding it? I have already selected 're-signing' it.

Thank you

One QSO 'Already Uploaded' - how to find it

Mark Steele
 

All,

I have one QSO somewhere in my log that is tripping up my uploads to LoTW. Is there a direct way of finding it? I have already selected 're-signing' it.

Thank you

Yaesu FTDX-101D SUB

Patrick Moonen
 

Hello,

Today made qso on my sub band but when I log qso it takes freq from MAIN and put also mode CW.
My Main band was also 20m DATA-U for FT8.
Can I fix this by changing settings ?

73 Pat - ON3CQ

Re: Invalid Amateur Call

Lou Everett, Sr.
 

Create a separate data base in ACLog and don’t upload them to LoTW.

Lou WA5LOU

On Tue, Apr 7, 2020 at 10:08 AM Bill <nc4mi@...> wrote:
I have a lot of MARS Radio calls in my log. The Special Event Station calls are being shown as an invalid call when I upload other calls to LoTW. These calls only have 3 letter characters as the call sign such as (NBL). They are used by MARS station during their Ham to MARS yearly Armed Forces Day crossband test. Is there a way I can work around the error message?

--
Lou WA5LOU


Re: Invalid Amateur Call

Christopher Scibelli
 

I don't bother logging those QSOs.  AC Log wasn't designed for a once a year event.  Maybe you could use a paper log for those becuz LoTW won't recognize them, either.

73,

Chris  NU1O


-----Original Message-----
From: Bill <nc4mi@...>
To: N3FJPSoftwareUsers <N3FJPSoftwareUsers@groups.io>
Sent: Tue, Apr 7, 2020 11:08 am
Subject: [N3FJPSoftwareUsers] Invalid Amateur Call

I have a lot of MARS Radio calls in my log. The Special Event Station calls are being shown as an invalid call when I upload other calls to LoTW. These calls only have 3 letter characters as the call sign such as (NBL). They are used by MARS station during their Ham to MARS yearly Armed Forces Day crossband test. Is there a way I can work around the error message?