Re: [wsjt-devel] Type 2 compound callsigns support

[Bill Somerville]

On 20/04/2018 21:59, g...@isect.com wrote:

Hi Bill.

/LH is another common lighthouse designation, and I guess a vanishingly rare
Norwegian location modifier

73
Gary  ZL2iFB


Hi Gary,

thanks for that, added. No idea how I missed that one.

73
Bill
G4WJS.


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Type 2 compound callsigns support

[gary]

Hi Bill.

/LH is another common lighthouse designation, and I guess a vanishingly rare
Norwegian location modifier

73
Gary  ZL2iFB

-Original Message-
From: Bill Somerville <g4...@classdesign.com> 
Sent: Saturday, 21 April 2018 8:36 a.m.
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Type 2 compound callsigns support

On 14/04/2018 21:48, Alessandro Gorobey via wsjt-devel wrote:
> Hi Bill,
>
> sorry for the intrusion,
>
> but I read some public lists with multiple "/".
>
> Limiting to
>
> https://lotw.arrl.org/lotw-user-activity.csv
> https://sourceforge.net/p/wsjt/wsjt/8597/tree//branches/wsjtx/cty.dat
>
> I found many "/" suffixies
> /LH /LGT /QRPP /Q /R /[A-Z] .
>
> Some are found on
> https://illw.net/
> http://www.arrl.org/jamboree-on-the-air-jota/
> and others
>
> Other seem to me unintelligible.
>
> /FF is for Flora and Fauna, form feed or other ?
> /AM is also for Amplitude Modulation ?
>
> There is a comprensive list of all of them ?
>
> Thank in advance and apologize if /OOT
>
> --
> 73
> Sandro
> IW3RAB

Hi Sandro,

thanks for those suggestions. I will incorporate some of the more common
ones. We need not worry about 4 letter suffixes like /JOTA or /QRPP as they
cannot be source encoded by the WSJT-X modes. The suffix /AM is most
commonly aeronautical mobile and that definitely needs to go in. I have also
included /R /Q /FF /FD /AM /MM /LT and /LGT. These can easily be amended as
we go as there is no protocol change, they are used only to block them from
being looked up as a DXCC Entity name for display purposes.

73
Bill
G4WJS.



--
Check out the vibrant tech community on one of the world's most engaging
tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Type 2 compound callsigns support

[Bill Somerville]

On 14/04/2018 21:48, Alessandro Gorobey via wsjt-devel wrote:

Hi Bill,

sorry for the intrusion,

but I read some public lists with multiple "/".

Limiting to

https://lotw.arrl.org/lotw-user-activity.csv
https://sourceforge.net/p/wsjt/wsjt/8597/tree//branches/wsjtx/cty.dat

I found many "/" suffixies
/LH /LGT /QRPP /Q /R /[A-Z] .

Some are found on
https://illw.net/
http://www.arrl.org/jamboree-on-the-air-jota/
and others

Other seem to me unintelligible.

/FF is for Flora and Fauna, form feed or other ?
/AM is also for Amplitude Modulation ?

There is a comprensive list of all of them ?

Thank in advance and apologize if /OOT

--
73
Sandro
IW3RAB


Hi Sandro,

thanks for those suggestions. I will incorporate some of the more common 
ones. We need not worry about 4 letter suffixes like /JOTA or /QRPP as 
they cannot be source encoded by the WSJT-X modes. The suffix /AM is 
most commonly aeronautical mobile and that definitely needs to go in. I 
have also included /R /Q /FF /FD /AM /MM /LT and /LGT. These can easily 
be amended as we go as there is no protocol change, they are used only 
to block them from being looked up as a DXCC Entity name for display 
purposes.


73
Bill
G4WJS.


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Type 2 compound callsigns support

[Alessandro Gorobey via wsjt-devel]

Hi Bill,

sorry for the intrusion,

but I read some public lists with multiple "/".

Limiting to

https://lotw.arrl.org/lotw-user-activity.csv
https://sourceforge.net/p/wsjt/wsjt/8597/tree//branches/wsjtx/cty.dat

I found many "/" suffixies
/LH /LGT /QRPP /Q /R /[A-Z] .

Some are found on
https://illw.net/
http://www.arrl.org/jamboree-on-the-air-jota/
and others

Other seem to me unintelligible.

/FF is for Flora and Fauna, form feed or other ?
/AM is also for Amplitude Modulation ?

There is a comprensive list of all of them ?

Thank in advance and apologize if /OOT

--
73
Sandro
IW3RAB

Il 13/04/2018 16:28, Frode LA2RL ha scritto:

Hi Bill,

There is also /AM for Aeronautical mobile operation.

73 Frode, LA2RL

On Fri, Apr 13, 2018 at 3:55 PM, Bill Somerville > wrote:


On 12/04/2018 11:42, Игорь Ч via wsjt-devel wrote:

.
It is either lack of code or just bad example in the documentation:

"QSOs involving *Type 2* compound callsigns might look like either
of the following sequences:

CQ K1ABC/VE1 FN75"
where country is not being recognized properly for this callsign in WSJT-X 
1.9-rc3:
.
102200 21 0.0 970 ~ CQ K1ABC/VE1 FN75  !U.S.A.
.
As it is up to local authorities to grant a licence, probably some extended 
support is required in the code to recognize country properly for type 2 
compound callsigns.
.
73 Igor UA3DJY


Hi Igor,

I can resolve this situation a little better than currently but
there will always be some ambiguity, for example some callsigns like
G4W/RI9F are hard to analyse and correctly determine the effective
prefix.

As part of this I need to form a list of commonly used suffixes that
are not used to represent a DXCC entity. Currently I have:

/0 /1 /2 /3 /4 /5 /6 /7 /8 /9 /P /QRP /FD

/A /M and /MM are ambiguous but as the UK is CEPT which recommends
using a prefix I am happy to interpret /M as meaning mobile and /MM
as meaning maritime mobile rather than operating in the UK. The same
applies to /A meaning alternative location instead of U.S.A..

*Question to all*: What other commonly used suffixes are there that
are not also used as country prefixes? Note that four character
suffixes without any digits, like /JOTA, can be ignored as they
cannot be encoded in the WSJT-X protocols.

73
Bill
G4WJS.



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/wsjt-devel





--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel





--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Type 2 compound callsigns support

[Frode LA2RL]

Hi Bill,

There is also /AM for Aeronautical mobile operation.

73 Frode, LA2RL

On Fri, Apr 13, 2018 at 3:55 PM, Bill Somerville 
wrote:

> On 12/04/2018 11:42, Игорь Ч via wsjt-devel wrote:
>
> .
> It is either lack of code or just bad example in the documentation:
>
> "QSOs involving *Type 2* compound callsigns might look like either of the
> following sequences:
>
> CQ K1ABC/VE1 FN75"
> where country is not being recognized properly for this callsign in WSJT-X 
> 1.9-rc3:
> .102200 21 0.0 970 ~ CQ K1ABC/VE1 FN75  !U.S.A.
> .
> As it is up to local authorities to grant a licence, probably some extended 
> support is required in the code to recognize country properly for type 2 
> compound callsigns.
> .
> 73 Igor UA3DJY
>
> Hi Igor,
>
> I can resolve this situation a little better than currently but there will
> always be some ambiguity, for example some callsigns like G4W/RI9F are hard
> to analyse and correctly determine the effective prefix.
>
> As part of this I need to form a list of commonly used suffixes that are
> not used to represent a DXCC entity. Currently I have:
>
> /0 /1 /2 /3 /4 /5 /6 /7 /8 /9 /P /QRP /FD
>
> /A /M and /MM are ambiguous but as the UK is CEPT which recommends using a
> prefix I am happy to interpret /M as meaning mobile and /MM as meaning
> maritime mobile rather than operating in the UK. The same applies to /A
> meaning alternative location instead of U.S.A..
>
> *Question to all*: What other commonly used suffixes are there that are
> not also used as country prefixes? Note that four character suffixes
> without any digits, like /JOTA, can be ignored as they cannot be encoded in
> the WSJT-X protocols.
>
> 73
> Bill
> G4WJS.
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Type 2 compound callsigns support

[Bill Somerville]

On 12/04/2018 11:42, Игорь Ч via wsjt-devel wrote:

.
It is either lack of code or just bad example in the documentation:

"QSOs involving *Type 2* compound callsigns might look like either of 
the following sequences:


CQ K1ABC/VE1 FN75"
where country is not being recognized properly for this callsign in WSJT-X 
1.9-rc3:
.
102200 21 0.0 970 ~ CQ K1ABC/VE1 FN75  !U.S.A.
.
As it is up to local authorities to grant a licence, probably some extended 
support is required in the code to recognize country properly for type 2 
compound callsigns.
.
73 Igor UA3DJY


Hi Igor,

I can resolve this situation a little better than currently but there 
will always be some ambiguity, for example some callsigns like G4W/RI9F 
are hard to analyse and correctly determine the effective prefix.


As part of this I need to form a list of commonly used suffixes that are 
not used to represent a DXCC entity. Currently I have:


/0 /1 /2 /3 /4 /5 /6 /7 /8 /9 /P /QRP /FD

/A /M and /MM are ambiguous but as the UK is CEPT which recommends using 
a prefix I am happy to interpret /M as meaning mobile and /MM as meaning 
maritime mobile rather than operating in the UK. The same applies to /A 
meaning alternative location instead of U.S.A..


*Question to all*: What other commonly used suffixes are there that are 
not also used as country prefixes? Note that four character suffixes 
without any digits, like /JOTA, can be ignored as they cannot be encoded 
in the WSJT-X protocols.


73
Bill
G4WJS.

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Type 2 compound callsigns support

[John]

Gary,

It is worth mentioning that the USA and Canada are not member countries of CEPT 
(European Conference of Postal and Telecommunications Administrations) and 
therefore these two countries (and other non-members) do not necessarily follow 
CEPT recommendations.  

It would be unwise to include CEPT recommendations as part of WSJT-X 
documentation, or to specify in WSJT-X code any particular method of using 
prefixes/suffixes which may not conform to different licence areas.  As you 
mention  this "opens a massive can of worms that WSJT-X is not going to fix”.   
At best WSJT-X should permit the use of either prefixes or suffixes and allow 
users to make the obvious correct interpretations that arise from annotations 
from the scanning of cty.dat

— John G4KLA




smime.p7s
Description: S/MIME cryptographic signature
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Type 2 compound callsigns support

[oe1eqw]

I'm afraid to say but AFAIK there are a lot more countries which require 
a SUFFIX and not a PREFIX - only countries which accept CEPT-license 
require a prefix.
WSJT-X gives us as a feature the country of the compound callsign - so 
it should be the right country, independent of prefix or suffix.


73
Enrico, OE1EQW



Am 12.04.2018 um 22:45 schrieb g...@isect.com:


Friends,

I understand the reciprocal agreement between USA and Canada, 
specifically, pre-dates the CEPT arrangement by many years, and 
specifies a locational /suffix/ … whereas under CEPT and (I believe) 
under most other reciprocal agreements, a locational /prefix/ is the 
norm, leaving the /suffix/ to designate the type of installation e.g. 
mobile, maritime mobile, portable, aeronautical mobile etc.


So, the VE or W locational /suffix/ is an exception … hence probably 
not an ideal example to use for the global audience.


Prefixes, suffixes, special calls, remote operations, /QRP, IOTA & 
zones references, and whether to log or ignore suffixes etc. opens a 
massive can of worms that WSJT-X is not going to fix, so I suggest 
ducking the issue as far as possible in the documentation, preferably 
using the more common CEPT locational /prefix/ as an example rather 
than the exceptional VE /suffix/?


That still leaves the issue of the program correctly identifying the 
locations of stations from their callsigns: good luck with that, given 
the vagaries of licensing and inconsistent usage in practice!  The 
grid reference is an alternative means of identifying where someone 
actually is … but perhaps the whole issue is best left to our logging 
software rather than WSJT-X.


73

Gary ZL2/GW4iFB/email!


[rest snipped]
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Type 2 compound callsigns support

[gary]

Friends,

 

I understand the reciprocal agreement between USA and Canada, specifically,
pre-dates the CEPT arrangement by many years, and specifies a locational
suffix . whereas under CEPT and (I believe) under most other reciprocal
agreements, a locational prefix is the norm, leaving the suffix to designate
the type of installation e.g. mobile, maritime mobile, portable,
aeronautical mobile etc.

 

So, the VE or W locational suffix is an exception . hence probably not an
ideal example to use for the global audience.  

 

Prefixes, suffixes, special calls, remote operations, /QRP, IOTA & zones
references, and whether to log or ignore suffixes etc. opens a massive can
of worms that WSJT-X is not going to fix, so I suggest ducking the issue as
far as possible in the documentation, preferably using the more common CEPT
locational prefix as an example rather than the exceptional VE suffix?

 

That still leaves the issue of the program correctly identifying the
locations of stations from their callsigns: good luck with that, given the
vagaries of licensing and inconsistent usage in practice!  The grid
reference is an alternative means of identifying where someone actually is .
but perhaps the whole issue is best left to our logging software rather than
WSJT-X.  

 

73

Gary  ZL2/GW4iFB/email!

 

From: John LeRoy via wsjt-devel <wsjt-devel@lists.sourceforge.net> 
Sent: Friday, 13 April 2018 4:31 a.m.
To: wsjt-devel@lists.sourceforge.net
Cc: John LeRoy <w4jklle...@aim.com>
Subject: Re: [wsjt-devel] Type 2 compound callsigns support

 

https://www.ic.gc.ca/eic/site/025.nsf/eng/h_6.html#tao4


1.  I am an amateur radio operator visiting Canada from another country.
While in Canada can I use my call sign from my home country? 


As per the document RIC-9: Call sign policy and special event prefixes
<https://www.ic.gc.ca/eic/site/smt-gst.nsf/eng/sf02102.html> , you may use
the call sign assigned by your country's administration in Canada, but you
must bring your amateur radio operator's certificate/licence and have
obtained a CEPT certificate from your home administration. If your country
is not part of the CEPT agreement you must obtain a letter of authority from
the Amateur Radio Service Centre (ARSC)
<https://www.ic.gc.ca/eic/site/025.nsf/eng/h_00010.html> . Visiting amateurs
must include the prefix of the geographical location, and the area of
operation with the identification of their station. Therefore, an amateur
from the United Kingdom with the call sign G who will be operating in
Winnipeg, Manitoba, would append the prefix "Portable VE4" or "/VE4" to
their home call sign, and transmit "Winnipeg" at least once during each
communication. 

 

On 4/12/2018 12:00 PM, Wolfgang wrote:

Hello Claude and all,
 
in 9.2.II of that referred document, it says:
 
"...by adding an oblique character ("/")"
 
They say 'adding' and for CW this would mean '/p' or something.
 
in 9.2.c it says "...by adding the Canadian amateur call sign
prefix...'
 
This would mean, if we follow the previous logic of 'adding':
/ and prefix is according to the mentioned
'Schedule IV' table.
 
A ham of a CEPT country has to set it in front, "...an amateur
station licensed by the Government of the United States.."
(see 9.2 of that document) has to append the canadian prefix. (?)
 
73's de OE1MWW
Wolfgang
 
 
 
Thursday, April 12, 2018, 5:22:50 PM, you wrote:
 

On 04/12/2018 04:17 PM, John LeRoy via wsjt-devel wrote:

 

Hi John & All,

 

Canada requires a postpend. Check the Canadian regs.

 

According to the recent information (CQ-DL 4-2018) about the operation
according to the CEPT agreement, Canada requires a prefix, as usual,
such as VE4/ VO2/ VY2/ etc.

 

Perhaps, there is more information here:
http://www.ic.gc.ca/eic/site/smt-gst.nsf/eng/sf01226.html

 

Best wishes,
Claude (DJ0OT)

 


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net> 
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

 
 
73 de Wolfgang
OE1MWW
 
--
Amateur radio is the most expensive type of free-of-charge communication!
Amateurfunk ist die teuerste Art der kostenlosen Kommunikation!
 
 

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net> 
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

 

-

Re: [wsjt-devel] Type 2 compound callsigns support

[Wolfgang]

Hello Neil and all

> KN3ILZ/VE1 ... so it should be 'clickable'

Yes, clickable - but the problem mentioned by Igor, UA3DJY
WSJT-X does not tag you in Canada, if it sees 'KN3ILZ/VE1', it will
locate you in '~U.S.A.'

So, any appendix with /Vxx should be tagged as in Canada.

Another problem area is the cty.dat.

KC2FZN will be registered as on the Northern Mariana Islands (KH0), but
he operates in NY. Reason - there is a 'KC2F' in the table of cty.dat
as on the Northern Mariana Islands. Surprisingly the FCC registered a
call sign 'KC2F' plus a call sign 'KC2FZN'.

WSJT-X runs apparently a pattern match in cty.dat with 'KC2F'
and assigns both to the Mariana Island. Additional, KC2F is according
to QRZ.com registered NY too. Wrong, or old entry in cty.dat plus a
decoding issue. Kind of a chain of 'whoops' ;-)


73 de Wolfgang
OE1MWW

--
Amateur radio is the most expensive type of free-of-charge communication!
Amateurfunk ist die teuerste Art der kostenlosen Kommunikation!


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Type 2 compound callsigns support

[Neil Zampella]

John ...

Here's a link that confirms your suggested use:

http://wp.rac.ca/operating/canada-united-states-reciprocal-operating-agreement/


FWIW .. running a Tx6 transmission throught jt9code.exe using 'CQ 
KN3ILZ/VE1 FN00' returns a recognition that's its a type 2 compound 
call, so it should be 'clickable'



Neil, KN3ILZ



On 4/12/2018 11:51 AM, John wrote:

Hi Claude,

The link you refer to contains:

9.2 The operator of an amateur station licensed by the Government of the United 
States shall identify the station:

• (a) by transmitting the call sign assigned to the licensee’s station 
by the Federal Communications Commission;
• (b) if transmitting:
• (i) by radiotelephony, by adding the word "mobile" or 
“portable,” or
• (ii) by radiotelegraphy, by adding an oblique character 
(“/”); and
• (c) by adding the Canadian amateur call sign prefix set out in Column 
I of an item of Schedule IV for the geographical location of the station set 
out in Column II of that item.

which suggests that the correct form is:K1ABC/VE1

Postpend not prefix.

— John G4KLA



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Type 2 compound callsigns support

[John LeRoy via wsjt-devel]

https://www.ic.gc.ca/eic/site/025.nsf/eng/h_6.html#tao4

1.


   I am an amateur radio operator visiting Canada from another
   country. While in Canada can I use my call sign from my home
   country?

   As per the document RIC-9: Call sign policy and special event
   prefixes
   , you
   may use the call sign assigned by your country’s administration in
   Canada, but you must bring your amateur radio operator’s
   certificate/licence and have obtained a CEPT certificate from your
   home administration. If your country is not part of the CEPT
   agreement you must obtain a letter of authority from the Amateur
   Radio Service Centre (ARSC)
   . Visiting
   amateurs must include the prefix of the geographical location, and
   the area of operation with the identification of their station.
   Therefore, an amateur from the United Kingdom with the call sign
   G who will be operating in Winnipeg, Manitoba, would append the
   prefix “Portable VE4” or “/VE4” to their home call sign, and
   transmit “Winnipeg” at least once during each communication.


On 4/12/2018 12:00 PM, Wolfgang wrote:

Hello Claude and all,

in 9.2.II of that referred document, it says:

"...by adding an oblique character (“/”)"

They say 'adding' and for CW this would mean '/p' or something.

in 9.2.c it says "...by adding the Canadian amateur call sign
prefix...'

This would mean, if we follow the previous logic of 'adding':
/ and prefix is according to the mentioned
'Schedule IV' table.

A ham of a CEPT country has to set it in front, "...an amateur
station licensed by the Government of the United States.."
(see 9.2 of that document) has to append the canadian prefix. (?)

73's de OE1MWW
Wolfgang



Thursday, April 12, 2018, 5:22:50 PM, you wrote:


On 04/12/2018 04:17 PM, John LeRoy via wsjt-devel wrote:
Hi John & All,

Canada requires a postpend. Check the Canadian regs.

According to the recent information (CQ-DL 4-2018) about the operation
according to the CEPT agreement, Canada requires a prefix, as usual,
such as VE4/ VO2/ VY2/ etc.
Perhaps, there is more information here:
http://www.ic.gc.ca/eic/site/smt-gst.nsf/eng/sf01226.html
Best wishes,
Claude (DJ0OT)
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


73 de Wolfgang
OE1MWW

--
Amateur radio is the most expensive type of free-of-charge communication!
Amateurfunk ist die teuerste Art der kostenlosen Kommunikation!


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Type 2 compound callsigns support

[Wolfgang]

Hello Claude and all,

in 9.2.II of that referred document, it says:

"...by adding an oblique character (“/”)"

They say 'adding' and for CW this would mean '/p' or something.

in 9.2.c it says "...by adding the Canadian amateur call sign
prefix...'

This would mean, if we follow the previous logic of 'adding':
/ and prefix is according to the mentioned
'Schedule IV' table.

A ham of a CEPT country has to set it in front, "...an amateur
station licensed by the Government of the United States.."
(see 9.2 of that document) has to append the canadian prefix. (?)

73's de OE1MWW
Wolfgang



Thursday, April 12, 2018, 5:22:50 PM, you wrote:

> On 04/12/2018 04:17 PM, John LeRoy via wsjt-devel wrote:

> Hi John & All,

>> Canada requires a postpend. Check the Canadian regs.

> According to the recent information (CQ-DL 4-2018) about the operation
> according to the CEPT agreement, Canada requires a prefix, as usual,
> such as VE4/ VO2/ VY2/ etc.

> Perhaps, there is more information here:
> http://www.ic.gc.ca/eic/site/smt-gst.nsf/eng/sf01226.html

> Best wishes,
> Claude (DJ0OT)

> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel


73 de Wolfgang
OE1MWW

--
Amateur radio is the most expensive type of free-of-charge communication!
Amateurfunk ist die teuerste Art der kostenlosen Kommunikation!


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Type 2 compound callsigns support

[John]

Hi Claude,

The link you refer to contains:

9.2 The operator of an amateur station licensed by the Government of the United 
States shall identify the station:

• (a) by transmitting the call sign assigned to the licensee’s station 
by the Federal Communications Commission;
• (b) if transmitting:
• (i) by radiotelephony, by adding the word "mobile" or 
“portable,” or
• (ii) by radiotelegraphy, by adding an oblique character 
(“/”); and
• (c) by adding the Canadian amateur call sign prefix set out in Column 
I of an item of Schedule IV for the geographical location of the station set 
out in Column II of that item.

which suggests that the correct form is:K1ABC/VE1

Postpend not prefix.

— John G4KLA

smime.p7s
Description: S/MIME cryptographic signature
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Type 2 compound callsigns support

[Claude Frantz]

On 04/12/2018 04:17 PM, John LeRoy via wsjt-devel wrote:

Hi John & All,

> Canada requires a postpend. Check the Canadian regs.

According to the recent information (CQ-DL 4-2018) about the operation
according to the CEPT agreement, Canada requires a prefix, as usual,
such as VE4/ VO2/ VY2/ etc.

Perhaps, there is more information here:
http://www.ic.gc.ca/eic/site/smt-gst.nsf/eng/sf01226.html

Best wishes,
Claude (DJ0OT)

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Type 2 compound callsigns support

[John LeRoy via wsjt-devel]

Canada requires a postpend. Check the Canadian regs.


On 04/12/2018 07:50 AM, Gene Marsh wrote:

Igor,

Almost all countries use a ‘prepend’ designation:

- DV2/W8NET, when I’m in the Philippines

- VE3/W8NET, when I’m in Canada

But, if I’m in a another area of the USA:

- W8NET/M

- W8NET/MM

- W8NET/7

Your example is:
- K1ABC/VE1
... doesn’t conform.

Better:
- VE1/K1ABC

73 de W8NET Gene
3905 Century Club Master #47
Portage County Amateur Radio Service (PCARS) since 2008
ARRL A-1 Op

On Apr 12, 2018, at 6:42 AM, Игорь Ч via wsjt-devel 
> wrote:



Hello all,
.
It is either lack of code or just bad example in the documentation:

"QSOs involving *Type 2* compound callsigns might look like either of 
the following sequences:


CQ K1ABC/VE1 FN75"
where country is not being recognized properly for this callsign in WSJT-X 
1.9-rc3:
.
102200 21 0.0 970 ~ CQ K1ABC/VE1 FN75  !U.S.A.
.
As it is up to local authorities to grant a licence, probably some extended 
support is required in the code to recognize country properly for type 2 
compound callsigns.
.
73 Igor UA3DJY




--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org ! 
http://sdm.link/slashdot

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net 


https://lists.sourceforge.net/lists/listinfo/wsjt-devel



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Type 2 compound callsigns support

[Gene Marsh]

Igor,

Almost all countries use a ‘prepend’ designation:

- DV2/W8NET, when I’m in the Philippines 

- VE3/W8NET, when I’m in Canada 

But, if I’m in a another area of the USA:

- W8NET/M

- W8NET/MM

- W8NET/7

Your example is:
- K1ABC/VE1
... doesn’t conform. 

Better:
- VE1/K1ABC

73 de W8NET Gene
3905 Century Club Master #47
Portage County Amateur Radio Service (PCARS) since 2008
ARRL A-1 Op

> On Apr 12, 2018, at 6:42 AM, Игорь Ч via wsjt-devel 
>  wrote:
> 
> Hello all,
> .
> It is either lack of code or just bad example in the documentation:
> "QSOs involving Type 2 compound callsigns might look like either of the 
> following sequences:
> 
> CQ K1ABC/VE1 FN75"
> where country is not being recognized properly for this callsign in WSJT-X 
> 1.9-rc3:
> .
> 102200 21 0.0 970 ~ CQ K1ABC/VE1 FN75  !U.S.A.
> .
> As it is up to local authorities to grant a licence, probably some extended 
> support is required in the code to recognize country properly for type 2 
> compound callsigns.
> .
> 73 Igor UA3DJY
> 
> 
> 
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Type 2 compound callsigns support

[Игорь Ч via wsjt-devel]

Hello all,
.
It is either lack of code or just bad example in the documentation:
"QSOs involving  Type 2 compound callsigns might look like either of the 
following sequences:
CQ K1ABC/VE1 FN75"
where country is not being recognized properly for this callsign in WSJT-X 
1.9-rc3:
.
102200 21 0.0 970 ~ CQ K1ABC/VE1 FN75  !U.S.A.
.
As it is up to local authorities to grant a licence, probably some extended 
support is required in the code to recognize country properly for type 2 
compound callsigns.
.
73 Igor UA3DJY




--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel