This morning in response to an (unusual?) call sign: E770D (zero D) registered in QRZ.COM
Snippet from ALL.TXT. Using 77 bit FT8
084130 5 0.1 471 ~ CQ E770D
084200 0 0.1 472 ~ CQ E770D
181019_084215 Transmitting 14.078 MHz FT8: E770D G4KLA I
084230 10 0.1 472 ~ CQ E770D
181019_084245 Transmitting 14.078 MHz FT8: E770D G4KLA I
Note that the trailing letters of my locator were not transmitted, or shown on
the main panel.
Experiments show that if the call sign does not contain 3 digits, eg E77XD
then the transmission is correct, ie E77XD G4KLA IO92.
Similarly if the call sign has an extra letter, eg E770DX then the
transmission is E770DX G4KLA with not even the first letter of my
locator present.
With 75 bit FT8, with E770D the Generate Std Msgs panel has a purple backround
instead of the normal grey. Indicating a problem, perhaps?
The truncation effect is also present so this is not 75/77 bit problem
Trying ft8code doesn’t help since "ft8code -t "crashes with a seg fault in
genft8.f90
Page 5, para 6 of the Quick Start Guide implies that nonstandard call signs
(such as E770D) will be recognized. Is this the case here? Should <…> be
shown in Std Msg?
Conclusions: there seems to be a problem with call signs with a succession of
3 digits such as E770D
there is a problem with ft8code
— John G4KLA
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
