1) A 1KHz run up worked for me in this contest. Other times, I have moved up only 500Hz. Either way, you have to keep in your head where callers with smaller rx bandwidths might be at their max.
2) I have infrequently seen this too and have not been able to associate with any particular sequence of operation. I had it happen once during the contest when I had enabled tx to CQ long before the tx cycle started - I usually set a CQ during the last few seconds of a cycle just to make sure the whole message gets out. 3) Short answer is no. I just get up to talk to the wife for 20 to 30 minutes. During this contest, I went was putting up xmas lights during the breaks. Al Pawlowski, K6AVP Los Osos, CA USA > On Dec 3, 2018, at 07:57, wsjt-devel-requ...@lists.sourceforge.net wrote: > > Date: Mon, 3 Dec 2018 07:39:21 -0800 > From: Bill <brightl...@gmail.com <mailto:brightl...@gmail.com>> > To: wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net> > Subject: [wsjt-devel] FT8 RU - Band Segments - XMIT Dropouts > > > 1. This is the first time I have used the "go up 2 KHz" to avoid congestion > tactic. I really wish that this would be implemented in normal operation > since its frequently impossible to find a space to play on 40 and 20. The > issue I have with the "2 KHz" jumps are that the bottom 1 KHz of the > waterfall is useless since those decodes are usually from the previous > lower band segment. While WSJT-X decodes them fine the operators are > listening to the calls on the lower segment (higher tones) and when I call > them on the higher segment (lower tones) I am not decoded for them. In > normal operation the segment is useable from well below 500 to well above > 2500. Wouldn't it make sense to make the segment jumps to 3 KHz to give the > operators a clean segment to work with? > > 2. I have random issues when I change transmit frequency where the > transmitter keys but there is no audio. This is either happening when I > shift click on the waterfall or when I manually type the desired frequency > into the TX selection window. The problem is fixed by quickly hitting Halt > TX then Enable TX. I have found the need to keep my rig's xmit monitor on > to let me know when this happens. This problem occurs in both the Mac > version 1.9.1 and Windows RC5. I've seen this mentioned by others but I > can't seem to find the known problem list to see if it is there. > > 3. Does anyone have any good responses to tell the XYL when she thinks I am > crazy to be staring at a computer screen and listening to beeping for 24 > straight hours???
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
