+ AA6YQ comments below

Does anyone know whether any of the Commander user-defined controls
available on the DXLab website are usable with the new FTDX-101D or MP?

+ The FTDX-101 CAT instruction set is similar to those of the FTDX 3000, 5000, and 9000, but with one more digit in commands and responses that convey frequencies. If there's a user-defined control for the older radios that you'd like to try with your 101, I suggest that you check each CAT command in the control to see if the 101 will accept it.

73,

Dave, AA6YQ

Does anyone know whether any of the Commander user-defined controls available on the DXLab website are usable with the new FTDX-101D or MP?  Any info much appreciated!  73 to all.

Jan N0JR

Dave et al,
The pre-release version of SpotCollector is running well. The whole suite is running like a well oiled clock 😊. Thanks for your help.
73,
Mike
NA5U

It is possible that your QSO partner uploaded the QSO with some different information (mode, time, etc.)  causing him not to find a match.

I would not lose sleep over it, specially if you see the QSO when you search your clublog.

73.
Carl - WC4HG

No sweat Bill.  Glad that you were able to sort it out.

73.
Carl - WC4H

Thanks Dave !!!
Best 73, Steve KH6CT

+ AA6QY comments below

I think I once had Spot Collector set up to display the bearing from my QTH to the DX station. I selected the Azmiuth field and gave it the caption Bearing, but nothing displays. Am I having another Senior Moment ??

+ Take a look at

< https://www.dxlabsuite.com/dxlabwiki/SpotDatabaseDisplayAzimuth>

73,

Dave, AA6YQ

I think I once had Spot Collector set up to display the bearing from my QTH to the DX station.  I selected the Azmiuth field and gave it the caption Bearing, but nothing displays.  Am I having another Senior Moment ??
Steve KH6CT

+ AA6YQ comments below

On Thu, Sep 12, 2019 at 10:56 AM, Bill Stravinsky wrote:

What both of you needed to tell me was "hey dummy, there are separate panels for normal QSLing and Online Qsling", hi.  After I still didn't see that I tried

to justify the way I was doing things.  I won't even tell you how I was sending Lotw requests in the beginning then along came EQsl and ClubLog.  That was

2 or 3 years ago when I started to use DXL.  I wound up with my own system using only some of the features of DXL.

 

Anyway, late last night after replying to Dave's latest email, I looked hard at the process and saw what you both were trying to convey to me.  I had a small

amount of Lotw & EQsl requests that I had to edit so they would stop showing up when I hit "add requested" and now have a clean slate.  From now on I will

do it the way it was intended to be done.  Even though how I was accomplishing it was working it was still a jury rigged process on my part.  My next batch of

online QSL requests will be done how you tried to show me.

 

I did manage to figure out the process for making labels to attach to my cards for normal QSLing and tested it on regular printer paper.  It appears it should

work and I have a little over 300 cards that need labels.  I will be trying to use the program the way it was laid out to do, hi.

 

Thanks again and sorry I acted a little bull headed.  Maybe I'll become a DXL power user yet, hi.

+ There's no need to apologize, Bill. As you posted, there are often several ways to accomplish a task in DXLab, and it's a natural tendency to stick with the first one you find that works. However, it is also natural to point out a "better way" when one is available, and that what happened in this thread. 

+ To see all of the items recorded with each QSO, take a look at

<https://www.dxlabsuite.com/dxkeeper/Help/Items.htm>

       73,

             Dave, AA6YQ

+ AA6YQ comments below

snip<

In response to your answer .. I am lazy, so when I click upload to Clublog that's the end of it. I do not change QSO's on clublog because I have neither the time or the inclination to do so - DXKeeper is my "bible" and I do not need to change a QSO there because my CW is faultless - it's the others!

+ There's no need to manually change a QSO's Club Log status; I was just pointing out that this is a way that a QSO's Club Log status might be made incorrect.

73,

Dave, AA6YQ

I am always amazed by your prompt responses. I don't respond so fast in my day job !!  I'm sure DXKeep er is not your day job!
In response to your answer .. I am lazy, so when I click upload to Clublog that's the end of it. I do not change QSO's on clublog because I have neither the time or the inclination to do so - DXKeeper is my "bible" and I do not need to change a QSO there because my CW is faultless - it's the others!  No this is a mystery to me because the QSO was accurately logged  - mode - time - etc. (the usual errors)  so even if the QSO did not get uploaded the first time, I am clicking upload to clublog maybe once or twice a day and eventually it should have gone through or been flagged as dupe. As you suggest I will pass this thread of conversation to Clublog.


73
David
A92GE

+ AA6YQ comments below

Here's a Pathfinder question. I'm running FT8 with WSJT-X, JTAlerts and a Flex 6500. When I click on a callsign, WSJT-X populate as
well as DXView and Pathfinder. Pathfinder however does not pull in the information about the selected station. I have to click the
QRZ button in Pathfinder or DXView.
Possibly this is correct but I thought Pathfinder would auto populate. Any guidance is appreciated.

+ When I extended SpotCollector to directly interoperate with WSJT-X, I missed the scenario where the user double-clicks a Spot
Database Entry for a station running a "K1JT mode" like FT8 or FT4, but hasn't logged a QSO with the Entry's station. This defect
has been corrected in the next version of SpotCollector, which I've sent you so you can give it a try.

73,

Dave, AA6YQ

+ AA6YQ comments below

According to DXKeeper all my QSO's are uploaded to Clublog. I do this after every time I finish on the air. However someone asked me why their QSO could not be found on club log and when I checked it wasn't there. DXKeeper said it was uploaded. I right clicked on the QSO in the log page and uploaded it to clublog again. I right clicked and uploaded it to club log a second time and I got the error message Upload to Club log succeeded dupe (or words to that effect). It was now appeared on a search in clublog. Obviously although it was originally reported as uploaded it wasn't and when I tried twice it definitely had been. So this poses two questions - why was it originally reported as uploaded when it wasn't and how do I now check all the QSO's in my log against club log's version of my log to make sure all QSO's are all there and there are no dupes?

+ DXKeeper only marks a logged QSO as "uploaded to ClubLog" if it was uploaded with a positive response from Club Log. If a logged QSO marked in DXKeeper as "uploaded to Club Log" is not present in Club Log and you haven't been manually altering the Club Log status of logged QSOs, then I suggest asking Club Log about it.

+ You can spot check an individual logged QSO by directing DXKeeper to upload it to Club Log and seeing if the response is "dupe". There is no "check all logged QSOs to confirm their presence in Club Log" function; I doubt that the Club Log folks would appreciate my adding one.

73,

Dave, AA6YQ

According to DXKeeper all my QSO's are uploaded to Clublog. I do this after every time I finish on the air. However someone asked me why their QSO could not be found on club log and when I checked it wasn't there. DXKeeper said it was uploaded. I right clicked on the QSO in the log page and uploaded it to clublog again. I right clicked and uploaded it to club log a second time and I got the error message Upload to Club log succeeded dupe (or words to that effect). It was now appeared on a search in clublog. Obviously although it was originally reported as uploaded it wasn't and when I tried twice it definitely had been. So this poses two questions - why was it originally reported as uploaded when it wasn't and how do I now check all the QSO's in my log against club log's version of my log to make sure all QSO's are all there and there are no dupes?

73

David
A92GE

+ AA6YQ comments below

I think maybe I didn't explain the problem well. In this image

https://imgur.com/5Zr2XmB

the green sides can already be dimensioned, but I would like the red side, like that of the "Log QSOs" tab, to widen following the right side of the main window giving me more space for the columns. I hope this time I clarified the problem.

+ I misunderstood. I thought you were reporting that after switching to a new PC after your previous PC broke, the lower-resolution monitor you were using made it impossible to alter the size of the "my QTHs" tab.

+ In the next version of DXKeeper, the width of the table shown on the "my QTHs" tab expands to use the available horizontal space.

+ Thanks!

73,

Dave, AA6YQ

+ AA6YQ comments below

I'm asking because I'm not certain about the mechanism. Maybe the following statement, taken from the Iota-World site, "Programme
Information | Add QSOs from Club Log" page, is a bit misleading or maybe is not so clear for a non-english person:

"Once IOTA Management has accepted the Club Log matched QSOs and any others in your application that are supported by QSL cards, it
will credit the QSOs to your IOTA Award account."

What is not clear is if the "that are supported by QSL cards" statement is related only to paper submissions or if it is related to
*ALL* submitted QSOs, including the Club Log matches.

Effectively, this sentence says also: "has accepted Club Log matched QSOs...".

Not very clear, at least for me.

+ Accepting "Club Log matched QSOs" is clearly not the same as accepting LoTW confirmations.

73,

Dave, AA6YQ

Here's a Pathfinder question. I'm running FT8 with WSJT-X, JTAlerts and a
Flex 6500. When I click on a callsign, WSJT-X populate as well as DXView and
Pathfinder. Pathfinder however does not pull in the information about the
selected station. I have to click the QRZ button in Pathfinder or DXView.
Possibly this is correct but I thought Pathfinder would auto populate. Any
guidance is appreciated.
73,
Mike
NA5U