SDR console 3.4 and Yaesu FTdx5000

[OH1KT]

Hello. I'm still a beginner with SDR programs. I would have asked if I could use the Yaesu FTdx5000 radio as a PAN adapter with SDR Console 3.4. I would be grateful if someone could give advice on how to do it. My configuration is FTDx 5000 Tranceiver HamRadio Deluxe log program and SDR-Console 3.4 FunCube SDRpro+ USB receiver.

[Max]

Hello. I'm still a beginner with SDR programs. I would have asked if I could use the Yaesu FTdx5000 radio as a PAN adapter with SDR Console 3.4. I would be grateful if someone could give advice on how to do it. My configuration is FTDx 5000 Tranceiver HamRadio Deluxe log program and SDR-Console 3.4 FunCube SDRpro+ USB receiver.

Yes, it seems that the FTdx5000 has an IF output:
https://www.youtube.com/watch?v=sXZtrLKD9zU

Firstly install the Funcube Dongle to work with SDR COnsole:
https://www.sdr-radio.com/rtl-dongles

Having got that working, you would set up SDR Console to sync with the FTdx5000 using the "External Radio" feature:
https://www.sdr-radio.com/external-radio

Most commonly this is done using Omnirig........ use only the version downloaded from HERE (currently v1.20):
https://www.dxatlas.com/omnirig/

The antenna input of the Funcube is connected to the FTdx5000 IF output....... again see notes here regarding the IF Offset mode:
https://www.sdr-radio.com/external-radio

You need to find the correct IF offset to enter for the FTdx5000. I think it is 9000kHz (2nd IF) for the FTdx5000? If you want it perfectly synchronised with the Funcube on SDRC (as you should) you may then need to add some additional small offsets to the individual modes depending on how the 5000 works to generate LSB/USB/CW etc. If you SDRC tunes in the opposite direction to the FTdx then you may also need to use the "Invert Spectrum" option in the External Radio settings in SDR Console.

I do not know what the achievable bandwidth of the panadapter would be at the 9MHz IF output? If you find it displays a disappointing narrow bandwidth output because of bandpass filtering in the FTdx (I don't think this is the case though) then the alternative is to run the Funcube from the RX Output of the FTDX with no offset (Antenna Mode in SDRC instead of IF Offset mode),but the performance of the Funcube at HF is most likely quite disappointing. I have a feeling much better to stick to the IF output for the best performance.

Hope it helps.

73

Max

[OH1KT]

Hi Max. First of all, thank you very much for your help. I have already made some progress with that program, but there are a couple of points that I don't fully understand.
First of all, should I set the physical radio in that Omnirig program to Kenwood 2000 or my own, i.e. Yaesu FtDX5000, or both when connecting it to the SDR console? It is also unclear whether I should use some kind of virtual port in that Omnirig program or should I put Yaesu's physical COM3 port in it. As a virtual port program, I have Eltima's program, which makes creating virtual ports very simple. Funcube does give a signal to the SDR console and the S-meter also shows readings, but it does not follow Yaesu's VFO changes in any way. Another thing I don't understand is connecting the LOG program. Of course, I cannot select the Kenwood 2000 radio as the radio in the log program, because Yaesu certainly does not work with HamRadioDeluxe anymore. The HRD Log program can also use the DDE feature, i.e. connect it to many third-party programs via IP address and port, but I don't know if the SDR console supports this option. The goal is of course to get the whole thing to work together, i.e. Yaesu and SDR console and HamRadioDeluxe.

[jdow]

SDR Console only understands Kenwood 2000. So its end of the Omnirig chain should be set accordingly.
{^_^}

[OH1KT]

Thanks for the answer. So Kenwood 2000 should be set in OmniRig program RIG_1 tab settings this OK. If I understand correctly, Kenwood 2000 COM port is the one for which virtual COM port has been created by Eltima's VSPM program. Now we should also get Yaesu 5000 transceiver to work with SDR Console. Yesu's physical port in my case is COM3. Eltima's VSPM has created one virtual COM port pair on the computer which are COM 8 and 9. Is the intention that Omnirig program must have two radios, one is that Kenwood and the other Yaesu which are both connected to their own virtual ports? This is the thing that I unfortunately do not understand. I think I have tried several options and always the end result is that the SDR console does show the signal that comes from the Funcube dongle which is in the radio's IF connector. However, the frequency does not change in the console even if the radio's VFO frequency is changed. It would be great if I could get a step-by-step guide on how to do this correctly and also how I can connect the HamRadioDeluxe logging program so that the whole thing works together.

[Max]

Take a look at this video. The link takes you to when the rig is connected to SDRC time but you might want to spin further back in the video to see setup of Omnirig. I don't think you need to because you already got it installed:

https://youtu.be/KqPNkjQ_cXU?t=591

Omnirig is used to connect SDRC to the physical COM port on the rig, so in Omnirig you need to set Rig1 to your radio type (FTdx5000) and set COM port to match the rig (COM3). Match baud rate to whatever the rig is set to. Maybe start with 19,200 although I see in the video he sets 115,200. But whatever it is, make sure they are matched.

When it comes to connecting third party software, this is where the VSP manager comes in. For each piece of software you need a pair of Com ports, one TO and one FROM. In your case you have COM 8/9. So if you connect SDRC to HRD, in SDRC tick COM8 and leave COM9 unticked. Then inside HRD (sorry, I'm not familiar with it) set it to COM9

See also here:
https://www.sdr-radio.com/SerialPort#Configuration

For each other remote program (WSJT-X for example) you will need a unique pair of Ports set up in VSP Manager.

I must admit I don't have a 100% full understanding of Omnirig, but I think this should get you connected. The mention of the Kenwood TS-2000 is because that is how SDRC appears to Omnirig if you use it to connect to other programs. I must admit I'm unclear as to what happens when you have external radio connected using Omnirig and also a third party program that also uses. Maybe this is where "Rig2" comes into play? I think it's fairly rare as most software seems to use Hamlib protocol instead of Omirig. In this case all you need is the unique COM port pair as I described above.

As far as I can see, HRD does not use Omnirig but uses it's own proprietary COM system so it should be no issue because Omnirig will only be connecting to the FTdx5000.

Hope this is all valid as I don't actually use an External Radio myself. Life is much easier when you use an SDR transceiver! (Mine is Hermes Lite 2).

73

Max

[OH1KT]

Hi Max. Thanks for your help again I tried yesterday by setting the Omnirig settings as you advised. The Omnirig settings are Yaesu radio and the port is Com3. I started the console and added that combination to the console after pressing the question mark. From the opened window I started the Omnirig program and closed it with the OK button. Unfortunately, the console does not react at all to the Yaesu VFO settings, even if I press the Tracking button. I am starting to suspect that the FunCube pro+ dongle I am using is possibly damaged. I will try again today with another RTL V3 stick and see what happens. I will first try to get just the Tranceiver to work together with that console and only then will I start thinking about connecting the logging program.

73 Ilkka

[OH1KT]

Hi Max. I finally got the program working. It was a lot of work before I could connect the Yaesu to the console. The cause of the problem was the console version 3.4 Beta. For some reason it refused to work at all with the radio and synchronize data. I already suspected my own radio at some point and installed the console on another computer and tested the Funcube SDR receiver with it. The Funcube does work as a receiver only in that 3.4 beta version and receives just fine and changes frequency and all other functions just as it should. The only problem is the compatibility with the Yaesu radio, it doesn't work as it should, so there is some error in the program. When I installed version 3.2 everything worked immediately as it should. It may be that the problem is related to the signal being taken to the console from the radio's IF connector. I can't confirm that, because I mainly use Yaesu radios (FTdx5000 and FTdx10). I haven't tried that CAT connection to the HRD log program yet, but I think that could work now too. I have to leave something exciting for tomorrow Once again, thank you very much for your instructions, they helped me get a good idea of ​​the correct configuration and it was a lot of help. I don't know if I can somehow report that beta version problem to the developer through this forum so that they can fix it. The console itself is very good and versatile and that's why I wanted to use its versatile features to complement my own radio station.

73 and Merry Xmas
Ilkka

[Max]

Hi Max. I finally got the program working. It was a lot of work before I could connect the Yaesu to the console. The cause of the problem was the console version 3.4 Beta. For some reason it refused to work at all with the radio and synchronize data. I already suspected my own radio at some point and installed the console on another computer and tested the Funcube SDR receiver with it. The Funcube does work as a receiver only in that 3.4 beta version and receives just fine and changes frequency and all other functions just as it should. The only problem is the compatibility with the Yaesu radio, it doesn't work as it should, so there is some error in the program. When I installed version 3.2 everything worked immediately as it should. It may be that the problem is related to the signal being taken to the console from the radio's IF connector. I can't confirm that, because I mainly use Yaesu radios (FTdx5000 and FTdx10). I haven't tried that CAT connection to the HRD log program yet, but I think that could work now too. I have to leave something exciting for tomorrow Once again, thank you very much for your instructions, they helped me get a good idea of ​​the correct configuration and it was a lot of help. I don't know if I can somehow report that beta version problem to the developer through this forum so that they can fix it. The console itself is very good and versatile and that's why I wanted to use its versatile features to complement my own radio station.

73 and Merry Xmas
Ilkka

Good to hear that Ilkka. Pleased you got it working. It's odd about 3.4 though as I would not have thought that Simon changed anything in the External Radio/CAT code. Only he will know this of course. I am sure he will read this post and comment accordingly. Actually I just checked the Release notes for 3.4 and no mention of CAT/External Radio code.

V 3.2 is a long way back so if there is an issue it might have crept in at just about any update since way-back. Did you try the 3.3 Release version? Wonder why you went all the way back to 3.2? Maybe you tried 3.3 and still not working for you.

Just to say (as I think I mentioned) I do not and never have used External Radio so I can't test it this end. I do connect quite a few programs to SDRC via CAT or Virtual COM ports and they are all still working as they should.

Maybe if you get time move to 3.3 Release Version and see if the problem is still there? I think Simon would find that useful.

73

Max