The spotter may not have decoded 3DA0AO in a CQ, but in a QSO. Being quite rare, I guess 3DA0AO was quite busy, with callers front, back, left and right, not requiring CQs to conduct QSOs. Nevertheless, it is of course best practice to make a CQ call every now and then.
Another issue may be that 3DA0AO is a non-standard call sign, which may not respond to double-clicking the QSO line in the Band Activity window. I know there was a discussion a while ago, where it was proposed to make an exception for 3DA# and define it as a standard prefix (as it is for eSwatini, ex Swaziland), but I don't remember if that has been executed. However, as you say, if double-clicking doesn't move the call into the DX field, entering the callsign by six clicks does. However, the spotter may not know this method of preparing a call, so your point of failing to read instructions may be very valid. But then again, that is no news. Frode LA6VQ tir. 17. sep. 2019 kl. 19:44 skrev Andy Durbin <a.dur...@msn.com>: > "FT8 F/H. NO CQ. CANNOT CALL" was seen in a spot of 3DA0AO. Don't FT8 > ops know it's possible to type the DX call in the DX Call box if they have > no decodes of the DX to click on. But why would they want to call if they > have no decodes of the DX to click on? Isn't rule 1 - don't call if you > can't hear (decode) the DX? > > Is failure to read the instructions the reason for this spot message or > could there be some other explanation? > > 73, > Andy k3wyc > > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel >
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
