I should also add that I had to manually switch from TX1 to TX3 to complete the QSO.
73 Bill AE6JV On 9/18/19 at 5:02 PM, ae...@arrl.net (Bill Frantz) wrote: > On 9/18/19 at 3:21 AM, frodeigla...@gmail.com (Frode Igland) wrote: > > >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. > > I had a lot of trouble with double clicking this call sign and ended up > typing it in. Everything seems to have worked, because I got LotW > confirmation of the QSO today. --------------------------------------------------------------------------- Bill Frantz |"After all, if the conventional wisdom was working, the 408-356-8506 | rate of systems being compromised would be going down, www.pwpconsult.com | wouldn't it?" -- Marcus Ranum _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
