Thanks for explanation..
AL, K0VM
On 2/10/2020 10:27 AM, Joe Taylor wrote:
Hi Al,
On 2/9/2020 1:05 PM, K0VM wrote:
WSJT-x V 2.1.2
In the sequence below my CQ was answered by a station with a
non-standard call sign (??)
I had several minutes earlier tried to call PJ4/NE9U, but I am not
sure who called me with a non-standard call. UW5EJX/MM was also
active on the band.
200209_172645 18.100 Tx FT8 0 0.0 2170 CQ K0VM EN42
200209_172645 18.100 Rx FT8 10 0.4 1534 K0VM <...> +08
200209_172645 18.100 Rx FT8 10 0.4 1539 F8AEJ KD4RE 73
200209_172645 18.100 Tx FT8 0 0.0 2170
A station with a nonstandard callsign should always use the Tx1
message to respond to a CQ. In this case he has used Tx2, which
includes only a hash code for his call, and evidently this was a
station you had not previously decoded.
In my next transmission the TX text was blank and WSJT disabled
'Enable TX'.
TX Enable could not be re-enabled until I closed and restarted WSJT-x .
Auto seq and Call 1st where enabled.
WSJT-X will not transmit a blank message, so if one of the radio
buttons next to a blank message entry field is selected, Enable Tx
will be turned off. But there's no need to closed and restarted
WSJT-X. Rather, you could select Tx6 (your CQ message) or enter
something in DX Call, click Gen Std Msgs, etc., to re-generate
non-blank Tx messages.
-- 73, Joe, K1JT
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
