Resending after switching my subscribed email from my ARRL forwarding one to the address my mailer attaches.

I've run into a couple of bugs with 2.4.0 wsjtx.

My setup:
    Running wsjtx on Ubuntu Linux 20.04
    Rig is Yaesu FT991A
    Using the built in USB audio codec in the rig

Problem 1.
    WSPR works fine, both receive and transmit work.  The power slider works to change output power (changing audio level to upper sideband data)     Switch to FT8 using rig split frequency, and any attempt to transmit gave me a full 100 watt carrier that the slider won't change.

    Finally tracked it down to the VFO-B isn't being configured to data-upper, but instead went to (or stayed at) FM.  Hence a full power carrier.
    FT-8 doesn't work well with an FM modulated carrier :-(.
    I have finally gotten my VHF array ready do go up, and I was using 2M FM through a repeater and got VFO-B set to FM.     That mode setting didn't get switched to data-upper when I went back to HF FT-8.  VFO-A for receive DID change back to data-upper just by using wsjtx.     Could there be a problem in hamlib in regard to split operation?  Might be specific to the FT-991A allowing different A and B modes.

Problem 2.
    When switching from FT-8 back to WSPR, where I leave my rig when I do other things, the 'transmit enable' button turns off by itself     after the first tune cycle.  If I stay there, and turn it back on after that first cancel, it seems to stay on, at least most of the time.  I have seen     it turn off again after the second tune cycle when the band is changed, but only occasionally.

    At least the printing of 'transmitting ...' when just doing the tune cycle in the RC went away after the official release of 2.4.0.

Gordon, WA9WTK






_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to