Date   

Re: Last Names not recording in log

Frank C. D'Amato
 

Here is a brand new callsign that was just issued on 4/7/2020, I never had any contact with this callsign and looked it up today for the first time, The name field is only showing his fist name, but the comment field has his complete name?  How can this be?


--


Frank - KB2MXV


Re: Last Names not recording in log

Scott Davis
 

Hi Frank,

Thanks for your follow up.  The full name is either carried forward from a previous contact with the same station, or the Callbook data source that you have selected.

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: Wed, Apr 8, 2020 2:15 pm
Subject: Re: [N3FJPSoftwareUsers] Last Names not recording in log

Scott,

Where is the full name information come from in the Comments field? That data is always correct, its just the name field itself.
--


Frank - KB2MXV


Re: 599

Scott Davis
 

Hi Rino,

Thanks for your e-mail.  RST is not part of the CW Ops CWT exchange.  Therefore it is not included with the QSO record in the contest software or transferred via ADIF afterwards.

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: rino <ve9vic@...>
To: N3FJPSoftwareUsers@groups.io
Sent: Wed, Apr 8, 2020 12:30 pm
Subject: [N3FJPSoftwareUsers] 599

Hi Scott,  after the CWops cwt contest when I transfer my data to my main n3fjp log it’s ok for the cwops number as I enter N3FJP_SPCNUM  into the box reserved for cwops in my main log, it’s also worked with other logging program like n1mm that I use for some contest, thank , but when I transfer the data from the n3fjp contest log to my main log I don’t get the RST even if in the contest log I checked to* record rst line* and I set *cw default 599,* I have to edit one contact at the time in my main log , is there a way to do that otherwise ? of course in the contest log there is no rst on the screen.
 
73,
 
Rino, VE9VIC


Re: Last Names not recording in log

Frank C. D'Amato
 

Scott,

Where is the full name information come from in the Comments field? That data is always correct, its just the name field itself.
--


Frank - KB2MXV


599

VE9VIC...Rino
 

Hi Scott,  after the CWops cwt contest when I transfer my data to my main n3fjp log it’s ok for the cwops number as I enter N3FJP_SPCNUM  into the box reserved for cwops in my main log, it’s also worked with other logging program like n1mm that I use for some contest, thank , but when I transfer the data from the n3fjp contest log to my main log I don’t get the RST even if in the contest log I checked to* record rst line* and I set *cw default 599,* I have to edit one contact at the time in my main log , is there a way to do that otherwise ? of course in the contest log there is no rst on the screen.

 

73,

 

Rino, VE9VIC


Re: Change selected QSO date.

Lou Everett, Sr. <loueverettsr@...>
 

Your certificate has a start date for QSO’s that can be entered.  Usually this date will be when you officially received your current call sign.  Check this date in TQSL.

Lou WA5LOU

On Wed, Apr 8, 2020 at 11:16 AM bill graf <billgraf@...> wrote:
I am in the process of uploading to LOTW some of my old log books from 2001 and everything
going smooth. I'm getting around 7 to 8 QSL's per every 26 QSO log sheet.
Don't understand a date range on a LOTW Certificate? Please explain?
Bill K9RR

--
Lou WA5LOU



Re: MSQP - Log Submission Requirements

Megin Murphy
 

I confirmed with Malcolm, W5XX, who runs the QSO party, and he confirmed what Scott said.  Just send what the N3FJP software provides when exporting a Cabrillo file.

 

73, Megin, K5IJ

 

From: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io> On Behalf Of Jim Harris
Sent: Wednesday, April 8, 2020 11:20 AM
To: N3FJPSoftwareUsers@groups.io
Subject: Re: [N3FJPSoftwareUsers] MSQP - Log Submission Requirements

 

I thought the summary was a part of the file I sent.  Do I just send it as a separate attachment.

Forgive me as this is my first contest.

I had 61 contacts, 61 QSO points, 48 multipliers, for a total 2,928 points.

Jim Harris KF5TPT

(H) 662-893-3289

(C) 901-383-3104

U.S. Air Force Auxiliary


Treat everyone with politeness, even those who are rude to you,not because they are nice but because you are.

 

 

 

 

On Wed, Apr 8, 2020 at 8:32 AM Megin Murphy <meginamurphy@...> wrote:

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: MSQP - Log Submission Requirements

Jim Harris
 

I thought the summary was a part of the file I sent.  Do I just send it as a separate attachment.
Forgive me as this is my first contest.
I had 61 contacts, 61 QSO points, 48 multipliers, for a total 2,928 points.
Jim Harris KF5TPT
(H) 662-893-3289
(C) 901-383-3104
U.S. Air Force Auxiliary

Treat everyone with politeness, even those who are rude to you,not because they are nice but because you are.




On Wed, Apr 8, 2020 at 8:32 AM Megin Murphy <meginamurphy@...> wrote:

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: Change selected QSO date.

bill graf
 

I am in the process of uploading to LOTW some of my old log books from 2001 and everything
going smooth. I'm getting around 7 to 8 QSL's per every 26 QSO log sheet.
Don't understand a date range on a LOTW Certificate? Please explain?
Bill K9RR


Re: Change selected QSO date.

Larry Banks
 

Hi Bill, (call?),
 
Check your LoTW certificate date.  ACLog does not use your date for this at all.

73 -- Larry -- W1DYJ

 
 

From: Bill
Sent: Wednesday, April 08, 2020 11:53
Subject: [N3FJPSoftwareUsers] Change selected QSO date.
 
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: Change selected QSO date.

Lou Everett, Sr. <loueverettsr@...>
 

Are you within the date range of your LoTW Certificate?  I believe If you are trying to upload QSOs that you made before that date range, then they will bounce.  

Lou WA5LOU

On Wed, Apr 8, 2020 at 10:54 AM Bill <nc4mi@...> wrote:
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

--
Lou WA5LOU



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. 

7361 - 7380 of 48370