|
AC Log & import ADIF from WSJT-X
Dave
Any info on where to find the WSJT-X log file so I can import it into AC Log?????
I have done the "open log directory" in WSJT-X and see the following path, user/appdata/local/wsjt-x I try looking for it when I want to import that data into AC Log but I cannot find this path. I have only been using AC Log for a few weeks and I have only been using WSJT-X for 10 days or so which means I am a beginner at this stuff. Thanks much, 73, Dave KC3AM
|
|
|
|
Re: Can't delete QSO
Ryan – you need to exit the edit window first.
73 -- Larry -- W1DYJ
From: Ryan Trullinger
Sent: Monday, December 16, 2019 8:03
Subject: [N3FJPSoftwareUsers] Can't delete QSO I
Wanted to make sure that my lookup worked, it does but now I can't delete the
contact I used to check. The "window" underneath the edit QSO dialog is not
clickable.
|
|
|
|
Re: ARRL RTTY Contest Module
Scott Davis
Hi Ed,
Thanks for your e-mail. The updated version of the ARRL RTTY software is already on the site. The functionality of ARRL RTTY and the rest of the contest software is / will be identical to the 10 meter software that you used this past weekend. Lord willing, I hope to complete, compile and upload the rest of the updated contest software by early January.
Thanks for all your testing and good information this past weekend.
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: Edward Van Cleave <ed_vanc@...> To: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io> Sent: Sun, Dec 15, 2019 5:29 pm Subject: [N3FJPSoftwareUsers] ARRL RTTY Contest Module
Ok, 10M contest prop was awful, but very interesting propagation nonetheless. Once my CW keying port issues were resolved, the 10M contest module was rock solid with F key CW performance and logging.
Now, the ARRL RTTY Round Up is ahead and W0VC will be operating FT8 exclusively. I don't have the antennas or power to operate RTTY. Then the ARRL VHF contest with varied multiple modes, and W0VC with two radios.
Eager to see what the updated contest apps look like.
73,
Ed, W0VD
|
|
|
|
Re: ARRL RTTY Contest Module
Edward Van Cleave <ed_vanc@...>
No problems here, but MN is a single ARRL section, so easier. Just posted my meager 10M score and received confirmation from the ARRL robot.
73,
Ed, W0VC
From: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io> on behalf of Frank MacKenzie-Lamb <maclamb@...>
Sent: Sunday, December 15, 2019 5:26 PM To: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io> Subject: Re: [N3FJPSoftwareUsers] ARRL RTTY Contest Module Anybody else have a problem submitting the cabrillo file but ARRL web submission only recognized EMA or WMA?
Well at least I had a great ground wave ☹ What terrible condx and more to come ☹ ☹ Winkeyer worked great!
Frank NG1I MA
From: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io> On Behalf Of
Edward Van Cleave
Ok, 10M contest prop was awful, but very interesting propagation nonetheless. Once my CW keying port issues were resolved, the 10M contest module was rock solid with F key CW performance and logging.
Now, the ARRL RTTY Round Up is ahead and W0VC will be operating FT8 exclusively. I don't have the antennas or power to operate RTTY. Then the ARRL VHF contest with varied multiple modes, and W0VC with two radios.
Eager to see what the updated contest apps look like.
73,
Ed, W0VD
|
|
|
|
Re: ARRL RTTY Contest Module
Anybody else have a problem submitting the cabrillo file but ARRL web submission only recognized EMA or WMA?
Well at least I had a great ground wave ☹ What terrible condx and more to come ☹ ☹ Winkeyer worked great!
Frank NG1I MA
From: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io> On Behalf Of Edward Van Cleave
Sent: Sunday, December 15, 2019 5:30 PM To: N3FJPSoftwareUsers@groups.io Subject: [N3FJPSoftwareUsers] ARRL RTTY Contest Module
Ok, 10M contest prop was awful, but very interesting propagation nonetheless. Once my CW keying port issues were resolved, the 10M contest module was rock solid with F key CW performance and logging.
Now, the ARRL RTTY Round Up is ahead and W0VC will be operating FT8 exclusively. I don't have the antennas or power to operate RTTY. Then the ARRL VHF contest with varied multiple modes, and W0VC with two radios.
Eager to see what the updated contest apps look like.
73,
Ed, W0VD
|
|
|
|
ARRL RTTY Contest Module
Edward Van Cleave <ed_vanc@...>
Ok, 10M contest prop was awful, but very interesting propagation nonetheless. Once my CW keying port issues were resolved, the 10M contest module was rock solid with F key CW performance and logging.
Now, the ARRL RTTY Round Up is ahead and W0VC will be operating FT8 exclusively. I don't have the antennas or power to operate RTTY. Then the ARRL VHF contest with varied multiple modes, and W0VC with two radios.
Eager to see what the updated contest apps look like.
73,
Ed, W0VD
|
|
|
|
More clarity on the 10M Contest keying issue?
Edward Van Cleave <ed_vanc@...>
Appreciate the questions, but let me clarify again. The issue was caused by a sleepy Windows virtual COM port. It was NOT the Silicon Labs USB driver update that resolved the problem. Could have fixed the issue before the update. The update, however,
prompted me to examine my port settings which led me to turn off the Power Management settings, thus correcting the 10M CW F key keying issue caused by the sleeping port. In other words, the port had to be awakened (it was powered down) for the keyboard to
work properly. Again, thanks Scott.
The Icom website is still linking to its 6/2018 USB driver software (v 1.30). This applies to all IC-7300, IC-7610, and IC-9700 owners. I own two of these rigs. The Silicon Labs update that Windows found brings me to their 6/2019 (v10.1.8.246). This is
a Silicon Labs update, not an Icom update. Everything still works, so will let it be until an issue arises.
Again, the fix could have been made in the original Icom USB virtual COM port driver (v1.30) settings.
10M Contest Module now working great. Wish the 10M conditions were better so I could give a better trial run.
Ed, W0VC
|
|
|
|
Re: Virtual COM port update clarification about keying fix.
toggle quoted messageShow quoted text
From: Edward Van Cleave
Sent: Sunday, December 15, 2019 2:30 PM To: N3FJPSoftwareUsers@groups.io Subject: [N3FJPSoftwareUsers] Virtual COM port update clarification about keying fix.
A couple of you have emailed me directly about my discovery that COM port settings were the root of my 10M contest module CW keying problem. I could have remedied the issue before I updated the Silicon Lab driver software. Was using the driver version listed on the Icom website for my IC-7610, before I asked Windows to find an update.
The fix was a setting in the Silicon Labs CP210x UART Bridge COM properties window accessed from Windows 10 Device Manager. Go to the Power Management Tab and uncheck the box labelled "Allow the computer to turn off this device to save power."
I also played around with the port settings and the 10M contest module Transmit CW settings to improve the CW speed control. Scotts Description Window provides details I had overlooked. My IC-7610 uses DTR for keying, so changed the port Flow Control setting in Windows from None to Xon/Xoff. Also switched ACLog Timing options. Used "Timer" before, now "Loop" (Loop delay is set to 476.190, Loop Sec set to 0), and transmitted speed is closer to my Icom rig keyer. A much improved match to my rig and computer configuration.
Hope that clarifies.
Ed, W0VC
|
|
|
|
Re: Inability to access DX Spotting on ACL.
George Davenport
I tried both...neither worked, then suddenly everything is fine...guess both were down.
-- George-- KM4ODS
|
|
|
|
Virtual COM port update clarification about keying fix.
Edward Van Cleave <ed_vanc@...>
A couple of you have emailed me directly about my discovery that COM port settings were the root of my 10M contest module CW keying problem. I could have remedied the issue before I updated the Silicon Lab driver software. Was using the driver version
listed on the Icom website for my IC-7610, before I asked Windows to find an update.
The fix was a setting in the Silicon Labs CP210x UART Bridge COM properties window accessed from Windows 10 Device Manager. Go to the Power Management Tab and uncheck the box labelled "Allow the computer to turn off this device to save power."
I also played around with the port settings and the 10M contest module Transmit CW settings to improve the CW speed control. Scotts Description Window provides details I had overlooked. My IC-7610 uses DTR for keying, so changed the port Flow Control
setting in Windows from None to
Xon/Xoff. Also switched ACLog Timing options. Used "Timer" before, now "Loop" (Loop delay is set to 476.190, Loop Sec set to 0), and transmitted speed is closer to my Icom rig keyer. A much improved match to my rig and computer configuration.
Hope that clarifies.
Ed, W0VC
|
|
|
|
Re: Inability to access DX Spotting on ACL.
Lou Everett, Sr. <loueverettsr@...>
Choose a different DX Cluster host. VE7CC seems to be down.
On Sun, Dec 15, 2019 at 10:14 AM George Davenport <KM4ODS@...> wrote: Same problem here...DXspots and Ve7cc...neither connect... --
Lou WA5LOU
|
|
|
|
Re: Inability to access DX Spotting on ACL.
George Davenport
Same problem here...DXspots and Ve7cc...neither connect...
tested my telnet and it seems to be fine...
|
|
|
|
Re: Inability to access DX Spotting on ACL.
Hi Orville,
Try a different host. I noticed that ve7cc was not working this
morning.
73 -- Larry -- W1DYJ
From: Orville Burg, II
Sent: Sunday, December 15, 2019 10:39
Subject: [N3FJPSoftwareUsers] Inability to access DX Spotting on
ACL. Scott, For some reason I am unable to access DX Spotting. Portions of the configuration screen are greyed out per the screenshot below. I tried upgrading from 6.5 to 6.6 and that had no effect. Any thoughts appreciated.
Orville, K5VWW
|
|
|
|
Re: Inability to access DX Spotting on ACL.
Scott Davis
Hi Orville,
Thanks for your e-mail. This FAQ will get you going:
http://www.n3fjp.com/faq.html#q95
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: Orville Burg, II <orville@...> To: N3FJPSoftwareUsers <N3FJPSoftwareUsers@groups.io> Sent: Sun, Dec 15, 2019 10:39 am Subject: [N3FJPSoftwareUsers] Inability to access DX Spotting on ACL. Scott,
For some reason I am unable to access DX Spotting. Portions of the configuration screen are greyed out per the screenshot below. I tried upgrading from 6.5 to 6.6 and that had no effect.
Any thoughts appreciated.
Orville, K5VWW
|
|
|
|
Inability to access DX Spotting on ACL.
Orville Burg, II
Scott, For some reason I am unable to access DX Spotting. Portions of the configuration screen are greyed out per the screenshot below. I tried upgrading from 6.5 to 6.6 and that had no effect. Any thoughts appreciated.
Orville, K5VWW
|
|
|
|
FOUND IT!
Edward Van Cleave <ed_vanc@...>
Thanks to Scott's suggestion of a potential hardware issue behind the 10M Contest module F key CW keying issue I was having, I updated the Silicon Lab virtual COM drivers.
Because of the driver update, I checked all the COM port settings. Based upon Scott's guess that the port was at zero state when striking an F key, I discovered by turning off the port power management control in the related tab, everything began working fine.
Thanks Scott!
Ed, W0VC
|
|
|
|
Re: ACLOG DXSpots
Scott Davis
Hi Craig,
Thanks for your e-mail. There is a huge list of DX spotting sites to choose from 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: Craig Raper via Groups.Io <kj4ikb@...> To: N3FJPSoftwareUsers <N3FJPSoftwareUsers@groups.io> Sent: Sun, Dec 15, 2019 9:09 am Subject: [N3FJPSoftwareUsers] ACLOG DXSpots Seems I only have there telenet connections available now for dxspotting DXspots.com has become iffie at best one of them requires you to sign up with them and never any luck with Ve7cc has never been any good for me.
|
|
|
|
Re: 10M contest module 5.9 issue?
Edward Van Cleave <ed_vanc@...>
Frank,
Am running CW from my computer keyboard. Goes right to the Icom virtual COM port for keying.
Did update the driver, but no difference.
The keyboard is wireless, so should try the wired version to see it that may be part of the issue.
Ed, W0VC
From: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io> on behalf of Frank MacKenzie-Lamb <maclamb@...>
Sent: Sunday, December 15, 2019 7:58 AM To: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io> Subject: Re: [N3FJPSoftwareUsers] 10M contest module 5.9 issue? Are you keying CW with your keyboard or have something like a Winkeyer?
From: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io> On Behalf Of
Scott Davis via Groups.Io
Hi Ed,
Thanks for your e-mail. There have been no changes to the actual CW keying. I can't duplicate what you describe here. I'm by no means a hardware guy, but I suspect your PC's com port is reporting open before it is fully ready to accept data. That could be a hardware or device driver problem. 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----- With the 10M contest conditions so variable, have not really had an opportunity to give the updated 10M contest module a good run.m
Had no issues in module set-up. Programmed in all the exchange data I needed into the F keys. Yet, there is one little thing I don't understand.
Whenever I boot the software module, it takes two keystrokes of the F1 key (my callsign W0VC) for the module to become reliable in response to the F keys. This is the pattern: boot up the module; press the F1; it keys the rig in mid-callsign; but on second try, it works thereafter.
How do I fix this?
Ed, W0VC
|
|
|
|
ACLOG DXSpots
Craig Raper
Seems I only have there telenet connections available now for dxspotting DXspots.com has become iffie at best one of them requires you to sign up with them and never any luck with Ve7cc has never been any good for me.
|
|
|
|
Re: Terrible Condx
I’m still running it a Pat says, the condx are BAD up here in New England too ☹
From: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io> On Behalf Of Larry Stowell K1ZW
Sent: Sunday, December 15, 2019 7:32 AM To: N3FJPSoftwareUsers@groups.io Subject: Re: [N3FJPSoftwareUsers] Terrible Condx
Thanks Pat I just couldn't find the right description for conditions until I read your e-mail right on 73 Larry K1ZW On 12/15/2019 6:49 AM, Pat Whelton wrote:
|
|
|
