That's why there's third-party utilities, its not a core part of the program. Neil, KN3ILZ On 2/17/2021 12:53 PM, Michel Bernard VE2BJG wrote:

There is no grid listed in the DX GRID box ... so when the operator clicked to resend the 73, the system did not see a GRID since it was previously cleared. Neil,

For Q65 it looks like using configurations is a must. On the graph you need to set it to ‘Q65’ - if you just change mode the graph mode does not change. It works fine with a

Thanks for the reply, Charlie, I'll look into setting up different configurations as well. Cheers - Dave (G0DJA)

On Wed, Feb 17, 2021 at 01:03 PM, Bill Somerville wrote: If your QSO partner elects to send an RR73 message in reply to your R+report message then they should not expect any reply.Bill, that is a

Similar to JTDX, is it possible to get a WAV played when there is activity or a valid decode. Since activity is almost invisible when signals are weak, there would be less danger of falling asleep

John, look again at the exchange! EA4SM never sent his gridsquare. 73 Bill G4WJS. On 17/02/2021 18:18, JP Tucson, AZ wrote:

Actually, I am looking at the log box with the empty "grid" block. Something I have been trying to inform you about for a while. As you can see, it DOES happen to other users. But hey, whatever...

John, you must be looking at a different exchange from the one I see. 73 Bill G4WJS. On 17/02/2021 18:07, JP Tucson, AZ wrote:

Notice also that the logging box DID NOT PICK UP THE GRID SQUARE! ...though it is clearly listed in the data exchanges! 73 - John - N7GHZ

On 17/02/2021 17:59, Ken WB8UFC wrote: Ken, the only reasonable replies to an RR73 message are either nothing, a 73 message, or some free text message sending extra

On Wed, Feb 17, 2021 at 12:49 PM, Ken WB8UFC wrote: I'll try deferring the logging and see if that makes a difference.Nope. No difference. I didn't log and it WSJT-X still sent the 73 in response to

On Wed, Feb 17, 2021 at 11:27 AM, Reino Talarmo wrote: At what point you log the QSO? Have you already logged the QSO before you receive the repeated RRR or RR73?You directed that to Chuck, but I have

Chuck, That is definitely NOT the behavior I observe. Like you, I click the "Enable Tx" immediately after logging the contact. In the snapshot below, when that second RR73 was sent at 173600, "Enable

correction for 'f' read 'g'. There is also no 'g' in Q65, although it is selectable in -rc1.

Hi John That hashtag now exists and I've created others to ensure they exist for every mode. We're bound by what is possible on groups.io and I don't think it's possible to create a hashtag in that

I had some issue, sent one to config#? No response, yet. Bob KI0G

Hi David I think that's happening because you were on a submode letter (f) when in JT4 and when going to Q65 that would have persisted as the selected submode. There is currently no f submode coded

From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Chuck - KY4CU Sent: 17. helmikuuta 2021 16:51 To: main@WSJTX.groups.io Subject: Re: [WSJTX] CQ instead of 73 #FT8 I usually

No problem, try 50.275 MHz and 30A, there seems to be a lot of activity there. People have also been on 50.235 MHz 120E