+ AA6YQ comments below

Got it now, just needs a bit of experimentation to get it how I want it.
I was just overwhelmed by the quantity of possibilities and the detail that you have built into the software.

+ All of that is required to comply with the WAS award rules.

 
Just one more thing, if I delete/remove all the fields in the SC display that I don't need (or display) will it help/improve the SC response. 

+ Slightly, but every little bit helps.

        73,

            Dave, AA6YQ

+ AA6YQ comments below

Based on guidance from Dave I looked at each discrepancy.  Dave offered that I would note "likely understand the source of all of them,..."  Well...  I'm not convinced that two of the discrepancies were consistent.  So painstakingly I went line by line and using the Discrepancy record, the log, the LoTW QSO selector and sorts by DXCC without a specific call, I finally got to assess each one and make the necessary changes

+ So that we can better help the next op attempting a DX4WIN=>DXKeeper transition, what are some examples of the sources of the discrepancies?

        73,

              Dave, AA6YQ 

SUCCESS!!!!!  finally...

Based on guidance from Dave I looked at each discrepancy.  Dave offered that I would note "likely understand the source of all of them,..."  Well...  I'm not convinced that two of the discrepancies were consistent.  So painstakingly I went line by line and using the Discrepancy record, the log, the LoTW QSO selector and sorts by DXCC without a specific call, I finally got to assess each one and make the necessary changes.  Along the way I learned that I could not make two changes at once.  I learned that I had to run a new discrepancy report after each edit to make sure I did not introduce a "new" discrepancy.

But all that said, I learned a lot - mostly subtleties where the issue was semantics with word choices and understanding what was really meant in an instruction.  No fault of the Wikis or the help offered, just my own stubbornness with 
anticipated results as opposed to what really happened.

Thanks to everyone that offered insight and guidance.  Please understand I was not trying to be difficult, but in several cases I did exactly what was offered and came up with a different result, only to do it again and get the "right" result.

The community is OUTSTANDING!!!!

Thanks to all.

Rick N0YY

 

+ AA6YQ comments below

Thanks for your response Joe. That seems to have been the problem there was no entry in the propagation field in the propagation pane. Due to screen space that is a pane that I never have up. I noticed that other log entries had F2 in that field so I entered that and the QSO was counted and entered in the Marathon report.

You know I've been participating in the Marathon for the last 4 or 5 years and I don't think that has ever happened before. I wonder if I've ever missed counting another QSO in past years because of this. What would have caused DXK not to have F2 entered in that field? Better yet what causes DXK to enter F2 in that field?

+ That is the result of a defect inadvertently introduced in DXKeeper 16.5.7 that fails to initialize a new (via the Capture window or Main window's "Log QSOs" tab) QSO's Propagation Mode item if "Default Propagation Mode by Band" is not enabled on the Configuration window's Defaults tab.

+ I have sent you a new version of DXKeeper that corrects this defect. 

+ Until this new version is publicly released, uses can work around it by enabling "Default Propagation Mode by band" on the Configuration window's Defaults tab, and setting all three band selectors to the desired default Propagation Mode.

+ To view QSOs with missing Propagation Mode items as a result of the regression, filter the Log Page Display with the SQL expression

(QSO_BEGIN>#2022-05-21#) and (LEN(PROP_MODE)=0)

If all the Propagation Mode items of all of these QSOs should be set to the same value -- e.g. F2 -- then

1. backup your log (Configuration window, Log tab, Backup button)

 

2. in the "Modify QSOs" panel at the bottom of the "Advanced Sorts, Filters, and Modifiers" window,

 

2.a. set the "Item name" selector to PROP_MODE

 

2.b. set the "Item new value" selector to the correct propagation mode (e.g. F2)

 

 
+ If  the Propagation Mode items of all of these QSOs should be set to different values as a function of Band or Date Range, then make the corrections in segments. For example

A. backup your log (Configuration window, Log tab, Backup button)

B. filter the Log Page Display with (QSO_BEGIN>#2022-05-21#) and (LEN(PROP_MODE)=0) and (Band = '6M')

C. use the "Modify QSOs" panel to set all QSOs in the Log Page Display to ES

 

D. filter the Log Page Display with (QSO_BEGIN>#2022-05-21#) and (LEN(PROP_MODE)=0) and (Band <> '6M')

 

E. use the "Modify QSOs" panel to set all QSOs in the Log Page Display to F2

 

 

     73,

           Dave, AA6YQ

 

 

 

+ AA6YQ comments below

I do not have specs on the cable, I picked it up off Amazon.

+ Connectivity requirements for the TS-440S are documented here:

https://www.dxlabsuite.com/dxlabwiki/ConnectingKenwood

Here are the Dxlab Commander settings.

+ This group does not convey images.Commander settings for the TS-440S are documented here:

https://www.dxlabsuite.com/dxlabwiki/TranceiverControlKenwood

        73,

               Dave, AA6YQ

 

+ AA6YQ comments below

I'll perform this test later today and report back the results, but it isn't just Pathfinder. When I Sync LoTW QSLs in DXKeeper, DXView cycles through some callsigns as well.

+ With Pathfinder and DXView running, please do the following:

1. on the General tab of DXKeeper's Configuration window, check the "Log debugging info" box

2. on the QSL tab of DXKeeper's Main window,

2a. set the "QSL Via" panel to LoTW

2b. click the "Sync LoTW QSLs" button

3. on the General tab of DXKeeper's Configuration window, uncheck the "Log debugging info" box

4. attach the errorlog.txt file from your DXKeeper folder to an email message, and send the message to me via

aa6yq (at) ambersoft.com

       73,

             Dave, AA6YQ

Thanks for your response Joe. That seems to have been the problem there was no entry in the propagation field in the propagation pane. Due to screen space that is a pane that I never have up. I noticed that other log entries had F2 in that field so I entered that and the QSO was counted and entered in the Marathon report.

You know I've been participating in the Marathon for the last 4 or 5 years and I don't think that has ever happened before. I wonder if I've ever missed counting another QSO in past years because of this. What would have caused DXK not to have F2 entered in that field? Better yet what causes DXK to enter F2 in that field?

Julio

I do not have specs on the cable, I picked it up off Amazon.
Here are the Dxlab Commander settings. Thank You


Dennis

I'll perform this test later today and report back the results, but it isn't just Pathfinder. When I Sync LoTW QSLs in DXKeeper, DXView cycles through some callsigns as well.

Thanks Dave,
Got it now, just needs a bit of experimentation to get it how I want it.
I was just overwhelmed by the quantity of possibilities and the detail that you have built into the software. 
Just one more thing, if I delete/remove all the fields in the SC display that I don't need (or display) will it help/improve the SC response. (It's very good anyway).

Thanks again
Tony G4CJC

# more AA6YQ comments below

On Tue, Jul 12, 2022 at 9:53 PM Dave AA6YQ <aa6yq@...> wrote:

<snip> 

Also -- when choosing modes, does "ALL" mean all? 

+ In which panel of what window?

 

The Mode button at the bottom Spot Collector.

@ Clicking the All button in the "SpotCollector Mode Filter" window checks all of the mode boxes in that window.

 

So -- does that mean that Spot Collector looks for every mode, or just lets everything through without checking? 

# Start here:

https://www.dxlabsuite.com/dxlabwiki/CollectingSpots

       73,

              Dave, AA6YQ

@ more AA6YQ comments below

On Tue, Jul 12, 2022 at 7:45 PM Dave AA6YQ <aa6yq@...> wrote:

<snip> 

Also -- when choosing modes, does "ALL" mean all? 

+ In which panel of what window?

 

The Mode button at the bottom Spot Collector.

@ Clicking the All button in the "SpotCollector Mode Filter" window checks all of the mode boxes in that window.

       73,

             Dave, AA6YQ

+  AA6YQ comments below

Thanks Dave, I was actually thinking about the reverse direction. By toying around with the serial debugger, I wasn't sure if I sent DT0 to the Secondary port whether that would get passed to the primary. 

+ My previous response was incorrect. With both the primary transceiver being one of the Elecraft models previously specified and the secondary CAT port protocol set to "Elecraft",

 - If Commander receives a DT; from the secondary transceiver, Commander sends the secondary transceiver a DTx; command, where X is the primary transceiver's data submode.

 - If Commander receives a DTx; from the secondary transceiver, if the primary transceiver is configured to follow the secondary transceiver, Commander sends the DTx command to the primary transceiver.

       73,

            Dave, AA6YQ

Thanks Dave, I was actually thinking about the reverse direction. By toying around with the serial debugger, I wasn't sure if I sent DT0 to the Secondary port whether that would get passed to the primary. 

Thanks again! 

Ok Joe, thanks, that did the trick. I had tried that (by guessing) earlier but Omni-rig didn't pick up the change 'till a reboot. 

Thanks for the help! This makes life a tad easier! Commander is behaving much better than Omni-rig was. 

-Steve

+ AA6YQ comments below

In Spot Collector, one can choose up to 89 modes to show.

 

WOW!

 

Is there a way to cut that back to the 8-12 that I might actually use?  It's a bit difficult to find a particular one in amongst "all the trees".

+ Yes. See the "Determining the Mode Being Used by a Spotted Station" section in

https://www.dxlabsuite.com/dxlabwiki/CollectingSpots

+ Edit your current sub-band definition files to remove entries for modes that aren't of interest, and save the result a unique filename, like KD5XB_BandModes.txt. Then at the bottom of the Main window's General tab, click the Select button in the "Sub-band Definition" panel, and select your modified sub-band definition file.

 

Also -- when choosing modes, does "ALL" mean all? 

+ In which panel of what window?

         73,

               Dave, AA6YQ

 

What are the specs of that cable? Kenwood does not use DTR (or DTR and
DSR) but *REQUIRES* both RTS (an input from the computer to tell the
rig it is OK to send data) and CTS (an output to the computer to tell
the computer it is OK to send data). The RTS/CTS pair is "Hardware
handshake".

The TS-440, as with other Kenwood rigs of that era (6 pin DIN serial
connector) require TTL level signals. RS-232 level signals (the
negative voltage) can damage the rig.

73,

... Joe, W4TV