rsaue wrote:I simply do not agree...
Then you are flat wrong, simple as that.
The onus has ALWAYS been on the digi-mode software developers to make their software work with the radio, not the other way around. The reason for this is because Sun, Kenwood, Yaesu, Flex, Elecraft, and openHPSDR (Thetis) will each continue to produce their own, unique interfaces.
That is why the digi mode programs allow you to select the radio type. Flex did not make their software support RX2 for JTDX or WSJT-X or any other digi mode software, the digi mode software developers made their software support Flex. Same for SunSDR. Same for Kenwood. And so on. If you want them to support Thetis then they need to be lobbied appropriately to do so. It can be done. I spent a lot of time lobbying the author of DXLab to support serial CAT over IP for Thetis and was ultimately successful.
Perhaps most importantly, if the hamlib folks (
https://hamlib.github.io/) can be lobbied appropriately then much of the digi mode software we all love that uses hamlib will attain RX2 capability. This includes WSJT-X, Fldigi, and others.
Unless and until all radio manufacturers and developers decide to standardize their radio control interfaces this situation will not change. Indeed, this is the reason hamlib came to be. Because of the significant amount of work already expended by all of the various developers such a change seems unlikely. Expert Electronics would love TCI to take over the world, but it's just not going to happen. While there are things to like about TCI, too much work has been sunk into serial CAT by ALL the radio makers the world over just to see it abandoned.