Bill,
I was on 14.076 with V2. Its likely the other station was on V1 so
you're likely correct and it'll all be resolved when everyone's on V2..
Just reporting..
AL, K0VM
On 11/5/2018 3:10 PM, Bill Somerville wrote:
On 05/11/2018 20:38, Al wrote:
( 2.0.0 RC3, Win10 1803)
This might have been reported before or it might just be an
incompatiblity between 1.9.1 and RC3..
I would not expect auto seq to respond to a transmission that did not
include my call sign..
AL, K0VM
Hi Al,
what dial frequency were you operating on?
I am asking because that behaviour is expected pre v2, the
auto-sequencer is allowed start a QSO with a compound callsign holder
replying to a CQ with their Tx1 message, even though it does not
contain your callsign, but only if their frequency is close to your Tx
frequency. This may be considered ambiguous but since the QSO will not
complete if they were not intending to call you there is not a real
problem. With v2 your callsign hash code will be in their Tx1 message
which means there is reasonably high probability it is indeed you they
are calling.
73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
