开云体育

Hi Dave,

Many thanks for your advice.
It works now.

Best regards,

Georges F6DFZ?

I have already used the bulk modifying method on my log, it works...

Related to this.

As I mentioned before I previously used XMLog. I exported my adif log
from that and imported it into DXKeeper. I was pleased to see that it
has imported all the QSL sent/received and eQSL/LOTW received fields
correctly. But I have never worried about marking eQSL and LOTW (or
ClubLog) QSOs as requested/confirmed, everything is uploaded to those
anyway.

I suppose I could use bulk modify to mark all my QSOs as eQSL/LOTW sent
if I really want.

My paper QSLs and paper DXCC records back to 1969 are incomplete
anyway. My first DXCC applications were all via paper cards and I have
never gone through my boxes of old cards, some now disposed of, and
marked them up in the paper log. LOTW has combined everything and that
is where I look to see what I am missing.

But when LOTW is back I will need to properly synchronise the two as
that is how DXK seems to work. I will have some more questions on that
later.

For the moment what is the quickest way to mark all my QSOs as sent to eQSL?

73 Dave G3YMC

+ AA6YQ comments below

Thanks Dave, That is what I was looking for.? I don't know why I couldn't find it.? Probably the same reason I missed importing with the wrong QTH, etc.? I'm getting old and can't see.

+ This article describes option to make the text on your monitor easier to read:

+ When searching for information in "Getting Started with DXLab" (aka "the Wiki"), search its table of contents:

+ Search the table of contents for the word

modifying

+ would have gotten you there.

?

? ? ? ?73,

? ? ? ? ? ? ?Dave, AA6YQ

Thanks Dave, That is what I was looking for.? I don't know why I couldn't find it.? Probably the same reason I missed importing with the wrong QTH, etc.? I'm getting old and can't see.

Thanks again.

+ AA6YQ comments below

I am trying to configure this combo with Commander.
I use IC-7100, address 88, Com port 7, Baud rate 19200.
I have a Multi radio configuration with my IC-7300, which works flawlessly.

As soon as I switch Commander to the G106, the G106 transceiver goes in transmit mode. Frequency, mode and commands (A, B, A=B, AxB...) work perfectly, but the G106 is in TX in permanence, even if I click to the RX button on Commander.

Can somebody help me to solve this problem ?

+ Due to insufficient documentation and Xiegu declining to provide a loander, Commander does not support the G106.

+ In the "Primary CAT Serial Port" panel on the Configuration window's Ports tab, set the DTR and RTS selectors to "off" (unless one of them is used to provide power to the interface between your computer and radio).

+ Make the same change in the G106's row in the "CAT Serial port" panel on the Configuration window's MultiRadio tab.

? ? ? 73,

? ? ? ? ? Dave, AA6YQ

?

+ AA6YQ comments below

I know there is a way to correct my mistake, but I can't seem to figure out how.
I imported about 120 QSO's using an ADIF file, but........... I didn't realize I had MyQTH for the wrong location and the QSL status set top "R" for QSL cards so all were improted with the wrong info. All of the imported QSO's needed to have these items changed. (Note: A plus that LOTW is down as they didn't get uploaded automatically with the wrong info.) Anyway, I corrected all of the info one by one, but I know there was a way to do a bulk change, but I need either pointed to the correct area of help or someone please give me the info needed to do this in the future. as I know I will pull another bonehead move again. Ha!

+ Step-by-step instructions are here:



+ Don't skip step 1!

73,

Dave, AA6YQ

Hi to the group,

I am trying to configure this combo with Commander.
I use IC-7100, address 88, Com port 7, Baud rate 19200.
I have a Multi radio configuration with my IC-7300, which works flawlessly.

As soon as I switch Commander to the G106, the G106 transceiver goes in transmit mode. Frequency, mode and commands (A, B, A=B, AxB...) work perfectly, but the G106 is in TX in permanence, even if I click to the RX button on Commander.

Can somebody help me to solve this problem ?

Thanks and best regards,

Georges F6DFZ?

I know there is a way to correct my mistake, but I can't seem to figure out how.
I imported about 120 QSO's using an ADIF file, but...........? I didn't realize I had MyQTH for the wrong location and the QSL status set top "R" for QSL cards so all were improted with the wrong info.? All of the imported QSO's needed to have these items changed. (Note: A plus that LOTW is down as they didn't get uploaded automatically with the wrong info.)? Anyway, I corrected all of the info one by one, but I know there was a way to do a bulk change, but I need either pointed to the correct area of help or someone please give me the info needed to do this in the future. as I know I will pull another bonehead move again. Ha!

TIA
WB7UOF ~ Walt

Filter the log page display before invoking the ClubLog
functions on the Check Progress tab.

IOTA HF: Freq < 30
IOTA VHF: Freq > 30

73,

... Joe, W4TV

Just sat the same here
--
John P.
WA2FZW

The IOTA website supports HF and VHF IOTA's seperately.
It is not possible in DXK to seperate and manage those 2 awards
Like UK (IOTA EU-005) I have confirmed on HF and VHF (2m & 6m).
And Verified on the IOta-site on HF, but not (yet) on VHF.

Any tips how to manage this in DXK

73

Aart PA3C

As of 9 AM EDT (1300z), the LotW Status page is reporting
all three ports (services) down. Ports 443 and 80 showed
~83% availability but the overall uptime was only ~7%.

I would suspect that network testing was being done over
night. It may portend some progress but not "production"
status.

73,

... Joe, W4TV

The server status page reported 2 of 3 servers online this morning, but ARRL has not said anything about using it yet.?

I might suggest that trying to use it before ARRL gives the go ahead could cause more problems?

--
John P.
WA2FZW

I am able to log in to my LoTW home page. DXKeeper successfully executed a "Sync LoTW QSLs" operation, reporting the confirmation of two QSOs made just before the onset of the "incident".

Both operations were very slow.

A request to display recently accepted QSOs eventually displayed "Internal Server Error".

A request to display the status of LoTW's Queue of submitted but not-yet-processed QSOs has yet to complete after many minutes.

I could find no new update regarding LoTW or ARRL IT infrastructure on the ARRL's web page, nor any guidance as to how users should resume their use of LoTW.

My advice is to hold off on any interaction with LoTW - either direct or via DXKeeper - until the ARRL has posted an update on its usability.

? ? ? ?73,

? ? ? ? ? ? ? ? Dave, AA6YQ

On Tue, Jun 25, 2024 at 10:11 AM, ab2ul wrote:

I have recently started experiencing an issue with DXLab Launcher stopping Kiwisdr online program.

About 3 weeks ago I began using the N1NTE KiwiSDR site during a Net while using the DX lab suite. During the first week and a half or so everything worked fine. Suddenly the KiwiSDr site stopped working. After some experimenting I learned that DX Lab Launcher stops the KiwiSDR from running even if all the other DX Lab software has not been started up.


Below is the setup and conditions:

DXLab Launcher 2.3.2 Triggers the following programs:

Commander, DXKeeper, DXView, Pathfinder, SpotCollecter with DX Atlas. It then triggers Chrome, Mozilla Thunderbird, and

Mulveyware - Alpha9500 control software.


In Chrome I manually start the KiwiSDR site. The address I use is .


I'm looking for any help finding the adjustments to reconcile this conflict

+ After handling startup tasks, the Launcher does nothing but wait for events from its user interface (like "minimize all DXLab windows") or messages via DDE from DXLab applications (like "DXView has started"). I suggest that you ask the KiwiSDR developers why their application has stopped running; perhaps they have an analog to the diagnostic errorlog mechanism in DXLab applications. If they have questions about the Launcher, don't hesitate to give them my contact information.

? ? ?73,

? ? ? ? ? ? ?Dave, AA6YQ?

Hello,

I have recently started experiencing an issue with DXLab Launcher stopping Kiwisdr online program.

About 3 weeks ago I began using the N1NTE KiwiSDR site during a Net while using the DX lab suite. During the first week and a half or so everything worked fine. Suddenly the KiwiSDr site stopped working. After some experimenting I learned that DX Lab Launcher stops the KiwiSDR from running even if all the other DX Lab software has not been started up.


Below is the setup and conditions:

DXLab Launcher 2.3.2 Triggers the following programs:

Commander, DXKeeper, DXView, Pathfinder, SpotCollecter with DX Atlas. It then triggers Chrome, Mozilla Thunderbird, and

Mulveyware - Alpha9500 control software.


In Chrome I manually start the KiwiSDR site. The address I use is .


I'm looking for any help finding the adjustments to reconcile this conflict

73 de AB2UL - Tom

The correct ADIF is:

mode = MFSK
submode = Q65?

73,

... Joe, W4TV

On 6/24/2024 4:59 AM, aart wedemeijer PA3C wrote:

So I have to upload the QSO
mode = MFSK
submode = Q65?
Or mode = Q65
73,
Aart PA3C

So I have to upload the QSO

mode = MFSK
submode = Q65?

Or mode = Q65

73,

Aart PA3C

+ AA6YQ comments below

I tried to upload qso's with mode Q65C to Eqsl.
But they were refused.

Any tips, or is Eqsl not up to date with (not-so-new) new modes?
Something with mode/submode but could not find in the wiki how to solve this issue.

+ The ADIF specification does not define Q65C as a valid mode or submode:

? ? ?73,

? ? ? ? ?Dave, AA6YQ

I tried to upload qso's with mode Q65C to Eqsl.
But they were refused.

Any tips, or is Eqsl not up to date with (not-so-new) new modes?
Something with mode/submode but could not find in the wiki how to solve this issue.

73

Aart PA3C