![]() When Fldigi is installed in the Program files structure Microsoft has a tendency to block communication between Fldigi and other applications as it put to much security on the Program files Structure. You do not need to re-install it just copy it from one directory to another. My other suggestion to you is to change the directory where Fldigi is located in. If you click the up arrow near the clock you should see its icon (Little Blue Man) double click on that and it will open the gateway back open. Clicking on an SSB spot always works ok.Īfter the gateway is loaded and it has connected to Fldigi it minimizes itself to the area near the clock. It’s consistently this way, but that’s just odd. NOW, here’s the strange part…If I click the spot several times (fairly quickly), it will move to the EXACT spot frequency (not with audio offset) and then magically populate the correct MODE in the capture window for DXKeeper (that part I want) The problem with that is there’s no audio offset and you can’t see the signal you’re looking for of course. It was previously set to PSK31, so even though you might be clicking on an RTTY spot, it would set it to PSK31. I’ve set the “Log Mode for PKT or PKT-R” selection in the Commander Options window to nothing (ie: blank) since it only allows a single option. When I click on a spot in SpotCollector, the spot is transferred to DXLabs apps and fldigi as normal, except the mode in the DXKeeper capture window is missing. My setup is an FTdx3000, using the internal sound card (which requires the rig to be in DATA-USB mode) with current version of fldigi and DXLabs suite with commander. I’ve spent hours trying to figure this out. ![]() To configure the radio control, turn off or disable any other rig control configured (flrig, RigCAT, etc), and then configure the Hamlib interface as shown.Love the utility, but evidently I’m too stupid to make this work properly. Note that fldigi needs to have been compiled with Hamlib support, which is commonly done. fldigiįldigi can easily connect to wfview using wfview’s built-in rigctld emulation. For the port, use “127.0.0.1:4534”, replacing “4534” with your port as specified in wfview. For port type, select “Hamlib NET rigctl”. The Radio Setting name is user-defined, set it as you wish. Various other settings are optional but I would recommend setting PTT method to CAT, Mode to Data/Pkt and Split to either Fake It or Rig (rig based split support is still experimental in wfview though). Pressing Test CAT should result in the button turning green, which means it is talking to rigctld. Simply select the Rig: of “Hamlib NET rigctl” and enter 127.0.0.1: into Network Server. Setup of WSJT-X is very straight-forward (this should be the same for the majority of software that is based on WSJT-X like JTDX and JS8-Call). Once the above is saved, I found that I needed to restart Log4OM before it was able to connect to the wfview rigctld. If you haven’t changed the port in wfview to 4532, you will need to enter 4533 in the Port box below. Once done, select the Hamlib tab and enter the address and port of your wfview computer (if the same machine then 127.0.0.1). Within “Settings/Program Configuration/CAT Interface” select Hamlib as the CAT engine. No other configuration of wfview is required, below are the required settings for various software that has been tested so far: Jump down: Log4OM 2, WSJT-X, MacLoggerDX, fldigi Log4OM 2 (NextGen) configurationįirstly you must be running the latest version of Log4OM 2 (currently 2.17.0.0). The port can be changed without restarting wfview, simply uncheck/check Enable RigCtld to restart the rigctld emulation. The port number must be greater than 1024. If you are confident that no other rigctld is running, you can set this to 4532 which will be the default port on most software. The default port is set to 4533 so as not to conflict with any existing rigctld that is running. ![]() To enable rigctld emulation, simply put a check next to “Enable RigCtld” within the wfview Settings tab, on the “External Control” page. When supported, this is now the recommended/preferred method of connecting software to wfview (rather than virtual serial port/pseudo tty) as this utilizes a caching mechanism which avoids ‘spamming’ the rig with large numbers of duplicate CI-V requests. Wfview has the ability to emulate a subset of the Hamlib rigctld protocol which allows a number of applications to connect for rig control purposes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |