Reino,
Respectfully -- that is not a good answer.  You addressed the WSJT-X issue 
while WSPR was the problem.  Having said that - constructively, WSJT-X must 
accept what are now called non-standard calls.  They are non-standard only to 
the WSJT-X programmers and not the ham radio world.  They are authorized and 
recognized by the FCC and perhaps also by worldwide communications governing 
bodies.  MANY people use "non-standard" call signs, including several 
DXpeditions.  I hope the WSJT-X programmers find the coding "real estate" to 
normalize all call signs.  I know your programming issues behind the problem.

You all are going a great job - keep up the good work.
        Danny        W4/AH6FX ... or AH6FX/W4 ... et al

    On Friday, February 21, 2020, 7:36:44 AM EST, Reino Talarmo 
<reino.tala...@kolumbus.fi> wrote:  
 
 
Bill,

Thanks, for sure. I should have read more carefully, hi!

73, Reino oh3mA

  

From: Bill Somerville [mailto:g4...@classdesign.com] 
Sent: 21. helmikuuta 2020 11:59
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] 7 Digit Callsigns

  

Reino,

  

Matt's query is abut WSPR mode, there are no CQ calls and the structured 
messages are much simpler since they are beacon transmissions. The handling of 
non-standard calls is also different from QSO modes.

  

73
Bill
G4WJS.

  

On 21/02/2020 06:39, Reino Talarmo wrote:


Hi Matt,

You should be possible to send CQ message without grid square locator and make 
contacts with the help on hashed call sign using automatic message generation. 
There strong limits what can be included into a single message, when the basic 
call sign is 7 characters long. As a workaround you could use free text 
messages for your grid square locator such as ‘VK3FDLL AB12’ or ‘AB12 VK3FDLL’ 
and broadcast that message now and then, or send as the last message of a QSO 
‘LOC AB12 73’. Other station can see that is belongs to you from the frequency. 
That kind of method is used in the EU VHF contest messages as a part of the 
protocol. Note that free text maximum is 13 characters including space 
characters. 

73, Reino oh3mA

 

From: Matt VK3FDLL [mailto:matt+vk3f...@geekle.id.au] 
Sent: 21. helmikuuta 2020 7:08
To: wsjt-devel@lists.sourceforge.net
Subject: [wsjt-devel] 7 Digit Callsigns

 

Hi there,

 

I'm using WSJT-X (WSPR Mode) for quite a while for receiving and now I've 
attempted to transmit.

I am a Foundation Licence holder in Australia (VK), which means I have a 7 
digit callsign - VK3FDLL

 

With various tests, I can hear my WSPR transmissions away from my station and 
WSJT-X can even decode my transmissions. However the decoding only occurs on 
transmissions where my callsign is hashed (Type 3 message, I believe?)

Transmissions where my full, 7 digit callsign (and 4 digit grid square locator) 
is transmitted are not decoded by WSJT-X

 

Are you able to point me in the right direction as to how I can achieve being 
decoded correctly? Or does the software and/or protocol simply don't support a 
7 digit callsign?

 

Regards,

Matthew Jones - VK3FDLL


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

Reply via email to