Date   

Re: NU4N/qrp

Scott Davis
 

Hi Dave,

Dennis is correct.  You can't use the / character as part of a file name.  Just stick to letters and numbers and you will be fine.

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: Dennis - WU6X <wu6x@...>
To: N3FJPSoftwareUsers@groups.io
Sent: Wed, Apr 29, 2020 9:33 am
Subject: Re: [N3FJPSoftwareUsers] NU4N/qrp

Hi Dave,
I just did something similar ... however, on Bart's suggestion at ARRL, I used my call only in TQSL, then "named" the station location during the last step in creating a new station in TSQL. Then, when uploading to LOTW from within N3FJP, I select the desired station location from the dropdown and everything worked just fine. In my case, I was trying to setup a "/4" for one of the remote bases I use on the East coast. Bart suggested I just use my call only, no appendage, and then name the new location appropriately in TSQL.
Hopefully that works for you,
73, Dennis - WU6X


Re: DELEWARE QSO OUT OF STATE

Mike Olbrisch
 

Sorry about the Support load Scott.  Some of us try to head off the stuff we know.  But no one is as expert as you.  Without your direct intervention several years ago, I would have been stuck on version 3.x until I changed computers.  Who would have ever suspected a missing FONT would cause a failure to load!

 

Stay safe, stay healthy.  We’ll continue to help when we can.

 

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 Scott Davis via groups.io
Sent: Wednesday, April 29, 2020 8:19 AM
To: N3FJPSoftwareUsers@groups.io
Subject: Re: [N3FJPSoftwareUsers] DELEWARE QSO OUT OF STATE

 

Hi Dave,

 

Thanks for your e-mail.  I had hoped to support DE again (I used to, but had to drop DE support after a rule change) before their contest this time, but with all the other projects, and especially the daily, overflowing support e-mail volume, there just hasn't been close to an opportunity for the coding time required.

 

Please see this FAQ 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: Dave via groups.io <kc3am@...>
To: N3FJPSoftwareUsers@groups.io
Sent: Wed, Apr 29, 2020 9:07 am
Subject: Re: [N3FJPSoftwareUsers] DELEWARE QSO OUT OF STATE

Hey Scott,

What software would you suggest for me being in Delaware and operating the QSO party.

Dave KC3AM

On 04/28/2020 16:24, Scott Davis via groups.io wrote:

Hi Mel,

 

Thanks for your e-mail.  Sorry, I don't currently support the DE party at this time.

 

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 28, 2020 3:44 pm
Subject: [N3FJPSoftwareUsers] DELEWARE QSO OUT OF STATE

I am unable to locate the deleware out of state qso part logging program

 

Mel

NE9A

-------- Original Message --------
Subject: Re: [N3FJPSoftwareUsers] ASlog w/ fldigi crashes on TX
From: "Paul" <nh7wb@...>
Date: Tue, April 28, 2020 11:01 am
To: N3FJPSoftwareUsers@groups.io

Agreed,  I have been working on that,  still, cant see how it worked so well so long before problem arose.  have lots of chokes. obviously need more.

--
73, Dave KC3AM


Re: DELEWARE QSO OUT OF STATE

Scott Davis
 

Hi Dave,

Thanks for your e-mail.  I had hoped to support DE again (I used to, but had to drop DE support after a rule change) before their contest this time, but with all the other projects, and especially the daily, overflowing support e-mail volume, there just hasn't been close to an opportunity for the coding time required.

Please see this FAQ here:


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

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 via groups.io <kc3am@...>
To: N3FJPSoftwareUsers@groups.io
Sent: Wed, Apr 29, 2020 9:07 am
Subject: Re: [N3FJPSoftwareUsers] DELEWARE QSO OUT OF STATE

Hey Scott,
What software would you suggest for me being in Delaware and operating the QSO party.
Dave KC3AM
On 04/28/2020 16:24, Scott Davis via groups.io wrote:
Hi Mel,

Thanks for your e-mail.  Sorry, I don't currently support the DE party at this time.


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 28, 2020 3:44 pm
Subject: [N3FJPSoftwareUsers] DELEWARE QSO OUT OF STATE

I am unable to locate the deleware out of state qso part logging program

Mel
NE9A
-------- Original Message --------
Subject: Re: [N3FJPSoftwareUsers] ASlog w/ fldigi crashes on TX
From: "Paul" <nh7wb@...>
Date: Tue, April 28, 2020 11:01 am
To: N3FJPSoftwareUsers@groups.io

Agreed,  I have been working on that,  still, cant see how it worked so well so long before problem arose.  have lots of chokes. obviously need more.
--
73, Dave KC3AM


Re: NU4N/qrp

Dennis - WU6X
 

Hi Dave,
I just did something similar ... however, on Bart's suggestion at ARRL, I used my call only in TQSL, then "named" the station location during the last step in creating a new station in TSQL. Then, when uploading to LOTW from within N3FJP, I select the desired station location from the dropdown and everything worked just fine. In my case, I was trying to setup a "/4" for one of the remote bases I use on the East coast. Bart suggested I just use my call only, no appendage, and then name the new location appropriately in TSQL.
Hopefully that works for you,
73, Dennis - WU6X


Re: DELEWARE QSO OUT OF STATE

Dave
 

Hey Scott,

What software would you suggest for me being in Delaware and operating the QSO party.

Dave KC3AM

On 04/28/2020 16:24, Scott Davis via groups.io wrote:
Hi Mel,

Thanks for your e-mail.  Sorry, I don't currently support the DE party at this time.


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 28, 2020 3:44 pm
Subject: [N3FJPSoftwareUsers] DELEWARE QSO OUT OF STATE

I am unable to locate the deleware out of state qso part logging program

Mel
NE9A
-------- Original Message --------
Subject: Re: [N3FJPSoftwareUsers] ASlog w/ fldigi crashes on TX
From: "Paul" <nh7wb@...>
Date: Tue, April 28, 2020 11:01 am
To: N3FJPSoftwareUsers@groups.io

Agreed,  I have been working on that,  still, cant see how it worked so well so long before problem arose.  have lots of chokes. obviously need more.
--
73, Dave KC3AM


NU4N/qrp

 

Hello Scott how are ya ?

Hey i made a new logbook using NU4N/qrp. But in the LOTW page I changed the call to NU4N/qrp with correct password and named the location qrp which match's the TQL locatiom.
The upload works great but I get an error when I want download from LOTW.
Any help apppreciated
73 Ya'll take care.


Re: DELEWARE QSO OUT OF STATE

Mel Marcus
 

That is ok . last time what I wanted was there but I did not see it.

all set up for the upcoming qso parties this weekend. 

Best to you and Kim

Mel

-------- Original Message --------
Subject: Re: [N3FJPSoftwareUsers] DELEWARE QSO OUT OF STATE
From: "Scott Davis via groups.io" <SNKDavis@...>
Date: Tue, April 28, 2020 3:24 pm
To: "N3FJPSoftwareUsers@groups.io" <N3FJPSoftwareUsers@groups.io>

Hi Mel,

Thanks for your e-mail.  Sorry, I don't currently support the DE party at this time.


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 28, 2020 3:44 pm
Subject: [N3FJPSoftwareUsers] DELEWARE QSO OUT OF STATE

I am unable to locate the deleware out of state qso part logging program

Mel
NE9A
-------- Original Message --------
Subject: Re: [N3FJPSoftwareUsers] ASlog w/ fldigi crashes on TX
From: "Paul" <nh7wb@...>
Date: Tue, April 28, 2020 11:01 am
To: N3FJPSoftwareUsers@groups.io

Agreed,  I have been working on that,  still, cant see how it worked so well so long before problem arose.  have lots of chokes. obviously need more.


Re: DELEWARE QSO OUT OF STATE

Scott Davis
 

Hi Mel,

Thanks for your e-mail.  Sorry, I don't currently support the DE party at this time.


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 28, 2020 3:44 pm
Subject: [N3FJPSoftwareUsers] DELEWARE QSO OUT OF STATE

I am unable to locate the deleware out of state qso part logging program

Mel
NE9A
-------- Original Message --------
Subject: Re: [N3FJPSoftwareUsers] ASlog w/ fldigi crashes on TX
From: "Paul" <nh7wb@...>
Date: Tue, April 28, 2020 11:01 am
To: N3FJPSoftwareUsers@groups.io

Agreed,  I have been working on that,  still, cant see how it worked so well so long before problem arose.  have lots of chokes. obviously need more.


DELEWARE QSO OUT OF STATE

Mel Marcus
 

I am unable to locate the deleware out of state qso part logging program

Mel
NE9A

-------- Original Message --------
Subject: Re: [N3FJPSoftwareUsers] ASlog w/ fldigi crashes on TX
From: "Paul" <nh7wb@...>
Date: Tue, April 28, 2020 11:01 am
To: N3FJPSoftwareUsers@groups.io

Agreed,  I have been working on that,  still, cant see how it worked so well so long before problem arose.  have lots of chokes. obviously need more.


Re: Installation never completes.

ku4cg@...
 

Thanks Scott I got it working. 


Re: ASlog w/ fldigi crashes on TX

Paul
 

Agreed,  I have been working on that,  still, cant see how it worked so well so long before problem arose.  have lots of chokes. obviously need more.


Re: ASlog w/ fldigi crashes on TX

Scott Davis
 

Hi Paul,

Thanks for your e-mail.  Those are classic symptoms of RF in the shack.  You'll need to correct that before the software will function properly.

Good luck!

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: Paul <nh7wb@...>
To: N3FJPSoftwareUsers@groups.io
Sent: Tue, Apr 28, 2020 11:11 am
Subject: [N3FJPSoftwareUsers] ASlog w/ fldigi crashes on TX

all was working fine with ts-590s suddenly had fldigi freeze on TX with ant1, had to close and reopen , worked fine on ant2
then failed again on ant1.  got error msg, cant remember but about conflict with com port?  also lost rig control on AClog but could reestablish with settings.   tried several times, same result.


ASlog w/ fldigi crashes on TX

Paul
 

all was working fine with ts-590s suddenly had fldigi freeze on TX with ant1, had to close and reopen , worked fine on ant2
then failed again on ant1.  got error msg, cant remember but about conflict with com port?  also lost rig control on AClog but could reestablish with settings.   tried several times, same result.


Re: Partial Duplicate QSOs...

Scott Davis
 

Hi Dale,

Thanks for your e-mail.  When you download records from LoTW, one of two things happen.  Either existing records are marked appropriately (and not added a second time), or you will receive the prompt letting you know that one or more records not currently in your database were downloaded and give you the option to add them.  If you answer No, then there won't be any additional records added.

The criteria for a match are as follows:

-  The callsign must match the call of the station worked.

-  The band must match the band of the station worked.

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

So, for your added records, something in the criteria is not matched.  My guess would be the data format.

The records without the additional detail are the ones you just downloaded from LoTW.  LoTW does not maintain all the QSO record detail on their database.

I hope that this helps.

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: Dale Martin <kg5u@...>
To: N3FJPSoftwareUsers@groups.io
Sent: Tue, Apr 28, 2020 10:42 am
Subject: [N3FJPSoftwareUsers] Partial Duplicate QSOs...

 
In September of last year, I purchased the ACL Log. I immediately loaded it with most of my N1MM ADIFs and ADIFs from textfiles from a logger program I wrote in VB5 years ago.  That amounted to 29k+ QSOs in the ACL—I have not and probably won’t load the 55k+ CWops CWT contest log entries).  Last night, I believe I have finally finished editing the ACL log to my satisfaction, removing duplicates, ‘cleaning up’ line items (inserting default RSTs, Frequencies, and such), writing vba macros to do the clean-ups, and finally getting the log looking ‘nice’.
 
This morning I went through the log and confirmed it does, indeed, to my way of believing how a log should look, look ‘nice’. At least, now when I look at the log, I no longer have a great compulsion to spend time ‘fixing’ the visible entries; meaning more on-the-air time.
 
Then, I went and downloaded the latest (since March) LOTW confirmations.
 
Fortunately, there were only about 40 or 50 of them. I picked one and entered it in the ACL Logsheet Call entry field to see what other QSOs I may have had with that station. What came up were two entries, one a partial duplicate of the other. I looked at my Excel version of the ACL log contents and the QSO was there with the QSL-S & R fields both a ‘N’.
 
In the ACL Log, that QSO entry is now blue and the QSL-S & R fields are both a ‘Y’. I’m okay with that. However, the second entry in the ACL log for the same QSO, is blue with both QSL-S & R fields both a ‘Y’.  But, it is showing empty Frequency, RST-S and -R’s, Off times, and Grid squares, telling me it was the confirmation just downloaded from LOTW. Why is the LOTW download function ADDING and entry and not just updating it?  
 
Also, another call in my ‘new’ log with the QSL-S/R  tags showing ‘Y’s and the LOTW QSL S/R tags are showing ‘Y’ also received a duplicate confirmation also. Why is that?
 
Is this duplication thing normal? Do I now have to go through my log every time I download an updated LOTW confirmation and manually remove the partial duplicate QSOs?
 
Is that listing of LOTW downloads that appears on the ACL LOTW page kept anywhere to access and view outside of ACL?
 
Did I do something wrong that I’m seeing and having to edit out these duplicates?
 
73,
Dale, kg5u
 


Partial Duplicate QSOs...

Dale Martin, KG5U
 

 

In September of last year, I purchased the ACL Log. I immediately loaded it with most of my N1MM ADIFs and ADIFs from textfiles from a logger program I wrote in VB5 years ago.  That amounted to 29k+ QSOs in the ACL—I have not and probably won’t load the 55k+ CWops CWT contest log entries).  Last night, I believe I have finally finished editing the ACL log to my satisfaction, removing duplicates, ‘cleaning up’ line items (inserting default RSTs, Frequencies, and such), writing vba macros to do the clean-ups, and finally getting the log looking ‘nice’.

 

This morning I went through the log and confirmed it does, indeed, to my way of believing how a log should look, look ‘nice’. At least, now when I look at the log, I no longer have a great compulsion to spend time ‘fixing’ the visible entries; meaning more on-the-air time.

 

Then, I went and downloaded the latest (since March) LOTW confirmations.

 

Fortunately, there were only about 40 or 50 of them. I picked one and entered it in the ACL Logsheet Call entry field to see what other QSOs I may have had with that station. What came up were two entries, one a partial duplicate of the other. I looked at my Excel version of the ACL log contents and the QSO was there with the QSL-S & R fields both a ‘N’.

 

In the ACL Log, that QSO entry is now blue and the QSL-S & R fields are both a ‘Y’. I’m okay with that. However, the second entry in the ACL log for the same QSO, is blue with both QSL-S & R fields both a ‘Y’.  But, it is showing empty Frequency, RST-S and -R’s, Off times, and Grid squares, telling me it was the confirmation just downloaded from LOTW. Why is the LOTW download function ADDING and entry and not just updating it?  

 

Also, another call in my ‘new’ log with the QSL-S/R  tags showing ‘Y’s and the LOTW QSL S/R tags are showing ‘Y’ also received a duplicate confirmation also. Why is that?

 

Is this duplication thing normal? Do I now have to go through my log every time I download an updated LOTW confirmation and manually remove the partial duplicate QSOs?

 

Is that listing of LOTW downloads that appears on the ACL LOTW page kept anywhere to access and view outside of ACL?

 

Did I do something wrong that I’m seeing and having to edit out these duplicates?

 

73,

Dale, kg5u

 


Re: LOTW UPload

Tom & Barb Valosin
 

Fred and others:

If it is any help: Many of the programs that list the grid square are based on the grid square of the Post Office, not the actual grid square of the station.

I had to correct mine on the Buckmaster program a coupe of years ago and since then it comes up correctly.

Tom, WB2KLD

On 4/27/2020 2:30 PM, fred.libby@... wrote:
New Info.My problem was an incorrect grid square info related to my station location in  TQSL. My grid square is CM98iq. The incorrect data was CM98hq. I don't know how long the wrong data was there, however the latest TSQL Version 2.5.2 included the ability to detect incorrect location data. As soon as I corrected the error all my uploads are accepted.. The suppressed files are are now in my log.


Re: Power settings

John K9IJ
 

Ruarto,

Are you logging FT8 qsos with JTAlert ?

John - K9IJ

On 4/27/2020 12:54 PM, Ruarto wrote:

I normally stay at one power setting (45w) but occasionally will pump it up to 90.

But each qso it logs as 95w.    How can I change it so that I don’t have to go back and edit each and every entry?

 

 

 

Sent from Mail for Windows 10

 


-- 
No trees were killed in the sending of this message. However, a large number of electrons were terribly inconvenienced !

k9ij@...
Webmaster, Network Admin, Janitor


Re: LOTW UPload

Scott Davis
 

Hi,

Thanks for the good report!

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-----
To: N3FJPSoftwareUsers@groups.io
Sent: Mon, Apr 27, 2020 2:30 pm
Subject: Re: [N3FJPSoftwareUsers] LOTW UPload

New Info.My problem was an incorrect grid square info related to my station location in  TQSL. My grid square is CM98iq. The incorrect data was CM98hq. I don't know how long the wrong data was there, however the latest TSQL Version 2.5.2 included the ability to detect incorrect location data. As soon as I corrected the error all my uploads are accepted.. The suppressed files are are now in my log.


Re: Power settings

Scott Davis
 

Hi Ruarto,

Thanks for your e-mail.  AC Log always defaults to the last power entered on subsequent contacts.  Just be sure to enter the proper power level any time you change power and the following QSOs will automatically have the correct value.

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: Ruarto <rhgalyan@...>
To: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io>
Sent: Mon, Apr 27, 2020 1:54 pm
Subject: [N3FJPSoftwareUsers] Power settings

I normally stay at one power setting (45w) but occasionally will pump it up to 90.
But each qso it logs as 95w.    How can I change it so that I don’t have to go back and edit each and every entry?
 
 
 
Sent from Mail for Windows 10
 


Re: Installation never completes.

Scott Davis
 

Hi KU4CQ,

Thanks for your e-mail.  I'm sorry that you've run into trouble.  It sounds like your Internet protection software is clamping down on the installer.  Giving the installer the proper permissions in you protection software will correct 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: ku4cg via groups.io <ku4cg@...>
To: N3FJPSoftwareUsers@groups.io
Sent: Mon, Apr 27, 2020 1:41 pm
Subject: [N3FJPSoftwareUsers] Installation never completes.

I am trying to install the FD log on a Windows 10 Dell Laptop. The installer starts then disappears. Any help would be welcome.