On 06/06/2015 14:00, Steven Franke wrote: > Bill, Hi Steve & All, >> On Jun 6, 2015, at 10:18 AM, Bill Somerville <g4...@classdesign.com> wrote: >> >> On 06/06/2015 05:36, Steven Franke wrote: >> Hi Steve, >>> Replying to my own observation — the behavior is more complex than I >>> realized. I think that the program is actually trying to raise ptt on the >>> Rx-only band, 630m, but a hamlib error message occurs and then seems to >>> cause the program to drop Tx Enable. (The radio is a TS-480.) This is >>> consistent with Joe’s suspicion that hamlib errors were canceling Tx Enable. >> The unintended change in r5542 would have disabled any gating of send >> commands for Rx only bands. If a rig returns a CAT error when sent to a >> non-HAM band or if asked to SEND on a non-HAM band then a rig control >> error is likely. We do not distinguish between CAT errors we can ignore >> and those we can't, apart from some obvious cases where a retry might >> work. It is up tp the operator to ensure that WSJT-X doesn't try and >> make the rig do something it can't. Now that Rx only during band hopping >> is being honoured both for messages and tune up this should not be an issue. > I’ve just now confirmed that r5543 is back to not transmitting in non-hopping > mode unless the band that we are sitting on happens to be active in the > scheduler. I think that this may be the behavior that Josh commented on > earlier. I have added code to use the Tx scheduling used in band hopping for non-hopping WSPR, this should mean that the Tx/Rx ratio and Tx periods will be determined by your adapted random sequence that minimizes consecutive Tx periods.
Single band WSPR and band hopping WSPR should now be doing what I think we have agreed. > > While you are on a roll, I’ll just mention another wish-list item. We already > have a Tx Next button — it would be nice to have a Next Band selector that > would override the band-picking algorithm. This could just be a box with > up-down arrow to cycle through the bands… This could be active in both > hopping _and_ non-hopping modes. Couldn't this be achieved by simply selecting a different band from the main window drop down? We would have to define what that meant when hopping is active, for example it could disable hopping or it could use the selected band for one period then return to the normal schedule. 73 Bill G4WJS. ------------------------------------------------------------------------------ _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
