Today 2024-12-31 is the last day you can log QSOs for submission to the 2024 DX Marathon. After you've logged your last QSO for this award program, follow these instructions so that SpotCollector can begin identifying active stations with whom a logged QSO will advance your progress towards the 2025 DX Marathon: https://www.dxlabsuite.com/dxlabwiki/ResetMarathonAwardTracking After you execute these instructions, you will still be able to generate a 2024 DX Marathon progress report or submission: depress the CTRL key while clicking the Progress or Submission button in the "CQ DX Marathon" panel on the Main window's "Check Progress" tab; a small window will ask you to specify the desired year, after which clicking it's OK button will generate the desired progress report or a submission respectively. The 2025 Marathon rules split the QRP class into "QRP Limited" and "QRP Unlimited" classes, and split the Formula class into "Formula 100W" and Formula Unlimited" classes: https://dxmarathon.com/rules/2025/ These changes have already been implemented in the next version of DXKeeper; if you'd like to help test this new version, send email to me via aa6yq (at) ambersoft.com 73, Dave, AA6YQ

If I work a POTA station and then QSL via LoTW I will not have his location correct. He would have ,mine if he uses LotW or QRZ but I would not have his unless I look it up and manually edit it before logging it from Capture window or other spot. I do not know what the requirements are for him to get credit. If there are a lot of them on it is a really big pain to look up the park location and enter it. I guess the LoTW QSO will work for the Entity but the grid will be incorrect. Is there an easy way to do the correct logging without using the POTA log and then have to transfer to QRZ and LotW or is it just not worth the bother to work POTA stations since he likely would not get a credit anyway? The same thing is a problem if working a Mobile in a state QSO party or other spot that requires the correct grid square. It certainly is much easier to log stations that are at the licensed location :>-) 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

Recently I lost all my setup information for WSJT-X and DXlab. I have everything back working again, but before that I worked about 30 QSOs using WSJT-X where the QSOs were not sent to DXkeeper. I have the contents of the WSJT-X ADIF file for those QSOs. Is there a way to get them into DXKeeper after the fact and have them wind up in the proper chronological order? -- 73, Pete N4ZR

When using DXKeeper and trying to obtain Marathon statistics, I now get both the above error codes. Very recently I had to move my Documents folder off from C: to D: because I was running out of disk space. I suspect that there was a file (or more) moved that cannot now be found by DXKeeper. I researched the error codes here but could not find any answers. Also, probably related, now when I clear the SpotCollector database, I get the message "unable to recreate spot database after clearing". Any help will be appreciated! Thanks. Bill KF0IQ

HNY, I have a Flex 6600, and would like to have 2 instances of WSJT-X logging QSOs to DXKeeper. Is anyone doing this? 73, Fred, AE4ED

I had earlier decided to migrate back to DXKeeper. I ran into several problems, but as of this morning most of the issues had been resolved. Right now the most irrating issue deal with upload and down load with QRZ. So matter what I do, I cannot get any qso data transfer up to QRZ, or down. When upload a record to QRZ, the response I get is "can't upload to QRZ: QSO's Station Callsign item KE5WCT dosen't match QRZ callsign specified on the QSL Configuration window's QRZ tab." I can export those qso's to an ADIF file and then upload (from QRZ site) and the file is inport ok. Once a qso is input to QRZ, I cannot 'Sync QRZ's QSL's'. The response I get back is a list of errors that reference QRZ QSO records, only two of which have anything to do with my log files. I have asked QRZ to look into this, but nothing heard so far. I have read as deeply into the DXKeeper manual but the more I read the more I don't understand (hihi). Now for more detail. I have four QRH locations assigned (as a result of moving about one every four years) This has necessitated the creation of seperate log files in my logs as well as those at eQSL (no problems there), and at QRZ. Untill this migration started, there was no issue with upload/download with HRD LogBook. And as my last attempt this morning, that was still good to go. My only problem is with the DXKeeper. I have rebuild the 'MyQTH' for QRZ and everything that I am able to see is correct. I am using the correct assigned API password assigned by QRZ (confirmed). Now I do anything else to do but to come here and seep assistance. What suggestions or study material do you have to could lead to a resoliution?? Sync QRZ QSLs2024-12-28 05:52:41 UTC "QRZ ADIF error report: Date Time Call Band Mode Submode Station Call Result QRZ Sync QSLs: QSO reported as confirmed is not present in log (LogID = 1192090140) QRZ Sync QSLs: QSO reported as confirmed is not present in log (LogID = 1194142077) QRZ Sync QSLs: QSO reported as confirmed is not present in log (LogID = 1201414635) KN4PHS QRZ Sync QSLs: QSO reported as confirmed is not present in log (LogID = 1202239445) W1MM QRZ Sync QSLs: 4 QSLs processed, 0 log entries updated, 4 errors" -- Mike Wilson USN RET KE5WCT

Is there a way to block certain FT3 skimmers so as not to see those spots? VE3EID seems to throw a lot of bogus spots......also , does the command SKIMVALID work on FT# spots? I know on cw skimmers, the SKIMVALID needs to have 2 or more skimmers validate the callsign before spotting.....yes, sometimes even bogus spots make it thru, but I'm looking to eliminate a lot of the garbage on ft# skimmers.

Hi Dave, I noted that from 15.0.1 there is now a "R" format for the ICOM "scrambled" frequency code to use in a command generating slider. I am struggeling with this as I cannot find out how the mapping between the slider setting & bounds and the frequency offset works. Is there any code example of such a RIT-slider ? -- SM0HEV/Jens

I think the Marathon rules differentiate between some countries in the DXCC list vs other lists, like Sicily, IT9 is counted separately from Italy.......yet my IT9 contacts in DXkeeper show Italy. Are those separate countries accounted for when preparing a submission?

I have spotcollector configured to show needed spots, previously, when I would work a spot and log it, that entry in spotcollector would be deleted, not sure what happened, but that no longer works.

... via the Databases tab of DXView's Configuration window. Terminate DXKeeper and SpotCollector before directing DXView to update these databases. The eQSL AG Database contains 186,829 callsigns that are Authenticity Guaranteed members of eQSL.cc. The LotW Database contains 211,447 callsigns known to participate in the ARRL's Logbook of the World (LoTW), of which 80,914 submitted QSOs to LoTW within the past 365 days; of those 80,914 callsigns, - 67,663 (84%) submitted QSOs during the last 180 days - 56,642 (70%) submitted QSOs during the last 90 days - 51,169 (63%) submitted QSOs during the last 60 days - 42,519 (53%) submitted QSOs during the last 30 days - 24,780 (31%) submitted QSOs during the last 7 days The RDA Database specifies 57,501 callsigns and the Russian Districts from which they have operated. The USAP Database contains callsigns and locations for 844,839 stations in the United States, Hawaii, Alaska, Puerto Rico, US Virgin Islands, Guam, Marianas Islands, and American Samoa; a station's location is determined from the zipcode on file for that callsign with the US Federal Communications Commission. Thanks to Tom KQ5S for the USAP database update! 73, Dave, AA6YQ

Hi, In an effort to repair an issue with SpotCollector I uninstalled DXLab, deleted the folders and eliminated references to DXLab in the registry. I reinstalled as Administrator and now Launcher shows no Program Paths for Commander, Pathfinder, PropView, SpotCollector or WinWarbler. So I cannot install or upgrade these programs. Also there are no folders for each of these programs in the DXLab folder. Each install attempt results in the same problem.

I have N6WS set up as a spot source and it is working correctly, but apparently I do not have the proper host addresses and ports for W3LPL and VE7CC. Can someone please advise? Thanks, Jim W2SM

The "1x1" button on Pathfinder (v 5.3.5) currently goes to http://www.1x1callsigns.org/index.php?option=com_jumi&fileid=4 When trying to look up a 1x1 callsign, I get an error screen from the 1x1callsigns.org site, that ultimately states "404 Component not found". When manually going to https://1x1callsigns.org/ I can successfully perform a lookup. I haven't tried to use this particular button for a while, so I don't know if this is something new, a temporary issue with the 1x1 site, or what. I searched as best I could on groups.io and couldn't find a recent solution. Happy Holidays and 73, Ken, KJ9B

Dave, some software creates its own log as you know, and of those there are programs that do that logging in ADIF format. Can DXKeeper be configured to automatically scavenge a log like that to automate the inclusion into DXKeeper? As an example, WSJTX creates an ADIF by default. If I had WSJTX running, and DXKeeper running, could automatically update itself, on a QSO by QSO basis, rather than going through a batch update? It streamlines things. 73 Doug W5GA

Running thru some options in my head.....right now I have two spot sources, and for the most part, they serve my needs.......however, I may want to try a third source, strictly using ft8 skimmer spots......is that possible? I get some ft8 spots from the 2 I use, but I think I may be missing some stuff.....

The current version of SpotCollector can be configured to recognize POTA references in spot notes, and places them in a POTA field in each Spot Database Entry. An SQL expression can thus be used to filter the Spot Database Display to contain only entries for stations in specified Parks, and/or trigger audio/email announcements. If you configure a user-defined field in DXKeeper whose Caption is set to POTA, then DXKeeper can be directed to generate a POTA progress report. The above functionality is described here: https://www.dxlabsuite.com/dxlabwiki/UserAwardProgressreports Today's discussion here led me to discover that browsing to https://pota.app/#/park/XX-NNNN will display POTA information about the park whose POTA reference is XX-NNNN - including a grid square. For example https://pota.app/#/park/US-0321 displays POTA information about the Great Meadows National Wildlife Refuge. This could be exploited by adding a "Display POTA info" command in the SpotCollector's right-mouse menu when the selected Spot Database Entry contains a POTA reference; when executed, this command would direct the specified web browser to display the park's POTA information page. Would this be useful? While it's technically possible to scrape the POTA information page's HTML to extract the grid square and use that to update the Spot Database Entry's "DX Grid" field, this approach is fragile in the face of changes to the POTA information page's format, which I suspect will be frequent given the relative youth of this award program. 73, Dave, AA6YQ

+ AA6YQ comments below You have tried to help with this problem for me before. We were not able to solve it. I was just hoping something had changed or maybe you have had some new experiences that could solve my issue. I've attached the SpotCollector ErrorLog.txe per your instructions. + Yes, I remember now. When we pursued this back in August, we narrowed it down to problematic behavior unique to your system. No one had previously reported this behavior, and no one has reported it since: + Here's the way the interaction between SpotCollector and PropView should proceed: 1. SpotCollector directs PropView to generate a propagation forecast for a particular callsign on a specified band and mode 2. PropView creates a script for VOACAP that will generate that forecast 3. PropView deletes the existing spsnr.txt file 4. PropView directs Windows to execute a batch file that invokes VOACAP with the generated script; the batch file directs PropView to place its results in spsnr.txt 5. PropView checks every 100 ms for spsnr.txt to appear 6. After spsnr.txt appears, PropView waits for VOACAP to terminate 7. After VOACAP terminates, PropView processes the data in spsnr.txt and returns the results to SpotCollector On your system, step 6 never completes: Windows continues to report that VOACAP is running, as shown in this excerpt from your PropView errorlog.txt file: 2024-08-17 14:19:22.198 > IONCAPModule.RunScript: SNR = 1, BatFilename = C:\DXLab\PropView\itshfbc2\run\spsnr.bat, ScriptFilename = C:\DXLab\PropView\ITSHFBC2\run\sspscript.txt 2024-08-17 14:19:22.211 > SP PID = 7892 2024-08-17 14:19:22.218 > IonCapModule.PredictSNR, script executed 2024-08-17 14:19:22.318 > IONCAPModule.HandleSNRTimer, SNRPredictionName = SP, SNRState = 1, SNRCount = 0, IgnorePIDStatus = False 2024-08-17 14:19:22.323 > C:\DXLab\PropView\ITSHFBC2\run\spsnr.txt does not exist 2024-08-17 14:19:22.426 > IONCAPModule.HandleSNRTimer, SNRPredictionName = SP, SNRState = 1, SNRCount = 1, IgnorePIDStatus = False 2024-08-17 14:19:22.432 > PID 7892 is still running 2024-08-17 14:19:22.537 > IONCAPModule.HandleSNRTimer, SNRPredictionName = SP, SNRState = 1, SNRCount = 2, IgnorePIDStatus = False 2024-08-17 14:19:22.543 > PID 7892 is still running 2024-08-17 14:19:22.648 > IONCAPModule.HandleSNRTimer, SNRPredictionName = SP, SNRState = 1, SNRCount = 3, IgnorePIDStatus = False 2024-08-17 14:19:22.654 > PID 7892 is still running 2024-08-17 14:19:22.755 > IONCAPModule.HandleSNRTimer, SNRPredictionName = SP, SNRState = 1, SNRCount = 4, IgnorePIDStatus = False 2024-08-17 14:19:22.761 > PID 7892 is still running 2024-08-17 14:19:22.867 > IONCAPModule.HandleSNRTimer, SNRPredictionName = SP, SNRState = 1, SNRCount = 5, IgnorePIDStatus = False 2024-08-17 14:19:22.873 > PID 7892 is still running 2024-08-17 14:19:22.976 > IONCAPModule.HandleSNRTimer, SNRPredictionName = SP, SNRState = 1, SNRCount = 6, IgnorePIDStatus = False 2024-08-17 14:19:22.982 > PID 7892 is still running 2024-08-17 14:19:23.086 > IONCAPModule.HandleSNRTimer, SNRPredictionName = SP, SNRState = 1, SNRCount = 7, IgnorePIDStatus = False 2024-08-17 14:19:23.091 > PID 7892 is still running + PropView uses Windows' OpenProcess function in the kernel32 library to determine if VOACAP is running. + Why VOACAP behaves this was on your system alone is beyond my ability to diagnose; I didn't develop it, and I don't have the ability to insert diagnostics as I have in each DXLab application. + Checking our email thread from back then, I don't see that we tried rebooting Windows into "Safe Mode with Networking" and then starting SpotCollector and PropView (and nothing else) to see if they interact correctly. Rebooting Windows into "Safe Mode with Networking" prevents Windows from starting any other applications - including your anti-malware. It's a Hail Mary to be sure, but... 73, Dave, AA6YQ

When I attempt to upload a spot to SC of T32TTT, it never shows up. I'm getting spots for 60m to show up in the Spot list, but spots originated by me are not showing up, whether I choose Cluster or Local. All other bands accept my spots. I have no pre-filter checked. What could be the cause? 73, N0AN Hasan

After several years of using DxKeeper, DxView and Commander, mostly without spotting, but, when I did do spotting I went online to DXSummit and setup the command for spots emanating from north America. However, over the last few days, in the morning, I read (some) of the SpotCollector documentation and Commander bandspread information. Then, this morning, I did sort out how to change the font size in the bandspread for spots. That had been a slight holdup since the default install was invisible. But, I changed the fonts for all bands to 10 and, on my old screen, it is perfect now. I set spot collector to only collect spots only from one source, k1rfi in the config. Then, I started it and watched the bandspread in commander. Amazing!!. Now, in Commander's bandspread, I see a spot and I can click it in Commander's Bandspread and my old FT-1000MP goes right to the frequency immediately. Having modulated the old MP manually, except in contests with N1MM, I feel like I have a whole new rig setup! If the spots are too dense they automatically reform the bandspread to make them more visible. That is software that thinks!! So, I am writing to say THANK YOU to Dave and whomever else may have participated in design and implementation. Spot collector with the Commander Bandspread is just truly amazing. I wish everyone the best of the New Year. -- Mike KM2B