Yes, I used the FTdx5000 rig entry, in lack of FTdx3000. And no, it did not change the VFO B to USB on transmit. I didn't notice, so lost two full days of good FT8 conds from JW-land. And yes, I tested again after I discovered it, and it repeated itself. Easily avoidable when you know, and "FAKE IT" of course is safe.
73 de Tom OH6VDA /JW6VDA > 3. nov. 2018 kl. 17:16 skrev Black Michael <mdblac...@yahoo.com>: > > I guess you were using the FTDX5000 rig entry? > > Can you repeat this problem? I do notice that VFOB mode does not get set > until you transmit. > So if you make the mode on VFOB LSB and start WSJT-X it will stay LSB until > you transit. > But, when you transmit it should change VFOB's mode to USB if you have USB > selected in WSJT-X's rig setup. > > de Mike W9MDB > > > > > On Saturday, November 3, 2018, 8:13:04 AM CDT, Tom Ramberg via wsjt-devel > <wsjt-devel@lists.sourceforge.net> wrote: > > > Hi. I just returned from my recent mini expedition as JW6VDA. During the stay > I mainly used version 1.9.1, and used a FTdx3000, CAT control set to RIG. > Because I also did some SSB split on 40 meters, VFO B was set to LSB, and was > left there. Going back to FT8, it took me two days (sic) to realise that > WSJT-X did not force VFO B to go to USB. As a result, I was transmitting LSB > and made no contacts until I realised the problem. Operator error, of course. > Using FAKE IT was no problem. I have not checked it out on version 2.0 RC#, > but if it is an issue there too, it might be considered to force also VFO B > to USB when checking RIG. > > 73 de Tom OH6VDA / JW6VDA > > Sendt fra min iPad Air 2 > _______________________________________________ > 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
