Hi all,

Please allow me to return to the problem of the non standard messages,
when using auto sequencing, as usual with FT8. Here when using rc2.

Concerned entries from ALL.TXT:

170915_093400  Transmitting 10.136 MHz  FT8:  CQ DJ0OT JN58
093415  11  0.2 1619 ~  DJ0OT SM4EMO JO79
170915_093430  Transmitting 10.136 MHz  FT8:  SM4EMO DJ0OT +11
093445  13  0.2 1620 ~  DJ0OT SM4EMO R+04
170915_093500  Transmitting 10.136 MHz  FT8:  SM4EMO DJ0OT RRR
093515   9  0.3 1620 ~  TU CLAUDE 73
170915_093530  Transmitting 10.136 MHz  FT8:  CLAUDE DJ0OT

As we can see, the software is switching to the second word of the non
standard message, considering it as the callsign of the partner station,
now. As a consequence, the log entry is wrong too.

<call:6>CLAUDE <gridsquare:0> <mode:3>FT8 <rst_sent:3>+11
<rst_rcvd:3>+04 <qso_date:8>20170915 <time_on:6>093415
<qso_date_off:8>20170915 <time_off:6>093549 <band:3>30m
<freq:9>10.137620 <station_callsign:5>DJ0OT <my_gridsquare:6>JN58tc
<comment:25>FT8  Sent: +11  Rcvd: +04 <eor>

I think that, in this form, the error will be recognized too late, e.g.
when sending to a QSL service. I have added a further test in the
software processing the log, in order to test the plausibility of the
callsign. Although this is not superfluous, it is not really a solution.

Best wishes,
Claude (DJ0OT)

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to