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

Thank you, Dave !
Franco

+ 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

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

+ 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

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

+ 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

# 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

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

+ AA6YQ comments below

Is there realtime tracking for dxcc satellite? 

+ There's not. You're the second user to express interest.

       73,

              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

 

 

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

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

+ 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

 

--
Ron Sirois

+ 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

I am puzzling over a question about a confirmation of a certain state on 10m in these days of lesser (but improving) propagation.

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.   I performed a Recompute under the DXKeeper Check Progress tab, but that did not change the results.

On the DXKeeper's Realtime Award Tracking window, if I change the WAS Award Progress Filter from "R" to "C" for confirmed, then the state in question disappears from the display because the state and corresponding QSO are not recognized as confirmed. 

I am wondering if I have made a mistake with some setting or entry to generate this problem or perhaps I have made an error on this single QSO entry.

Operating System:    Windows 10 Pro with 32 GB RAM

DXKeeper                    16.3.2

DXView                        4.7.9

Thanks for such great tools to use for our hobby, and thanks in advance for directing me toward a solution.

73,

    Jerry    K7VIT

thanks Dave...and Joe.....got it....

Rig 2 is active in commander, and wsjt is set for dxlab as the radio