Hi Sam,
It seems you must have called CQ before calling HB9FAN, so the "Call
1st" behavior was armed to respond to any caller. Its text turns red
when armed.
I guess you are saying that your transmission to HB9FAN should have
disarmed "Call 1st". Maybe, but that is not how it has worked up to
now. To disarm "Call 1st" you can uncheck its box, toggle "Enable TX"
to off, or hit "Halt Tx".
-- Joe, K1JT
On 2/27/2020 11:15 AM, Sam W2JDB via wsjt-devel wrote:
Hi Reino,
I am aware of the first call function when calling CQ, I am not aware of
that when I am calling a particular station as that would be a problem
if I am calling a rare dx or a grid that I need or a station that I
need. In the case where I am calling a particular station, that should
be the only station that WSJT-X should answer. It that is not the case,
then I think as a software developer, it is an oversight.
73,
Sam W2JDB
-----Original Message-----
From: Reino Talarmo <[email protected]>
To: 'WSJT software development' <[email protected]>
Sent: Thu, Feb 27, 2020 11:07 am
Subject: Re: [wsjt-devel] WSJT-X Improperly responding to a station not
called in TX1
Hi Sam,
You had Call 1st checked. I have understood that it is intended to give
protocol permission/request to response to the first decoded message to
you as long as you are not yet in a call. If HB9FAH has answered to you,
then he will have been in your call and protocol would have continued
that QSO with HB9FAH.
73, Reino oh3mA
Hi Bill and Joe,
This is the second time that WSJT-X changed a process from calling
a particular station to answering a station that called me.
I have attached a screen shot showing that WSJT-X is calling HB9FAN with
my call sign at 144816. It then decodes station SP6VXO calling me and
switches from TX1 to TX2 with my station responding to SP6VXO.
I don't believe that this should be permitted. Once WSJT-X is calling
with TX1 to a specific station, it should not respond automatically to
any other station calling me.
FYI, I do have 2 pass decoding enabled and decode set to deep. Hope that
helps.
Thanks for all the prior help.
73,
Sam W2JDB
PossibleBug2.jpg
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
