1. N3FJPSoftwareUsers@groups.io
  2. Messages
   Date   
Re: Under eLogs/LOTW ALL DATA no longer works properly

Dave
 

I meant to say I use All Since now not Confirmed Since.

Dave
k4em
Re: Help with VSPE

Dave C
 

Larry,

I'm using the 64 bit version of VSPE.  Sorry you're having trouble.  Make sure the baud rate, handshaking (DTR & RTS), and no. of stop bits are all the same for all the devices/applications that are using the shared COM port.

Good luck,
Dave, K8WDA
Reminder: Use RAC for Today's Hamvention QSO Party!

Scott Davis
 

Hi All,

Just a reminder to use the RAC Contest Log for today's Hamvention QSO Party, since it is set up for dupe checking for both SSB and CW, with entry fields that can be used for this event. 

The Hamvention exchange is signal report and first year in attendance (enter 2020 if never attended), so just enter the year in the Prov / Serial field. The scoring is just the number of QSOs, so ignore the score statistics and just report your total QSOs, + (number of contacts with W8BI X 10) to 3830 Scores.  On the Setup form, you can leave the Province field blank.

You'll find the complete Hamvention QSO Party rules here:  https://wwrof.org/hamvention-qso-party/

And the RAC software here:  http://www.n3fjp.com/rac.html

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...
Re: 6.6 Upgrade and font issues

Scott Davis
 

Hi AB8WD,

Thanks for your e-mail.  I'm sorry that you have run into trouble.  I don't know why you would be experiencing that.  Please try clicking Reset to Default, close and restart the software and see if the fonts display okay.

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: AB8WD via groups.io <AB8WD@...>
To: N3FJPSoftwareUsers@groups.io
Sent: Fri, May 15, 2020 6:12 pm
Subject: Re: [N3FJPSoftwareUsers] 6.6 Upgrade and font issues

I have to do this every time I open the software it never keeps the setting.

Re: Help with VSPE

Don Munson
 

I use the 64 bit version and it works just as described below.  I used the 32 bit version on an old Win 7 machine and it works perfectly as well.

 

Once “gotcha” is to have to watch the port settings you assign to the new comport and make that match exactly in AC Log.  If the virtual port is at 19.2 then you have to set your rig control to 19.2 or whatever the speed is.  That trips me up when I switch between my TS2K COM Port and my IC7300 comport in AC Log for control.

 

W4GFQ

 

From: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io> On Behalf Of Larry Krist
Sent: Friday, May 15, 2020 11:27 PM
To: N3FJPSoftwareUsers@groups.io
Subject: Re: [N3FJPSoftwareUsers] Help with VSPE

 

Dave is this the 64 bit of 32 bit version, I cannot get it to work with ac log at all.

Larry  N8CWU

On 5/14/2020 3:08 PM, Dave C via groups.io wrote:

Angelo,
I'm using VSPE successfully to share or "split" the single com port on my TS-590SG with several applications on my PC including ACLOG and WSJT-X.  Attached is a screen shot of my VSPE splitter configuration.  Hopefully the picture will provide the help needed.  The baud rate is obviously your choice.  Just be sure the 590 and all applications are set to the same rate.  Also remember that the 590 has to be completely powered down and restarted for a baud rate change to take effect.

I think VSPE must sense the processor type and therefore requires a license if it is 64 bit.  Also, you may want to consider using a higher COM number for the virtual serial port just to assure no conflict with other COM ports on your PC.

Good luck,
Dave, K8WDA
Re: Help with VSPE

Larry Krist - N8CWU
 

Dave is this the 64 bit of 32 bit version, I cannot get it to work with ac log at all.

Larry  N8CWU

On 5/14/2020 3:08 PM, Dave C via groups.io wrote:

Angelo,
I'm using VSPE successfully to share or "split" the single com port on my TS-590SG with several applications on my PC including ACLOG and WSJT-X.  Attached is a screen shot of my VSPE splitter configuration.  Hopefully the picture will provide the help needed.  The baud rate is obviously your choice.  Just be sure the 590 and all applications are set to the same rate.  Also remember that the 590 has to be completely powered down and restarted for a baud rate change to take effect.

I think VSPE must sense the processor type and therefore requires a license if it is 64 bit.  Also, you may want to consider using a higher COM number for the virtual serial port just to assure no conflict with other COM ports on your PC.

Good luck,
Dave, K8WDA
Re: 6.6 Upgrade and font issues

AB8WD-Willie
 

I have to do this every time I open the software it never keeps the setting.
Re: 6.6 Upgrade and font issues

Scott Davis
 

Hi Thomas,

Thanks for your e-mail.  Here is the button that you are looking for:

FontBearingDistance.JPG



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: Chip Harleman <twhjr@...>
To: N3FJPSoftwareUsers@groups.io
Sent: Fri, May 15, 2020 4:20 pm
Subject: [N3FJPSoftwareUsers] 6.6 Upgrade and font issues

Know this isn't a big deal but, after I upgraded to Version 6.6 from 6.5, the font size for bearing, miles, cont, qsl's and times are so small I can barely see them on 1080P.  I read the release notes and saw ... "Font control for bearing, miles, time, etc. (click Settings > Appearance > Colors & Fonts) ...  I read what I could find but how does one increase the font size for just these fields?

Thanks to the group.

Thomas, W6TWH

6.6 Upgrade and font issues

Chip Harleman
 

Know this isn't a big deal but, after I upgraded to Version 6.6 from 6.5, the font size for bearing, miles, cont, qsl's and times are so small I can barely see them on 1080P.  I read the release notes and saw ... "Font control for bearing, miles, time, etc. (click Settings > Appearance > Colors & Fonts) ...  I read what I could find but how does one increase the font size for just these fields?

Thanks to the group.

Thomas, W6TWH
Re: Under eLogs/LOTW ALL DATA no longer works properly

Jim Shorney
 

The way I understand how this works from watching it all these years is that the "SINCE" queries for new *confirmations* that have come in since the selected date, independent of the actual the QSO date. If you look at your display of downloaded data you sill see a R Date that the confirmation was received by LoTW. I routinely see confirmations for Qs as far back as 1999 just doing a "SINCE". See attached photo of a run I just did; you will see an R Date of yesterday for two contacts made in 2000 and 2001. So there is no real need to use ALL DATA, you don't gain anything and it takes extra time. I do occasionally roll the "SINCE" date back a few months because I am a bit paranoid about missing one because the streams crossed. Still much quicker than using ALL. 16,000+ in my log.

73

-Jim
NU0C

On Fri, 15 May 2020 08:53:30 -0400
"Bob Stothfang" <bobstothfang@gmail.com> wrote:

Occasionally though I would use "All Data" to do a complete look back to
see if someone from way back decided to upload their log and every now
and then I would get a confirmation from the early days. I knew it would
take some time to process the whole log so I would start it and then do
something else and check back later. Maybe even something non-HAM related.
Re: Under eLogs/LOTW ALL DATA no longer works properly

Scott Davis
 

Hi Bob,

Thanks for your thoughts and comments.  All Data stopped working after ARRL made a change to how their server responds to the query.  I'm not directly involved with the LoTW folks, so I don't have anything more specific than that.

The next release will default to a date older than all of us (unless any of us are over 120) for All Data, so the functionality will be restored.

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: Bob Stothfang <bobstothfang@...>
To: N3FJPSoftwareUsers@groups.io
Sent: Fri, May 15, 2020 8:53 am
Subject: Re: [N3FJPSoftwareUsers] Under eLogs/LOTW ALL DATA no longer works properly

Scott

I'm too am curious...What changed to cause "All Data" to stop working? I suspect LoTW is the culprit.

I have never used "Confirmed Since".

I have been using your ACL for five years and up until a couple of months ago I have only used two buttons to check LoTW for confirmations. Early on I would just use "All Data" until my log size reached a point where it would take too long to process. That was about the size when your software started warning about the time involved (log size over 1000 QSOs) to use "All Data". I then switched to using "All Since" and would adjust the date accordingly to a date in the recent past, maybe a week or a couple of months time frame. This made the processing time tolerable.

Occasionally though I would use "All Data" to do a complete look back to see if someone from way back decided to upload their log and every now and then I would get a confirmation from the early days. I knew it would take some time to process the whole log so I would start it and then do something else and check back later. Maybe even something non-HAM related.

About a month or two ago I started one of these complete "look backs" and I noticed that it completed VERY QUICKLY, even before I got up from the  desk. I solved the problem by using "All Since" with the "since" date being day #1 for my log. It still takes the "walk away from the desk " time to process since I told it to do everything in the log, but it does work.

Thanks for your GREAT SOFTWARE PACKAGE and all the work you do to update and support it.
I recommend it highly to anyone in need of logging software.

73,

Bob - W8RES

    

On 05/15/2020 07:51, Scott Davis via groups.io wrote:
Hi Dave,

You should routinely use All Since, not Confirmed Since, so that your sent but unconfirmed records are marked as well.  

I am going to reorder those buttons on the LoTW form in the next release.

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 <k4em@...>
To: N3FJPSoftwareUsers@groups.io
Sent: Fri, May 15, 2020 6:45 am
Subject: Re: [N3FJPSoftwareUsers] Under eLogs/LOTW ALL DATA no longer works properly

Soon after I started using ACLog I had an issue with Confirmed Since, Scott recommended trying ALL DATA. That fixed my issue so I continued using ALL DATA.
I now use Confirmed Since with no issues.
 
I was just wondering why ALL DATA stopped working, but Scott replied with the answer.
 
Thanks,
Dave

--

Re: Under eLogs/LOTW ALL DATA no longer works properly

Bob Stothfang
 

Scott

I'm too am curious...What changed to cause "All Data" to stop working? I suspect LoTW is the culprit.

I have never used "Confirmed Since".

I have been using your ACL for five years and up until a couple of months ago I have only used two buttons to check LoTW for confirmations. Early on I would just use "All Data" until my log size reached a point where it would take too long to process. That was about the size when your software started warning about the time involved (log size over 1000 QSOs) to use "All Data". I then switched to using "All Since" and would adjust the date accordingly to a date in the recent past, maybe a week or a couple of months time frame. This made the processing time tolerable.

Occasionally though I would use "All Data" to do a complete look back to see if someone from way back decided to upload their log and every now and then I would get a confirmation from the early days. I knew it would take some time to process the whole log so I would start it and then do something else and check back later. Maybe even something non-HAM related.

About a month or two ago I started one of these complete "look backs" and I noticed that it completed VERY QUICKLY, even before I got up from the  desk. I solved the problem by using "All Since" with the "since" date being day #1 for my log. It still takes the "walk away from the desk " time to process since I told it to do everything in the log, but it does work.

Thanks for your GREAT SOFTWARE PACKAGE and all the work you do to update and support it.
I recommend it highly to anyone in need of logging software.

73,

Bob - W8RES

    

On 05/15/2020 07:51, Scott Davis via groups.io wrote:
Hi Dave,

You should routinely use All Since, not Confirmed Since, so that your sent but unconfirmed records are marked as well.  

I am going to reorder those buttons on the LoTW form in the next release.

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 <k4em@...>
To: N3FJPSoftwareUsers@groups.io
Sent: Fri, May 15, 2020 6:45 am
Subject: Re: [N3FJPSoftwareUsers] Under eLogs/LOTW ALL DATA no longer works properly

Soon after I started using ACLog I had an issue with Confirmed Since, Scott recommended trying ALL DATA. That fixed my issue so I continued using ALL DATA.
I now use Confirmed Since with no issues.
 
I was just wondering why ALL DATA stopped working, but Scott replied with the answer.
 
Thanks,
Dave

--

Re: Under eLogs/LOTW ALL DATA no longer works properly

Scott Davis
 

Hi Dave,

You should routinely use All Since, not Confirmed Since, so that your sent but unconfirmed records are marked as well.  

I am going to reorder those buttons on the LoTW form in the next release.

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 <k4em@...>
To: N3FJPSoftwareUsers@groups.io
Sent: Fri, May 15, 2020 6:45 am
Subject: Re: [N3FJPSoftwareUsers] Under eLogs/LOTW ALL DATA no longer works properly

Soon after I started using ACLog I had an issue with Confirmed Since, Scott recommended trying ALL DATA. That fixed my issue so I continued using ALL DATA.
I now use Confirmed Since with no issues.
 
I was just wondering why ALL DATA stopped working, but Scott replied with the answer.
 
Thanks,
Dave
Re: QRZ look up data not functioning

Scott Davis
 

Hi Mike,

Thanks for your e-mail.  I'm sorry that you've run into trouble.  The two typical causes for that error are an incorrect call / password combination, or AC Log's inability to access the QRZ site.

The only settings in AC Log related to QRZ Online lookup are:

-  A valid QRZ UserName
-  A valid QRZ Password
- The check box checked to Enable QRZ Internet Lookup
-  Make sure no other callbook lookup options are selected.

In addition:

-  You'll need to set your Windows Protection and / or Internet protection software to allow AC Log to access the Internet
-  A QRZ subscription in good standing

Also, make sure that you don't have any unusual characters in your user name or password.  If you stick to letters and numbers you will be fine.

That's all there is to it and there isn't anything else to change or set.  I haven't had any other reports of problems, so if you continue to have trouble, please try reentering your user name and password and then double check your account status with the QRZ folks. 

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: Michael Canady N5GJQ <n5gjq@...>
To: N3FJPSoftwareUsers@groups.io
Sent: Thu, May 14, 2020 6:36 pm
Subject: [N3FJPSoftwareUsers] QRZ look up data not functioning

Not sure what happened.  For some reason when I enter a call sign for logging in a new contact in AC log 6.6, the program does not retrieve the appropriate QRZ data, eg. name, address, etc. I receive the following error message:

"There was an error obtaining a key on signing into QRZ lookup. Please verify that your system is on line and that you have entered the correct user name and password".  I checked my QRZ Premium Account and everything appears ok; Internet connection ok.  Using Windows 10 and Avast protection software, and do not think it is blocking AC log 6.6 access.  I went into the API setting of 6.6 and checked the top box as instructed but got "false" report instead of "true" for port selection.  Not sure what to do from here.  Please advise.  LoTW functions fine and  I can upload and download without problem.  Also, can enter QSO information manually; just that 6.6 will not automatically retrieve QRZ data.

Thanks for your help.
Mike  N5GJQ

Re: Under eLogs/LOTW ALL DATA no longer works properly

Dave
 

Soon after I started using ACLog I had an issue with Confirmed Since, Scott recommended trying ALL DATA. That fixed my issue so I continued using ALL DATA.

I now use Confirmed Since with no issues.

 

I was just wondering why ALL DATA stopped working, but Scott replied with the answer.

 

Thanks,

Dave
QRZ look up data not functioning

Michael Canady N5GJQ
 

Not sure what happened.  For some reason when I enter a call sign for logging in a new contact in AC log 6.6, the program does not retrieve the appropriate QRZ data, eg. name, address, etc. I receive the following error message:

"There was an error obtaining a key on signing into QRZ lookup. Please verify that your system is on line and that you have entered the correct user name and password".  I checked my QRZ Premium Account and everything appears ok; Internet connection ok.  Using Windows 10 and Avast protection software, and do not think it is blocking AC log 6.6 access.  I went into the API setting of 6.6 and checked the top box as instructed but got "false" report instead of "true" for port selection.  Not sure what to do from here.  Please advise.  LoTW functions fine and  I can upload and download without problem.  Also, can enter QSO information manually; just that 6.6 will not automatically retrieve QRZ data.

Thanks for your help.
Mike  N5GJQ
Re: Under eLogs/LOTW ALL DATA no longer works properly

Jim Shorney
 

I have never used ALL DATA. Just ALL SINCE and CONFIRMED SINCE. These often bring in new confirmations for QSOs up to 20 years old (my log starts in 1999). I occasionally roll back the CONFIRMED SINCE date back a few months and it sometimes picks up a straggler or two.

73

-Jim
NU0C


On Thu, 14 May 2020 03:44:49 -0700
"Dave" <k4em@bellsouth.net> wrote:

I upload my logs at the end of each day, next morning I download my confirmations from LOTW using 'ALL DATA'.
When I use ALL DATA now it only confirms the previous days QSO's. It used to scan my logs and update QSO's 5, 10 15 years old and take 10 or 15 minutes.
This started about a month ago, I made no changes to ACLog. It's worked as it should for 3 years then it didn't the next day.

Dave
k4em
Re: FTDX3000 Using N3FJP and SDRUNO

Jim...N3MVX
 

JR,
Thanks so very much for the info about VSPE (Virtual Serial Port Emulator). I installed it, set it up and it works great with ACLOG, my FTDX 3000  and SDRUNO. Been trying to figure out how to do this for sometime. The function keys still work for CW. 
Thanks again,
73....Jim....N3MVX
Re: Help with VSPE

Dave C
 

Angelo,
I'm using VSPE successfully to share or "split" the single com port on my TS-590SG with several applications on my PC including ACLOG and WSJT-X.  Attached is a screen shot of my VSPE splitter configuration.  Hopefully the picture will provide the help needed.  The baud rate is obviously your choice.  Just be sure the 590 and all applications are set to the same rate.  Also remember that the 590 has to be completely powered down and restarted for a baud rate change to take effect.

I think VSPE must sense the processor type and therefore requires a license if it is 64 bit.  Also, you may want to consider using a higher COM number for the virtual serial port just to assure no conflict with other COM ports on your PC.

Good luck,
Dave, K8WDA
Re: FT-* does not send DX spot

Malcolm Pelham <malcolm.pelham@...>
 

I am not sure.  Nothing has been changed from the time it was working until now.

Malcolm Pelham
WF5K

On May 13, 2020, at 5:34 PM, Lou Everett, Sr. <loueverettsr@...> wrote:


Hmmmm!  Strange.  Mine working perfect.  I tried three different ones and they worked just fine.  I wonder if it has something to do with your ISP?

Lou WA5LOU

On Wed, May 13, 2020 at 5:23 PM Malcolm Pelham <malcolm.pelham@...> wrote:
Yep. Same outcome.

Malcolm Pelham
WF5K

On May 13, 2020, at 4:24 PM, Lou Everett, Sr. <loueverettsr@...> wrote:


Did you happen to try another DX Cluster server?

Lou WA5LOU

On Wed, May 13, 2020 at 3:48 PM Malcolm Pelham <malcolm.pelham@...> wrote:
I just sent Lee VE7CC a screenshot of my problem which I have been having for sometime.  Last night I noticed a command error message in the VE7CC telnet.  The message said, Show/DX command Error....so I am hopeful he can give me some insight on how to fix it.

Mal
WF5K

On Wed, May 13, 2020 at 3:20 PM K4GM-George <k4gm@...> wrote:
There is definitely something wrong with VE7CC today.   I am getting limited spots and many are greyed out although I did not filter them out.   

73, George K4GM

George Marzloff
16154 Bradford Road
Culpeper, VA   22701



On 5/13/2020 3:24 PM, Malcolm Pelham wrote:
Thanks Scott, but I think there is some error message on the VE7CC telnet host.  I just sent a screen shot to Lee to give me his idea on what is happening.

Thanks Mal WF5K

On Wed, May 13, 2020 at 5:15 AM Scott Davis via groups.io <SNKDavis=aol.com@groups.io> wrote:
Hi Malcolm,

Thanks for your follow up.  I was referring to your DX Spotting filters (either the settings you have set on your Telnet host, or in the software (More Filtering from the DX Spotting setup form)).  Since an error is returned by the Telnet hosts and no one else is having a problem, it is most likely the settings you have on your Telnet sites.

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: Malcolm Pelham <malcolm.pelham@...>
To: N3FJPSoftwareUsers@groups.io
Sent: Tue, May 12, 2020 4:07 pm
Subject: Re: [N3FJPSoftwareUsers] FT-* does not send DX spot

What filter settings are you speaking of?

Malcolm Pelham
WF5K

On May 12, 2020, at 5:18 AM, Scott Davis via groups.io <SNKDavis=aol.com@groups.io> wrote:


Hi Malcolm,

Thanks for your e-mail.  Odds are your FT8 spots are going out fine too, but your filter settings are preventing you from seeing them.  Correcting your filter settings  will very likely do the trick.

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: Malcolm Pelham <malcolm.pelham@...>
To: N3FJPSoftwareUsers@groups.io
Sent: Mon, May 11, 2020 9:45 pm
Subject: [N3FJPSoftwareUsers] FT-* does not send DX spot

When I first started using ACL 6.6 everything in DX Spot worked great wen it came to spotting FT-8 DX.  All of a sudden it stopped spotting DX on Digital, but it works on CW and SSB.  Could there have been a Windows 10 update that caused this anomaly or an Internet protection program that is causing this?  If so how can I fix it.?  I am using Mcafee.  I am not a computer genius so please explain like you are talking to a 5 year old.  HI HI....Thanks for any help.

--
Lou WA5LOU


--
Lou WA5LOU
12401 - 12420 of 54072