Date   

Re: DX spotting setup screen: telnet host greyed out?

Mike M0AGP
 

Thanks Pat - I can't imagine how you ever found that - thank you!
73
Mike M0AGP


Re: DX spotting setup screen: telnet host greyed out?

Pat Whelton
 

Hey Mike.  I had this exact same problem several months ago and it took forever to find an answer.  You need to remove the checkmark for “Enable DX Spotting” then make your change and remember to put a checkmark back in “Enable DX Spotting”. 

 

Regards,

 

Pat – KZ5J

 

From: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io> On Behalf Of Mike M0AGP
Sent: Saturday, April 10, 2021 1:25 PM
To: N3FJPSoftwareUsers@groups.io
Subject: [N3FJPSoftwareUsers] DX spotting setup screen: telnet host greyed out?

 

Hello - this is a great product.  I am trying to use DX spotting and for some reason, unlike in the helpful video I watched on the topic, I cannot change numerous things in the top left box of the DX Spotting Setup screen, unlike the way it can be changed in the video. It looks like this:

What do I need to do pls?
Thanks
Mike M0AGP


DX spotting setup screen: telnet host greyed out?

Mike M0AGP
 

Hello - this is a great product.  I am trying to use DX spotting and for some reason, unlike in the helpful video I watched on the topic, I cannot change numerous things in the top left box of the DX Spotting Setup screen, unlike the way it can be changed in the video. It looks like this:

What do I need to do pls?
Thanks
Mike M0AGP


Re: Already Uploaded QSO suppressed on line 46

Bill Grover
 

Are you downloading from LoTW before you try to upload?

Bill Grover, N3EYF

William Grover


From: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io> on behalf of Frank C. D'Amato via groups.io <kb2mxv@...>
Sent: Friday, April 9, 2021 3:29:04 PM
To: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io>
Subject: [N3FJPSoftwareUsers] Already Uploaded QSO suppressed on line 46
 
I keep getting this error every time I upload to LOTW.

The record is good, but I even deleted the entry from my log and I get the same message with the next record on line 46.

What can be going wrong here.

I know I can just hit ignore and proceed, but it happens every time.

Is there some sort of database repair tool to fix this issue?

Thanks


--


Frank - KB2MXV


Re: Already Uploaded QSO suppressed on line 46

Bill Grover
 

Are you downloading from LoTW before you try to upload?

Bill Grover, N3EYF


From: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io> on behalf of Frank MacKenzie-Lamb via groups.io <maclamb@...>
Sent: Friday, April 9, 2021 3:31:55 PM
To: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io>
Subject: Re: [N3FJPSoftwareUsers] Already Uploaded QSO suppressed on line 46
 

I get this all the time….I checked on Tsql which showed it had been sent so I disregard the Error Detected and press ignore…..no worries Frank

 

Frank

NG1I

 

From: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io> On Behalf Of Frank C. D'Amato
Sent: Friday, April 9, 2021 3:29 PM
To: N3FJPSoftwareUsers@groups.io
Subject: [N3FJPSoftwareUsers] Already Uploaded QSO suppressed on line 46

 

I keep getting this error every time I upload to LOTW.

The record is good, but I even deleted the entry from my log and I get the same message with the next record on line 46.

What can be going wrong here.

I know I can just hit ignore and proceed, but it happens every time.

Is there some sort of database repair tool to fix this issue?

Thanks


--


Frank - KB2MXV


Re: LoTW Error Message

Bill Grover
 

FWIW I noticed on my certificate the last QSO date was several days before the certificate expired.

Valid:2019-06-24 00:00:00 - 2022-06-23 23:59:59
Call sign:N3EYF
DXCC entity:UNITED STATES OF AMERICA (291)
QSO Dates:2019-05-29 00:00:00 - 2022-06-12 23:59:59

William Grover


From: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io> on behalf of Bob K via groups.io <krug261@...>
Sent: Friday, April 9, 2021 11:20:59 AM
To: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io>
Subject: Re: [N3FJPSoftwareUsers] LoTW Error Message
 
Mike and Lou,

Fixed! I renewed my LoTW certificate and all is now well with the world. Interestingly, the certificate was not due to expire until June 11, but it still stopped me from uploading new QSOs. Which is probably the reason I didn't receive any notification of the impending expiration.

I've never understood why some people would choose to not have a LoTW account. However, it is a rather convoluted process and can easily see some people shying away.

Bob, KA2TQV


Re: Problem logging to AC log with new version

Scott Davis
 

Hi KC6MIE,

Thanks for your e-mail.  I'm sorry that you have run into trouble.  It sounds like you are referring to the error message JTAlert displays when it is unable to log to AC Log.  Increasing the delay time in JTAlert as detailed at the bottom of the JTAlert section here will correct that:

http://www.n3fjp.com/help/digitalsetup.html#jtalert

Be well and enjoy!

73, Kimberly, KA3SEQ

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: kc6mie <kc6mie@...>
To: 'n3fjpsoftwareusers@groups.io' <n3fjpsoftwareusers@groups.io>
Sent: Fri, Apr 9, 2021 9:31 pm
Subject: [N3FJPSoftwareUsers] Problem logging to AC log with new version

AC log is not letting me save the contact to my log but it tells me it is has been saved to my wsjt-x log.  This problem just started a while ago, once in a while now every contact.
S.


PowerSDR, CW, and ACL using ANAN 7000DLE MKII

John KC4LZN
 

I have the ANAN 7000DLE MKII and run ACL for logging and have set up the virtual COM port for frequency reading with no problem. I can generate CW with CWX in Thetis without any problem. It's cumbersome to work between CWX and ACL for contests and I'm having difficulty getting ACL setup for CW. Has anyone been successful in setting up CW with AcL and PowerSDR/Thetis?

73
John


Problem logging to AC log with new version

kc6mie
 

AC log is not letting me save the contact to my log but it tells me it is has been saved to my wsjt-x log.  This problem just started a while ago, once in a while now every contact.
S.


Re: A and B VFOs, Yeasu FTDX-10

Danny WD4LAM
 

BTW, latest edition on a Win 10 machine.


A and B VFOs, Yeasu FTDX-10

Danny WD4LAM
 

I can make the Log read either A or B VFOs, but, strangely enough, not both on my Yaesu FTDX-10.

What do I need to do?

Any help is greatly appreciated!


Re: Already Uploaded QSO suppressed on line 46

Scott Davis
 

Hi Frank,

Thanks for your e-mail.  Please see this FAQ here:


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

Be well and enjoy!

73, Kimberly, KA3SEQ

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 MacKenzie-Lamb <maclamb@...>
To: N3FJPSoftwareUsers@groups.io
Sent: Fri, Apr 9, 2021 3:31 pm
Subject: Re: [N3FJPSoftwareUsers] Already Uploaded QSO suppressed on line 46

I get this all the time….I checked on Tsql which showed it had been sent so I disregard the Error Detected and press ignore…..no worries Frank
 
Frank
NG1I
 
From: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io> On Behalf Of Frank C. D'Amato
Sent: Friday, April 9, 2021 3:29 PM
To: N3FJPSoftwareUsers@groups.io
Subject: [N3FJPSoftwareUsers] Already Uploaded QSO suppressed on line 46
 
I keep getting this error every time I upload to LOTW.

The record is good, but I even deleted the entry from my log and I get the same message with the next record on line 46.

What can be going wrong here.

I know I can just hit ignore and proceed, but it happens every time.

Is there some sort of database repair tool to fix this issue?

Thanks


--


Frank - KB2MXV


Re: Already Uploaded QSO suppressed on line 46

Frank MacKenzie-Lamb <maclamb@...>
 

I get this all the time….I checked on Tsql which showed it had been sent so I disregard the Error Detected and press ignore…..no worries Frank

 

Frank

NG1I

 

From: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io> On Behalf Of Frank C. D'Amato
Sent: Friday, April 9, 2021 3:29 PM
To: N3FJPSoftwareUsers@groups.io
Subject: [N3FJPSoftwareUsers] Already Uploaded QSO suppressed on line 46

 

I keep getting this error every time I upload to LOTW.

The record is good, but I even deleted the entry from my log and I get the same message with the next record on line 46.

What can be going wrong here.

I know I can just hit ignore and proceed, but it happens every time.

Is there some sort of database repair tool to fix this issue?

Thanks


--


Frank - KB2MXV


Already Uploaded QSO suppressed on line 46

Frank C. D'Amato
 

I keep getting this error every time I upload to LOTW.

The record is good, but I even deleted the entry from my log and I get the same message with the next record on line 46.

What can be going wrong here.

I know I can just hit ignore and proceed, but it happens every time.

Is there some sort of database repair tool to fix this issue?

Thanks


--


Frank - KB2MXV


Re: Possible BUG with AC Log 6.9 concerning Deleting Duplicates

William D'Agostino
 

Hi Scott and the group,

Thanks for your suggestion.  I tried it, but it didn't solve this strange problem.

So, I decided to take an "old-school" approach. 

I exported the AC Log ADFI file from yesterday, then re-installed my AC Log weekly backup, and then imported yesterday's ADFI file again.  I still had to manually deleted the 50+ duplicates from yesterday, but it did solve my problem although it wasn't an elegant solution.  In addition, I deleted my WSJT-X log file just in case the problem was caused by a corrupted file.

I successfully saved my QSOs from yesterday, and I avoided the need to manually delete the 1,000+ other duplicate QSOs which were created.

Thanks again, and I really enjoy using your logging programs.

73,
Will
WB1DMK


On Friday, April 9, 2021, 8:58:47 AM EDT, Scott Davis via groups.io <snkdavis@...> wrote:


Hi Will,

Thanks for your e-mail.  I'm sorry that you have run into trouble.  There haven't been any changes to the remove duplicates function.  I just double checked here and it continues to work fine.

First, try clicking Edit > Fill Fields Determined by Call, so that more of the fields that are compared have values and then try running the function.

If that doesn't correct the problem, compare two records that you believe are duplicates for these fields:

Capture.JPG

It is very likely one or more of the above fields have different values.

Thanks so much for your kind words on the software!

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: William D'Agostino via groups.io <william_dagostino@...>
To: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io>
Sent: Fri, Apr 9, 2021 8:31 am
Subject: [N3FJPSoftwareUsers] Possible BUG with AC Log 6.9 concerning Deleting Duplicates

Hi Everyone,

First, AC Log is a great product and I enjoy using it.

I just upgraded to AC Log 6.9 from AC Log 6.7, and this was my first time using AC Log 6.9.  I’m running a Windows 10 Dell laptop. 

Yesterday, I worked approximately 50 stations using WSJT-X FT8 on 60m.  Near the end of my radio session, I started getting AC Log error messages that the QSO was not “logged” into AC Log.  This has occasionally happen with AC Log 6.7, and I never had an issue with importing the WSJT-X log and deleting duplicates contacts in AC Log 6.7.

I imported the WSJT-X log file into AC Log 6.9 to recover the missing QSOs and then ran the “Remove Duplicates” function.  This is were the possible “bug” occurred.  The AC Log did not delete the duplicates.  I restarted my laptop and tried again with no success.  I now have duplicate QSOs for all of my contacts from yesterday as well as another 1,000+ duplicates ranging back for several months.

As mentioned above, I was previously using AC Log 6.7 before upgrading to AC Log 6.9, and I never had a problem with deleting duplicates after importing the WSJT-X log.

Has anyone else experienced this possible bug?  Does anyone have a solution?

Thanks,
Will
WB1DMK


Re: LoTW Error Message

Lou WA5LOU
 

I am glad you got it working, now.  That is all that matters.

Lou WA5LOU


On Fri, Apr 9, 2021 at 11:21 AM Bob K via groups.io <krug261=yahoo.com@groups.io> wrote:
Mike and Lou,

Fixed! I renewed my LoTW certificate and all is now well with the world. Interestingly, the certificate was not due to expire until June 11, but it still stopped me from uploading new QSOs. Which is probably the reason I didn't receive any notification of the impending expiration.

I've never understood why some people would choose to not have a LoTW account. However, it is a rather convoluted process and can easily see some people shying away.

Bob, KA2TQV


Re: LoTW Error Message

Mike Olbrisch
 

OUTSTANDING.  Glad it was helpful.  I do not see any E-mail from lou, so I have no clue what he recommended.  But I am certainly happy your system is up and running, so I assume the step-by-step list I sent you got you to the right place.

LoTW?  Some people are haters, they hate the ARRL for whatever reason and will have nothing to do with any of it.  Some just don’t care.  Some are afraid of it.  My experience with getting confirmations via LoTW is that digital operators are the best, then voice operators.  CW operators are the worst, it is almost like they are still back in time and never heard of computers.  It took me a year to get LoTW confirmation for all states CW, several months for voice, and 6 weeks for digital.  I finally had to resort to a CW sked for the last state in CW!  <grin>.

 

Sir, wishing you a SUPER Friday, and a BETTER weekend.

 

Vy73  –  Mike  –  KD5KC –  El Paso – Texas  –  DM61. 

 

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.   An EXIT is really an

ENTRANCE to someplace new.

 

 

 

 

From: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io> On Behalf Of Bob K via groups.io
Sent: Friday, April 9, 2021 9:21 AM
To: N3FJPSoftwareUsers@groups.io
Subject: Re: [N3FJPSoftwareUsers] LoTW Error Message

 

Mike and Lou,

Fixed! I renewed my LoTW certificate and all is now well with the world. Interestingly, the certificate was not due to expire until June 11, but it still stopped me from uploading new QSOs. Which is probably the reason I didn't receive any notification of the impending expiration.

I've never understood why some people would choose to not have a LoTW account. However, it is a rather convoluted process and can easily see some people shying away.

Bob, KA2TQV


Re: LoTW Error Message

Bob - KA2TQV
 

Mike and Lou,

Fixed! I renewed my LoTW certificate and all is now well with the world. Interestingly, the certificate was not due to expire until June 11, but it still stopped me from uploading new QSOs. Which is probably the reason I didn't receive any notification of the impending expiration.

I've never understood why some people would choose to not have a LoTW account. However, it is a rather convoluted process and can easily see some people shying away.

Bob, KA2TQV


Re: Possible BUG with AC Log 6.9 concerning Deleting Duplicates

Scott Davis
 

Hi Will,

Thanks for your e-mail.  I'm sorry that you have run into trouble.  There haven't been any changes to the remove duplicates function.  I just double checked here and it continues to work fine.

First, try clicking Edit > Fill Fields Determined by Call, so that more of the fields that are compared have values and then try running the function.

If that doesn't correct the problem, compare two records that you believe are duplicates for these fields:

Capture.JPG

It is very likely one or more of the above fields have different values.

Thanks so much for your kind words on the software!

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: William D'Agostino via groups.io <william_dagostino@...>
To: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io>
Sent: Fri, Apr 9, 2021 8:31 am
Subject: [N3FJPSoftwareUsers] Possible BUG with AC Log 6.9 concerning Deleting Duplicates

Hi Everyone,

First, AC Log is a great product and I enjoy using it.

I just upgraded to AC Log 6.9 from AC Log 6.7, and this was my first time using AC Log 6.9.  I’m running a Windows 10 Dell laptop. 

Yesterday, I worked approximately 50 stations using WSJT-X FT8 on 60m.  Near the end of my radio session, I started getting AC Log error messages that the QSO was not “logged” into AC Log.  This has occasionally happen with AC Log 6.7, and I never had an issue with importing the WSJT-X log and deleting duplicates contacts in AC Log 6.7.

I imported the WSJT-X log file into AC Log 6.9 to recover the missing QSOs and then ran the “Remove Duplicates” function.  This is were the possible “bug” occurred.  The AC Log did not delete the duplicates.  I restarted my laptop and tried again with no success.  I now have duplicate QSOs for all of my contacts from yesterday as well as another 1,000+ duplicates ranging back for several months.

As mentioned above, I was previously using AC Log 6.7 before upgrading to AC Log 6.9, and I never had a problem with deleting duplicates after importing the WSJT-X log.

Has anyone else experienced this possible bug?  Does anyone have a solution?

Thanks,
Will
WB1DMK


Re: Possible BUG with AC Log 6.9 concerning Deleting Duplicates

K8TS
 

Will;

Never experienced.

Go File>Remove Duplicates.  As long as they are identical in every way, ACL with delete them.  The one case I discovered in my log was ACL, or WSJT, or JTAlert was logging one q as FT8 and also logging the other q as DIGATAL.  I was able to manually remove them.  Don’t know the cause, but it has not reoccurred. If it shows two different modes, such as I just described, will not remove the 2nd instance.  Be careful, the process can not be reversed.

 

Someone speak up, but there should have been no reason to reload your ACL.  The ACL retains the q’s even as you change versions. If you are also using JTAlert, remember that it is changing to .NET 5 in the last couple of days.

Dale K8TS

 

 

Sent from Mail for Windows 10

 

From: William D'Agostino via groups.io
Sent: Friday, April 9, 2021 8:34 AM
To: N3FJPSoftwareUsers@groups.io
Subject: [N3FJPSoftwareUsers] Possible BUG with AC Log 6.9 concerning Deleting Duplicates

 

Hi Everyone,

 

First, AC Log is a great product and I enjoy using it.

 

I just upgraded to AC Log 6.9 from AC Log 6.7, and this was my first time using AC Log 6.9.  I’m running a Windows 10 Dell laptop. 

 

Yesterday, I worked approximately 50 stations using WSJT-X FT8 on 60m.  Near the end of my radio session, I started getting AC Log error messages that the QSO was not “logged” into AC Log.  This has occasionally happen with AC Log 6.7, and I never had an issue with importing the WSJT-X log and deleting duplicates contacts in AC Log 6.7.

 

I imported the WSJT-X log file into AC Log 6.9 to recover the missing QSOs and then ran the “Remove Duplicates” function.  This is were the possible “bug” occurred.  The AC Log did not delete the duplicates.  I restarted my laptop and tried again with no success.  I now have duplicate QSOs for all of my contacts from yesterday as well as another 1,000+ duplicates ranging back for several months.

 

As mentioned above, I was previously using AC Log 6.7 before upgrading to AC Log 6.9, and I never had a problem with deleting duplicates after importing the WSJT-X log.

 

Has anyone else experienced this possible bug?  Does anyone have a solution?

 

Thanks,

Will

WB1DMK

 

 

2661 - 2680 of 50526