locked Re: Expected response

Robert Lorenzini

Last week I saw a station calling a DX station on his freq and
his segment. That went on for almost an hour until someone
called him a lid. He could have never heard the DX during that
time. Split should be used almost always.

Bob - wd6dod

On 5/21/2019 1:59 PM, Gary Kohtala via Groups.Io wrote:

I concur with your statement. I too always have Hold Transmit Frequency checked. It is the only way I operate. I hate when stations insist on calling on my frequency, especially when there's more than one. It's an unnecessary mess.

Best regards,

Gary, K7EK

Radcliff, KY (EM77at)

Sent from BlueMail
On May 21, 2019, at 16:51, "K2EK Bill via Groups.Io" <aol.com@groups.io target=_blank>k2ek=aol.com@groups.io> wrote:
I do not have this problem since I always have "hold frequency" checked.

-----Original Message-----
From: Ed <pwp1@...>
To: Support <Support@HamApps.groups.io>
Sent: Tue, May 21, 2019 4:33 pm
Subject: [HamApps] Expected response


I started this discussion in the WSJT-X group but realize it belongs here. Here's a scenario.

I respond to a CQ by station 1 on frequency 1 but do not get a response and go on to answer another CQ from station 2 on frequency 2. Station 1 responds to my call on frequency 2 with a signal report. Within JTALERTX I double click on highlighted station 1. While my receive frequency switches to frequency 1 transmit frequency remains at Frequency 2. TX ENABLE is not activated.

Is this operating as designed? I would've expected TX ENABLE to be automatically enabled, transmit frequency set to frequency 2. and my signal report sent.

Thank you,

Ed Machak

Join Support@HamApps.groups.io to automatically receive all group messages.