开云体育

I imported my log from N1MM I used during the ARRL DX contest this weekend, however I'm a bit lost how to get those bulk contacts then uploaded into LOTW/QRZ/eQSL/Clublog from DxKeeper. Outside of the contest I use the capture window and each contact I log is immediately uploaded. I used this reference to import the log from N1MM: https://www.dxlabsuite.com/dxlabwiki/ImportN1MM I also did get some errors after importing as well. How do I fix that before uploading? "Illegal - can't find country code for callsign TO4A and TO3Z: QSO's DXCC entity is unspecified. " Thanks, Tim

On my Win 11 Computer I have running: DXKeeper SpotCollector DXView PropView WSJT-X JTAlert They all talk to each other fine. If I enter a call in WSJT-X DX Call Box, DXKeeper instantly performs a lookup of prior contacts with that station and lists them. On my Win 10 Computer I have : DXKeeper (only when Win11 copy is Closed!) JTAlert WSJT-X If, as I should, I close DXK on Win11, and bring up DXK on the WIN10, all the contacts are there. JTAlert displays the decoded wsjt-x contacts just fine. However, when I type a callsign in the DX Callbox in WSJT-X, DXKeeper does not perform a lookup of all the previous contacts. I'm stumped? What do I need to do when running the Networked copy of DXK (on Win10 machine), to act like the Win 11 does and perform a lookup of all prior contacts. It should be mentioned that the Win10 copy of DXK and WSJT-X is NOT configured for transmit. I don't even have a transmitter on the Win10 machine, just an SDR. JTAlert seems to be happy with this setup but the missing piece is WSJT-X won't force a Lookup of prior qsos with a call in DXKeeper. Ideas? 73, N0AN Hasan

I would like to "filter" Spotcollector in a way that it will give me the stationes (calls, (Band) Countiers) I need. I am very close to the magic ARRL 3000 mark and would like to "see" only (Unconfirmed) what I need. Thanks, Will K6ND

Has anyone else had my recent experience with multiple "spots" from a single callsign showing up in Spotcollector at the same time. In one instance a Polish station nearly filled the entire Spotcollector screen This just happened again with two or three callsigns showing up, filling the page. I do not think it is a Spotcollector issue per se but likely something from each of the Networks. Weird behavior, never experienced it before. de Paul NF1G

When using "QRZ.com via Pathfinder", which requires only a free QRZ account, lookups are rate-limited to one every 4 seconds. For DXers, this limit is only relevant when importing an ADIF or tab-delimited file with the "Import QSOs" tab's "Query callbook…" option enabled. The fact that Pathfinder downloads and displays QRZ's advertising does make lookups slower than using QRZ's "XML Data" service, which requires a paid subscription. You can specify a secondary callbook to use when the primary callbook is inaccessible or doesn't have an entry for the requested callsign. See https://www.dxlabsuite.com/dxkeeper/Help/Configuration.htm#Callbook%20Tab Step-by-step instructions are here: https://www.dxlabsuite.com/dxlabwiki/CallbookLookup 73, Dave, AA6YQ

QRZ prices are getting out of hand. No choice but to subscribe though. I remember it went from free to 15 to 25 and now 45+. XML is a requirement for reasonable usage of DXLABAS and I have to PRAISE Dave for this program. How he does a LOT more than QRZ and much better support is beyond my comprehension but THAKS DAVE. Outlook LT Gil W0MN Hierro Candente Batir de Repente 44.08226 N 92.51265 W EN34rb -- W0MN EN34rb 44.08226 N 92.51265 W Hierro candente, batir de repente HP Laptop

not sure why but if I type in vk9xu in to DXview it shows their grid as OH29 (heading of 334 degrees) BUT if I click on vk9xu in spotcollector it shows their grid as OC00 (heading of 185 degrees) any ideas? tnx Tim K9US

So I have received a QSL card for a QSO in my DXKeeper log. It is a paper card. On Log QSOs tab I "turn on" the QSL panel. I look down to the second line on the left and see "rcvd" ant to it's right a "down arrow" or carrot. A list of letters appears. I click on the Y letter because I have the card in my hand. Nothing. Nada. Minor disappointment. I look to the right and see "date rcvd" and a field. I start pushing in numbers for today's date. I'm sure my numlk is on. Again, nothin'. Did I manage to somehow lock the form so I can't do anything ham fisted and mess up my log? TIA Bill, NA8M

any problems with the gateway mine seems broken since last N1MM update the N1MM Logger.ini External Broadcast items seems ok 73 Stan N1ZX

Is it possible to have the contact that's been logged in DXKeeper Capture to show in the DXCommander Bandspread listings like the active DX stations from SpotCollector? Perhaps there's something in the DXCommander configuration that permits this? I'm thinking of something like what happens in N1MM+ when a station is logged - the call gets posted in light gray in the N1MM+ band map. It would be nice to see at a glance the calls worked and their frequency in one place like the DXCommander Bandspread. Maybe I'm just missing an option somewhere? 73, Ken KD2KW

Is it possible to add that? I have added a column , but when I scroll thru the dropdown, I dont see RegCode as a choice?

Greatly appreciate the recent update that automated the LoTW and Clublog syncing/updating features. Question: When you import a log, could you create a query window to pop up after the import and ask if you wish to backup the log now? Thanks for the great program.

Following a successful migration to a new Win11 machine, my only issue is that I cannot get Autoscroll to enable automatically. The appropriate tick box is enabled. I have tried rebuilding and deleting the spots database. Autoscroll does change red/blue as expected but will not disable automatically; what next should I check? Many thanks. David VK3BDX

Not too long ago I switched to the new release (2.7.0) of WSJT for FT8. For some reason now, the logged contact for WSJTis not getting relayed and captured by DXK. The contacts are logged in the WSJT log but don't get logged to DXK automatically. Contacts on other modes entered via the capture window or main log page work fine and are logged and i believe that version 2.6 had no problems with getting FT8 QSO logged automatically. My WSJT settings are UDP SERVER = 127.0.0.1 Network service port = 52000 log Automtically is checked UDP port server = 2237 Outgoing interface = Loopback_0 Multicast TTL = 1 Accept UDP requests is checked. Notify on UDP requests is checked. Accepted UDP request restores window is unchecked 2nd UDP server settings are Enable logged contact ADIF broadcast is checked server IP address = 127.0.0.1 Server port number = 12060 What do i need to do to get the WSJT logged QSO's to automatically get loaded to DXK? Is the issue in DXK config or WSJT config? Greg N9GB

When you highlight a call in SpotCollector DXView will show the progress for that country. Would it be possible for the band the DX station is on to be highlighted in DXView as well? Tom-KQ5S

I recently simplified my desktop removing NaP3 and reverting back to primarily DXL applications. I had been using the band change buttons on NaP3 versus the band change stepping function on the front of the K3s. I began using the band change buttons located on the bottom of the Commander Bandspread window. I noted an odd behavior. When using the band change buttons on Commander Bandspread, when you tune to a frequency then change bands, when you return to the original band, the radio reverts to a different frequency that where it was when it left that band. I found that annoying, as I often listen to a particular frequency on a band, change bands to see if I can hear a station spotted on RBN, only to return to the original band/frequency to continue what I was doing. I inquired of Dave about the process and was advised that Commander Bandspread will not set the band stack if there is a band change after establishing a frequency on the first band. The program was, in fact, designed to do just that. I found that an odd behavior. Why would any operator not want to return to the same frequency on any particular band when they returned to that band from someplace else. Lacking alternative, I set up band change buttons in the Commander User Defined Commands using the BN function from Elecraft Programmers Guide. They work perfectly, setting the bandstack when the defined dwell time has expired. The band change buttons consume a lot of User Defined button real estate, but work well. Don WB6BEE

Having become seriously addicted to POTA operations, I set up new LoTW station locations for each park I activate as well as new "MyQTH" locations, in order to have correct grid square and county info, primarily. I noticed this issue a couple of years ago, but didn't take the time to report it until now. If, when setting up a new "MyQTH" location, I have to exit the new QTH prior to completing the set up, I get the following error message: "Object doesn't support this property or method". When this error occurs, the only way to get out of it is to "force" DXKeeper to close via Task Manager. Also, when this happens, I find that the partially completed QTH location is indeed saved. I don't know if anyone else has run across this, but if there is any way to more "gracefully" exit a failed "MyQTH" set up attempt, it would probably be good. 73, Ken, KJ9B

I want to upload all 30K QSOs from LOTW. I go to the the Main window's QSL tab, click the Sync LotW QSOs button while depressing your keyboard's CTRL key and wait… and wait… and I go away and my screen shuts off. Then hours later I get a message that the download is aborted. Is this simply because it’s taking too long; should I prevent computer from going to sleep? I am trying to get DXKeeper to match with LOTW (where all my QSOs are). I was going to Sync QSOs first THEN QSLs, but I get the Abort each time. Takes HOURS. I also can not get DXKeeper to accept my QSL from Kure Island. Even when I type it in as if QSO is NOW and click the QSL as SENT and VERIFIED it shows up as only WORKED in DXKeeper!? Sorry for two presumably distinct problems. Paul K3STX

I’ve used DXlab for many years with zero issues. Today, when trying to upload to LOTW, I get a pop up stating “ no QSO’ whose LOTW QSL sent items are set to R and station calling items set to K6CTA”. Nothing is added to the queue. The only way to upload is to right click on the entry and select upload to LOTW:(my QTH) something has changed, but I can’t figure out what and how to fix it….any help is appreciated thanks 73, Ed K6CTA

Has anybody heard when they will be on 10m CW? Or is it wait and see? -- Bill W5EC