First of all, excuse my ignorance, since the latest version of JTDX has been released, I am using TCI instead of CAT and it works very well. But I have heard that VAC can also be substituted for TCI for TX and RX. Is that correct?. If correct, where can I find information on how to configure it with TCI?

Thanks

EA1AHA
Juan Carlos

Hola Carlos,

In JTDX, go to Settings/Preferences and select the Audio Tab. In the section Soundcard, there should be a tick box called Use TCI Audio. Tick that box and then click on the Refresh button to the left of the checkmark (I am using macOS JTDX, perhaps the layout is different in other OS).

That should be all you need to do to use TCI Audio, given that your CAT is already working fine.


Saludos,
Marinus, M0GLT

OK Marinus, everything ok, thank you. I hadn't seen that box for TCI.
Thanks

EA1AHA
Juan Carlos

I am trying to get JTDX running on my Win10 machine with JTDX v.2.2.256 corr and EESDR2 1.3.1 upd. 11 for my SunSDR2 DX - both on the most recent versions.
I also tried with different versions and combinations, I cannot get TCI to work. I also stopped VAC and CAT in EESDR2.

JTDX without TCI works smoothly with CAT and VAC, once I switch to TCI under Radio I am getting error messages or JTDX can stop crash completely. After restarting with TCI configured, the error message just comes up again.

Error message in the image attached 0.png: Rig failure: TCI failed set rxfreq.

Depending on the theoretically "irrelevant" CAT tick under PTT method the error message is changing to "Invalid PTT Method".

Error message: Invalid PTT method. 1.png

I did also stop all other relevant software running in parallel, PC restarted or running without antivirus and Firewall and had not luck.

Anyone having an idea what could be wrong or experiencing similar issues?
73, Peter - HB9BUN

--
HB9BUN

Thank you Aleksandr. TCI is on as I have also my PA connected to TCI and sometimes Log4OM as well. And also with Rig Power on and CT selecte I get the same error message: Rig Failure.
BTW also SDC is running properly via TCI at the same time. It must be another reason that is causing the issue.
73, Peter - HB9BUN

Has ev to do with something like s, I had RIG Error ...
the problem with TCI and JTDX is solved, it is only a matter of setting in win10 regional settings the format of the numbers which must be 123.456.780,00. with the format 123,456,780.00 it does not work. ev you need to install version 32 of JTDX.

Arturo, HB9MIR

Thank you all, and especially to Arturo. It is exactly what you describe. When I switch the regional settings in Windows from Swiss German to German German, everything work fine. Great to understand where the issue comes from. This should be easy to correct in the software.
Issue identified and workaround found for the time being. It would be nice to get this addressed!
Many thanks. 73 and good dx, Peter - HB9BUN

Peter and all users of JTDX, so much has already been communicated to the developers of JTDX from other forums.
I wish all users of JTDX a lot of DX
73 de Arturo, HB9MIR

But watch out, it can happen that with a win update to WIN the format 123,456,780.00 ... takes over again.
Arturo, HB9MIR

Hi Arturo, yes, watch carefully if you use the workaround changing regional settings. Some of my applications are writing different number formats to their files then. Last time I did this I had to manually correct data to get it all correct again. Probably these application do not properly use Windows servinces neither, but I got a mess.
It is important that such errors are corrected in the software.
I am happy to know where the issue is but without a correction I will not use it. The first thing that happened was that DXLab composer showed me wrong frequency formats for logged QSOs ... ;-(
73, Peter - HB9BUN