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] RX messages when using msk144 mode

[Jay Hainline]

Not sure if my message got through so will try again. 

 

Jay KA9CFD

 

From: Jay Hainline  
Sent: April 12, 2018 12:30
To: wsjt-devel@lists.sourceforge.net
Subject: [wsjt-devel] RX messages when using msk144 mode

 

Running WSJT-X v1.9.0-rc3 r8609 with Windows 10 64 bit. It has been brought
to my attention that the receive messages are no longer populating the right
side tx messages window when running with a station in msk144 mode. I made a
couple of meteor scatter contacts on 6 meters and see this behavior.  This
seems to be happening in the 1.9.0 RC versions. 1.8.0 works as before with
receive messages of your qso partner populating the right side window.
Please take a look. The left side band activity window can get very busy
when there are lots of stations on meteor scatter and your QSO partner's
messages will scroll off the top before you know it.

 

73 Jay

 

Jay Hainline KA9CFD

Colchester, IL  EN40om

 

--
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