Hi Palle,
On 6/6/2019 9:06 PM, Palle Preben-Hansen, OZ1RH wrote:
As reported b4 I experienced the error window "Invalid QSO Data Check
exchange sent and received" on nearly every of the 103 QSO's I did in
the mock contest. I have noticed two causes:
1. If my QSO was with a station not running in RTTY contest mode RU I
received a normal report like 'R-10' which is not a valid contest
report. This situation can be solved by a change in WSJT-X so a
station in QSO with a station in RTTY contest mode RU always answer
with the proper RTTY contest mode RU exchange. This requires that
the RU exchange is always required to be filled in at the
File>Settings>Advanced page. This applies both when a non mode RU
station calls a RU station and when a RU station calls a non RU
station and is similar to what I proposed in my mail from Tue, Apr
16, 12:13 AM. This logic also applies to NA and EU VHF contests,
ARRL fieldday and even F/H mode, so each station requests the type
of mode and exchange he needs for his contest, thus a contest and a
non contest station can QSO and their exchanges will keep the other
part happy. In fact two QSO partners being in different contests can
QSO and they both get the exchange they need for their particular
contest.
We have not attempted to make the program guess what the operator(s)
intend to do.
If you send a contest exchange to a station that has not enabled contest
messages, he will see a message encouraging him to enable contest
messages. The QSO can continue to completion, but to log it you will
need to enter something for "Exch Rcvd".
2. There is an error in WSJT-X so in some situations (for me almost
always) my valid _send_ exchange was not logged automatically and
had to be entered manually in the error window "Invalid QSO Data
Check exchange sent and received". My received exchange was almost
every time filled in on the "Invalid QSO Data....' window as is should.
I cannot reproduce this problem. Simulated QSOs using "OZ1RH JO55" work
just as expected in my test setup, with everything logged correctly and
automatically. If you believe there is anerror in WSJT-X, please follow
instructions for Bug Reports here:
http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-2.1.0-rc7.html#_bug_reports
... and give us an exact sequence of steps that will reproduce the problem.
-- 73, Joe, K1JT
73, Palle, OZ1RH
www.oz1rh.com <http://www.oz1rh.com> www.kh8.oz0j.dk
<http://www.kh8.oz0j.dk>
On Tue, Apr 16, 2019 at 12:13 AM Palle Preben-Hansen, OZ1RH
<[email protected] <mailto:[email protected]>> wrote:
Hi,
People are using EU VHF if they are in a contest requiring either a
serial number and/or the full 6-digit locator. This is required in
the major VHF contests in Europe. Many contests on HF also requires
a serial number, so this feature applies to more than just EU VHF.
I suggest the labeling on the Settings page is split into two saying:
"I need an exchange with serial number"
"I need an exchange with a 6-digit locator"
When a station calls CQ with one or both of these options set, FT8
of the answering station should just transmit the requested
exchange. No need for flashing a anything about a particular contest
mode.
If you have one or both of these options set and you call a station
his FT8 should send you the requested exchange.
The logic should be that you request the exchange you need and you
get it without intervention from the other station. This should keep
all happy and you only transmit the exchanges needed by the other
station.
This logic should be used for all kind of supported exchanges, e.g.
also the one for NA fieldday. It could also work the other way
around: if a station does not need your locator - transmit only what
the other station requests (though at present the abbreviated
4-digit locator is inherited in the protocol).
If a serial number is requested from you and you did not set a
starting serial number in your settings, your FT8 should just send
0001. To make sure everyone is able to send the full 6-digit locator
this should always be set in Settings.
73, Palle, OZ1RH.
- written on a Hawaiian Airlines plane on route to KH8, see
kh8.oz0j.dk <http://kh8.oz0j.dk/>
-----------------------------
_______________________________________________
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
