The RBN or skimmer station k9imm-# is spotting all decodes regardless of band to 6m.? Is there a way to filter this station out as a bad spotter?? Many of the FT mode skimmers are horrible.

开云体育

On 2025-02-27 12:09 PM, Dave AA6YQ wrote:

# if you set the "Handling of LoTW QSL inconsistency" panel to "Preserve log data, ignore LoTW data, and report inconsistencies when operation ends", no changes will be made to your logged QSOs, and you will be given a report that describes each discrepancy. You can then review that report, determine which discrepancies merit modifying your logged QSOs, and modify your logged QSOs accordingly,

I'm aware that one can have DXK prepare a "discrepancy report" and
go back to resolve the issue. That's not what I want ... I want
to be prompted for each discrepancy and resolve it on the fly as I
have selected in QSL Config -> LotW without being asked "are you
sure" just because there are more than 'N' new/updated QSLs.

I export new QSOs from my "radio" system to my "desk" machine every
day at 0000z, sync ALL and upload confirmed QSOs to eQSL from the
"desk" machine to keep both systems up to date. The extra "are
you sure" and "log is filtered" prompts get annoying when it is
something I do every day (and multiple times a day between the two
systems plus my backup N100).

73,

... Joe, W4TV


On 2025-02-27 12:09 PM, Dave AA6YQ wrote:

#more AA6YQ comments below

+ That's under your control: on the "QSL Configuration" window's LoTW tab,
set the "Handling of LoTW QSL inconsistency" panel to
"Preserve log data, ignore LoTW data, and report inconsistencies when
operation ends".

But I *want* to be made aware of inconsistencies and make the decision
what to do about them. In particular, I don't want DXK to blindly
follow changes from the idiots who move from Washington to Arizona or
Hawaii to Nevada and reload 50 years of logs with the new QTH.

# if you set the "Handling of LoTW QSL inconsistency" panel to "Preserve log data, ignore LoTW data, and report inconsistencies when operation ends", no changes will be made to your logged QSOs, and you will be given a report that describes each discrepancy. You can then review that report, determine which discrepancies merit modifying your logged QSOs, and modify your logged QSOs accordingly,
73,
Dave, AA6YQ

What do i need to do to get the WSJT logged QSO's to automatically
get loaded to DXK? Is the issue in DXK config or WSJT config?

Information on integrating WSJTX with DXLab Suite is here:

<>

There are two versions ... one "Direct" using SpotCollector:

<>

and one using JT Alert:

<>


73,

... Joe, W4TV

On 2025-02-27 12:38 PM, Greg via groups.io wrote:

Not too long ago I switched to the new release (2.7.0) of WSJT for FT8. For some reason now, the logged contact for WSJTis not getting relayed and captured by DXK.? The contacts are logged in the WSJT log but don't get logged to DXK automatically.? Contacts on other modes entered via the capture window or main log page work fine and are logged and i believe that version 2.6 had no problems with getting FT8 QSO logged automatically.? ?My WSJT settings are
UDP SERVER = 127.0.0.1
Network service port = 52000
log Automtically is checked
UDP port server = 2237
Outgoing interface = Loopback_0
Multicast TTL = 1
Accept UDP requests is checked.
Notify on UDP requests is checked.
Accepted UDP request restores window is unchecked
2nd UDP server settings are
Enable logged contact ADIF? broadcast is checked
server IP address = 127.0.0.1
Server port number = 12060
What do i need to do to get the WSJT logged QSO's to automatically get loaded to DXK? Is the issue in DXK config or WSJT config?
Greg N9GB

+ Those prevent a log of errors, some of which have consequences
that would be time-consuming to repair.

It may for someone who is not paying attention. On the other hand,
If I make a change to a filtered sub set of the log that is wrong,
I can always filter the log again and reverse the change.

+ That's under your control: on the "QSL Configuration" window's LoTW tab, set the "Handling of LoTW QSL inconsistency" panel to
"Preserve logdata, ignore LoTW data, and report inconsistencies when
operation ends".

But I *want* to be made aware of inconsistencies and make the decision
what to do about them. In particular, I don't want DXK to blindly
follow changes from the idiots who move from Washington to Arizona or
Hawaii to Nevada and reload 50 years of logs with the new QTH.

73,

... Joe, W4TV

On 2025-02-27 12:19 AM, Dave AA6YQ wrote:

+ AA6YQ comments below
All of "the log page display is filtered" prompts
+ Those prevent a log of errors, some of which have consequences that would be time-consuming to repair.
The LotW Sync prompt regarding inconsistencies when there are a large number of confirmations
+ That's under your control: on the "QSL Configuration" window's LoTW tab, set the "Handling of LoTW QSL inconsistency" panel to "Preserve log data, ignore LoTW data, and report inconsistencies when operation ends".
the eQSL "Add All" prompt when the log page display is filtered ...
+ That's another "the log page display is filtered" prompt.
73,
Dave, AA6YQ

+ AA6YQ comments below

All of "the log page display is filtered" prompts

+ Those prevent a log of errors, some of which have consequences that would be time-consuming to repair.

The LotW Sync prompt regarding inconsistencies when there are a large number of confirmations

+ That's under your control: on the "QSL Configuration" window's LoTW tab, set the "Handling of LoTW QSL inconsistency" panel to "Preserve log data, ignore LoTW data, and report inconsistencies when operation ends".

the eQSL "Add All" prompt when the log page display is filtered ...

+ That's another "the log page display is filtered" prompt.

73,

Dave, AA6YQ

Perhaps I’m working FT8 looking for needed calls. JTAlert gives me this info. I may not want to QSY to another frequency/band depending on the “need” for the spotted station. If the spot is just a new mode, say SSB, on an already confirmed band and I know band conditions are not good for my modest station I may decide not to QSY.

+ If you don't want to QSY right-click the Spot Database Entry and select "Display Award Tracking for ...". SpotCollector will display its "Realtime Award Tracking" window, which will show you exactly why the Entry is considered "Needed", including whether it's status is "unworked" or "unconfirmed".

73,

Dave,

开云体育

Perhaps I’m working FT8 looking for needed calls. ?JTAlert gives me this info. ?I may not want to QSY to another frequency/band depending on the “need” for the spotted station. ?If the spot is just a new mode, say SSB, on an already confirmed band and I know band conditions are not good for my modest station I may decide not to QSY. ??Or perhaps DXView shows I have worked the DX entity but it is not confirmed. ?I can double click on the “w” to see what call(s) I have worked and then click on the calls in DXKeeper ?to see when the last upload to LOTW was via DXView. ?I’m only interested in LOTW confirmations. ?These are all tools to help me decide how I want to operate. I am aware of SpotCollector’s color coding and use it.

Tom-KQ5S

--

Understand, but I don’t want to QSY until I see the data shown in the DXView Progress Window and then decide if I want to change bands/modes.

+ What's the problem with QSYing before you know it's "needed"?

73,

Dave, AA6YQ

开云体育

Understand, but I don’t want to QSY until I see the data shown in the DXView Progress Window and then decide if I want to change bands/modes. ?I just click the spot in SpotCollector then look at the DXView progress window to decide what I want to do. ?Highlighting the band of the clicked spot in DXView makes it easier/quicker to see data. ?I often click on a spot without looking at the other spot data and then go to DXView to make a determination of what I want to do.

--