Date   

locked Re: K2H/NAS and GRID SQUARE

Jim Shorney
 

I agree, I think this has run its course. To answer your question, Part 97 defines "indicator" but not "prefix".

73

-Jim
NU0C

On Sat, 02 May 2020 18:58:18 +0100
"Philip Rose via groups.io" <pvrose@...> wrote:

I don't really want to continue this, but I'll leave by asking how does the FCC document define the term it uses, international prefix (iirc). Our UK&CD licence does, or is the US government providing income for lawyers with lax regulation?

73 Phil GM3ZZA sk

--
73 Phil GM3ZZA


locked Re: K2H/NAS and GRID SQUARE

Reino Talarmo
 

Jim,
Those are the series and for the radio amateur usage two first characters
are normally used to indicate authority and used as prefix to indicate the
country. There is more information in
https://en.wikipedia.org/wiki/Amateur_radio_call_signs.
Perhaps the most relevant issue is that for radio amateur usage three
letters is not used as a prefix for location indication.

Also document
https://www.itu.int/en/ITU-R/terrestrial/fmd/Documents/fxm-art19-sec3.pdf
defines and confirms the issue
19.50 § 22 Call signs in the international series are formed as indicated in
Nos. 19.51
to 19.71. The first two characters shall be two letters or a letter followed
by a digit or a digit
followed by a letter. The first two characters or in certain cases the first
character of a call sign
constitute the nationality identification4.

Specially for us
19.67 Amateur and experimental stations
19.68 § 30 1)
– one character (provided that it is the letter B, F, G, I, K, M, N, R or W)
and a
single digit (other than 0 or 1), followed by a group of not more than four
characters, the last of which shall be a letter, or
– two characters and a single digit (other than 0 or 1), followed by a group
of not
more than four characters, the last of which shall be a letter.5

73, Reino OH3mA

-----Original Message-----
From: WSJTX@groups.io [mailto:WSJTX@groups.io] On Behalf Of Jim Shorney
Sent: 2. toukokuuta 2020 19:07
To: WSJTX@groups.io
Subject: Re: [WSJTX] K2H/NAS and GRID SQUARE


The DXCC list is not a complete listing of prefix blocks. See:

http://www.arrl.org/international-call-sign-series

73

-Jim
NU0C


On Sat, 2 May 2020 18:33:40 +0300
"Reino Talarmo" <reino.talarmo@...> wrote:

The latter part is covered by DXCC list, I assume. I have no idea what are
indicators specified by the FCC Rules.


locked Re: help -- suddenly no audio out to radio #AudioIssues #AudioIssues

Bill Somerville
 

Hi Bob,

try starting WSJT-X, changing the two audio devices to another device ("Settings->Audio"), then click "Ok". Then revert the settings back to the audio devices connected to your rig.

Also go through the procedure I list in this prior post:


to set up the Tx audio levels.

73
Bill
G4WJS.

On 02/05/2020 19:27, Bob Kircher wrote:

Bill, by "Tx audio offset" do you mean what is my Transmit frequency selected?

If that is what you mean any of the offsets.  300-hz, 1000-hz, 2000-hz, etc.

AND I have the same problem when I use WSPR.

And let me re-emphasize two things...

1) when I installed v2.1 on Wednesday it worked perfect for all of Wednesday and through most of Thursday until about 5pm and then suddenly it didn't work anymore.

2) I still have v1.9 on my computer and it still works perfect.  All the same settings because there is only one set of settings for all versions.  At least so it appears to me.  There is only one wsjt-x.ini file on my computer.

Bob.

Bob Kircher, K7QXY
Tigard, OR
(503) 789-3983 (cell)

Please be sure your contacts lists show kircherbob@... for my address.


On Sat, May 2, 2020 at 2:06 AM Bill Somerville <g4wjs@...> wrote:
On 02/05/2020 00:27, Bob Kircher wrote:
version 2.1 worked fine for 2 days.
Suddenly one minute it was okay.
Next minute no audio out to radio.  No configuration or Windows10 changes.
Long story short, 1.9 still works perfect.  But not 2.1, and not 2.0.
 
I uninstalled 2.1 and reinstalled still does not work.  Uninstalled and then installed 2.0 and it does not work.
All three same configuration using CODEX.  This is the way it has always been.  I used 1.9 extensively for WSPR.
I installed 2.1 two days ago so could be current and start working FT8.
All was good.  Then suddenly -- literally suddenly.
2.1 and 2.0 seems broke.
 
As far as I can tell all three use the same settings file.
WSPR still works perfect on 1.9.  Tune button works perfect on 1.9 any mode.
Decoding works okay on 2.1 and 2.0
BUT no audio out to radio with 2.1 or 2.0 using Tune button.  CAT control works, and Radio goes into transmit but no power output because not audio input from computer (except when using 1.9).
Go to computer and shutdown 2.0 and start up 1.9 and all works perfect with Tune button.
 
What happened?  What do I do?
Please help.  I'm dead in the water.

Hi Bob,

what Tx audio offset do you have set when this occurs?

73
Bill
G4WJS.



locked Re: help -- suddenly no audio out to radio #AudioIssues #AudioIssues

Bob Kircher
 

Bill, by "Tx audio offset" do you mean what is my Transmit frequency selected?

If that is what you mean any of the offsets.  300-hz, 1000-hz, 2000-hz, etc.

AND I have the same problem when I use WSPR.

And let me re-emphasize two things...

1) when I installed v2.1 on Wednesday it worked perfect for all of Wednesday and through most of Thursday until about 5pm and then suddenly it didn't work anymore.

2) I still have v1.9 on my computer and it still works perfect.  All the same settings because there is only one set of settings for all versions.  At least so it appears to me.  There is only one wsjt-x.ini file on my computer.

Bob.

Bob Kircher, K7QXY
Tigard, OR
(503) 789-3983 (cell)

Please be sure your contacts lists show kircherbob@... for my address.


On Sat, May 2, 2020 at 2:06 AM Bill Somerville <g4wjs@...> wrote:
On 02/05/2020 00:27, Bob Kircher wrote:
version 2.1 worked fine for 2 days.
Suddenly one minute it was okay.
Next minute no audio out to radio.  No configuration or Windows10 changes.
Long story short, 1.9 still works perfect.  But not 2.1, and not 2.0.
 
I uninstalled 2.1 and reinstalled still does not work.  Uninstalled and then installed 2.0 and it does not work.
All three same configuration using CODEX.  This is the way it has always been.  I used 1.9 extensively for WSPR.
I installed 2.1 two days ago so could be current and start working FT8.
All was good.  Then suddenly -- literally suddenly.
2.1 and 2.0 seems broke.
 
As far as I can tell all three use the same settings file.
WSPR still works perfect on 1.9.  Tune button works perfect on 1.9 any mode.
Decoding works okay on 2.1 and 2.0
BUT no audio out to radio with 2.1 or 2.0 using Tune button.  CAT control works, and Radio goes into transmit but no power output because not audio input from computer (except when using 1.9).
Go to computer and shutdown 2.0 and start up 1.9 and all works perfect with Tune button.
 
What happened?  What do I do?
Please help.  I'm dead in the water.

Hi Bob,

what Tx audio offset do you have set when this occurs?

73
Bill
G4WJS.



locked Re: K2H/NAS and GRID SQUARE

Kermit Lehman
 

The appended suffix is a New York county abbreviation.  Normally, they are used in the NY state QSO party.

Look up K2H on qrz.com.
 

73,
Ken, AB1J


-----Original Message-----
From: Lawrence Godek <LawrenceG94@...>
To: WSJTX@groups.io
Sent: Sat, May 2, 2020 5:56 pm
Subject: Re: [WSJTX] K2H/NAS and GRID SQUARE

Those are all part of a special event to honor first responders in NYC as I read it.  Mo idea what the particular suffix means other than maybe the suffix of the users station.

-------- Original message --------
From: Herb Blue <WB8ASI@...>
Date: 5/2/20 7:58 AM (GMT-07:00)
To: WSJTX@groups.io
Subject: Re: [WSJTX] K2H/NAS and GRID SQUARE

FWIW, yesterday I saw K2H/SU on my cluster as being from Eqypt, and K2H/RE as being from Russia.   Have not seen any of those today.  73 Herb WB8ASI
On May 2, 2020 at 10:52 AM Jim Shorney < jshorney@...> wrote:



I don't, thank you. I have operated NU0C/0 and also as W1AW/0.

73

-Jim
NU0C

On Sat, 2 May 2020 14:42:35 +0000 (UTC)
"Kermit Lehman via groups.io" < ktfrog007@...> wrote:

Then don't ever operate as NU0C/M (UK-England).  Or /MM (UK-Scotland) or /AM (Spain).
73,Ken, AB1J


-----Original Message-----
From: Jim Shorney < jshorney@...>
Sent: Sat, May 2, 2020 2:26 pm
Subject: Re: [WSJTX] K2H/NAS and GRID SQUARE


Yes, and that is the problem. Self assigned Callsign /indicators that fall within the prefix block of another country are not legal in the USA per 97.119(4)(c). I wrote below that most ops are not aware of this. Now you are.


73

-Jim
NU0C

On Sat, 2 May 2020 14:01:43 +0000 (UTC)
"Kermit Lehman via groups.io" < ktfrog007@...> wrote:

This is done frequently and forever in state QSO parties.  In-state ops append their county abbreviation and out-of-state ops append their state abbreviation.    
73,
Ken, AB1J/MA

-----Original Message-----
From: Jim Shorney < jshorney@...>
To: WA2NDV via groups.io < frankatcvc@...>
Sent: Sat, May 2, 2020 2:00 am
Subject: Re: [WSJTX] K2H/NAS and GRID SQUARE


You need to verify the legality of your /indicators. Relevant text is Part 97 97.119(4)(c):

"No self-assigned indicator may conflict with any other indicator specified by the FCC Rules or with any prefix assigned to another country."


73

-Jim
NU0C


 


locked Re: help -- suddenly no audio out to radio #AudioIssues #AudioIssues

Richard Lawn
 

I had similar problems yesterday just as I went to make some EME contacts and got really frustrated. Finally after suspecting that it was a usb reassign error due to a win 10 upgrade, I realized that what was reported was a hamlib error. I searched for hamlib and it allowed me to reinstall it. While an error popped up during the install process it did fix the problem. Then in the middle of an EME QSO I lost audio output. I ended up restarting the computer and the problem seemed to be fixed. Haven’t tried it yet today. The real frustration came in the trouble shooting process was when I tried to connect CAT using other applications such as HRD and MSHV and found there were no problems. I also tried my 7610 and it worked just fine with WSJT-X. If this continues I may have to return to WSJT for eme work as I’m still not convinced that I have this solved. I’ll read through some of the other suggestions made.

Rick, W2JAZ 


--

--
Rick, W2JAZ 


locked Re: K2H/NAS and GRID SQUARE

 

I don't really want to continue this, but I'll leave by asking how does the FCC document define the term it uses, international prefix (iirc). Our UK&CD licence does, or is the US government providing income for lawyers with lax regulation?

73 Phil GM3ZZA sk

--
73 Phil GM3ZZA


locked Re: K2H/NAS and GRID SQUARE

Lawrence Godek
 

Those are all part of a special event to honor first responders in NYC as I read it.  Mo idea what the particular suffix means other than maybe the suffix of the users station.

-------- Original message --------
From: Herb Blue <WB8ASI@...>
Date: 5/2/20 7:58 AM (GMT-07:00)
To: WSJTX@groups.io
Subject: Re: [WSJTX] K2H/NAS and GRID SQUARE

FWIW, yesterday I saw K2H/SU on my cluster as being from Eqypt, and K2H/RE as being from Russia.   Have not seen any of those today.  73 Herb WB8ASI
On May 2, 2020 at 10:52 AM Jim Shorney < jshorney@...> wrote:



I don't, thank you. I have operated NU0C/0 and also as W1AW/0.

73

-Jim
NU0C

On Sat, 2 May 2020 14:42:35 +0000 (UTC)
"Kermit Lehman via groups.io" < ktfrog007@...> wrote:

Then don't ever operate as NU0C/M (UK-England).  Or /MM (UK-Scotland) or /AM (Spain).
73,Ken, AB1J


-----Original Message-----
From: Jim Shorney < jshorney@...>
Sent: Sat, May 2, 2020 2:26 pm
Subject: Re: [WSJTX] K2H/NAS and GRID SQUARE


Yes, and that is the problem. Self assigned Callsign /indicators that fall within the prefix block of another country are not legal in the USA per 97.119(4)(c). I wrote below that most ops are not aware of this. Now you are.


73

-Jim
NU0C

On Sat, 2 May 2020 14:01:43 +0000 (UTC)
"Kermit Lehman via groups.io" < ktfrog007@...> wrote:

This is done frequently and forever in state QSO parties.  In-state ops append their county abbreviation and out-of-state ops append their state abbreviation.    
73,
Ken, AB1J/MA

-----Original Message-----
From: Jim Shorney < jshorney@...>
To: WA2NDV via groups.io < frankatcvc@...>
Sent: Sat, May 2, 2020 2:00 am
Subject: Re: [WSJTX] K2H/NAS and GRID SQUARE


You need to verify the legality of your /indicators. Relevant text is Part 97 97.119(4)(c):

"No self-assigned indicator may conflict with any other indicator specified by the FCC Rules or with any prefix assigned to another country."


73

-Jim
NU0C


 


locked Re: No menu available below WSJT-X header

Lawrence Godek
 

That may be but never the less that's where FT4 activity is happening.

-------- Original message --------
From: Jim Brown <k9yc@...>
Date: 5/1/20 12:25 PM (GMT-07:00)
To: WSJTX@groups.io
Subject: Re: [WSJTX] No menu available below WSJT-X header

On 5/1/2020 7:44 AM, Lawrence Godek wrote:
> Just a lot of stations use FT4 on 14080 and 7047 and i do participate
> when i happen to tune across those freq's.

7047 kHz is part of the CW band widely used for casual QSOs, QRP, QRS,
QSO parties, and county hunters. It is absolutely the wrong place for a
digital watering hole.

73, Jim K9YC


locked Re: K2H/NAS and GRID SQUARE

Paul F6EXV <f6exv@...>
 


Remember that CEPT says "preceded"... so if you go to Scotland, you shall operate MM/K8BL, not K8BL/MM

73
Paul F6EXV

Le 02/05/2020 à 19:03, K8BL BOB LIDDY a écrit :

Why don't you folks look up K2H on QRZ(dot)COM and read
the explanation of what the Calls actually mean?

Also, some Spotting Networks appear to be truncating the suffixes
of those Special Event Stations at 2 Letters. That is why they are
showing up as random Entities. The K2H Stations are sending their
Call Suffixes properly and legally per:

GL/73,    Bob  K8BL



On Saturday, May 2, 2020, 10:58:24 AM EDT, Herb Blue <wb8asi@...> wrote:


FWIW, yesterday I saw K2H/SU on my cluster as being from Eqypt, and K2H/RE as being from Russia.   Have not seen any of those today.  73 Herb WB8ASI
On May 2, 2020 at 10:52 AM Jim Shorney < jshorney@...> wrote:



I don't, thank you. I have operated NU0C/0 and also as W1AW/0.

73

-Jim
NU0C

On Sat, 2 May 2020 14:42:35 +0000 (UTC)
"Kermit Lehman via groups.io" < ktfrog007@...> wrote:

Then don't ever operate as NU0C/M (UK-England).  Or /MM (UK-Scotland) or /AM (Spain).
73,Ken, AB1J


-----Original Message-----
From: Jim Shorney < jshorney@...>
Sent: Sat, May 2, 2020 2:26 pm
Subject: Re: [WSJTX] K2H/NAS and GRID SQUARE


Yes, and that is the problem. Self assigned Callsign /indicators that fall within the prefix block of another country are not legal in the USA per 97.119(4)(c). I wrote below that most ops are not aware of this. Now you are.


73

-Jim
NU0C

On Sat, 2 May 2020 14:01:43 +0000 (UTC)
"Kermit Lehman via groups.io" < ktfrog007@...> wrote:

This is done frequently and forever in state QSO parties.  In-state ops append their county abbreviation and out-of-state ops append their state abbreviation.    
73,
Ken, AB1J/MA

-----Original Message-----
From: Jim Shorney < jshorney@...>
To: WA2NDV via groups.io < frankatcvc@...>
Sent: Sat, May 2, 2020 2:00 am
Subject: Re: [WSJTX] K2H/NAS and GRID SQUARE


You need to verify the legality of your /indicators. Relevant text is Part 97 97.119(4)(c):

"No self-assigned indicator may conflict with any other indicator specified by the FCC Rules or with any prefix assigned to another country."


73

-Jim
NU0C


 


    


locked Re: K2H/NAS and GRID SQUARE

Jim Shorney
 

This I have said.

On Sat, 2 May 2020 10:19:34 -0700
"Jim Brown" <k9yc@...> wrote:

I have operated NU0C/0 and also as W1AW/0.
Both /0 designations are legal, but have been unnecessary for 50 years.


locked Re: K2H/NAS and GRID SQUARE

Jim Shorney
 

That seems to narrow it down a bit:

"No self-assigned indicator may conflict with any other indicator specified by the FCC Rules (such as "AA", "AG", "AE" or "KT") or with any prefix assigned to another country (such as "DL", "F", "G" or "VE")."

However, that's not quite what 97.119 says. As I wrote, it seems to be a bit of a gray area. Given the fluidity of callsign assignments these days and that the ITU blocks are granular to three letters my choice would be not to do it. YMMV as they say. Clearly using a two letter indicator that maps to another DXCC if you are not there would be wrong and every ham should know that. It seem that /MM is a special case. "Maritime Mobile" is a commercial service governed by FCC Part 80 for the USA. I found this page on "maritime mobile amateur radio" but it is UK-centric:

https://en.wikipedia.org/wiki/Maritime_mobile_amateur_radio

In any case it seems to require a thorough knowledge of local and international regulations. I would assume that anyone smart enough to run a boat is probably aware of the rules. :)

73

-Jim
NU0C

On Sat, 2 May 2020 17:03:03 +0000 (UTC)
"K8BL BOB LIDDY" <k8bl@...> wrote:

Why don't you folks look up K2H on QRZ(dot)COM and readthe explanation of what the Calls actually mean?https://www.qrz.com/lookup/k2h

Also, some Spotting Networks appear to be truncating the suffixesof those Special Event Stations at 2 Letters. That is why they areshowing up as random Entities. The K2H Stations are sending theirCall Suffixes properly and legally per:https://www.fcc.gov/wireless/bureau-divisions/mobility-division/amateur-radio-service/special-event-call-signs

GL/73,    Bob  K8BL


On Saturday, May 2, 2020, 10:58:24 AM EDT, Herb Blue <wb8asi@...> wrote:

FWIW, yesterday I saw K2H/SU on my cluster as being from Eqypt, and K2H/RE as being from Russia.   Have not seen any of those today.  73 Herb WB8ASI
On May 2, 2020 at 10:52 AM Jim Shorney < jshorney@...> wrote:


I don't, thank you. I have operated NU0C/0 and also as W1AW/0.
73
-Jim NU0C
On Sat, 2 May 2020 14:42:35 +0000 (UTC) "Kermit Lehman via groups.io" < ktfrog007@...> wrote:

Then don't ever operate as NU0C/M (UK-England).  Or /MM (UK-Scotland) or /AM (Spain). 73,Ken, AB1J

-----Original Message----- From: Jim Shorney < jshorney@...> To: WSJTX@groups.io Sent: Sat, May 2, 2020 2:26 pm Subject: Re: [WSJTX] K2H/NAS and GRID SQUARE

Yes, and that is the problem. Self assigned Callsign /indicators that fall within the prefix block of another country are not legal in the USA per 97.119(4)(c). I wrote below that most ops are not aware of this. Now you are.
http://www.arrl.org/international-call-sign-series
73
-Jim NU0C
On Sat, 2 May 2020 14:01:43 +0000 (UTC) "Kermit Lehman via groups.io" < ktfrog007@...> wrote:

This is done frequently and forever in state QSO parties.  In-state ops append their county abbreviation and out-of-state ops append their state abbreviation.     73, Ken, AB1J/MA
-----Original Message----- From: Jim Shorney < jshorney@...> To: WA2NDV via groups.io < frankatcvc@...> Cc: WSJTX@groups.io Sent: Sat, May 2, 2020 2:00 am Subject: Re: [WSJTX] K2H/NAS and GRID SQUARE

You need to verify the legality of your /indicators. Relevant text is Part 97 97.119(4)(c):
"No self-assigned indicator may conflict with any other indicator specified by the FCC Rules or with any prefix assigned to another country."
http://www.zerobeat.net/drakelist/drakemod/tr7mod.html
73
-Jim NU0C

 




locked Re: K2H/NAS and GRID SQUARE

Paul F6EXV <f6exv@...>
 

Hi all
May I stress on
QUOTE
The license holder must use his national call sign preceded...
UNQUOTE

I hold the call sign WH7S too, but I am French. So wherever I go  and wish to operate under the CEPT agreement, I must use my F6EXV callsign, not any other that I hold.
There is a tendency to forget this part of the rule...

73
Paul

Le 02/05/2020 à 18:27, Kai-KE4PT a écrit :

Construction of call signs:
CEPT Recommendation T/R 61-01 gives some guidance on the construction of call signs for stations transmitting from a host country subscribing to the CEPT provisions, as does the USA:
"2.3 When transmitting in the visited country the licence holder must use his national call sign preceded by
the call sign prefix of the visited country as indicated in ANNEX 2: and ANNEX 4:. The call sign prefix
and the national call sign must be separated by the character “/” (telegraphy) or the word “stroke”
(telephony)."
USA subscribes to the CEPT recommendation, so GM3ZAA or OH3MA  transmitting in the '4' call area of the USA would identify as W4/GM3ZAA of W4/OH3MA. I would identify as ZL/KE4PT when transmitting from New Zealand.
I guess that leaves it as a default that the self-assigned maritime mobile designation '/MM' should be appended to the end of a call sign. In mid-Atlantic Ocean I'd identify as KE4PT/MM.

With kindest regards,
Kai Siwiak, KE4PT


On 5/2/2020 11:33, Reino Talarmo wrote:

Phil,

Perhaps this gives a hint or two:

§ 97.119 Station identification.

(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 latter part is covered by DXCC list, I assume. I have no idea what are indicators specified by the FCC Rules.

 

(g) When the station is transmitting under the authority of § 97.107 of this part, an indicator consisting of the appropriate letter-numeral designating the station location must be included before the call sign that was issued to the station by the country granting the license. For an amateur service license granted by the Government of Canada, however, the indicator must be included after the call sign. At least once during each intercommunication, the identification announcement must include the geographical location as nearly as possible by city and state, commonwealth or possession.

73, Reino OH3mA

 

From: WSJTX@groups.io [mailto:WSJTX@groups.io] On Behalf Of Philip Rose via groups.io
Sent: 2. toukokuuta 2020 18:08
To: WSJTX@groups.io
Subject: Re: [WSJTX] K2H/NAS and GRID SQUARE

 

NU0C/M is not a valid GB call – it would be M/NU0C, likewise MM/NU0C and in Spain EAx/NU0C where x is the regional number. Over here /M is required if we are mobile on land or in-shore waters, /MM in international waters. Do FCC really intend you not to use the prefix a visiting amateur would have to prefix or suffix their home call? The WAA-WZZ series are not prefixes in my mind, whereas W4 or KP4 would be.

 

Phil GM3ZZA.

 


[TRUNCATED]


    


locked Re: K2H/NAS and GRID SQUARE

Jim Brown
 

On 5/2/2020 7:52 AM, Jim Shorney wrote:
I have operated NU0C/0 and also as W1AW/0.
Both /0 designations are legal, but have been unnecessary for 50 years. Since then, the address on our licenses is a MAILING address, not a station location. The address on my license is in California. The only time I use /6 is on CW during 6M band openings, so that callers won't turn their beams in the wrong direction. And I haven't done that for 3 years, because CW has been non-existent on 6M for that long. :)

The use of /<COUNTY> suffixes has long been common in state QSO parties by mobiles and portable setups that move from county to county during the weekend. You'll hear a LOT of that this weekend from those of us working 7QP, NEQP, and INQP. For example, /NVWHI for White Pine Co, NV, one of six counties our team activated last year. COVID-19 has us operating from home this year.

73, Jim K9YC


locked Re: K2H/NAS and GRID SQUARE

Herb Blue - WB8ASI
 

Already have checked it all out.  No problem.  My Alerts just keep me awake when triggering on truncated spots.  I worked my "Egypt" station K2H/SUF from Suffolk County, NY  for COVID-19 Heros, and he's in my log.  73, Herb

On May 2, 2020 at 1:03 PM K8BL BOB LIDDY <k8bl@...> wrote:

 
Why don't you folks look up K2H on QRZ(dot)COM and read
the explanation of what the Calls actually mean?

Also, some Spotting Networks appear to be truncating the suffixes
of those Special Event Stations at 2 Letters. That is why they are
showing up as random Entities. The K2H Stations are sending their
Call Suffixes properly and legally per:

GL/73,    Bob  K8BL



On Saturday, May 2, 2020, 10:58:24 AM EDT, Herb Blue <wb8asi@...> wrote:


FWIW, yesterday I saw K2H/SU on my cluster as being from Eqypt, and K2H/RE as being from Russia.   Have not seen any of those today.  73 Herb WB8ASI
On May 2, 2020 at 10:52 AM Jim Shorney < jshorney@...> wrote:



I don't, thank you. I have operated NU0C/0 and also as W1AW/0.

73

-Jim
NU0C

On Sat, 2 May 2020 14:42:35 +0000 (UTC)
"Kermit Lehman via groups.io" < ktfrog007@...> wrote:

Then don't ever operate as NU0C/M (UK-England).  Or /MM (UK-Scotland) or /AM (Spain).
73,Ken, AB1J


-----Original Message-----
From: Jim Shorney < jshorney@...>
Sent: Sat, May 2, 2020 2:26 pm
Subject: Re: [WSJTX] K2H/NAS and GRID SQUARE


Yes, and that is the problem. Self assigned Callsign /indicators that fall within the prefix block of another country are not legal in the USA per 97.119(4)(c). I wrote below that most ops are not aware of this. Now you are.


73

-Jim
NU0C

On Sat, 2 May 2020 14:01:43 +0000 (UTC)
"Kermit Lehman via groups.io" < ktfrog007@...> wrote:

This is done frequently and forever in state QSO parties.  In-state ops append their county abbreviation and out-of-state ops append their state abbreviation.    
73,
Ken, AB1J/MA

-----Original Message-----
From: Jim Shorney < jshorney@...>
To: WA2NDV via groups.io < frankatcvc@...>
Sent: Sat, May 2, 2020 2:00 am
Subject: Re: [WSJTX] K2H/NAS and GRID SQUARE


You need to verify the legality of your /indicators. Relevant text is Part 97 97.119(4)(c):

"No self-assigned indicator may conflict with any other indicator specified by the FCC Rules or with any prefix assigned to another country."


73

-Jim
NU0C


 
 
 


 


locked Re: K2H/NAS and GRID SQUARE

K8BL BOB LIDDY <k8bl@...>
 

Why don't you folks look up K2H on QRZ(dot)COM and read
the explanation of what the Calls actually mean?

Also, some Spotting Networks appear to be truncating the suffixes
of those Special Event Stations at 2 Letters. That is why they are
showing up as random Entities. The K2H Stations are sending their
Call Suffixes properly and legally per:

GL/73,    Bob  K8BL



On Saturday, May 2, 2020, 10:58:24 AM EDT, Herb Blue <wb8asi@...> wrote:


FWIW, yesterday I saw K2H/SU on my cluster as being from Eqypt, and K2H/RE as being from Russia.   Have not seen any of those today.  73 Herb WB8ASI

On May 2, 2020 at 10:52 AM Jim Shorney < jshorney@...> wrote:



I don't, thank you. I have operated NU0C/0 and also as W1AW/0.

73

-Jim
NU0C

On Sat, 2 May 2020 14:42:35 +0000 (UTC)
"Kermit Lehman via groups.io" < ktfrog007@...> wrote:

Then don't ever operate as NU0C/M (UK-England).  Or /MM (UK-Scotland) or /AM (Spain).
73,Ken, AB1J


-----Original Message-----
From: Jim Shorney < jshorney@...>
Sent: Sat, May 2, 2020 2:26 pm
Subject: Re: [WSJTX] K2H/NAS and GRID SQUARE


Yes, and that is the problem. Self assigned Callsign /indicators that fall within the prefix block of another country are not legal in the USA per 97.119(4)(c). I wrote below that most ops are not aware of this. Now you are.


73

-Jim
NU0C

On Sat, 2 May 2020 14:01:43 +0000 (UTC)
"Kermit Lehman via groups.io" < ktfrog007@...> wrote:

This is done frequently and forever in state QSO parties.  In-state ops append their county abbreviation and out-of-state ops append their state abbreviation.    
73,
Ken, AB1J/MA

-----Original Message-----
From: Jim Shorney < jshorney@...>
To: WA2NDV via groups.io < frankatcvc@...>
Sent: Sat, May 2, 2020 2:00 am
Subject: Re: [WSJTX] K2H/NAS and GRID SQUARE


You need to verify the legality of your /indicators. Relevant text is Part 97 97.119(4)(c):

"No self-assigned indicator may conflict with any other indicator specified by the FCC Rules or with any prefix assigned to another country."


73

-Jim
NU0C


 


locked Re: K2H/NAS and GRID SQUARE

Jim Shorney
 

Why does it say at the top of the page "Prefix assignments by the International Telecommunications Union (ITU)"?

Actual callsign prefixes are derived from the allocations within the listed blocks.

More info here:

https://www.itu.int/en/ITU-R/terrestrial/fmd/Pages/call_sign_series.aspx

For example, New Zealand is allocated ZKA-ZKZ, ZLA-ZLZ, ZMA-ZJZ. Seems pretty obvious. I would welcome clarification from the FCC.


73

-Jim
NU0C


On Sat, 2 May 2020 17:25:49 +0100
"Philip Rose via groups.io" <pvrose@...> wrote:

Jim,

I understand that, but those are not prefixes nor even prefix blocks. They are the ITU defined callsign series and the ITU What does the FCC mean when they say prefixes? To me a prefix when applied to an amateur callsign by prepending or appending is. I presume it Is defined elsewhere in that document you have been quoting.

73 Phil GM3ZZA.

Sent from Mail for Windows 10

From: Jim Shorney
Sent: 02 May 2020 17:06
To: WSJTX@groups.io
Subject: Re: [WSJTX] K2H/NAS and GRID SQUARE


The DXCC list is not a complete listing of prefix blocks. See:

http://www.arrl.org/international-call-sign-series

73

-Jim
NU0C


On Sat, 2 May 2020 18:33:40 +0300
"Reino Talarmo" <reino.talarmo@...> wrote:

The latter part is covered by DXCC list, I assume. I have no idea what are indicators specified by the FCC Rules.


locked Re: K2H/NAS and GRID SQUARE

Herb Blue - WB8ASI
 

Egypt is back today, and I need it for DXCC ATNO.

On May 2, 2020 at 10:58 AM HERB BLUE <herb.blue@...> wrote:

FWIW, yesterday I saw K2H/SU on my cluster as being from Eqypt, and K2H/RE as being from Russia.   Have not seen any of those today.  73 Herb WB8ASI
On May 2, 2020 at 10:52 AM Jim Shorney < jshorney@...> wrote:



I don't, thank you. I have operated NU0C/0 and also as W1AW/0.

73

-Jim
NU0C

On Sat, 2 May 2020 14:42:35 +0000 (UTC)
"Kermit Lehman via groups.io" < ktfrog007@...> wrote:

Then don't ever operate as NU0C/M (UK-England).  Or /MM (UK-Scotland) or /AM (Spain).
73,Ken, AB1J


-----Original Message-----
From: Jim Shorney < jshorney@...>
Sent: Sat, May 2, 2020 2:26 pm
Subject: Re: [WSJTX] K2H/NAS and GRID SQUARE


Yes, and that is the problem. Self assigned Callsign /indicators that fall within the prefix block of another country are not legal in the USA per 97.119(4)(c). I wrote below that most ops are not aware of this. Now you are.


73

-Jim
NU0C

On Sat, 2 May 2020 14:01:43 +0000 (UTC)
"Kermit Lehman via groups.io" < ktfrog007@...> wrote:

This is done frequently and forever in state QSO parties.  In-state ops append their county abbreviation and out-of-state ops append their state abbreviation.    
73,
Ken, AB1J/MA

-----Original Message-----
From: Jim Shorney < jshorney@...>
To: WA2NDV via groups.io < frankatcvc@...>
Sent: Sat, May 2, 2020 2:00 am
Subject: Re: [WSJTX] K2H/NAS and GRID SQUARE


You need to verify the legality of your /indicators. Relevant text is Part 97 97.119(4)(c):

"No self-assigned indicator may conflict with any other indicator specified by the FCC Rules or with any prefix assigned to another country."


73

-Jim
NU0C


 

 


locked Re: K2H/NAS and GRID SQUARE

Kai-KE4PT
 

Construction of call signs:
CEPT Recommendation T/R 61-01 gives some guidance on the construction of call signs for stations transmitting from a host country subscribing to the CEPT provisions, as does the USA:
"2.3 When transmitting in the visited country the licence holder must use his national call sign preceded by
the call sign prefix of the visited country as indicated in ANNEX 2: and ANNEX 4:. The call sign prefix
and the national call sign must be separated by the character “/” (telegraphy) or the word “stroke”
(telephony)."
USA subscribes to the CEPT recommendation, so GM3ZAA or OH3MA  transmitting in the '4' call area of the USA would identify as W4/GM3ZAA of W4/OH3MA. I would identify as ZL/KE4PT when transmitting from New Zealand.
I guess that leaves it as a default that the self-assigned maritime mobile designation '/MM' should be appended to the end of a call sign. In mid-Atlantic Ocean I'd identify as KE4PT/MM.

With kindest regards,
Kai Siwiak, KE4PT


On 5/2/2020 11:33, Reino Talarmo wrote:

Phil,

Perhaps this gives a hint or two:

§ 97.119 Station identification.

(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 latter part is covered by DXCC list, I assume. I have no idea what are indicators specified by the FCC Rules.

 

(g) When the station is transmitting under the authority of § 97.107 of this part, an indicator consisting of the appropriate letter-numeral designating the station location must be included before the call sign that was issued to the station by the country granting the license. For an amateur service license granted by the Government of Canada, however, the indicator must be included after the call sign. At least once during each intercommunication, the identification announcement must include the geographical location as nearly as possible by city and state, commonwealth or possession.

73, Reino OH3mA

 

From: WSJTX@groups.io [mailto:WSJTX@groups.io] On Behalf Of Philip Rose via groups.io
Sent: 2. toukokuuta 2020 18:08
To: WSJTX@groups.io
Subject: Re: [WSJTX] K2H/NAS and GRID SQUARE

 

NU0C/M is not a valid GB call – it would be M/NU0C, likewise MM/NU0C and in Spain EAx/NU0C where x is the regional number. Over here /M is required if we are mobile on land or in-shore waters, /MM in international waters. Do FCC really intend you not to use the prefix a visiting amateur would have to prefix or suffix their home call? The WAA-WZZ series are not prefixes in my mind, whereas W4 or KP4 would be.

 

Phil GM3ZZA.

 


[TRUNCATED]


locked Re: K2H/NAS and GRID SQUARE

 

Jim,

 

I understand that, but those are not prefixes nor even prefix blocks. They are the ITU defined callsign series and the ITU  What does the FCC mean when they say prefixes? To me a prefix when applied to an amateur callsign by prepending or appending is. I presume it Is defined elsewhere in that document you have been quoting.

 

73 Phil GM3ZZA.

 

Sent from Mail for Windows 10

 

From: Jim Shorney
Sent: 02 May 2020 17:06
To: WSJTX@groups.io
Subject: Re: [WSJTX] K2H/NAS and GRID SQUARE

 

 

The DXCC list is not a complete listing of prefix blocks. See:

 

http://www.arrl.org/international-call-sign-series

 

73

 

-Jim

NU0C

 

 

On Sat, 2 May 2020 18:33:40 +0300

"Reino Talarmo" <reino.talarmo@...> wrote:

 

> The latter part is covered by DXCC list, I assume. I have no idea what are indicators specified by the FCC Rules.

 

 


--
73 Phil GM3ZZA