Thanks to a fellow amateur for this information. ITU document: https://www.itu.int/en/ITU-R/terrestrial/fmd/Documents/fxm-art19-sec3.pdf
See also: https://www.itu.int/en/ITU-R/terrestrial/fmd/Pages/identifications.aspx 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. -- finger painting on glass is an inexact art - apologies for any errors in this scra^Hibble ()/)/)() ..ASCII for Onno.. On Fri., 21 Feb. 2020, 18:57 Onno Benschop, <o...@itmaze.com.au> wrote: > Isn't there an ITU standard for callsigns? > > AFAIK the Australian Foundation call complies with that standard. > > -- > finger painting on glass is an inexact art - apologies for any errors in > this scra^Hibble > > ()/)/)() ..ASCII for Onno.. > > On Fri., 21 Feb. 2020, 18:02 Bill Somerville, <g4...@classdesign.com> > wrote: > >> 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 >> <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
