John, Did you think to search for this? https://wsjtx.groups.io/g/main/topic/74699578#11480 Bruce N7XGR

You're one those who annoy me by not sending their locator. The UK licence requires you to send a location, also I like to update a map with locations of those I work. If you do as you do my logger

Not really Roger - just that if you have a local transmitting in one sequence then try not to transmit opposite period. Whenever possible call at the same time as they do, that way neither of you will

Hi Roger, I don't normally do that, but when chasing DX, along with many others, this seems to work better. I always send my grid when calling CQ. Being in an "ordinary" square, if

I’m a newbie on the forum, been using WSJT-X for somewhat less than a year. I upgraded to v2.2.1 and the CAT control no longer works correctly with my FT-891. I get a Hamlib error message.

I agree that it would be nice to have a highlight for all unworked stations. However, N3FJP Amateur Contact Log does the job when I select a likely contact. WB6DIK, Dick

Thank you Neil for your help I did install the 64 bit version and it does run OK with no apparent problem so far, except for the fact that I could not find a way to differentiate between the

Not sure if this is related to your problem, but check your audio output device name and make doubly sure you have the correct device listed. See here... Re: [WSJTX] Linux HamLib Error #hamlib #linux

Hi Bill, thank you for your reply. I'll try to work this out on Wednesday, the next time I can play a little with my radios. 73 Steven, DL8SE

So you are saying that as I have an omni-directional aerial and have no possibility of raising a beam that I cannot operate when there's DX around as I can see no way I can comply with the

Hi, no VOX us not switched on on the rig. And all I have changed is the audio device names in the drop down menus and everything is working fine now. Funny you should say that tho, I have noticed

I'm disappointed to read that Bob as that's not very considerate to those of us who want the grid, including myself. Do you call CQ without your grid as well? Just so you know I don't answer Message

On 07/06/2020 17:13, groups@... wrote: Roger, the protocol applies to those with omni-directional aerial just as much, in fact even more so. The intention is to avoid

TX1 can be disabled by double-clicking on the TX1 button. 73 -Jim NU0C "Bob G8HGN" <g8hgn73@...> wrote:

Hi Bob, You are missing something. In User Guide section 7.1. Standard exchange there is a note: Several options are available for circumstances where fast QSOs are desirable. Double-click the Tx1

Hi Bill, You seem to be working with one hand tied behind your back, hi! Yes the big opening, called CQ on 50.323 immediately called back by XE2X, we exchanged reports, but no RR73/RRR

Hi  Bob, I'm not aware that the auto-sequencer was started by "Enable Tx " alone, it doesn't seem very desirable behaviour to me, but maybe it did an d has been "fixed". When the big 6m opening has

Hi Bill, OK, I usually don't double click on a call if I'm going to go Message 2 1st, as if I do the TX will send message 1 straight away. So I usually manually enter the call and then

Hi Chris, clear the DX Grid before doing a lookup unless you are sure the grid there is correct. ESC to abandon a QSO should clear the DX call and grid. Checking "Settings->Reporting->Clear DX call

And I need to know what to do with my omnidirectional antenna? It seemed to get me around Europe and a bit beyond last week without bothering about any protocol which makes no sense to