#USE FLDIGI FOR GENERAL LOGGING HOW TO#
#USE FLDIGI FOR GENERAL LOGGING PDF#
#USE FLDIGI FOR GENERAL LOGGING UPDATE#
#USE FLDIGI FOR GENERAL LOGGING WINDOWS 10#

I now have none of the Rig Control options in any of the flrig, RigCAT, Hamlib, XML-RPC, Hardware PTT or GPIO tabs checked. Restarting seems to have been the answer. Maybe someone here on the forum has some experience doing that. I don't know if a COM Port 'splitter' software would do the trick here. I don't want to give that fldigi feature up just because I'm using SDRUno or HDSDR as a Panadaptor.

#USE FLDIGI FOR GENERAL LOGGING UPDATE#

Without this information going to fldigi, I have to always remember to manually update the fldigi logging panel with mode and frequency before I click the 'send to log' button. Having the frequency/mode in fldigi track the rig makes logging with fldigi so easy. Finally, the ultimate goal I'm trying to achieve is to leverage SDRUno or HDSDR (via an RSP-1a) as a Panadaptor and use their ability to QSY by clicking on a signal in the Panadaptor display but withoutlosing frequency information being sent from the FTDX-5000 to fldigi. Especially since it is clear that one can have multiple instances of fldigi connected to multiple different rigs. I only mentioned that I 'thought' it would be strange if flrig was unable to support multiple instances each controlling a separate xcvr. Also, FWIW I only have one instance of flrig running and that is to the FTDX-5000. After the restart it now seems to work and is no longer coupled to flrig. I would think that if you can run multiple instances of fldigi you can run multiple instances of flrig, each connected to a different radio and tell fldigi which one to communicate.ĭING DING DING!! WE HAVE A WINNER! Thanks Cliff.

#USE FLDIGI FOR GENERAL LOGGING HOW TO#

I'm hoping Dave or someone can advise me how to decouple the VHF instance from flrig. I've turned off *Enable flrig xcvr control with fldigi client*, turned off *Use RigCat* and even changed the flrig's TCP host address from 127.0.0.1 to 127.0.0.9 and changed the Port number. I've tried everything I can think of to decouple the VHF instance from talking to flrig but nothing seems to work. The problem is that if I click on anything (freq, mode, etc) in the /*VHF instance */it sends that to flrig and flrig changes the freq, mode, etc of the FTDX-5000. All appears to be fine until I launch flrig connected to the CAT input of the FTDX-5000.

#USE FLDIGI FOR GENERAL LOGGING PDF#

PDF on running multiple instances of fldigi so that I can operate two rigs a vhf rig for FSQ and a Yaesu FTDX-5000 for general HF work.

#USE FLDIGI FOR GENERAL LOGGING WINDOWS 10#

Here's the details of my setup: Windows 10 PC fldigi 4.0.18 flrig 1.3.41.31beta N5PY I would think that if you can run multiple instances of fldigi you can run multiple instances of flrig, each connected to a different radio and tell fldigi which one to communicate.

I've turned off Enable flrig xcvr control with fldigi client, turned off Use RigCat and even changed the flrig's TCP host address from 127.0.0.1 to 127.0.0.9 and changed the Port number.

The problem is that if I click on anything (freq, mode, etc) in the VHF instance it sends that to flrig and flrig changes the freq, mode, etc of the FTDX-5000.

Use fldigi for general logging