Again, thanks for the responses everyone. When set to split I’m finding that WSJT-X will “turn on” a B slice that was originally not on and occasionally change it’s frequency though it keeps Tx set to the A slice and is listening via DAX on the A slice. So that B slice isn’t actually doing anything. WSJT-X will keep it on sometimes, turn it off sometimes, then back on again, leave the frequency unchanged for a long time, and perhaps change it again. All of this is when using the Maestro. When operating with SmartSDR on a PC, it will often ignore the B slice altogether and set up a C slice and do the same things with it - again, even though it’s not actually using it.
All of that still seems odd given it’s moving the actual frequency of the VFO that it could only expect to be “listening” on in those cases. By the way, it also moves the frequency of the A slice (set to Tx) which might make a bit more sense until you notice that it usually only moves it for the first transmission. For the next transmission, it almost always sets the freq back to where it started an doesn’t touch it again for the rest of the QSO. If it thinks its moving a Tx VFO to center the passband, why would it only do that for only one transmission? In any case, I think you guys answered my basic question by explaining that WSJT-X isn’t set up for split with Flex radios at all in the first place. So the weird behavior is possibly something happening as the interface/Flex interprets commands actually intended for a Kenwood radio. Again, thanks for the response - much appreciated! > On Oct 27, 2018, at 12:17 PM, Black Michael via wsjt-devel > <wsjt-devel@lists.sourceforge.net> wrote: > > The flex backend in hamlib which WSJT-X uses is just using the standard > Kenwood calls to set split. > > All that does is the SP1 command which should simply turn on split > > It also sets the freq and mode for VFOB using the standard kenwood commands. > > It knows nothing of slices. > > So it's really "assuming" your Flex is setup up as a simple rig with two VFOs > on one slice that can be controlled via the standard Kenwood commands. > > de Mike W9MDB > > > On Saturday, October 27, 2018, 1:58:35 PM CDT, Ravella Russ > <starlite4...@gmail.com> wrote: > > > Thanks for the replies everyone. > > I’m trying to understand what WSJT-X is assuming about Flex 6xxx radios that > results in the odd behavior I described. WHY I want to operate split is > irrelevant to the question but just for information, I am trying to > experiment with different ways of using WSJT-X, mostly just to understand it. > I’ve read the documentation through and this aspect is not well covered. My > experience is use cases often follow (the suggestion regarding JA operation > on 160 is potentially a good example). Another is it appears to BE doing > something that doesn’t make sense and it may be helpful to report a bug but, > again, that’s irrelevant to my post.. All I’d like to know is if anybody > actually KNOWS what WSJT-X does or is trying to do in split mode when set to > a Flex 6xxx radio. > >> On Oct 27, 2018, at 9:01 AM, Bill Somerville <g4...@classdesign.com >> <mailto:g4...@classdesign.com>> wrote: >> > > On 27/10/2018 12:40, Jay Hainline wrote: >> Bill, Mike and others, >> >> >> You do realize that JA on 160 meters is restricted to using FT8 at 1908 khz? >> Practice has been for JA to call for DX at their allocation and listen for >> NA stations transmitting at 1840. Widening the bandwidth window is not very >> eloquent. Surely using a split VFO option with 2 slices would be more >> feasible. My 2 cents… >> >> >> 73 Jay KA9CFD >> >> > Hi Jay, > > I see no mention of top band in the OP, although there may be issues using > traditional split operating to work stations in a separate sub-band I don't > think that is related to the OP's query. Currently the use of SPLIT mode on a > rig by WSJT-X is incompatible with working stations on a separate sub-band as > SPLIT is used for a different purpose i.e. to extend Tx coverage up to the > bandwidth of the receiver and to ensure cleaner Tx signals free of unwanted > audio harmonics. > > 73 > Bill > G4WJS. > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net> > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net> > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > <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
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
