开云体育

If you are using DXKeeper and haven't upgraded it to version 18.1.4 (or later), please do so and then direct DXKeeper to "Recompute" before upgrading to SpotCollector 9.9.2. After upgrading SpotCollector 9.9.2 and starting it the first time, direct it to "Recompute".. This release - correctly logs a QSO from WSJT-X via direct interoperation submitted while Spot Database compaction is underway (tnx to Chuck KM3V) - prevents autoscroll from being inadvertently disabled - ensure thats the IRC Spot Source indicator is set to "red" when its disconnected (tnx to Jamie WW3S) - enlarges the space available to display error messages in the Network Service panel on the Configuration window's General tab (tnx to Salvatore I4FYV) - correctly sets the "Marathon Zone Need" field in Spot Database Entries that don't specify a CQ Zone (tnx to Joe W4TV) - disables the "QSY no mode change" right-mouse menu command when Commander isn't running and connected (tnx to Salvatore I4FYV) - makes the four VCR-style buttons above the vertical scrollbar behave as documented in https://www.dxlabsuite.com/spotcollector/Help/SpotDatabase.htm#Navigating%20the%20Spot%20Database (tnx to Salvatore I4FYV) - provides a "Discard spots of invalid callsigns" option on the Pre-filtering window that when enabled ignores spots whose base callsigns violate the ITU rules governing formation of callsigns: (tnx to Bj?rn SM7IUN and Joe W4TV) --- contains a / or ? --- contains more than one transition from letters to numbers --- begins with a digit that is followed by more than two letters --- contains more than two groups of digits separated by letters --- ends with a digit --- begins with more than 2 letters followed by a digit, and the first 2 letters aren't SS --- begins with a digit followed by 2 letters and a digit, and the first two characters aren't 3D - exploits DXKeeper 18.0.4's new Check command to display the progress of an activated K1JT callsign and the progress of a new "DX Call" in WSJT-X - adds a "QSY (no mode change) command to the Spot Database Display's right-mouse menu (tnx to Joe W4TV) - adds SFH, S/FH, and SF/H to the set of words encountered in spot notes that cause a generated Spot Database Entry's mode to be set to FT8 (tnx to Dale AA1QD) - allows <> in cluster source window macros (tnx to Jim KR9U) --- provides Realtime Award Tracking for the IOTA HF and VHF categories (tnx to Steve K4WA) --- adds an IotaMixedEn field to each Spot Database Entry, indicating whether pursuit of "IOTA Mixed" is enabled --- adds an IotaCatProg field to each Spot Database Entry, indicating the progress towards the entry's IOTA category (HF or VHF) --- adds an IotaCatEn field to each Spot Database Entry, indicating whether pursuit of the entry'sIOTA category (HF of VHF) is enabled --- adds an IotaCatWB4t field to each Spot Database Entry, indicating whether the entry's callsign has been previously worked in the the entry'sI OTA category (HF or VHF) - Increases the rate at which incoming spots are processed - updates the ConfigurationGeneral.htm, Prefiltering.htm and SpotDatabase.htm documentation files Notes: 1. Update your firewall and anti-malware applications to consider the new versions of SpotCollector.exe to be "safe" a. 0/13 Jotti scanners detected malware in SpotCollector.exe or SC_WSJTX.exe b. 0/72 VirusTotal scanners detected malware in SpotCollector.exe; 0/73 VirusTotal scanners detected malware in SC_WSJTX.exe 2. If this upgrade doesn't work correctly, see the "After an Upgrade" section of http://www.dxlabsuite.com/dxlabwiki/ApplicationStoppedWorking 3. After upgrading, to revert to the previous version of SpotCollector, see http://www.dxlabsuite.com/dxlabwiki/RevertApplicationVersion SpotCollector 9.9.2 is available via the DXLab Launcher, and via http://www.dxlabsuite.com/download.htm 73, Dave, AA6YQ

DXKeeper 18.1.4 automatically adds new several new fields to the current log's IOTA progress table in support of the new IOTA HF and VHF award categories, but makes no changes to the database table that contains your QSOs. Thus it does not offer to backup your log. Upgrade DXKeeper to version 18.1.4 before you upgrade SpotCollector to version 9.9.2. If you have the "Realtime Award Progress" box checked in the IOTA panel on the Configuration window's Awards tab, then like its predecessors this version will direct DXLab to pursue "IOTA Mixed". Since IOTA no longer offers this award, you may wish to uncheck the Mixed box in the IOTA panel on the Configuration window's Awards tab and check the HF and/or VHF boxes in that panel. Then click the Recompute button at the bottom of the Configuration window's Awards tab. Specifically, this version - prevents an errorlog.txt entry in DXCCCreditUI.DXCCCreditGrid_FetchCellTips when DXCC Credits have never been downloaded (tnx to Don AD0K) - corrects explanatory popup explanations associated with Region items (tnx to Eddy ON5JK) - provides the "Sync All" buttons with explanatory popups - prevents "the Sync All" command from generating "Bad file name or number" errorlog entries (tnx to Salvatore I4FYV) - prevents a superfluous SyncAll button from appearing in the lower-right corner of the Main window's "Check Progress" tab (tnx to John N4QWF) - when updating a logged QSO to reflect LoTW confirmation results in a change in the logged QSO's DXCC entity or CQ zone due to the resolution of a discrepancy between the information in the logged QSO and the information reported by LoTW, this version correctly updates Realtime Award Tracking for Marathon if it is enabled (tnx to Joe W4TV) - prevents a "program error 52 in module ADIF.GenerateResultsHeader" errorlog entry when LoTW reports a QSO not present in the current log (tnx to Joe W4TV) - starts "Sync eQSL QSLs" by checking eQSL.cc accessibility in a user-abortable manner (tnx to Joe W4TV) - recognizes the new "Rejected" response when uploading a QSO to Club Log (tnx to Joe W4TV) - enables the display of multiline messages from QSLing services (tnx to Ian VK6DW) - if the Sync Club Log QSLs, Sync LoTW QSOs, Sync LoTW QSLs, or Sync QRZL QSLs functions are invoked with a blank date beneath them, prompts the user to specify a valid date (tnx to Joe WQ6Q) - adds a "QSL to Windows Clipboard" command to the Log Page Display's right-mouse menu - corrects a defect in the calculation of the "Mixed Score by Band" and "Mixed Score by Mode" sections of the DX Marathon progress report (tnx to Carlo IK2RPE) - prevents "Subscript out of range errors" in MarathonModule.GenerateMarathonProgressReport and recovers from program errors in that procedure (tnx to Joe W4TV) - renames the 'Marathon Year, Category, and Score Sheet Information' window to 'Marathon Year and Submission Information', and renames the button in the Marathon Bands & Modes panel (Configuration window, Awards tab) that displays it to 'Year and Submission Info' - prevents an "Object doesn't support this property or method" error when switching Main window tabs after defining a new myQTH but not yet saving it (tnx to Ken KJ9B) - on the Main window's "my QTHs" tab, updates the "Set myQTH ID" button's explanatory popup to include the myQTH ID to which the myQTH ID items of all QSOs in the Log Page Display will be set - adds HF and VHF checkboxes to the IOTA panel on the Configuration window's Awards tab that govern the IOTA progress report (tnx to Steve K4WA) - removes the IOTAMEM checkbox from the IOTA panel on the Configuration window's Awards tab, as IOTA no longer support IOTAMEM (tnx to Valeria IK1ADH) - provides realtime award tracking for the IOTA HF and VHF award categories (tnx to Steve K4WA) - after re-initializing the IOTA realtime progress table, directs the user to initiate a recompute operation in DXKeeper followed by a recompute operation in SpotCollector (tnx to Dave W6DE) - provides a "Status Key" on the right side of the Realtime Award Tracking window's IOTA tab that explains t

I am about to post release notes for DXKeeper 18.1.4 and SpotCollector 9.9.2. The primary driver for these two releases is the introduction of Realtime Award Tracking for the new IOTA HF and VHF Award Categories. Since this took several months, quite a few unrelated defects were corrected, and several unrelated enhancements were included. Please upgrade DXKeeper 18.1.4 first; if you're pursuing IOTA awards, adjust your award objectives in the IOTA panel on the Configuration window's Awards tab, and then click the Recompute button at the bottom of that tab. The release notes for these new versions understate the contributions of the several DXLab users who helped bring these new versions to fruition. They tested many unreleased versions of each application, reporting defects that you will not encounter and making suggestions that simplify the upgrade process. The responsibility for any remaining defects is mine alone. 73, Dave, AA6YQ

Eric KE5DTO of FlexRadio informs me that the new Aurora series transceivers announced at Dayton are software-compatible with the 6000 and 8000 series Signature models. Thus setting Commander's "Radio Model" selector to FLEXSIG should enable use of these new transceivers with DXLab. 73, Dave, AA6YQ

When I use Pathfinder to lookup a callsign I get the Pathfinder not logged into QRZ. But I have verified that I am logged in. I can click on the Pathfinder icon in the Tray and it opens and when I click on QRZ it looks up the callsign. My password and Automatic look up filled in and checked. Any recommendations? 73, George W2GS

I have tested the S50CLX POTA/SOTA cluster describe below with SpotCollector, and confirmed that POTA tags are correctly captured. There were no SOTA tags spotted during my test. 73, Dave, AA6YQ Maybe it would be interesting for users of your programme to improve the reception of telnet DXCluster spots for interested group of users of POTA and SOTA programme. On the S50CLX DXCluster I have implemented the integration of spots that are not part of the classical telnet DXCluster network. More in my note below. The user of your programme would thus have the possibility to select in the programme the reception of specific spots via a button, with predefined commands to be sent to the S50CLX DXCluster after a successful connection. Sorting, searching by reference ... etc is a matter of implementing such spots into DXLab software. The idea for the buttons are: 1. POTA ONLY spots -> command executed: ACC/SPOTS INFO -POTA- 2. SOTA ONLY spots -> command executed: ACC/SPOTS INFO -SOTA- 3. BOTH POTA&SOTA spots -> command executed: ACC/SPOTS INFO -POTA- OR INFO -SOTA- 4. S50CLX CLUSTER DEFAULT (all spots) -> command executed: CLEAR/SPOTS ALL A connection via telnet protocol to S50CLX s50clx.infrax.si:41112 which is a completely free service is required to receive such tagged POTA/SOTA spots. Good luck, 73s Dan S50U ** POTA and SOTA enthusiasts! POTA (Parks On The Air) and SOTA (Summits On The Air) are internationally renowned programmes. They encourage licensed radio amateurs to operate outdoors in nature parks or on mountain peaks. Operators making contacts in parks or on summits are called activators, and the other operators who contact them are hunters. On the S50CLX telnet DXCluster I implemented the collection of spots from POTA and SOTA that are not part of the classical telnet DXCluster network (potaapp and sotawatch). Such spots are tagged with [-POTA-] and [-SOTA-] respectively. In the comment field a spot tagged as such carries: POTA: - International POTA reference number, example: SI-0831 - Mode of operation, example: CW - POTA reference name, example: Preval Vrh Ravni SOTA: - International SOTA peak reference number; example: S5/CP-002 - Mode of operation; example: SSB - SOTA summit name, altitude, points; example: Porezen, 1630m, 8 points With the right settings, the exact DX spots you want can be received and this is achieved using the filters below. To change an existing filter, simply overwrite it with a new command. Each command (BOLD formatted text) must be entered on a new line, confirm the entry by pressing ENTER. - for receiving only POTA spots, command: ACC/SPOTS INFO -POTA- - for receive only SOTA spots, command: ACC/SPOTS INFO -SOTA- - for receiving POTA and SOTA spots, command: ACC/SPOTS INFO -POTA- OR INFO -SOTA- The CLEAR/SPOTS ALL command removes all set filters and the S50CLX passes us all SOTA, POTA, DXCluster and optionally RBN (SET/SKIMMER <mode>) spots. In cases where you do not want to receive POTA and SOTA spots e.g. in a contests, use the command as the first filter before all others REJ/SPOTS 1 INFO -POTA- OR INFO -SOTA- Spot forwarding is based on the DXSpider DXCluster software validation and normalisation algorithm, rejecting duplicates spots and ensuring quality spots in the face of increasingly frequent malicious attacks on global amateur radio DXCluster network. The S50CLX DXCluster can be reached via telnet at: s50clx.infrax.si port 41112 My small contribution to the promotion of outdoor activities in POTA and SOTA hamradio programmes. :-) Spread the news, thanks 73 Danilo S50U sys S50CLX DXCluster p.s. The information is also published on the Radioklub Cerkno S50E website https://s50e.si/pota-sota-dxcluster/ -- S50CLX DX Cluster <https://s50clx.infrax.si>

I would like to see some macro buttons added to the right side of the spectrum/waterfall window similar to the way you have the fequencies on the left side. I have several K4 macros I use to set the waterfall display depending on the mode I'm working. For example,on FT8, I have a macro to move the FT8 frequency to the left side of the waterfall and set the span to 30khz. This way I can see the main frequency, say 28074, and the frequencies that the DXpedition stations usually use. I also have macros for CW and SSB. While not directly related to DXkeeper, but to panadapters in general, I have macros that will turn dual on (VFO A and VFO B) panadapters. I have a macro that will toggle the K4 external monitor from mirroring the radio display to only displaying the panadapter. I have other macros that are related to the panadatper. It would be nice to be able to put any macros that are panadapter related on the spectrum/watgerall display. It would be an easy way to access them. I am aware of the macro buttons on Commander but I have the panadpter on a different monitor. Having macro buttons on the panadapter would be more convenient. Just a thought. -- Tom-KQ5S

Greetings to all! The number of Spot Database Entries as shown in configuration spot database tab, does it count unique callsigns of spots or not? Is there a way to prune DB by keeping a specific amount of unique callsigns? TKS! 73 de SV1CDN, Dennis!

This is the setup I am trying to use now. All software is current. dxl is using flexsig and slicemaster is using whatever it uses to connect to ssdr. Seems to set WSJTX to HRD for the rig on port 7832. it all seems to be working ok after some trial and error with manuals. but if i click a call in wsjtx the call info does not populate dxk or its capture window. so i dont get any info until the qso is over when wsjtx does send the entry to dxk. Also when the wsjtx spots go to spot collector, If i click on one it changes slice A to the spot freq even though i was on slice B. So it causes an interlock issue trying to TX on the same freq for both slices. Thanks!!! -- 73, Greg - AB7R Flex 8600 PGXL & TGXL AG

Hi, I am trying to print QSL labels on TOWER W100 labels on A4 sheets that are nominally 297 X 210 mm. The labels are 37 X 70 mm in 3 columns and 8 rows. The column offsets should be 0, 70, 140 as the label width is 70 with no gaps between. My printer is a Canon TS3400 and it imposes a left margin of 3.387 mm and a top margin of 2.963 mm. DXKeeper consequently reduces the printable area to 288.961 X 203.2 mm and determines the allowed column offset limits based on the reduced area and will not print if the offset exceeds the limit e.g. for column 3 the limit is 133 and it should be 140. If I select "Ignore printer imposed margins", it sets them to 0, but it retains the reduced printable area and offset limits determined before. Is there a workaround or remedy for this? Thank you. Jan, ZS1IS

Just built a new Win11 box and installed a fresh copy of DXLab. Successfully imported my QSO database from DXLab on the old Win10 box. Fresh app talks to the rig and logs QSOs FB. I have populated the Special Callsigns database in SpotCollector with previously used Club member info. I can see that SpecialCallsigns.mdb has been created in SpotCollector's Database folder. I have done a full shutdown and restart of the app. But in DXView | Config | General | Options panel, the 'Query Special Callsign database' option remains 'greyed out'. So I guess there is a step I am missing? 73 Dave

Hi Group, I finally bit the bullet and my new Flex 8400 should be here tomorrow. Is the documentation in TransceiverControlFlexradio - DX Lab Suite Wiki up-to-date for this radio? It is going to be a big change from my Kenwood TS-570 and trying to get ready to get on the air with DXLab. Thanks! Norman KC9NVN

...by setting the Model selector to "Xcvr Ctrl App" on the "External Modem" tab of WinWarbler's Configuration window? When so configured, WinWarbler transmits RTTY by directing Commander to send the outgoing characters to the K4 via an appropriate CAT command, and displays RTTY characters decoded by the K4 and received by way of Commander. This scheme is supported with the K3 and worked with the K4 demonstrator that Elecraft loaned me, but it appears that new CAT commands may now be required. 73, Dave, AA6YQ

Sorry to add another non-specific "Spots don't display" question. But spots stopped displaying. Windows 11, Nvidia RTX3060i with Studio Driver 576.02, Spot Collector 9.8.3 Only spot source is N6WS and I see spots rolling in on the status window. If it's a clue, when I compact the spots database I see spots flash on the spot collector window briefly and then go away.

Can't seem to get it to single space. Don't know what I did, but no success.

Listing or Printing Needed Grids. Is there a way to generate needed grids? The progress report show worked grids. It would be nice to have a sheet of needed grids printed out. Mike W0MU

Last November I had a catastrophic system crash that required me to do a full rebuild with new hardware. I cloned the old drive and got the OS running, no data was lost, and DX Lab Suite reinstalled painlessly. But somehow, something corrupted JT Alert. I've tried purging every last vestige of it from my system, reinstalling about a dozen different versions but no matter what I do, it will not operate in any kind of stable fashion. It will delay QSO logging by 45-90 seconds, not allow me to interact with it during that time and in general make logging or even operating the WSJT software itself impossible. I had been using JT Alert 2.16.6 for a few years and until the crash it had been perfect, and quite frankly I preferred it to the newer versions, but I'll take anything at this point. As a result I had no choice but to delete it and I'm no longer able to log directly into DX Keeper, having to regularly import an ADIF from WSJT's log file. This is getting very old very fast. Are there any alternatives to JTAlert that will allow me to run the JT modes and log directly into DXKeeper? Honestly, if I could just get JT Alert 2.16.4 or 2.16.6 working again I'd be happy but that ship has apparently sailed. Please and thank you.

I've recently started encountering the infamous "Invalid Port Number (8002), thePort = primary CAT port, port number = 4, settings = 115200,N,8,1" message box when trying to start Commander. Device manager shows COM4 to be up and working. Unplugging / re-plugging the USB cable and disabling / reenabling the COM port doesn't resolve it. The only solution seems to be to uninstall the device, reboot and let Windows reinstall it. Then the port will open fine until the machine is rebooted again. Then we're back to invalid port and the need to reinstall. Edition Windows 11 Pro Version 23H2 Installed on ?11/?19/?2022 OS build 22631.5189 Experience Windows Feature Experience Pack 1000.22700.1077.0 Commander ver 16.1.0 Anyone had this variation of the error crop up? Thanks!

? Hello Dave, I have been using DX Keeper and other DX Labs programs since midyear 2020 with great success and have never had a problem whatsoever. I am totally sold on the DX Lab Suite and have recommended it to many of my friends. Last year I submitted for the DX Marathon as Mixed Formula 100W, but I also kept tabs on my Challenge progress from inside DX Keeper just because it was fun. This year in 2025, I am pursuing the DX Marathon Challenge. Periodically I check my progress from inside DX Keeper using the Check Progress Tab and then clicking the Progress Button in the DX Marathon Challenge Section. This has been working every time without fail both last year and this year until recently. I'm not really sure when it stopped working. I figured I had pushed some button wrong and hadn't paid much attention to it but then yesterday I decided to delve into it and see what I might have messed up. What happens is, when I push the button to run the report nothing happens, other than the DX Keeper Title Bar displaying the following Message: See DXKeeper Errorlog.txt. I have tried almost every other Progress Report on the page, and they all seem to work just fine. When looking at the DXKeeper Errorlog.txt, it has two errors that I can see that are repeatable. Here is what is generated into the Error Log every time I try to run the Progress report: 2025-04-22 20:42:25.424 > program error 48 in module MarathonModule.GenerateMarathonProgressReport, State = 10: Error in loading DLL 2025-04-22 20:42:25.432 > MarathonCountryCodeIndex = 0 2025-04-22 20:42:25.440 > I = 1001 2025-04-22 20:42:25.447 > J = 21 2025-04-22 20:42:25.453 > theCode = 0 2025-04-22 20:42:25.459 > theZone = 0 2025-04-22 20:42:25.466 > regionID = 0 2025-04-22 20:42:25.472 > theBandField = 0 2025-04-22 20:42:25.479 > theModeField = 0 2025-04-22 20:42:25.485 > CounterIndex = 0 2025-04-22 20:42:25.494 > program error 91 in module DXLogMain.MarathonProgressCmd_Click: Object variable or With block variable not set I went back in the log, and it appears that the first time these errors started showed up was on April 15, 2025, with Version 17.9.9. I am running up to date Windows 11 on a Dell i7 Computer. I am going to need help fixing this since this is beyond my paygrade and training. It seems like something may have gotten corrupted. Thanks for the fantastic software and for the excellent support! 73! David Simms (N4IW) Lynchburg, VA -- Thanks, David, N4IW

Spot Collector is claiming that a zone is needed for DX Marathon, but I have already worked/confirmed that zone. I noticed this on 6m today when I worked a few stations in zone 4 and SC was still flagging stations on that zone as needed. And it was still highlighting the stations just worked. At least a couple of the stations I worked uploaded to LOTW and I confirmed them, so the CQ zone info was valid. Rebooted PC, restarted DXLab and did a recompute in the award progress tab. Checked the award tracking for some of the highlighted spots and it still says they are "unworked, needed" for DX Marathon. Suggestions? Chuck KM3V