[SADXA] KH1 on 160m: all's well that ends well

Jim Wysocki wysocki1 at mindspring.com
Tue Aug 21 23:39:26 EDT 2018


Thanks to a very conscientious QSL manager, my FT8 KH1/KH7Z 160m QSO was 
finally confirmed.  To make a long story short, we compared our two 
time-synched transaction files with one another. In doing so we 
discovered that the KH1 software logged both signal reports and sent out 
a command that mimicked a completed exchange and then told mine to stop 
transmitting.  But while my software received both signal reports and 
then automatically logged the QSO, theirs didn't.

The TX and RX records from this exchange should provide the engineers 
with a few clues on at least one latent software bug. (There is a way to 
occasionally lop 15-second segments off of a QSO exchange.  But under a 
specific set of circumstances the software on one side of the exchange 
can occasionally lock up and then fail to log the completed QSO, even 
though it met the criteria for a valid contact.)

FT8 is still a work in progress but I like how the development team is 
working to constantly improve it.  In this case a closer examination of 
one particular QSO revealed a software bug that's going to get fixed.

Jim  W9FI



More information about the SADXA mailing list