Yet another attempt from K1JT to minimize RF transfer in a meteorscatter QSO:

Very difficult QSOs are significantly easier if you use single-tone reports, rogers, and 73s. With just a bit of practice/experience, it’s very easy to tell a real “R26” from the occasional false decode of same. In most contests, of course, everyone should use grid locators.

WSJT 9.0 is set up to make all these things easy.


On the main screen you can select (or not select) single-tone messages for Rx, Tx, both, or neither.
— 73, Joe, K1JT“

I can not see any reason for using a single tones as messages in meteorscatter communication. A single tone is not a message. It is only a carrier that holds no other information than “it’s presence”.

This is the usual K1JT “make QSO’s as easy as possible” crap.

Very difficult QSOs are significantly easier if you use single-tone reports, rogers, and 73s”

Of course they are, you just need to receive a fraction of a carrier, no information what so ever. Then again, we see these QSO’s end up in listings as initials, new squares, distances etc.

If we accept single tones as a substitute for a real message then we might as well accept a tone for both calls also. Oh… not far from hashed calls in WSJT 9..

The downward spiral of QSO integrity, that K1JT started when he introduced his “Deep Search” concept (which is nothing but a guessing routine), is also taking meteorscatter to a record low if we accept his suggestions.

No need for IARU Region 1 to define QSO standards when a required message can be substituted by a single carrier.

The bright colour of the WSJT software package started flaking many years ago. Now the only thing left is it’s totally black cover.

In CW we don’t substitute messages with carriers, we chop the carrier up in a smart way so we can communicate in a secure and intelligent way, sending and receiving ANY message we want.

CW is King!!

Peter SM2CEW