开云体育

+ AA6YQ comments below The IC-7800 has a DB9 jack marked RS-232C that provides a built-in CI-V interface. + You're right, Joe. Later Icom transceivers provide a USB connection with a built-in CI-V

The IC-7800 has a DB9 jack marked RS-232C that provides a built-in CI-V interface. You will need to set Miscellaneous (Others) Set Mode (in the Icom Menu system) to CI-V in order to enable the CI-V

+ AA6YQ comments below + You must connect a COM port on your computer to an Icom CI-V interface, which is in turn connected to the Remote jack on the backpanel of your IC-7800. You can build or buy

I am running an Icom 7800 which I had hooked up to DX Lab until about a year ago when we moved. I cannot remember for the life of me how I had it hooked up but am thinking a ran an RS-232 cable from

# More AA6YQ comments below # *CORRECTION!* Depress the *ALT* key while clicking the CBA button. # See https://www.dxlabsuite.com/dxkeeper/Help/UpdateLogFromCallbook.htm 73, Dave, AA6YQ

+ AA6YQ comments below + Some of your logged QSOs were missing grid squares because when you imported them, you had the "Ignore geocoded grid squares..." option enabled in the QRZ panel on the

Dave and all, Last update. I did uncheck the " Ignore geocoded gridsquare" box after deleting all previously imported contacts with the missing grids. Upon a much more lengthy import, essentially

Dave, OK, that process did not work BUT, I re-red the instructions and INSTEAD of pressing the DELETE key on my keyboard Pressed CNTRL and then clicked Delete on the LogQSO's pane and boom.....all

OK, Wait, I did the following. 1.? Uninstalled DXKeeper. 2.? Deleted KM2B.mdb 3.? Reinstalled DXKeeper from DXLauncher. Restarted DXKeeper.? Log is empty. So, all good.? ?Although, if you

Dave, Many thanks for the detailed information "Ignore geocoded gridsquare ..." box was indeed marked checked and I have now unchecked it and then spent some time trying to properly delete the

Thanks. It's not that important but if the feature were there, I would use it. Sometimes I'm not looking at the Commander window but looking at the radio to perform some adjustment or function. The

Before installing or upgrading to DXView 4.9.8, review the Notes below. This version - correctly processes a CTRL-click in the user-specified digital mode family row of the Main window's Progress

Two things to check: Firstly ensure that in WSJTX the Secondary UDP Server is not active (File -> Settings -> Reporting - bottom block Secondly under JTAlert settings ensure that under

What does this mean? Once you have received 73 or RR73 the QSO is complete and WSJTX/JT Alert prompts you to log the QSO. Anything after than is unnecessary - if you are prompted to log again

+ AA6YQ comments below + That's most likely a JTAlert configuration issue. I suggest that you review the step-by-step instructions

When I finish a QSO on ft8 and log it, JTAlert sends that log file to my DXKeeper log file. ?Exactly what I want. ?Then when I send my response and send my response and power, when I hit ok a second

+ AA6YQ comments below + In support of visually-impaired operators, the "Transceiver Announcements" panel on the Audio tab of SpotCollector's Configuration window can be configured to announce

Related question: Is it possible to have an *audible* band edge warning in addition to the visual/color change? -- 73, Norm/KC1BMD

Thank you very much sir! I also prefer your first recommendation. 73 de Dave, W5SV

+ AA6YQ comments below + You can eliminate the error in one of two ways: 1. Restore the QSO to your log so that it will "match" what LoTW reports when you invoke "Update from LoTW"; if the QSO