VK6NX пишет:
hari пишет:
Hence there should be no need to "force" HAMs to it by locking out other tuners
EE does not lock out 3rd party tuners. It is opposite. Full automatic tuners does not require any integration at all, they just work out of carrier, hence plug-n-play. Semi-automatic tuners can be integrated via EE's API.
The RS485 protocol likely passes around additional information, as the exact frequency being used to facilitate storage of tuning solutions. Not everything speaks Ethernet/IP to be integrated within TCI.
Opening EE's ATU comm source code does not make any sence at all. It was designed to work with specific equipment via specific port. Let's say EE gave you the code. You have found comms protocol is incompatible with you 3rd party tuner. What is next? Ask EE to modify the code to support your tuner? Or ask your tuner vendor to modify their equipment? Then complain to EE about code is not supporting what you want? This is a dead loop.
First: I didn't ask for the source code, my request is about the interface description. Second: it always amazes me how buyers of products with proprietary interfaces even try to find arguments why it is good to lock them out of the products they bought. I do understand a "don't care" attitude, but arguing for closed-ness of interfaces is kinda weird..
If the interface description were published, you're neither forced to use a 3rd party product nor to hook up your own DIY project to that interface.
It is not relevant what ICOM does; they are non-SDR and simply have no other choice to integrate semi-tuners, rather then provide description of their interfaces.
This is not about SDR/non-SDR, it is about publishing detailed interface information for ports on the transceiver one did buy.
In opposite, EE uses API to its full power, providing us with easy and most flexible way to integrate practically anything. You can even ingrate your automatic coffee machine to start brewing when you are switching to your favourite band or mode. Including tuners, of course, practically any kind (search my earlier posts on this forum for an example of non-automatic tuner with TCI feedback).
See above re IP. The EE ATU isn't using IP either. There is good reason for rs485 in such situations, with the tuner being hooked up at the mast.