The error message you are gettingwhen you close Fldigi is a normal message. 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. Love the utility, but evidently I’m too stupid to make this work properly.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |