Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
- DXLab
- Messages
Search
Re: QRZ subscription value?
Dave, following your instructions got my DXK running properly again.? ?But when I logged some new QSOs and attempted upload to LoTW a similar problem came up:
?
In DXK QSL tab...
<Add Requested> <Enable All>
LoTW operations panel...
<Upload to LoTW>
all the QSO's enabled are immediately disabled and this error message plays for each:
?
Disabled QSL Queue entry for 6Y7EI on 2025-03-14 at 21:02:17 - station location "Williston, Florida" specified in QSO's QTHID item "williston" doesn't match station location "Williston" selected on the QSL Configuration window's LotW tab
?
Seems like somewhere there is a QTHID "williston," with station location "Williston, Florida" that is accessed when trying to upload to LoTW.
?
Can you help once again?? I really appreciate your patience...
?
Bruce - W4NDX |
Re: Invalid administrative subdivision errors
Thanks, Dave.? Old logs gone, KG6JOT and AE6JW logs imported no errors.? Next to import the big pile for NU6T.?? Rich, NU6T On Fri, Mar 14, 2025 at 3:17?PM Dave AA6YQ via <aa6yq=[email protected]> wrote:
--
Richard Hill |
Re: Invalid administrative subdivision errors
# More AA6YQ comments below
+ I believe that my instructions were to depress the CTRL key while clicking the Delete button above the Log Page Display> + My previous instructions were incorrect: I did say CTRL-CBA. No harm done. Do the CTRL-Delete to remove all QSOs from the current log. ? ? ? 73, ? ? ? ? ? ?Dave, AA6YQ |
Re: Invalid administrative subdivision errors
+ AA6YQ comments below
depress the CTRL button while clicking the CBA button above the Log Page Display+ The CBA button performs a callbook lookup. + I believe that my instructions were to depress the CTRL key while clicking the Delete button above the Log Page Display> ? ? ?73, ? ? ? ? ? Dave, AA6YQ |
Re: Invalid administrative subdivision errors
I'm losing track in the long series.? I've cut and pasted here.? My comments after the "*". This is where I think I am in the process: _____________ + AA6YQ comments below Repeated steps, Clicked on the "X" to the right of the Filter:None box, Pressed?Control and clicked on the CBA button at the same time.? I got a DXKeeper QRZ Subscriber login text box with the message, " no QRZ callsign specified."? Click OK results in a DXKeeper text box that says, "Callbook error when looking up VU2ELJ: Program Error."+ In the "Primary Callbook" panel at the top of the Configuration window's Callbook tab, select the "None" option in the upper-left corner".? ? *? Done _________________ + OK, then direct DXKeeper to delete all the QSOs in your current log: on the Main window's Log QSOs tab, 1. at the bottom of the tab, click the Filter panel's X button so that all QSOs are present the Log Page Display 2. depress the CTRL button while clicking the CBA button above the Log Page Display I still see log entries in the log window at the bottom of the "Log QSOs" tab.? I think they should be gone after this operation.? Two log entries are highlighted in pink.? The callsign for one of the highlighted calls is displayed in the top " panel on this QSO:" "Log QSOs" tab. I thought the above set of actions would empty my logbook. Rich, NU6T
Richard Hill |
Re: spot with notes from WinWarbler?
+ AA6YQ comments below
+ Reviewing the Reference Documentation of each DXLab application you've been using may reveal useful functionality that you didn't investigate during your initial scan. ? ? ? ? 73, ? ? ? ? ? ? ?Dave, AA6YQ |
Re: spot with notes from WinWarbler?
+ AA6YQ comments below
+ That's described in the 3rd paragraph of the "Generating DX Spots" sub-section of Logging section of WinWarbler's Reference Documentation:? ? ? ?73, ? ? ? ? ? ? ?Dave, AA6YQ |
spot with notes from WinWarbler?
Can I spot with notes from WinWarbler?
say working a POTA station... I log him from WW then go to dxkeeper
right click on his call to get the spot with notes to come up and?
inform that he is pota.? I did not find in on a quick search.
I did expand the layout on WW and did find I have a POTA window
Tx for the software... before the suite...and learn something new
all the time. Powerful!? Tnx dave.
Murf
n7uvh
? |
Re: QRZ subscription value?
On 2025-03-13 9:03 PM, Ron DeBlock wrote:
- import from LoTW. LoTW confirmations are imported and count towardThat does appear to be a better way to simplify getting QSOs into QRZ log for non-subscribers. One can create a logbook for a previous callsign. I did so for myI tried it and at least for callsigns that have been reassigned one needs to "prove" ownership for the time period in question. That will be a real problem for my original Extra Class call from 1978- 1995 ... I doubt that I have copies of that license and it was prior to the records in the current FCC ULS (although they could verify a claim if the bothered to *gasp* look in a printed Callbook from that era). 73, ... Joe, W4TV On 2025-03-13 9:03 PM, Ron DeBlock wrote: One can submit? QSOs to QRZ for free via multiple methods, I have used them all: |
Re: Connecting Grid Tracker to DXkeeper for automatic logging
There is one interoperation... GT will send QSO to DXKeeper setup is under?config/logging I do not use GT under Windows. I prefer JT Albert. I have used it under Linux, no JT Alert linux available. Thanks Dan KC2STA On Thu, Mar 13, 2025 at 8:53?PM Joe Subich, W4TV via <lists=[email protected]> wrote:
--
Dan Ziolkowski KC2STA SKCC #4290T Ubuntu LINUX |
Re: Recovering from crash - DXKeeper QSOs upload to LoTW error
+ AA6YQ comments below
When uploading QSOs to LoTW, previously logged QSOs recovered to DXKeeper from OneDrive log backup are uploading to LoTW without any errors. However, New QSOs, logged since the recovery are being disabled thus: "Disabled QSL Queue entry for 9K2GR on 2025-03-13 at 23:22:08 - station location "Williston, Florida" specified in QSO's QTHID item "w4ndx" doesn't match station location "W4NDX" selected on the QSL Configuration window's LotW tab" I have chased this around until I am dizzy. How do I resolve this? + Your 9K2GR QSO specifies a "myQTH ID" of "W4NDX". + On the Main window's "my QTHs" tab, the "my QTH" whose "myQTH ID" is "W4NDX" specifies and LoTW "Station Location" of Williston, Florida". That's confusing! + However, in the TQSL panel at the bottom of the "QSL Configuration" window's LoTW tab, you have the "station location" selector set to "W4NDX" -- which is not the same as the "Williston, Florida" specified in the LoTW selector in your "W4NDX" myQTH. + You evidently have one "LoTW Station Location" named W4NDX and another named "Williston, Florida". That's confusing! + The confusion stems from your defining a "myQTH" whose "ID" is "WN4DX" and that species an LoTW Station Location of "Williston, Florida". + A callsign is a poor choice for a "myQTH ID" because it doesn't imply a geographic location. A callsign is also a poor choice for an "LoTW Station Location" - for the same reason. Both should specify a geographic location, like a village, city, or town name. + If all QSOs you make from Williston Florida are not made from the same location in that city, then I'll need to understand all of the locations from which you make QSOs before suggesting a course of action. + If all QSOs you make from Williston Florida are made from the same location in that city, then I suggest that you change the ID of your Williston Florida myQTH to "Williston", and change the name of your WN4DX LoTW "Station Location" to "Williston". + If you understand this and agree, then 1. backup your log (so you have a quick recovery path if you don't like the outcome) 2. in TQSL, change the name of your W4NDX "Station Location" to Williston 3. in DXKeeper, 3a. in the TQSL panel at the bottom of DXKeeper's "QSL Configuration" window's LoTW tab, click the Update button, and then select Williston in the "Station Location" selector 3b. on the Main window's "Log QSOs" tab, filter the Log Page Display to contain all of your QSOs whose "myQTH ID" is WN4DX ; double check this, as you'll be changing the "myQTH ID" of all of the QSOs in the "Log Page Display" to Williston 3c. on the Main window's "my QTHs" tab, 3c1. select the Entry whose myQTHID is WN4DX 3c2. change this Entry's ID to Williston 3c3. change this Entry's LoTW selector to Williston 3c4. click the Save button 3c5. make sure the Williston row in the table of myQTHs is selected 3c6. in the "Update QSOs in Log Page Display" panel, click the "Set myQTH ID" button; this will change the "my QTH ID" item of every QSO in the Log Page Display to "Williston" + Now all QSOs that you log with a "myQTH ID" of Williston will be uploaded to LoTW using your Williston "Station Location". 73, Dave, AA6YQ |
Recovering from crash - DXKeeper QSOs upload to LoTW error
¿ªÔÆÌåÓý
When uploading QSOs to LoTW,? previously logged QSOs recovered to DXKeeper from OneDrive log backup are uploading to LoTW without any errors.
However, New QSOs, logged since the recovery are being disabled thus:
"Disabled QSL Queue entry for 9K2GR on 2025-03-13 at 23:22:08 - station location "Williston, Florida" specified in QSO's QTHID item "w4ndx" doesn't match station location "W4NDX" selected on the QSL Configuration window's LotW tab"
I have chased this around until I am dizzy.? How do I resolve this???
Bruce, W4NDX.
-- Bruce - W4NDX |
How about W10?
Running W10 22H2 ... I have not seen anything here and know that this
IS NOT A WINDOWS SUPPORT LIST but, for better or worse, Windows is the dongle that makes the DXLab suite work (N1MM+ Logger, too, and if it wasn't for these two software packages ...) I've seen the traffic about W11's crapulence of late but don't remember seeing anything about W10 ... Oh, and I have no plans to take the forced upgrade to W11 come fall ... -- Peter Laws | VE[23]UWY / N5UWY | plaws0 gmail com | Travel by Train! |
Re: Connecting Grid Tracker to DXkeeper for automatic logging
+ AA6YQ comments below?
DXKeeper does not interoperate with Grid tracker.+ DXKeeper's interoperation with DXView and the latter's interoperation with DX Atlas and Google Earth provide more functionality than does Grid Tracker. For example, see + and + and https://www.dxlabsuite.com/dxview/ActiveStations10mGoogleEarth.jpg ? ? ? ?73, ? ? ? ? ? ? Dave, AA6YQ |
Re: QRZ subscription value?
One can submit? QSOs to QRZ for free via multiple methods, I have used them all:
toggle quoted message
Show quoted text
- manual entry at QRZ.com - import ADIF files - import from LoTW.? LoTW confirmations are imported and count toward QRZ awards. One can create a logbook for a previous callsign.? I did so for my prior call.? That one has not been reassigned, I'm not sure how it would work if it were reassigned. QRZ awards are all free. My normal practice is to upload my logs from DXKeeper to LoTW? then import to QRZ from LoTW. I do have a QRZ subscription because I find value in the site and want to support it.? However I have not configured DXKeeper to upload and sync with QRZ because...well, laziness :-)? I'll get around to it someday. 73, -Ron KR2D On 3/13/2025 8:50 PM, Joe Subich, W4TV wrote:
|
Re: Connecting Grid Tracker to DXkeeper for automatic logging
DXKeeper does not interoperate with Grid tracker.
toggle quoted message
Show quoted text
DXKeeper already offers two other interfaces for interoperating with WSJTX - direct (using SpotCollector) or with JT Alert. See: <> for more information. 73, ... Joe, W4TV On 2025-03-13 8:32 PM, Crispo, Alexander W via groups.io wrote:
I need some help in configuring Grid tracker to save my FT8 contacts to DXkeeper. |
Re: QRZ subscription value?
On 2025-03-13 8:29 PM, Dave AA6YQ wrote:
It appears that one can export an ADIF file of QSOs and manually import that file to QRZ log. One can not use the API interface supported by DXKeeper unless one is a QRZ.com subscriber and one can not download confirmations - even an ADIF file - unless one is a subscriber. I have not attempted to determine if one can set up a logbook for a previous callsign (particularly if the call has been reassigned) as it would be pointless. 73, ... Joe, W4TV On 2025-03-13 8:29 PM, Dave AA6YQ wrote: One thing that the ARRL got right is that anyone can submit confirmations to LoTW at no charge, whether they are an ARRL member or not. |
to navigate to use esc to dismiss