开云体育

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

+ AA6YQ comments below + As suggested here https://www.dxlabsuite.com/dxlabwiki/GettingStarted + slowly scan the Reference Documentation of each DXLab applications that you are using. Ignore the

You *CAN NOT* eliminate the error since you removed the questionable QSO from DXKeeper. LotW does not allow users to remove QSOs once uploaded. 73, ... Joe, W4TV

+ AA6YQ comments below + My response is here: /g/DXLab/message/228410 73, Dave, AA6YQ

Somehow, if there was a reply, I missed it; any clues r things I might try would be appreciated!

Thank You, Dave. I knew it had to be there, but just had not found it yet. Lots to read and understand! Grin. Rich, NU6T [email protected]> wrote: -- Richard Hill

+ AA6YQ comments below + No problem, Shige! + That configuration is not supported because it does not prevent the PW1 from encountering CI-V bus collisions, which can mangle frequency packets and

Joe, W6TV, Dave AA6YQ, and Dave, W6DE I'm sorry. I did not know that [email protected] could not send attachments. PC(DXLabCommander):USB A port?[USB cable]?IC-7600:USB B

I am taking this discussion off line. I will post a summary if this discussion works out. 73, Dave, w6de Sent: 20 March, 2025 19:07 To: [email protected] Subject: Re: [DXLab] IC-PW1 configuration in