CWID is not required in the USA. Why waste the bandwidth? It will just be more 
background noise in our ever crowded sliver of digital frequencies.
Best regards,
Gary, K7EK
---



    On Monday, October 21, 2019, 09:35:52 PM EDT, David A. Behar 
<david...@gmail.com> wrote:  
 
 Hi friends,
Just to clarify, the issue is not the identification interval... rather, the 
issue is whether it is possible to identify at all.
A callsign such as XX0YYYY is compliant with ITU Radio Regulations (Article 19, 
19.68), but as far as I can figure out it's not possible to identify with a 
callsign of that form using WSJT-X and WSPR (and I think it isn't possible to 
identify with any of the modes -- not even with the CW ID feature).
Note that ITU regulations explicitly provide for up to four characters after 
the digit, and it is only the last character which must be a letter. For 
example, the callsigns K7123X, K7ABCD, and K722AX are all valid callsigns 
according to the ITU regulations.
Furthermore, even longer callsigns are authorized Article 19 at 19.68A. ("On 
special occasions, for temporary use, administrations may authorize use of call 
signs with more than the four characters referred to in No. 19.68.") An example 
would be K7VERYLONGCALLSIGN -- perfectly compliant with ITU rules "on special 
occasions for temporary use".
In some jurisdictions under some circumstances a license requires a fraction 
bar and additional characters after the callsign.
In the U.S. -- and likely everywhere else -- national identification 
requirements can met by the transmission of the callsign in CW using 
International Morse Code. Notwithstanding any limitations in the 28-bit digital 
encoding scheme used for WSJT-X digital modes, a free-form CW ID callsign field 
would empower all users to perform their station identification duties -- 
something that is not currently possible with WSJT-X for some callsigns.
David / K7DB
_______________________________________________
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