Date   

Change selected QSO date.

Bill
 

I'm in the process of adding all of my old QSO's to my log. When I tried to upload the QSO's to LoTW I got an error that stated that the QSO's were outside of the selected QSO date. I checked the N3FJP user guide but I didn't find anything that would tell me how to change the date. Do I just simply keep clicking ignore or is there a way to change the date? Thanks again for the best logger program on the market Scott. 73, Bill


Re: MSQP - Log Submission Requirements

Scott Davis
 

Hi Megin,

Thanks for your e-mail.  The Cabrillo file format specification doesn't provide fields for that level of detail (QSO points and multipliers).  Even the claimed score, which my software does provide, is an optional field in the Cabrilllo spec, that isn't required for submittal.  

State QSO party sponsors use log checking software to calculate all the scoring values from the Cabrillo files they receive.  Very few require anything other than the Cabrillo file.  I've supported the MS QSO Party for a good while now and I've not ever had a problem report on the Cabrillo file my software creates.

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: Megin Murphy <meginamurphy@...>
To: N3FJPSoftwareUsers@groups.io
Sent: Wed, Apr 8, 2020 9:32 am
Subject: [N3FJPSoftwareUsers] MSQP - Log Submission Requirements

For the Mississippi QSO Party we have the following log submission requirements:
 
Each log must include a scoring summary showing the number of QSOs points, the multiplier,
and score. Logs without a scoring summary will be considered as a check log.
Exporting via adif or cabrillo does not bring in the scoring summary.  Is there something else we can do to bring in that information with our log?
 
73, Megin, K5IJ


Re: New TQSL-ACLog Conflict

Larry Stowell K1ZW
 

Steve

Well that's a change have always used confirm all, it wasn't the updated TQSL

It was something ~ about 4/1. I just did as you suggested but use the default of 1902

and it worked fine and finally did the 4 since 4/1.

Larry K1ZW

On 4/8/2020 9:11 AM, AI3KS wrote:
Larry,

I had a similar problem a few days ago. In looking at the raw info from, doing an "all confirmed" did not start at the beginning of the log. I had to to a "confirmed since" and change the date back to 1972.

Steve, AI3KS

On 20/04/08 08:10, Larry Stowell K1ZW wrote:

Interesting I have 4 entries since 4/1, all previous entries had my name in the

operator field. The 4 since the 1st have my call. I have all the latest 6.6 and new TQSL.

Just today those 4 showed up in LoTW Now I can't download those 4.

I always do all confirmed and it process 16,000+ the file in in 5 seconds.

Strange happening in LoTW !!!

73 Larry K1ZW

On 4/7/2020 8:15 PM, WX7HS via groups.io wrote:

I have discovered a problem with ACLog and the new TQSL version. When the Operator field is filled ( for example my first name), an error occurs when trying to log a QSO With LoTW. This error shows up as an invalid date range of the call sign certificate.  When I deleted an entry in the operator field, the problem went away. 


I tried to find a batch process to delete the operator information in my log but could not find a solution. Is editing each QSO the only way to delete text in the operator field?
73

Howard

WX7HS



MSQP - Log Submission Requirements

Megin Murphy
 

For the Mississippi QSO Party we have the following log submission requirements:

 

Each log must include a scoring summary showing the number of QSOs points, the multiplier,

and score. Logs without a scoring summary will be considered as a check log.

Exporting via adif or cabrillo does not bring in the scoring summary.  Is there something else we can do to bring in that information with our log?

 

73, Megin, K5IJ


Re: New TQSL-ACLog Conflict

AI3KS
 

Larry,

I had a similar problem a few days ago. In looking at the raw info from, doing an "all confirmed" did not start at the beginning of the log. I had to to a "confirmed since" and change the date back to 1972.

Steve, AI3KS

On 20/04/08 08:10, Larry Stowell K1ZW wrote:

Interesting I have 4 entries since 4/1, all previous entries had my name in the

operator field. The 4 since the 1st have my call. I have all the latest 6.6 and new TQSL.

Just today those 4 showed up in LoTW Now I can't download those 4.

I always do all confirmed and it process 16,000+ the file in in 5 seconds.

Strange happening in LoTW !!!

73 Larry K1ZW

On 4/7/2020 8:15 PM, WX7HS via groups.io wrote:

I have discovered a problem with ACLog and the new TQSL version. When the Operator field is filled ( for example my first name), an error occurs when trying to log a QSO With LoTW. This error shows up as an invalid date range of the call sign certificate.  When I deleted an entry in the operator field, the problem went away. 


I tried to find a batch process to delete the operator information in my log but could not find a solution. Is editing each QSO the only way to delete text in the operator field?
73

Howard

WX7HS



Re: New TQSL

Mike Olbrisch
 

Good morning Scott.

 

Reading the description below, it seems like something is going on automatically when your operating location isn’t your home location.

 

by using information from the station’s logging program.”

 

Anything new and “Automatic” sounds scary.  I have nearly 100 portable locations saved in T-QSL.  And it’s been working fine for 10 years.  Until I figure out what they are comparing to decide if my operating location is right or not, it is worrisome.  Until this virus thing is over, I won’t be operating anything portable anyway.

 

Vy73 – Mike – KD5KC

El Paso, Texas – DM61rt

 

 

 

From: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io> On Behalf Of Scott Davis via groups.io
Sent: Tuesday, April 7, 2020 17:03 PM
To: N3FJPSoftwareUsers@groups.io
Subject: Re: [N3FJPSoftwareUsers] New TQSL

 

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...

 

 

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-ACLog Conflict

Larry Stowell K1ZW
 

Interesting I have 4 entries since 4/1, all previous entries had my name in the

operator field. The 4 since the 1st have my call. I have all the latest 6.6 and new TQSL.

Just today those 4 showed up in LoTW Now I can't download those 4.

I always do all confirmed and it process 16,000+ the file in in 5 seconds.

Strange happening in LoTW !!!

73 Larry K1ZW

On 4/7/2020 8:15 PM, WX7HS via groups.io wrote:

I have discovered a problem with ACLog and the new TQSL version. When the Operator field is filled ( for example my first name), an error occurs when trying to log a QSO With LoTW. This error shows up as an invalid date range of the call sign certificate.  When I deleted an entry in the operator field, the problem went away. 


I tried to find a batch process to delete the operator information in my log but could not find a solution. Is editing each QSO the only way to delete text in the operator field?
73

Howard

WX7HS


Re: New TQSL-ACLog Conflict

Scott Davis
 

Hi Howard,

Thanks for your e-mail.  I'm sorry that you have run into trouble.  The Operator field is intended for your call sign.  You could contact the LoTW folks to see if there is a way to set TQSL to override the operator value check.

If not, ADIF Master is likely your best option.  Additional details are here:


http://www.n3fjp.com/faq.html#q63

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: WX7HS via groups.io <WX7HS@...>
To: N3FJPSoftwareUsers@groups.io
Sent: Tue, Apr 7, 2020 8:15 pm
Subject: Re: [N3FJPSoftwareUsers] New TQSL-ACLog Conflict

I have discovered a problem with ACLog and the new TQSL version. When the Operator field is filled ( for example my first name), an error occurs when trying to log a QSO With LoTW. This error shows up as an invalid date range of the call sign certificate.  When I deleted an entry in the operator field, the problem went away. 

I tried to find a batch process to delete the operator information in my log but could not find a solution. Is editing each QSO the only way to delete text in the operator field?
73

Howard

WX7HS


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

Mark Steele
 

Dave, none of my log entries have a blank for that field. Because I log to LoTW, eQSL, Club Log and paper, every log entry has at a minimum of two entries (EB) so I had to scroll thru 29K+ looking for one that was missing an 'L'. My eyes are old and tired. It took a little bit. 


Re: Yaesu FTDX-101D Main & SUB

Scott Davis
 

Hi Pat,

Thanks for your e-mail.  I'm not familiar with the Yaesu FTDX-101D, so I don't know if there is a way to set the rig to return the active VFO.  Perhaps others in the group will have some useful insights for you.

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: Patrick Moonen <onl4008@...>
To: N3FJPSoftwareUsers@groups.io
Sent: Wed, Apr 8, 2020 4:42 am
Subject: [N3FJPSoftwareUsers] Yaesu FTDX-101D Main & SUB

Hello, 

When I switch radio from MAIN to SUB my logbook does not follow. 
It only keeps displaying the info of the MAIN. 

73 Pat - ON3CQ


Re: CWOPS

Scott Davis
 

Hi Mel,

Thanks for your e-mail.  Windows will only allow one iteration of each program installed at a time, but you can certainly have both CWOPS Open and CWOPS CWT on your PC simultaneously.  Just be sure that you have uninstalled the previous version(s) of the software first.

Upgrade steps are here:


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: Mel Marcus <melm@...>
To: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io>
Sent: Tue, Apr 7, 2020 8:43 pm
Subject: [N3FJPSoftwareUsers] CWOPS

Scott

I tried to download both CWOPS contest programs but it seems like only one can be installed at anyone time. is this the way it is supposed to be

Mel
NE9A



You receive all messages sent to this group.

This user group is a great forum for asking questions and sharing ideas with the valuable resource of both new and experienced N3FJP Software users, but it does get busy. There is an easy way to cut down on the e-mail volume.

If you only want to receive announcements from Kimberly and me regarding upgrades and new products, please join our "announcements only" list instead. We keep e-mail to the "announcements only" list to an absolute minimum. Please join here:

https://groups.io/g/N3FJPSoftware

Then unsubscribe from this user group by sending a blank e-mail to:N3FJPSoftwareUsers+unsubscribe@groups.io

As always, thanks for your interest, kind thoughts, support and spreading the word about our software!

73, Scott & Kimberly
N3FJP & KA3SEQ
http://www.n3fjp.com/

Serving the Amateur Radio Community with general logging and contesting software since 1997.
Your Subscription | Contact Group Owner | Unsubscribe [melm@...]


Re: New TQSL-ACLog Conflict

WX7HS@...
 

I have discovered a problem with ACLog and the new TQSL version. When the Operator field is filled ( for example my first name), an error occurs when trying to log a QSO With LoTW. This error shows up as an invalid date range of the call sign certificate.  When I deleted an entry in the operator field, the problem went away. 


I tried to find a batch process to delete the operator information in my log but could not find a solution. Is editing each QSO the only way to delete text in the operator field?
73

Howard

WX7HS


Yaesu FTDX-101D Main & SUB

Patrick Moonen
 

Hello, 

When I switch radio from MAIN to SUB my logbook does not follow. 
It only keeps displaying the info of the MAIN. 

73 Pat - ON3CQ


CWOPS

Mel Marcus
 

Scott

I tried to download both CWOPS contest programs but it seems like only one can be installed at anyone time. is this the way it is supposed to be

Mel
NE9A




You receive all messages sent to this group.

This user group is a great forum for asking questions and sharing ideas with the valuable resource of both new and experienced N3FJP Software users, but it does get busy. There is an easy way to cut down on the e-mail volume.

If you only want to receive announcements from Kimberly and me regarding upgrades and new products, please join our "announcements only" list instead. We keep e-mail to the "announcements only" list to an absolute minimum. Please join here:

https://groups.io/g/N3FJPSoftware

Then unsubscribe from this user group by sending a blank e-mail to:N3FJPSoftwareUsers+unsubscribe@groups.io

As always, thanks for your interest, kind thoughts, support and spreading the word about our software!

73, Scott & Kimberly
N3FJP & KA3SEQ
http://www.n3fjp.com/

Serving the Amateur Radio Community with general logging and contesting software since 1997.
Your Subscription | Contact Group Owner | Unsubscribe [melm@...]
_._,_._,_


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