I had this happen last year sometime with my K3. Bill and I were on Skype a couple times trying to track down the cause - ultimately we determined it was an HRD thing. My solution was to dump HRD.
Not very helpful, I know (sorry) - maybe you'll have better luck tracking it down. Jim S. N2ADV > On Jul 10, 2017, at 2:18 PM, Jim - N4ST <newsgr...@jimpricejr.com> wrote: > > I have the issue that when I start WSJT-X, or change configurations, it puts > my Elecraft K3S in split mode. That causes the WSJT-X CAT comms to fail > because I have "FAKE IT" selected and that mode cannot initiate when the rig > is already in split mode. WSJT-X is setup to communicate with HRD 6.4.x as > the controller for the K3S. A quick push of a macro button on the K3S > cancels the split mode allows WSJT-X CAT comms to initiate properly. > Anybody else seen this? > > Windows 10, WSJT-X r7838, HRD 6.4.0.659 > > P.S. - It would be totally awesome if WSJT-X configurations changes could > optionally send out user defined macros over the CAT channel. > > _______ > 73, > Jim - N4ST > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
