Something similar happened to me with hamlib. v3.1 for w64 + wsjt-x 1.8 rc2 & 3. Following the advice of members of this dev list, I reset the frequency list in wsjt-x (right click in the list + reset in the menu which appears) and then wsjt-x and hamlib worked again together.
73 Phil Le 5 nov. 2017 à 22:59, Radio User <[email protected]> a écrit : For reasons that are rather fundamental, SoDaRadio (an SDR transceiver that I developed and maintain) implements its own interface that follows the hamlib net protocol. This worked well with earlier versions of wsjtx and still works with fldigi. But with wsjtx 1.8.0-rc2 I get the "Hamlib error: Protocol error while getting current VFO frequency" error that is apparently fixed with a wsjtx specific hamlib library. Alas, I can't figure out what the protocol change was. Could someone please describe what feature wsjtx is attempting to exercise and what it expects as a return value? Or perhaps a pointer to the specific code? I'd really like to restore this function to SoDaRadio. matt ------------------------------------------------------------------------------ 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 [email protected] 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 [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
