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

Yes, that's what is says, and the FCC has continually interpreted "communication" very broadly.  Broadly enough that in the past they have several times informally said that they weren't going to require it every contact. Thousands of contesters have for decades made several contacts between

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

Ahh ... OK. Well, I don't normally use WSPR but I just switched to it and it let me enter a rather length string of gibberish for a callsign.  And at the bottom right of the Settings - General page it lets me set an interval for a periodic CW ID ... which I assume would be the same gibberish

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

And I think this would also be an issue for FT8 and other modes in jurisdictions (not those administered by the United States Federal Communications Commission) where station identification using the digital mode is not compliant and CW Morse identification is required.

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

You do need to ID with every contact. See Part 97.119 (a) “Each amateur station, except a space station or telecommand station, must transmit its assigned call sign on its transmitting channel at the end of each communication…” AK2L From: David Gilbert Sent: Sunday, October 20, 201

Re: [wsjt-devel] v2.1.0 and MacOS Catalina

Hi Bill, Thank you for the information regarding use of v2.0.1 WSJT-X with MacOS Catalina until until a MacOS build using Qt v5.13.1 is released. I have used v2.0.1 WSJT-X with MacLoggerDX 6.24 and TQSL 2.4.7 for the past week with no issues. 73, Robert Rearden ae...@att.net _

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

Hi Dave, the specific actual situation I have encountered involves using WSJT-X for WSPR (not FT8). Your thoughts? David / K7DB On Sun, Oct 20, 2019, 2:50 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

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

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.  So why not simply use the freeform 13-character TX5 message to periodically ID?  I've played around with it a bit and it will even accept a

[wsjt-devel] Suggestion: CW ID callsign

Hi friends, I am writing to share an idea... WSJT callsign encoding generally accommodates most amateur radio callsigns, but some callsigns -- e.g., some special-event callsigns, and callsigns which might use a *four character suffix* as provided at ITU RR19-7 §30

Re: [wsjt-devel] wsprnet abandoned

Dear Eric, At the side of the team for handling user requests and errors I am practically alone and have been so since the last 2 years. I do this in my free time whenever I remember to open the people management part of the site. I have offered myself for this role over 2 years ago and at that