Date   

Re: CW Decoding Software

Bo W4GHV
 

Yep it does transmit CW. Works nice with the handy Winkeyer too.
--
73, Bo W4GHV since '54


Re: rig setup

Larry Stowell K1ZW
 

Thanks Steve

It was a senior moment I back to the setup page and there

it is in the right window, It ccould have bit me.

73 Larry K1ZW

On 11/16/2019 5:44 PM, AI3KS wrote:

http://www.n3fjp.com/help/righelp.html

Steve, AI3KS

On 19/11/16 16:16, Larry Stowell K1ZW wrote:
I can't seem to find a path to the rig setup on Scott website???
HELP please



Re: rig setup

AI3KS
 

On 19/11/16 16:16, Larry Stowell K1ZW wrote:
I can't seem to find a path to the rig setup on Scott website???
HELP please


rig setup

Larry Stowell K1ZW
 

I can't seem to find a path to the rig setup on Scott website???
HELP please


Re: logging wrong info

Tory Wiedenkeller
 

Ok, thank you. I'll post my message there.


On Sat, Nov 16, 2019 at 4:30 AM Frank VE3FBZ <Ve3fbz@...> wrote:
Im using the same configuration without issue. 
I do not auto log and check the log window for accuracy.  I have not had to make any changes except to the hold over setting I may have changed..eg notes.
Good luck.


 Regards and 73s
VE3FBZ
London Amateur Radio Club




On Nov 16, 2019, at 07:08, Scott Davis via Groups.Io <SNKDavis=aol.com@groups.io> wrote:


Hi Tory,

Thanks for your e-mail.  I'm sorry that you have run into trouble.  You'll need to ping Laurie on that.  As long as you have rig interface disabled in AC Log, AC Log logs whatever JTAlert sends it.  You will find Laurie's JTAlert group here:


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: K6TGW.SLO <K6TGW.SLO@...>
To: N3FJPSoftwareUsers <N3FJPSoftwareUsers@groups.io>
Sent: Sat, Nov 16, 2019 6:55 am
Subject: [N3FJPSoftwareUsers] logging wrong info

I use N3FJP in conjunction with WSJT-X and JT-Alert. The WSJT-X is setup for rig control of my Icom 7300. I'm working almost entirely in FT8  among the: 80, 40, 20, 17m bands.
I've noticed on a few occasions now when I've logged a QSO, there is a discrepancy between the freq that N3FJP logs the QSO, and the actual freq the QSO took place on.
For ex. I recently had a QSO with a station in Alaska on 40m band. Everything seemed to log into N3FJP fine, but when I went back and looked at this log, it showed the QSO actually took place on the 80m band.
So, I'm wondering if anyone knows why this would happen and how to fix this problem?  I'm getting emails from these stations telling me the info is wrong. Of course it is. N3FJP is not logging the data correctly.


Re: Temporarily ignore rig settings in ACLog

K8TS
 

Larry;

I sometimes run into to that little glitch.  If it’s just a single contact or two, I just let ACL do it thing, and immediately go to “edit”, and change what needs to be changed.

That’s how you do it when you reach 70.  😊

Dale K8TS

 

Sent from Mail for Windows 10

 

From: Larry Banks via Groups.Io
Sent: Friday, November 15, 2019 6:04 PM
To: N3FJPSoftwareUsers@groups.io
Subject: Re: [N3FJPSoftwareUsers] Temporarily ignore rig settings in ACLog

 

Hi Gary,

 

Try Control-Shift R

 

73 -- Larry -- W1DYJ

 

 

 

-----Original Message-----

From: Gary Woods

Sent: Friday, November 15, 2019 16:33

To: N3FJP Software Users new IO group

Subject: [N3FJPSoftwareUsers] Temporarily ignore rig settings in ACLog

 

It there any quick way to make an entry in ACL that I want to ignore

the primary rig?  As in, I want to log a 2 meter contact, but ACL

insists i was on, say 75 meters?  I've been temporarily setting "no

rig, " then returning to "kenwood 2" when done, but with all the

clever stuff Scott has done, I suspect there's better way I'm not

clever enough to find.

Heck, I'm still happier with those glass NPN devices with the light

inside so you can tell when they['re on!

TIA

 

 

 

 

 

 


Re: logging wrong info

Frank VE3FBZ
 

Im using the same configuration without issue. 
I do not auto log and check the log window for accuracy.  I have not had to make any changes except to the hold over setting I may have changed..eg notes.
Good luck.


 Regards and 73s
VE3FBZ
London Amateur Radio Club
www.larc.ca 




On Nov 16, 2019, at 07:08, Scott Davis via Groups.Io <SNKDavis@...> wrote:


Hi Tory,

Thanks for your e-mail.  I'm sorry that you have run into trouble.  You'll need to ping Laurie on that.  As long as you have rig interface disabled in AC Log, AC Log logs whatever JTAlert sends it.  You will find Laurie's JTAlert group here:

https://hamapps.groups.io/g/Support

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: K6TGW.SLO <K6TGW.SLO@...>
To: N3FJPSoftwareUsers <N3FJPSoftwareUsers@groups.io>
Sent: Sat, Nov 16, 2019 6:55 am
Subject: [N3FJPSoftwareUsers] logging wrong info

I use N3FJP in conjunction with WSJT-X and JT-Alert. The WSJT-X is setup for rig control of my Icom 7300. I'm working almost entirely in FT8  among the: 80, 40, 20, 17m bands.
I've noticed on a few occasions now when I've logged a QSO, there is a discrepancy between the freq that N3FJP logs the QSO, and the actual freq the QSO took place on.
For ex. I recently had a QSO with a station in Alaska on 40m band. Everything seemed to log into N3FJP fine, but when I went back and looked at this log, it showed the QSO actually took place on the 80m band.
So, I'm wondering if anyone knows why this would happen and how to fix this problem?  I'm getting emails from these stations telling me the info is wrong. Of course it is. N3FJP is not logging the data correctly.


Re: logging wrong info

Scott Davis
 

Hi Tory,

Thanks for your e-mail.  I'm sorry that you have run into trouble.  You'll need to ping Laurie on that.  As long as you have rig interface disabled in AC Log, AC Log logs whatever JTAlert sends it.  You will find Laurie's JTAlert group here:

https://hamapps.groups.io/g/Support

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: K6TGW.SLO <K6TGW.SLO@...>
To: N3FJPSoftwareUsers <N3FJPSoftwareUsers@groups.io>
Sent: Sat, Nov 16, 2019 6:55 am
Subject: [N3FJPSoftwareUsers] logging wrong info

I use N3FJP in conjunction with WSJT-X and JT-Alert. The WSJT-X is setup for rig control of my Icom 7300. I'm working almost entirely in FT8  among the: 80, 40, 20, 17m bands.
I've noticed on a few occasions now when I've logged a QSO, there is a discrepancy between the freq that N3FJP logs the QSO, and the actual freq the QSO took place on.
For ex. I recently had a QSO with a station in Alaska on 40m band. Everything seemed to log into N3FJP fine, but when I went back and looked at this log, it showed the QSO actually took place on the 80m band.
So, I'm wondering if anyone knows why this would happen and how to fix this problem?  I'm getting emails from these stations telling me the info is wrong. Of course it is. N3FJP is not logging the data correctly.


Re: 6.6 ACLog changes

Scott Davis
 

Hi Michael,

Thanks for your e-mail,

Yes, click Settings > Appearance > Colors and Fonts.  Then click Change Main Form Font (Bearing, etc.) towards the lower left.

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 Payne <michael.f.payne@...>
To: N3FJPSoftwareUsers <N3FJPSoftwareUsers@groups.io>
Sent: Fri, Nov 15, 2019 9:55 pm
Subject: [N3FJPSoftwareUsers] 6.6 ACLog changes

Hello to all! I just updated to 6.6 version of ACLog, and everything went fine, except for a few things that shrunk. I can't hardly see Bearing, Miles and the one below miles, and also QSL Sent, QSL Received, Local time, and UTC time. After putting DX Spots back as enabled, these fields shrink to tiny unusable and extremely small text. If there is a way to correct this in settings, please tell me how to make the items readable. If this is not doable, then I would ask that these be first on the list to correct. Hopefully, there is a fix!

73,
Michael 


Re: Port Already In Use By Server

Scott Davis
 

Hi Anne,

Thanks for your e-mail.  Click Settings > Rig Interface and make sure that N3FJP API is not selected.  Do likewise with your CW set up.  Also, on the Settings > API form, make sure the bottom check box is unchecked,  That should 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: Anne KC9YL <KC9YL.anne@...>
To: N3FJPSoftwareUsers <N3FJPSoftwareUsers@groups.io>
Sent: Fri, Nov 15, 2019 8:08 pm
Subject: [N3FJPSoftwareUsers] Port Already In Use By Server

I have rig control set up thru N3FJP.  I operate FT8/FT4 and use JTAlert.  Logging works OK in N3FJP, but every time I open up AC Log, I get this popup:

Port Already in Use by Server
This program's server is already running on port 1100.  Please click Settings>Application Program Interface (API) to select another port for the client to use (and configure the receiving program similarly) or disable the server to free the port.

 I will get this popup periodically when ACLog is open, and need to click "OK" on all of them before my latest QSO will log. Since WSJT and JTAlert are talking to each other, I don't want to mess that up.
(LOTW download still isn't talking to N3FJP, but that's another story - uploads are OK, just no download)


logging wrong info

Tory Wiedenkeller
 

I use N3FJP in conjunction with WSJT-X and JT-Alert. The WSJT-X is setup for rig control of my Icom 7300. I'm working almost entirely in FT8  among the: 80, 40, 20, 17m bands.

I've noticed on a few occasions now when I've logged a QSO, there is a discrepancy between the freq that N3FJP logs the QSO, and the actual freq the QSO took place on.

For ex. I recently had a QSO with a station in Alaska on 40m band. Everything seemed to log into N3FJP fine, but when I went back and looked at this log, it showed the QSO actually took place on the 80m band.

So, I'm wondering if anyone knows why this would happen and how to fix this problem?  I'm getting emails from these stations telling me the info is wrong. Of course it is. N3FJP is not logging the data correctly.


6.6 ACLog changes

Michael Payne
 

Hello to all! I just updated to 6.6 version of ACLog, and everything went fine, except for a few things that shrunk. I can't hardly see Bearing, Miles and the one below miles, and also QSL Sent, QSL Received, Local time, and UTC time. After putting DX Spots back as enabled, these fields shrink to tiny unusable and extremely small text. If there is a way to correct this in settings, please tell me how to make the items readable. If this is not doable, then I would ask that these be first on the list to correct. Hopefully, there is a fix!

73,
Michael 


Port Already In Use By Server

Anne KC9YL
 

I have rig control set up thru N3FJP.  I operate FT8/FT4 and use JTAlert.  Logging works OK in N3FJP, but every time I open up AC Log, I get this popup:

Port Already in Use by Server
This program's server is already running on port 1100.  Please click Settings>Application Program Interface (API) to select another port for the client to use (and configure the receiving program similarly) or disable the server to free the port.

 I will get this popup periodically when ACLog is open, and need to click "OK" on all of them before my latest QSO will log. Since WSJT and JTAlert are talking to each other, I don't want to mess that up.
(LOTW download still isn't talking to N3FJP, but that's another story - uploads are OK, just no download)


Re: Temporarily ignore rig settings in ACLog

Larry Banks
 

Hi Gary,

Try Control-Shift R

73 -- Larry -- W1DYJ

-----Original Message-----
From: Gary Woods
Sent: Friday, November 15, 2019 16:33
To: N3FJP Software Users new IO group
Subject: [N3FJPSoftwareUsers] Temporarily ignore rig settings in ACLog

It there any quick way to make an entry in ACL that I want to ignore
the primary rig? As in, I want to log a 2 meter contact, but ACL
insists i was on, say 75 meters? I've been temporarily setting "no
rig, " then returning to "kenwood 2" when done, but with all the
clever stuff Scott has done, I suspect there's better way I'm not
clever enough to find.
Heck, I'm still happier with those glass NPN devices with the light
inside so you can tell when they['re on!
TIA


Re: Menu Font Size changed

Scott Davis
 

Hi JH,

Thanks for your follow up.  I'm really not sure why you are experiencing that.  There were no code changes associated with the menu from 6.5 to 6.6.  The only thing I can think to suggest is to click Settings > Appearance > Colors and Fonts and then Reset to Original Settings.

I hope that this helps.


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: John Hendry <archer@...>
To: N3FJPSoftwareUsers <N3FJPSoftwareUsers@groups.io>
Sent: Fri, Nov 15, 2019 4:48 pm
Subject: Re: [N3FJPSoftwareUsers] Menu Font Size changed

Here's what it looks like, if this helps:



JH


Re: Temporarily ignore rig settings in ACLog

AI3KS
 

Gary,

Disable rig interface, log the contact, re-enable rig interface

CTRL+Shift+R  toggles rig interface on/off

Steve, AI3KS


On 19/11/15 16:33, Gary Woods wrote:
It there any quick way to make an entry in ACL that I want to ignore
the primary rig?  As in, I want to log a 2 meter contact, but ACL
insists i was on, say 75 meters?  I've been temporarily setting "no
rig, " then returning to "kenwood 2" when done, but with all the
clever stuff Scott has done, I suspect there's better way I'm not
clever enough to find.
Heck, I'm still happier with those glass NPN devices with the light
inside so you can tell when they['re on!
TIA






Re: Menu Font Size changed

John Hendry
 

Here's what it looks like, if this helps:



JH


Re: Menu Font Size changed

John Hendry
 

Thanks... that fixed those fonts... but I still need a solution for the menu fonts.   I'm not finding anything that changed on Microsoft's side either.  

JH


Temporarily ignore rig settings in ACLog

Gary Woods
 

It there any quick way to make an entry in ACL that I want to ignore
the primary rig? As in, I want to log a 2 meter contact, but ACL
insists i was on, say 75 meters? I've been temporarily setting "no
rig, " then returning to "kenwood 2" when done, but with all the
clever stuff Scott has done, I suspect there's better way I'm not
clever enough to find.
Heck, I'm still happier with those glass NPN devices with the light
inside so you can tell when they['re on!
TIA


Re: Lost my LOTW

Scott Davis
 

Hi Ruart,

Thanks for your e-mail.  I'm sorry that you have run into trouble.  There are only a couple settings in AC Log, so you shouldn't have any trouble getting back up and running.  You likely changed your user name or sign on to an invalid value.  This FAQ will get you going:



And in case you need it, all five, AC Log LoTW configuration steps are here (steps 1 and 2 are likely all you need to correct, as neither station location or the TQSL path are used for downloading):



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: Fri, Nov 15, 2019 2:54 pm
Subject: [N3FJPSoftwareUsers] Lost my LOTW

I had LOTW and eQSL working fine,  but then decided I was  going to need to put up a 2nd location like a summer residence.    That started my decline.   Gads,   days shot.
 
I finally have it so AC will upload to LOTW ,   but it wont download.  Not with either location selected now also not with my original basic call sign.
 
I can go to the LOTW address and have it make a file for me that I can download,   but as far as clicking on the AC button,   no way.
 
Any thoughts on how to proceed next?   I considered deleting all accoutns other than my basic callsign and just telling folks to not use me for contests etc except when I am actually at my home QTH.
 
Getting real tired of working on this.   HRD apparently setup easier,  and I dont do contesting so HRD perhaps is a better choice.   Dunno.  
 
 
 
Sent from Mail for Windows 10