Date   

Re: Alert function

Scott Davis
 

Thanks Guys,

For all the good reasons already covered, my software is designed to properly map the designation, whether it be a prefix or suffix.

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 Wilson <radio.n4xu@...>
To: N3FJPSoftwareUsers@groups.io
Sent: Sat, May 23, 2020 7:24 am
Subject: Re: [N3FJPSoftwareUsers] Alert function

George,
Jim is correct; /SU is not allowed to designate a domestic operation, and of course, Scott's software is designed is designed to be in compliance with what IS allowed. Further, your statement that "anyone operating in a foreign country must sign with the foreign prefix BEFORE the call and not after" is only mandated for CEPT countries, not all. For example, the reciprocal licensing agreements with Canada and Honduras specify that the country of operation be designated AFTER the callsign. So for example, a Canadian operating in the USA would sign VE4homecall/W2. Likewise an American operating in Manitoba would sign W2homecall/VE4, and ANYONE operating in Honduras would sign homecall/HR. I'm sure there are other examples as well.

73, Bob N4XU


Re: Question on Grid download from LoTW

Paul AC9O
 

Hi Scott,

Was the download snippet helpful?

Thanks,

Paul, AC9O


Re: Counties Not Populating

Mitch NW0M
 

Hi Randy,

Welcome to ACLog!  It's a great logging program and you can always find help in this users forum.

To populate fields like county and grid square, you need to subscribe to a data service like QRZ.  Even though you have checked QRZ, you need to subscribe to their XML service in order to automatically populate other fields.  I have used their subscription for years and it's a great service.  I think it costs about $30/year. 

Good luck!!!

73, Mitch
NWØM


Re: Counties Not Populating

randymir@...
 

One point I need to clarify. I am currently using WSJT and importing the log into Amateur Software. I then click on Fill Fields Determined by Log and then Whole Log. I have tried both QRZ and AC checked under Logbook and still not able to get the County field to populate.

I will continue poking around.

Thanks.

73
Randy
KN6ISQ


Counties Not Populating

randymir@...
 

I recently got my license and am trying to figure out the best way to log my contacts. I'm really liking N3FJP's software, with the exception of one problem - I can't seem to get the county, and possibly other fields, to populate. I have both QRZ and AC Logs checked. It does populate some fields, but I really want to track counties too. 

I have not registered the software, could that be an issue? 

I know I must be missing something that is staring me in the face.

73
Randy
KN6ISQ


Re: Alert function

Bob Wilson
 

George,
Jim is correct; /SU is not allowed to designate a domestic operation, and of course, Scott's software is designed is designed to be in compliance with what IS allowed. Further, your statement that "anyone operating in a foreign country must sign with the foreign prefix BEFORE the call and not after" is only mandated for CEPT countries, not all. For example, the reciprocal licensing agreements with Canada and Honduras specify that the country of operation be designated AFTER the callsign. So for example, a Canadian operating in the USA would sign VE4homecall/W2. Likewise an American operating in Manitoba would sign W2homecall/VE4, and ANYONE operating in Honduras would sign homecall/HR. I'm sure there are other examples as well.

73, Bob N4XU


Re: Alert function

Jim Shorney
 

I think single letter suffixes are tolerated because so few of them map entirely to a specific country prefix. M could be MI, MW, etc. which are different countries or regions. Also it is my understanding that some countries do require /M or /P for mobile or portable. And of course /MM is universally accepted as Martime Mobile. There was a discussion in another group recently as to whether this applies to three letter suffixes because there are no assigned three letter ham prefixes but in my book a prefix is a prefix and that's how the blocks are assigned. /SU would legally identify the station as being somewhere in Egypt though, to the best of my knowledge. That would be a no-no and the op needs to be educated.

I first dug into this during the ARRL Centennail when I wanted to know why my SpotCollctor kept getting excited about DPRK spots when someone was spotting a W1AW/5 ("portable 5") as W1AW/P5. It wasn't the fault of the software.

73

-Jim
NU0C


On Fri, 22 May 2020 22:24:23 -0400
"Larry Banks via groups.io" <larryb.w1dyj=verizon.net@groups.io> wrote:

Hi Jim,

You beat me to it. K2H/SU is not allowed by the FCC.

Note that many other combinations are also not allowed but are used, such as
W1xxx/M which indicates the ham is in England. This is one of those rules
that is ignored all of the time, but Scott's logging SW should follow the
rules, as it does!

73 -- Larry -- W1DYJ


-----Original Message-----
From: Jim Shorney
Sent: Friday, May 22, 2020 21:37
To: N3FJPSoftwareUsers@groups.io
Subject: Re: [N3FJPSoftwareUsers] Alert function


This is expected behavior. SU is a prefix for Egypt. Per F.C.C. Part
97.119(C):

One or more indicators may be included with the call sign. Each indicator
must be separated from the call sign by the slant mark (/) or by any
suitable word that denotes the slant mark. If an indicator is self-assigned,
it must be included before, after, or both before and after, the call sign.
No self-assigned indicator may conflict with any other indicator specified
by the FCC Rules or with any prefix assigned to another country.

The /SU suffix of the K2 appears to be in violation of the last sentence of
the above paragraph.

73

-Jim
NU0C

On Fri, 22 May 2020 21:26:25 -0400
"K4GM-George" <k4gm@k4gm.com> wrote:

There is an anomaly in the DX spotting which should be fixed if not too
complicated. By way of example there is a special event station in
New Jersey identifying as K2H/SU which is perfectly proper. I assume SU
is short for a county but am not sure. However ACLog is treating this
station as if it were SU/K2H and alerting as an Egyptian station (SU)
and showing the station as being in Egypt in the list of spots.





Re: Alert function

Larry Banks
 

Hi Jim,

You beat me to it. K2H/SU is not allowed by the FCC.

Note that many other combinations are also not allowed but are used, such as W1xxx/M which indicates the ham is in England. This is one of those rules that is ignored all of the time, but Scott's logging SW should follow the rules, as it does!

73 -- Larry -- W1DYJ

-----Original Message-----
From: Jim Shorney
Sent: Friday, May 22, 2020 21:37
To: N3FJPSoftwareUsers@groups.io
Subject: Re: [N3FJPSoftwareUsers] Alert function


This is expected behavior. SU is a prefix for Egypt. Per F.C.C. Part 97.119(C):

One or more indicators may be included with the call sign. Each indicator must be separated from the call sign by the slant mark (/) or by any suitable word that denotes the slant mark. If an indicator is self-assigned, it must be included before, after, or both before and after, the call sign. No self-assigned indicator may conflict with any other indicator specified by the FCC Rules or with any prefix assigned to another country.

The /SU suffix of the K2 appears to be in violation of the last sentence of the above paragraph.

73

-Jim
NU0C

On Fri, 22 May 2020 21:26:25 -0400
"K4GM-George" <k4gm@k4gm.com> wrote:

There is an anomaly in the DX spotting which should be fixed if not too
complicated. By way of example there is a special event station in
New Jersey identifying as K2H/SU which is perfectly proper. I assume SU
is short for a county but am not sure. However ACLog is treating this
station as if it were SU/K2H and alerting as an Egyptian station (SU)
and showing the station as being in Egypt in the list of spots.


Re: Alert function

Jim Shorney
 

This is expected behavior. SU is a prefix for Egypt. Per F.C.C. Part 97.119(C):

One or more indicators may be included with the call sign. Each indicator must be separated from the call sign by the slant mark (/) or by any suitable word that denotes the slant mark. If an indicator is self-assigned, it must be included before, after, or both before and after, the call sign. No self-assigned indicator may conflict with any other indicator specified by the FCC Rules or with any prefix assigned to another country.

The /SU suffix of the K2 appears to be in violation of the last sentence of the above paragraph.

73

-Jim
NU0C

On Fri, 22 May 2020 21:26:25 -0400
"K4GM-George" <k4gm@k4gm.com> wrote:

There is an anomaly in the DX spotting which should be fixed if not too
complicated.    By way of example there is a special event station in
New Jersey identifying as K2H/SU which is perfectly proper. I assume SU
is short for a county but am not sure. However ACLog is treating this
station as if it were SU/K2H  and alerting as an Egyptian station (SU)
and showing the station as being in Egypt in the list of spots.


Alert function

K4GM-George
 

Hi Scott,

There is an anomaly in the DX spotting which should be fixed if not too complicated.    By way of example there is a special event station in New Jersey identifying as K2H/SU which is perfectly proper. I assume SU is short for a county but am not sure. However ACLog is treating this station as if it were SU/K2H  and alerting as an Egyptian station (SU) and showing the station as being in Egypt in the list of spots.    This station is very very active and generates very frequent audio alerts.  As I recall anyone operating in a foreign country must sign with the foreign prefix BEFORE the call and not after.  I think only KH6, KL7 and the US possessions are allowed AFTER a call but not before.    Obviously, this is not an urgent matter and at some point the special event station will go QRT; but this is something to address the next time you re-visit the the spotting function of ACLog.     I've been using your log for 15 years and have logged almost 70,000 QSOs in it. It's a good product and I appreciate your excellent support.

73, George K4GM


Re: NET logging option query

Tom & Barb Valosin
 

No worries Scott - I am just old school. Raised on paper logs when EVERTHING was in the log (9/9/63 received first license). Time on, freq, mode, power, every transmission including tune and test, their qth and name and time off. It did pay off a few years back - the "lone holdout" in the area still got over the air TV sigs - "I ain't payin for something thats free". ONLY person in the community NOT on cable. He complained to FCC, I replied to them with a copy of my log. It proved to FCC that I was not on the air at the times he cited in his complaint. Yep, when he got on my case and threatened to contact FCC I told him to log date and time in his complaint. (I knew I was not on air at times he said I was, so I told him to log the info - then the full and accurate log, plus my travel statement from work favored me). He ended up getting cable when the FCC told him "Based on the information supplied the amateur radio operator is not the cause of the interference cited in your complaint".

73, Tom

On 5/22/2020 9:22 AM, Scott Davis via groups.io wrote:
Hi Tom,

Thanks for your e-mail.  Sorry, most folks don't log an off time for individual net checkouts (or regular QSOs for that matter), so I have not included it in the net feature.  There is no need to add it after the fact, unless you actually need it for some reason.  Services such as LoTW don't look for a time off field.

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: Tom & Barb Valosin <valosin@...>
To: N3FJPSoftwareUsers@groups.io
Sent: Fri, May 22, 2020 9:08 am
Subject: [N3FJPSoftwareUsers] NET logging option query

Hello Kimberly & Scott
After all these years of using your fine program and logging net operations the hard way, entering each participant individually on ACL, then
editing, I finally discovered the NET function. Funny what one can do when CORONA keeps you shack-bound!
My questions is this - When I hit the save and log function which transfers the info to ACL, a great feature, is there any way to log the "time off" other than what I am doing - editing each participant line once the record is in ACL?
Be well & 73,
Tom. WB2KLD


Re: Upload error to LoTW

Ed Armstrong <edarm2@...>
 

Steve,

You were 100% right and this cured the problem.

Many TNX and 73,
Ed
ND8R

On Thursday, May 21, 2020, 08:33:41 PM EDT, AI3KS <ai3ks.01@...> wrote:


Ed,

Make sure your TQSL is up to date.

Steve, AI3KS

On 20/05/21 18:33, Ed Armstrong via groups.io wrote:
I am using ACLog 6.6 and am trying to upload a FT8 contact to LoTW and receive the error message "Invalid MODE (FT8) on line 38."

Is there a simple solution (I hope)?

73,
Ed
ND8R


Re: NET logging option query

Scott Davis
 

Hi Tom,

Thanks for your e-mail.  Sorry, most folks don't log an off time for individual net checkouts (or regular QSOs for that matter), so I have not included it in the net feature.  There is no need to add it after the fact, unless you actually need it for some reason.  Services such as LoTW don't look for a time off field.

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: Tom & Barb Valosin <valosin@...>
To: N3FJPSoftwareUsers@groups.io
Sent: Fri, May 22, 2020 9:08 am
Subject: [N3FJPSoftwareUsers] NET logging option query

Hello Kimberly & Scott
After all these years of using your fine program and logging net operations the hard way, entering each participant individually on ACL, then
editing, I finally discovered the NET function. Funny what one can do when CORONA keeps you shack-bound!
My questions is this - When I hit the save and log function which transfers the info to ACL, a great feature, is there any way to log the "time off" other than what I am doing - editing each participant line once the record is in ACL?
Be well & 73,
Tom. WB2KLD


NET logging option query

Tom & Barb Valosin
 

Hello Kimberly & Scott

After all these years of using your fine program and logging net operations the hard way, entering each participant individually on ACL, then
editing, I finally discovered the NET function. Funny what one can do when CORONA keeps you shack-bound!

My questions is this - When I hit the save and log function which transfers the info to ACL, a great feature, is there any way to log the "time off" other than what I am doing - editing each participant line once the record is in ACL?

Be well & 73,

Tom. WB2KLD


Re: Upload error to LoTW

AI3KS
 

Ed,

Make sure your TQSL is up to date.

Steve, AI3KS

On 20/05/21 18:33, Ed Armstrong via groups.io wrote:
I am using ACLog 6.6 and am trying to upload a FT8 contact to LoTW and receive the error message "Invalid MODE (FT8) on line 38."

Is there a simple solution (I hope)?

73,
Ed
ND8R


Upload error to LoTW

Ed Armstrong <edarm2@...>
 

I am using ACLog 6.6 and am trying to upload a FT8 contact to LoTW and receive the error message "Invalid MODE (FT8) on line 38."

Is there a simple solution (I hope)?

73,
Ed
ND8R


Re: ACL Audio alerts won't turn off

Ed Milcarsky
 

That was it, Thanks


Re: ACL Audio alerts won't turn off

Scott Davis
 

Hi Ed,

Thanks for your e-mail.  Also click eLogs > LoTW > ID Users and deselect the option to play the audio alert.  There is also an audio alert option on the Watch List form as well.

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: Ed Milcarsky <kg4arn@...>
To: N3FJPSoftwareUsers@groups.io
Sent: Thu, May 21, 2020 6:06 pm
Subject: [N3FJPSoftwareUsers] ACL Audio alerts won't turn off

I can't seem to get the audio alerts to turn off. 
Settings > Dx Spotting > Configure   and I have unchecked the Audio Alerts and the Speak Details:  DX and Needed Spot boxes.  I have restarted ACL and the PC.  No luck.
What am I missing?
de Ed KG4ARN


ACL Audio alerts won't turn off

Ed Milcarsky
 

I can't seem to get the audio alerts to turn off. 
Settings > Dx Spotting > Configure   and I have unchecked the Audio Alerts and the Speak Details:  DX and Needed Spot boxes.  I have restarted ACL and the PC.  No luck.
What am I missing?
de Ed KG4ARN


Re: CQ WW WPX Contest

Scott Davis
 

Hi Mel,

Thanks for your e-mail.  Wildcards that you can insert in your F key strings are:

$ for Call (Sends main form Call field value)

* for RST (sends RST value or 5NN if blank)

# for the next consecutive Serial Number 

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: Mel Marcus <melm@...>
To: N3FJP Group <N3FJPSoftwareUsers@groups.io>
Sent: Thu, May 21, 2020 2:48 am
Subject: [N3FJPSoftwareUsers] CQ WW WPX Contest

IN the contest I don't want to use rig control, but I do want to use the CW transmit function. I am able to send CW so that part is working, but in the contest , serial number is used. how do I get the CW to include the serial num and the 599

Mel

4381 - 4400 of 46142