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

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.

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

ct: 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-ac

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

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

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

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

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

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

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

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

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

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

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

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

le...@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 docu

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

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

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

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

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

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

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

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

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)

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

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.

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

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

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

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

[wsjt-devel] Type 2 compound callsigns support

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