VHFcontesting
[Top] [All Lists]

[VHFcontesting] Beware the FT8 Flaw

To: vhfcontesting@contesting.com
Subject: [VHFcontesting] Beware the FT8 Flaw
From: "Ron Klimas WZ1V" <wz1v@sbcglobal.net>
Reply-to: wz1v@sbcglobal.net
Date: Fri, 31 May 2019 07:05:41 -0400
List-post: <mailto:vhfcontesting@contesting.com>
Beware the FT8 fatal flaw. 
To be fair, it's really an FT8 operator flaw. 
I'm sure I'm not the only one who's annoyed by this. 
It reared it's ugly head again yesterday. 
EA8ABC (not real call) is calling CQ on 6M in Auto mode. 
CQ DX EA8ABC IL28. 
I manually enter his call to answer: 
EA8ABC WZ1V FN31. 
His computer replies WZ1V EA8ABC -10. 
My computer replies EA8ABC WZ1V R-18. 
Nothing back. 
My computer replies EA8ABC WZ1V R-18 
several more times with nothing back while 
meanwhile EA8ABC computer keeps calling CQ. 
I try to call him again from scratch. 
He answers with a signal report but aborts the contact. 
I send NO RR? 
EA8ABC sends ALREADY WKD. 
EA8ABC is so confident his JT software worked me 
he's in denial that his one time RR73 was never decoded. 
Beware herein lies the flaw: 
If this were the ARRL June VHF QSO Party, 
and we both submtted logs, EA8ABC would be penalized 
for claiming a QSO with me since he's not in my log. 
Neither could he get a confirmation via LOTW. 
If you use FT8 it can happen to you either way. 
You could be the one who gets penalized for trusting 
the software is always correct without human intervention. 
-73 Ron WZ1V


---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

_______________________________________________
VHFcontesting mailing list
VHFcontesting@contesting.com
http://lists.contesting.com/mailman/listinfo/vhfcontesting

<Prev in Thread] Current Thread [Next in Thread>