Re: [wsjt-devel] Fwd: Suggestion: CW ID callsign

Well, now I'm coming to believe you're just making a mountain out of an anthill. 1.  First of all, according to a post I saw from K1JT . "since June 15, 1983 FCC does NOT require US amateurs to use a CWID with data modes."  I haven't found the FCC statement that confirms that, but at le

Re: [wsjt-devel] Fwd: Suggestion: CW ID callsign

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 wrote: Hi friends, Just to clarify, the issue

[wsjt-devel] Fwd: Suggestion: CW ID callsign

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 XX0 is compliant with ITU Radio Regulations (Article 19, 19.68), but as far as

Re: [wsjt-devel] Suggestion: CW ID callsign

Agree on all.  When running in a contest I never go more than three contacts without giving my call, but usually go at least two unless conditions are dicey and I don't want anyone on the other end to have to wait through a couple of contacts before deciding whether they want to work me or no

Re: [wsjt-devel] wsprnet abandoned

Hi Erwin, Maybe the offers have never reached you, because the official wsprnet email adress (wsprnet at wsprnet.org) does reject e-mails since over a year. Otherwise there is no possibility of contacting the wsprnet team, except via the forum. PLEASE have a look at the forum. Also it is not poss

Re: [wsjt-devel] Suggestion: CW ID callsign

On 10/20/2019 2:44 PM, David Gilbert wrote: As best I know, you don't need to ID every contact, and I suspect you wouldn't even if moving around within a bandwidth as narrow as is typical for FT8. Far too much attention to identification is paid by those who don't operate much, and/or aren't

Re: [wsjt-devel] Suggestion: CW ID callsign

Hi Dave, Thanks for the response. If a call sign is specified in Settings which is not compliant with the requirements of the 28-bit encoding scheme, my recollection is that with WSPR the non-compliant callsign will code into some kind of nonsense in the *digital* message. In any case, a non-comp