Hall of fame
For both Logging and CAT control.
W4RLS: if your comment is towards my post
We are talking different things: TCI (Transceiver Control Interface) is developed by Expert Electronics or EESDR- it carries ALL information RX/TX frequency and audio using TCI interface- ANAN or Apache Labs has also introduced the EESDR TCI protocol inter there latest SDR software as well, it is MUCH FASTER in transferring data and audio information than any other source currently in use, MSHV, JTDX and a number of logging applications-or currently using TCI interface would be a big plus for those of use with RIGs that offer TCI , it's a simple click it to turn on and use it no configurations other than setting the port number used by TCI typically 4001 or 5001- Frequency control. Mode- RX/TX PTT and rx/rtx audio is all streamed over the interface: GitHub - maksimus1210/TCI: Transceiver Control Interface
For logging, sending a UDF packet with an ADIF record should be sufficient. N1MM+ uses a proprietary format, but that could be a possibility too. However, ADIF would be the better and more compatible option.
Another option is to send UDP broadcast packets in the same format as WSJT-X. There are several code examples for various languages on GitHub. Creating and sending the WSJT-X Status and Heartbeat packets would immediately make VaraC compatible with GridTracker and other apps that already work with WSJT-X.
If you would like to discuss further and to go into the packets or see an example, drop me a line. I've done the work to receive and decode these packets for my own logging program. While you'd be doing the encoding, it's a similar principle.
Great to hear: My Radio has an IP (actually use VPN for remote) , wonder if I could work remote without connecting my radio to a pc.
Kenwood remote TS-890s and Ts-590sg
Will it be able to also include TCI-UDP interfacing as well?