There has to be something wrong in the FT/x spotting system/mechanism.

The only thing "wrong" is that the *CLUSTER SOFTWARE* /ASSUMES/ that any
spot not in the "phone" bands is CW unless the spot contains the mode in
its comments.

The better software includes the digital mode in the comments but most
"manually" entered spots fail to include mode - whether that is JT65,
JT9, FT8, FT4, RTTY, PSK31, PSK63, PSK125, etc.

The Cluster system needs a "frequency map" for 3540-3650, 7040-7100,
10130-10150, 14050-14125, 18090-18110, 21050-21150, 24900-24930 and
28050-28200 with all of the common "centers of activity" (both primary
and secondary). DXLab Suite's SpotCollector includes such a "map" and
it catches 80%+ of the digital activity ... the big issue being FT8 F/H
operations that can be misidentified as RTTY and RTTY contest activity
that can be identified as FT8, FT4 or JT65/JT9 at times.

73,

... Joe, W4TV


On 2021-12-26 5:37 PM, Geoff Way wrote:

Joe, I agree that the RBN can be pretty "brain dead", but I'm having trouble swallowing the idea that a CW-decoding system is somehow locking onto and identifying an FT/x mode signal as CW. There has to be something wrong in the FT/x spotting system/mechanism.