Installed the new ESDR3 1.0.6 Beta with this setup:
Rig SunSDR2 DX with E-coder2 panel and SPE 1.3k-FA amplifier
ESDR3 1.0.6 Beta, Windows 10
VSPE virtual USB driver for logbook connection and CW keying
Radiosync TCI for CAT to amplifier, logbook and CW keying
My logbooks are DX4WIN and DXLog.
CW keying from logbooks works fine
FT8 with JTDX and TCI works fine.
Audio processing with Modmic4 mic carried over from previous version without problem.
Tested Mic1, E-coder2 mic, and they are working fine.
So far everything feels familiar.
Radiospot and RadioMacros still to be tested.

FB (Fine Business) as they say on CW.
Erik SM0JCA

Regarding the "re-upload" of Ver 1.06 Beta, announced 12/29/23 on TELEGRAM, how was this documented?
I didn't record the download on the 12/28 release but for the 12/29 download its 28122023, which appears it also didn't change?
The re-upload corrected some TCI issues with JTDX.
From this upgrade it appears that JTDX now use's TCI?
I installed JTDX and after setup I get a " TCI SDR" error.

I'm also having issues with SDC, which uses TCI, it connects but as an example, using the SWR function it doesn't work.

Tom W3FRG

Hallo Tom Svante in Sweden here. Merry Christmas and happy new year. I just started VarAC and also use SDC.What I can see it works as before (no problems) using RF2K-S as tuner not amplifire. (I use only 50 watt) SDR2 dx shows swr 1.0 Mic meter is also in place if I want to.
Maybe it was not answer to your question but tried to answer Hi.
Have a nice happy new year all the best 2024
from sm6usu Svante

JTDX use TCI long time ago.

Happy New Year Svante and best Seasons Greetings.

I errored on JTDX; I was thinking WSJTX.
I've used JTDX but like MSHV better.
I went back to 1.05 Beta from 1.06 to verify that the suspect pgms were working and help me understand what I was doing in error.
All work but SDC on the SWR function.

I'm somewhat concerned regarding the documentation between 1.06 Beta that was downloaded on the 28th and the re-download on the 29th.
The version number is identical as is the Build date.

I'll return to 1.06 Beta once that documentation is corrected.

Regards,
Tom W3FRG

Roger on that, it was my error as I was confusing it with wsjtx.

Season's Greetings

Tom W3FRG

Good. Have now ended a 20 minits long qso on VarAC on 40 M with a German guy. works perfect. All the best to you and yours.
73 de sm6usu

Working fine here. I'm interested what changes or improvements made to the updated beta. It looks and feels like the same as the previous betas.

Correction... looks like MSHV can't send audio via TCi while in Digi mode. RX is okay but no TX audio being passed while in TX.

Any tips?

I went back to version 1.0.5 beta... TCI on TX is working again.

I reverted back to the first rekease of 28 dec 1.06 same no tx on MSHV

sm4ive wrote: update TCI IS NOT WORKING no dX SPOT from TCI so reverted to 1.05

HI All
DE Developer of MSHV Software
Question is abut numeric version of TCI protocol
Question is to Developers of TCI protocol for ESDR
To the moment old TCI protocol versions is (string) 1.4, 1.5, .......1.9, in new version we have this -> 1.10 (as string) <- what is this ?
How all others software's to determine this version 1.9>1.10 ????????
New version of TCI protocol need to be 2.0
Or mаybe Developers of TCI protocol ESDR means first digit (1) is major version and second digit (10) is minor version ???????
Please answer of this, because MSHV for the moment not work correct for this simple reason, with this 1.10 TCI protocol
LZ2HV Christo. Developer of MSHV Software

HI again
I find in TCI protocol documentation this:
TCI ver. 1.9 29 July 2022
TCI ver. 1.9.1 31 May 2023
TCI ver. 1.10 31 May 2023
Question is:
How many dots do you intend to put into the protocol version ?
Because all other software must comply with it
Maybe something as this ver. 1.10.1.2.3.4.5.6.7....................
???

lz2hv wrote: EE just follows the Qt way of versioning (under spoiler).


Hence 1.10 superseeds 1.9.

lz2hv wrote: I guess it does not work not because of "version" number, but because of changes made in 1.10, which are yet to be reflected in MSHV. Please consult with github.com/ExpertSDR3/TCI/blob/main/TCI%20Protocol.pdf

For the future: I may suggest you contact Roman directly and ask him to bridge you to EE developers. This will give you the access to early notifications of TCI changes, leaving you fair enough time time to perform any needed modifications.