Date   

Modify QSOs in Log Page Display warning suggestion request / display total of filtered records

Ken Alker
 

I am experimenting with Modify QSOs in Log Page Display for the first time.  This is a great feature.  However, I can imagine that one could accidently change many MORE entries that one intended if this were used incorrectly.  I would like to suggest that the DXKeeper Modify QSOs window that pops up after pressing the Mod button inform the user as to how many QSOs they are about to modify.  This would, hopefully, draw attention to what is about to happen if the user expects to be modifying, say, 27 QSOs, but the window states they are about to modify 2938 QSOs.  I assume there is no way to quickly and easily "undo" such a mistake other than hoping one just backed up the database (please correct me if wrong).

Likewise (perhaps this should be a separate topic, yet it goes hand in hand), it would be nice if, after applying a filter to the database, 1) there were an indication on the screen that one is looking at a filtered view, and 2) there were a field showing of how many total records are in that view (such that one has a number to compare one's Modify QSO results against).  I know pressing the FFW arrow will scroll to the end of the QSO list and a "last record number" (which is also the total record count) will be displayed, but a "permanent" indicator would be nice.  I hope I'm not requesting something that is already there, but I've looked around on the screen and I don't see either of these indicators.  (NOTE: I am mildly color blind so if this is somehow being indicated using colors, I am likely not seeing it, especially if highlighted in red).


Re: Export, from dxkeeper, FT8 contacts in .adif format consumable by wsjtx?

 

Bill,

Many thanks for your detailed response and information.   I appreciate your time in answering.

Thank you.   I am still reading the detailed directions to fully interface DX Lab with wsjtx for interoperability.

As is always the case, the written instructions are thorough and detailed, but, I am going through the process slowly.

:-)

Thank you again.  


Re: Export, from dxkeeper, FT8 contacts in .adif format consumable by wsjtx?

g4wjs
 

On 10/10/2021 10:54, mike s wrote:
However, as noted, I think it is possible, within wsjtx, to see previously logged calls in the lower left window.   (I am not sure about this but read a thread here recently that gave me that perception).
Hi Mike,

that's not correct. The only status bar indication related to the WSJT-X ADIF log is when WSJT-X starts, it shows the number of worked before records loaded from its ADIF log file for a few seconds after the load completes. WSJT-X can highlight CQ calls from stations you have now worked before, or not worked before on the current band, but if you are using the full DX Lab Suite to WSJT-X integration then you will have new DXing goals highlighted, as defined by your DXKeeper log and award objectives.

There's no problem with using the DXKeeper ADIF export facility to create a replacement ADIF log for WSJT-X, you don't need to limit it to just FT8 contacts. If you do use the WSJT-X decode highlighting, you can highlight per the current mode or for all modes combined by changing the "Settings->Colors->Highlight by Mode" option.



--
73

Bill

G4WJS.


Export, from dxkeeper, FT8 contacts in .adif format consumable by wsjtx?

 

High level question:  Is it possible to export a standard .adif file from dxkeeper, containing of all my ft8 contacts, and use that file to replace the existing wsjtx log?  

Reason:  I think, based on reading another thread recently, that if I look at the lower left of wsjtx I will be able to see if I have already logged the call sign if that call sign is resident in the log wsjtx is conscious of.  

However, from the beginning of my use of wsjtx I have managed my contacts with (first HRD then dxkeeper).   Each time I migrated contacts from the wsjtx log I deleted the wsjtx log so that only new contacts would be in the log going forward.    

Now, all of my ft8 contacts are in dxkeeper and I have been typing in calls in dxkeeper to see if I already have them while running wsjtx.  However, as noted, I think it is possible, within wsjtx, to see previously logged calls in the lower left window.   (I am not sure about this but read a thread here recently that gave me that perception).

IF I export a standard adif from dxkeeper and replace the wsjtx simple wsjtx adif log at C:\Users\Owner\AppData\Local\WSJT-X/logs with the adif from dxkeeper can wsjtx consume it properly??

I understand I can run the experiment myself, but, having done such things on software I did not fully understand in the past, I have learned a bit of caution.

Thank you in advance for any thoughts.  

KM2B


Re: Filtering SC for special callsigns by mode

Dave AA6YQ
 

+ AA6YQ comments belows
might be this issue has been discussed before but I didn't find when using the search function in the group:

For using SC in a contest I need to hide the stations worked before on the band. I don't know how to set the SQL filter regarding the callsign because it has to be looked up in DXK before. The SQL expression for band and mode is clear, also filtering for new Multis is no problem for me.

Any proposal how to solve it would be nice. Thanks in advance

+ SpotCollector is not designed to provide assistance for contesting.

            73,

                    Dave, AA6YQ


Re: Filtering SC for special callsigns by mode

dl8le
 

Hello, 

might be this issue has been discussed before but I didn't find when using the search function in the group:

For using SC in a contest I need to hide the stations worked before on the band. I don't know how to set the SQL filter regarding the callsign because it has to be looked up in DXK before. The SQL expression for band and mode is clear, also filtering for new Multis is no problem for me.

Any proposal how to solve it would be nice. Thanks in advance

73

Juergen, DL8LE


Re: Medium Distance

3a2mw Franco Lucioni
 

Thank you, Dave !
Franco


Re: WinWarbler behavior on FSK

Dave AA6YQ
 

+ AA6YQ comments below

I’m seeing some behavior with WinWarbler that I can’t explain or resolve, so I hope someone can offer a bit of help. I’m trying to run it on FSK. If I boot into it and set all the parameters for FSK, it runs just fine. If I then boot Commander (or Commander with any or all of the other DXLab modules), WW no longer places the radio into transmit but will display a macro or typed message onscreen. It will also change the mode on the radio from RTTY-L to USB. If I close both WW and Commander and then re-boot WW, it comes up with the configuration reset to AFSK. I have to re-select FSK, re-enter EXTFSK64, and switch the radio back to RTTY-L to get it to run again. Configuration settings seem to match those described in the help files and match those in other online resources. The computer is running WIN 10 and the radio is a Yaesu FTdx-101MP. I could definitely use some advice here. Thanks in advance.

+ WinWarbler uses Commander to control your transceiver, so Commander should already be running when you change WinWarbler's "operating mode" to RTTY. Step-by-step instructions for RTTY FSK operation are here:

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

73,

Dave, AA6YQ


WinWarbler behavior on FSK

Jeff, K6JW
 

I’m seeing some behavior with WinWarbler that I can’t explain or resolve, so I hope someone can offer a bit of help. I’m trying to run it on FSK. If I boot into it and set all the parameters for FSK, it runs just fine. If I then boot Commander (or Commander with any or all of the other DXLab modules), WW no longer places the radio into transmit but will display a macro or typed message onscreen. It will also change the mode on the radio from RTTY-L to USB. If I close both WW and Commander and then re-boot WW, it comes up with the configuration reset to AFSK. I have to re-select FSK, re-enter EXTFSK64, and switch the radio back to RTTY-L to get it to run again. Configuration settings seem to match those described in the help files and match those in other online resources. The computer is running WIN 10 and the radio is a Yaesu FTdx-101MP. I could definitely use some advice here. Thanks in advance.

--Jeff


Re: DXKeeper: State QSO Tracks As R Even Tho It's a C

Dave AA6YQ
 

+ AA6YQ comments below

I have another 10m close-in QSO to confirm and an 80m Delaware QSO to work and confirm. At that point, I'll finally have the confirmations for 5BWAS.

+ Good hunting, Jerry!

73,

Dave, AA6YQ


Re: DXKeeper: State QSO Tracks As R Even Tho It's a C

Gerald Wilson
 

BINGO!    I followed your instructions, and my QSO partner's LOTW cfm entry now shows "GMSZ."   That QSO is now a hard "C" for confirmed.  Thank you for your guidance.

I have another 10m close-in QSO to confirm and an 80m Delaware QSO to work and confirm.  At that point, I'll finally have the confirmations for 5BWAS.    I couldn't have done it without DXLab Suite.

Thanks again es VY 73,

        Jerry    K7VIT


On 10/9/2021 20:37, Dave AA6YQ wrote:
# more AA6YQ comments below

Dave,    Thank you for your very prompt response.

+ ... What letters are present in this QSO's "LoTW Cfm" item?

The LOTW panel's "cfm" item is blank.   I did notice the absence of any letters there.   I searched around in my log and notice that during this earlier time period (i.e. 2006) very few LOTW confirmed QSOs have letters in the LOTW cfm item compared to all having an entries in more recent LOTW confirmed QSOs.  The QSO in question was confirmed in early 2007.   It's a close-in state but not line of sight for 10m.  😁

Should I resubmit this particular QSO to LOTW again because of updates to the LOTW program which have been made in recent years?

# It's not necessary to re-submit your QSO, as that won't change anything. However, your QSO partner may have subsequently re-submitted his or her QSO with more information in their "Station Location"; to see if this is the case, right-click the QSO's entry in the Log Page Display, and select "Update from LoTW" from the pop-up menu. DXKeeper will inform you if additional confirmations have been downloaded, and the QSO's "LoTW Cfm" item will be updated to so indicate.

       73,

              Dave, AA6YQ








Re: Realtime tracking for DXCC Satellite

Dave AA6YQ
 

+ AA6YQ comments below

Joe, if you have uploaded your QSOs to Logbook of the World, you can view your Satellite DXCC status in your LotW | Awards | “Your LoTW ARRL DXCC (DX Century Club) Account(s)” | Account Status table (just below the Digital status line).

+ DXKeeper's DXCC Progress Report shows "Satellite DXCC" Status. Joe's request was for realtime tracking of this award objective.

73,

Dave, AA6YQ


Re: Realtime tracking for DXCC Satellite

w6de
 

Joe, if you have uploaded your QSOs to Logbook of the World, you can view your Satellite DXCC status in your LotW | Awards |  “Your LoTW ARRL DXCC (DX Century Club) Account(s)” | Account Status table (just below the Digital status line).

73,

Dave, w6de

 

From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Joe W4WT via groups.io
Sent: Saturday, October 09, 2021 17:44
To: DXLab@groups.io
Subject: [DXLab] Realtime tracking for DXCC Satellite

 

Is there realtime tracking for dxcc satellite?  I see a satellite column in Progress but I don't see satellite in realtime.  Is there a config setting somewhere I might be missing?  I see it for WAS just not for DXCC.

Thanks,

Joe W4WT


Re: DXKeeper: State QSO Tracks As R Even Tho It's a C

Dave AA6YQ
 

# more AA6YQ comments below

Dave, Thank you for your very prompt response.

+ ... What letters are present in this QSO's "LoTW Cfm" item?

The LOTW panel's "cfm" item is blank. I did notice the absence of any letters there. I searched around in my log and notice that during this earlier time period (i.e. 2006) very few LOTW confirmed QSOs have letters in the LOTW cfm item compared to all having an entries in more recent LOTW confirmed QSOs. The QSO in question was confirmed in early 2007. It's a close-in state but not line of sight for 10m. 😁

Should I resubmit this particular QSO to LOTW again because of updates to the LOTW program which have been made in recent years?

# It's not necessary to re-submit your QSO, as that won't change anything. However, your QSO partner may have subsequently re-submitted his or her QSO with more information in their "Station Location"; to see if this is the case, right-click the QSO's entry in the Log Page Display, and select "Update from LoTW" from the pop-up menu. DXKeeper will inform you if additional confirmations have been downloaded, and the QSO's "LoTW Cfm" item will be updated to so indicate.

73,

Dave, AA6YQ


Re: DXKeeper: State QSO Tracks As R Even Tho It's a C

Gerald Wilson
 

Dave,    Thank you for your very prompt response.

+ ... What letters are present in this QSO's "LoTW Cfm" item?

The LOTW panel's "cfm" item is blank.   I did notice the absence of any letters there.   I searched around in my log and notice that during this earlier time period (i.e. 2006) very few LOTW confirmed QSOs have letters in the LOTW cfm item compared to all having an entries in more recent LOTW confirmed QSOs.  The QSO in question was confirmed in early 2007.   It's a close-in state but not line of sight for 10m.  😁

Should I resubmit this particular QSO to LOTW again because of updates to the LOTW program which have been made in recent years?

73,        Jerry    K7VIT



On 10/9/2021 07:27, Dave AA6YQ wrote:
+ AA6YQ comments below

If I use DXKeeper's Realtime Award Tracking window searching for "Requested" LOTW QSLs (or cards), the WAS Award Progress window shows an "R" for the state in question.   If I click on the "R" for that state, DXKeeper log-window shows me several QSOs for the state which are requested plus one (1) QSO which is marked in the Logpage display as confirmed by LOTW.

+ "Confirmed by LoTW" does not necessarily mean "Confirmed by LoTW for WAS". What letters are present in this QSO's "LoTW Cfm" item?

       73,

                 Dave, AA6YQ







Re: Realtime tracking for DXCC Satellite

Dave AA6YQ
 

+ AA6YQ comments below
Is there realtime tracking for dxcc satellite? 
+ There's not. You're the second user to express interest.

       73,

              Dave, AA6YQ


Re: Medium Distance

Dave AA6YQ
 

+ AA6YQ comments below
A friend of mine, non ham, asked me about the medium distance of a contact. I answered it can be between a few meters and the roughly 20K Kilometres of Chatham Island from Monaco, and CQ is the most exciting side of amateur radio. But, once at home, the Curiosity pushed me, and I tried to calculate the medium distance covered with one of my QSOs.
I exported a tab-delimited log file, but distance is not there.
A manual sum is impossible, having in my log > 60K QSOs with grid square and distance.
Is there any way to solve this "problem" ?

+ As is documented here

https://www.dxlabsuite.com/dxkeeper/Help/Export.htm#Exporting%20a%20tab-delimited%20file

+ a QSO's DISTANCE item is not exported in a tab-delimited file.

+ Make a copy of your log file, and then load the QSOs table from that copy into Microsoft Excel so you can compute your desired distance statistics. Delete the copy when you are finished.

        73,

             Dave, AA6YQ

 

 


Realtime tracking for DXCC Satellite

Joe W4WT
 

Is there realtime tracking for dxcc satellite?  I see a satellite column in Progress but I don't see satellite in realtime.  Is there a config setting somewhere I might be missing?  I see it for WAS just not for DXCC.

Thanks,

Joe W4WT


Medium Distance

3a2mw Franco Lucioni
 

Hi Dave and the Group,
A friend of mine, non ham, asked me about the medium distance of a contact. I answered it can be between a few meters and the roughly 20K Kilometres of Chatham Island from Monaco, and CQ is the most exciting side of amateur radio. But, once at home, the Curiosity pushed me, and I tried to calculate the medium distance covered with one of my QSOs.
I exported a tab-delimited log file, but distance is not there.
A manual sum is impossible, having in my log > 60K QSOs with grid square and distance.
Is there any way to solve this "problem" ?
Thanks !
73
Franco 3A2MW


Re: SpotCollector

Dave AA6YQ
 

+ AA6YQ comments below
I can’t figure out why my SpotCollector is displaying PY and ZS prefix spots.  The world map shows hundreds of spots but they don’t show up on SpotCollector.

+ While depressing the CTRL key, click the X button in the Filter panel at the bottom of SpotCollector's Main window.

+ Then review

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

+ and

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

    73,

        Dave, AA6YQ

 

5221 - 5240 of 208965