开云体育

Don't remember source, but somwhere found CI-V address 0xA4.

CIV commands reference for Xiegu transceivers. ( https://xiegu.eu/?sdm_process_download=1&download_id=3576 )

For the Xiegu X6200 I would try the IC-7300 driver with CI-V address 0x70. Bj?rn SM7IUN [email protected]> wrote:

+ AA6YQ comments below Is it possible to add Xiegu X6200 and other Xiegu transceivers to commander? + Support for the Xiegu X6200 is unlikely: 1. The User Manual for the Xiegu X6200 does not specify

Hello. Is it possible to add Xiegu X6200 and other Xiegu transceivers to commander?

+ AA6YQ comments below After a catastrophic computer failure, I'm now reconstructing DXLab after reinstalling Win 11. Prior to the crash, I had two user fields with drop down choices in DXKeeper. I'm

+ AA6YQ comments below After a catastrophic computer failure, I'm now reconstructing DXLab after reinstalling Win 11. Prior to the crash, I had two user fields with drop down choices in DXKeeper. I'm

After a catastrophic computer failure, I'm now reconstructing DXLab after reinstalling Win 11. Prior to the crash, I had two user fields with drop down choices in DXKeeper. I'm trying to re-create

Thanks Joe, I did enable, un-enable and re-enable and see if things changed. But no joy. vy 73, Dave, w0rx

Did you, perhaps, uncheck the "QSL" box as you printed labels, or addresses, etc.? If so, click "enable all" before clicking "Update Log" ... 73, ... Joe, W4TV

+ AA6YQ comments below I finished processing a batch of QSL cards from the bureau. After printing the labels, 3 col stick-ons, I pressed the "update log" button whose tooltip says: for each printed

I finished processing a batch of QSL cards from the bureau.? After printing the labels, 3 col stick-ons, I pressed the "update log" button whose tooltip says: for each printed QSL label, update the

Tnx Dave for the details. My problem was I was clicking for ssb/cw and it would work but not for ft8/4 which now makes sense. It is a very useful tool to stay away from dupes and of course, jt alert

+ AA6YQ comments below I read this in the documentation: "Unless you've checked an application's Log Debugging Info box, it should never produce an errorlog.txt file. If it does,..." I was doing some

Dave, I read this in the documentation: "Unless you've checked an application's Log Debugging Info box, it should never produce an errorlog.txt file. If it does,..." I was doing some housekeeping and

# More AA6YQ comments below Or they could use their satellite connection to work the rare island from their home station a few times while cooling their heels on the boat offshore, like several

I only activated US islands in FL, AL, and GA this year, so the DXCC confirmation wouldn’t be an issue in this case. So, I’ll take your suggestion, and worry about the rare one when/if I activate

+ AA6YQ comments below Instructions would be more consistent if the "log debugging info" check boxes were retitled "error log". You instructions and commentary refer often to "error log", but one has

It's clear that the root cause of the reported problems is erroneous DXCC information in QRZ callbook entries. Since you can't modify another station's QRZ callbook entry, the corrective action is to

+ AA6YQ comments below The IOTA report came back with the 'not found in log' indications. Some were easy to adjust, like KL7/call in the report and call/KL7 in my log. Ditto with just the call versus