I see the issue now. When I double click TX 1, it selects TX1 or TX2 which are empty. Pressing ESC resets it to TX 6. I didn't notice that and was just trying to call CQ. Sorry for being so thick. 73,

Of course different countries have different regulations. Honestly I have not looked into what ITU says about it. I've been writing specifically about the rules in the USA. 97.119(c) in full

Phil, Perhaps this gives a hint or two: § 97.119 Station identification. (c) One or more indicators may be included with the call sign. Each indicator must be separated from the call sign by the

NU0C/M is not a valid GB call – it would be M/NU0C, likewise MM/NU0C and in Spain EAx/NU0C where x is the regional number. Over here /M is required if we are mobile on land or in-shore waters, /MM

This issue first came to my attention during the ARRL Centennial when someone spotted W1AW/5 (W1AW "portable 5") as W1AW/P5. Multiple times. My SpotCollector lit up like a Christmas tree and I had to

FWIW, yesterday I saw K2H/SU on my cluster as being from Eqypt, and K2H/RE as being from Russia. Have not seen any of those today. 73 Herb WB8ASI

I don't, thank you. I have operated NU0C/0 and also as W1AW/0. 73 -Jim NU0C "Kermit Lehman via groups.io" <ktfrog007@...> wrote:

Then don't ever operate as NU0C/M (UK-England). Or /MM (UK-Scotland) or /AM (Spain). 73, Ken, AB1J

Yes, and that is the problem. Self assigned Callsign /indicators that fall within the prefix block of another country are not legal in the USA per 97.119(4)(c). I wrote below that most ops are not

This is done frequently and forever in state QSO parties. In-state ops append their county abbreviation and out-of-state ops append their state abbreviation. 73, Ken, AB1J/MA

Paul, to send the CQ message you must first click one of the Tx6 buttons. 73 Bill G4WJS.

Hi Bill, Not trying to send a blank message. I can't send a CQ which is populated under that condition. that message IS populated. Perhaps I am missing something basic? Thanks for the quick

Hi Paul, WSJT-X refuses to send a blank message. 73 Bill G4WJS.

I have been having an issue that I just figured out the conditions that it happens. At times, when first starting WSJT-X, I would click on Enable Tx and it would not stay enabled (Red). I had to stop

Bob, Go to Configurations>Default>Reset and then Go back to File>Settings and put in all the same data in General, Radio and Audio as you had them before. I had a similar problem as yours. Good

On 02/05/2020 00:27, Bob Kircher wrote: Hi Bob, what Tx audio offset do you have set when this occurs? 73 Bill G4WJS.

Because between 1.9 and 2.1 there was major changes under the hood. You didn't mention what version of Windows you're using. Do a search here on the group at groups.io and use the terms

Thanks John. I have done this and just did it again. Volume is max. The real question is why does it still work perfect when I use the version 1.9 installation and why not with 2.1 or 2.0? That

Do a right click on your speaker icon in lower right of task bar... Open volume mixer & double check wsjt-x level... bet it is on zero. I would also bet that without you knowing it, windows did an

It would appear so, there is no allocated callsign block starting with the number 1. Single digit call area indicators for mobile/portable stations are also OK and in fact used to be