Aww. Got it. Thanks Steve!
On 9/26/2018 2:55 PM, Steven Franke via wsjt-devel wrote:
Ken,
You are decoding frames that are being sent by someone who is still running
RC1. The person who is running RC1 is trying to send messages to EA1FA. The bug
in RC1 is such that whenever the first callsign in a message can be interpreted
as a valid hexadecimal number, it will send that first callsign as a
hexadecimal number in a telemetry message. People running RC2 will decode this
telemetry message and will display the hexadecimal number that it contains,
which is EA1FA in the examples that you are seeing.
In summary, what you are seeing is the result of a bug in the instance of
WSJT-X RC1 that is transmitting the message, and not due to a bug in your RC2
version of WSJT-X. The station that is transmitting the incorrect frames is not
EA1FA — it is someone who is trying to send a message to EA1FA.
Those incorrect messages should disappear once everyone moves to RC2 or newer
releases.
Steve K9AN
On Sep 26, 2018, at 4:29 PM, Ken Miller <k...@cwfam.com> wrote:
I went ahead and reinstalled WSJT-X v2.0.0-rc2, just in case. Using Win10 on a
I-5 quad core. Attached is a screen shot and my ALL.TXT file. I reset it right
after re-installing rc-2. The type of decode I was questioning yesterday is at
211315.
<ifoeljncodgdklhc.png>
Ken k6wgx
<ALL.TXT>_______________________________________________
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
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
