Hi guys, I am not sure where to ask this question as different software and writers are involved and perhaps my setup is a little unique. Everything is working perfectly (almost) so I have no complaints. I am running EESDR3 (latest versions) RadioSync, SDC/TCI, and Logger32 as my logger. Using SDC i generate cluster spots from various sources and these are transferred to EESDR3 screen - no problem. However, I do find it a little "clunky" to generate a spot using the cluster(s) in SDC and prefer to use the Cluster spotting within Logger32 as Its easier and I dont have to change screens etc. It does mean that I have to run a cluster within Logger32 to send my outgoing spot - if that makes sense.
My question is...... how do I get the incoming clusterspots within Logger32 to show on my EESDR3 screen? Logger32 is not TCI compliant and so I use radiosync for COM and PTT etc when using JTDX within Logger32. If i ask in Logger32 forum I'm told that its not a Logger32 problem to interconnect with another third party software, so now I start here, in the hope that someone in this forum may have come across the same problem and has a work around.
Tom - GM4FDM

SDC ; Telnet Server; Add spoter; shoose your prefered Telnet cluster server... Send the spots to panorama. I dont know how to send spots from Logger 32 to SDC SRI!
You could use same cluster in SDC as in Logger32 but with different call? Just gessing.

I think the best way is to create local server in SDC and use the same cluster as you were using in Logger32. In Logger32 you connect then to local SDC telnet server.
That should work.

At this stage it is not going to work with only Logger32 itself, Tom. TCI is mandatory for spots transfer to ESDR3.

If thisGM4FDM пишет: what you have as the solid response, then, it is not good. Perhaps, just contact the Logger32 developer directly and confirm if he is not willing to add TCI support into his log. If his answer would be definitely "no", then, perhaps, consider to change the log to some, which supports TCI with SPOT and SPOT_DELETE functions (page 30 of github.com/ExpertSDR3/TCI/blob/main/TCI%20Protocol.pdf).

Genrally speaking, it is all dependent from what you are expecting from spot functionality, i.e. do you need only local spots? Do you need only cluster(s) spots? Do you need combinations? The answer should define the software choice.

I recall Vasily and Roman telling that they have junior devs working on new SPOT consolidation SW, but not sure how far they gone. Perhaps just ask Roman.

It would be super nice to put telnet cluster spotting back in EESDR3 like the implementation in EESDR2.
Personally I find it annoying that if SDR3 looses connection them I have to restart two programs instead of just one to get spots.
Bob W7RH

Hmm....the spots created by SDC Telnet Server are transmitted directly to my radio screen no problem. If I wish to CREATE A SPOT I have to come out of my logging software, go back into SDC and grerate a spot in SDC telnet server and transmit that to the cluster. Thats ok if I am not busy and quiet. If I am working many stations and want to quickly spot one of them, I can generate a spot from with my logging software (Logger32) simply by right clicking. However, this does not route the spot to SDC telnet server, but only to the cluster which I have previously opened with my Logger if that makes sense. So I can more or less instantly send a spot by right clicking the mouse. Spots received from my open cluster withing the logger are displayed within a window opened WITHIN the software, BUT ARE NOT TRANSFERRED TO MY RADIO SCREEN, like the spots generated within SDC / telnet cluster.
Logger32 does not have TCI support but connects via radiosync, reats frequency, runs PTT etc via radiosync. If all that makes sense.