Hi Everyone, I have noted that when you select a frequency to operate on that hardware is not capable of then a Hamlib disconnect (i.e. The Settings/Radio configuration widgets) is thrown without any console error messages being recorded.
i.e. I run a FT-897D and an old IC-725 here… With either rig select 70Mhz first time … and it groans and returns to the previous state (as expected). Then select 70MHz again and a Hamlib disconnect without console warning traps being thrown on the console with both the FT-897D and the IC-725. Note that no console messages are displayed with the FT-897D; there are some messages displayed with the IC-725. Up-to-the-minute Hamlib snaps have had to be used (from the master repo) due to their being a lot of work going on in Hamlib with the FT8x7 range of Yaesu radios. I have worked this through heavily with Mike W9MDB on both Windows x64 and Linux Ubuntu 20.04 and I am very sure – backed up by responses to different radio technologies - that the issue is not with Hamlib. [ There is an appearance that the last state (i.e frequency, mode etc.) that the radio was on in WSJTX is saved rather than the last valid state. ] Its minor; few will observe this. Concern is that "Doctor...it's hurts when I do this....Doctor: then don't do that" could be responded back. That is not the point; as I have stated repeatedly many use this project as a template for programming and standards – even in the commercial world. Therefore it is our obligation to report as this small issue could cause huge issues later down the track. Thanks especially to Mike W9MDB and everyone else that has been helping and testing with my observations here. 73 Steve I VK3VM / VK3SIR
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
