开云体育

Hello, On DXKeeper, I just noticed since 2 days the following pbm with some QSO. Not all QSO. When I log a new QSO, the "award" checkbox is automatically checked. I'm used to work with DXKeeper without active checkbox. When the "award" checkbox is automatically checked when logging the QSO, the size of the DXKeeper is modified and I have after to resize it. Any idea please ? Many thanks. Best 73 de F5PHW Phil

Many Clubs provide for awards for working members on various bands throughout a single year. FOC, for example, has an award for working each member once per year on each band. The Leaderboard function provides a perfect mechanism for tracking progress on working club members on each band by identifying a spot with a specific color when it is unworked on a particular band for the defined time period (set for the current year). However, if you have worked that member during the year on that particular band, the Font Color reverts to the Unneeded DX font color. Technically, that's correct. But that results in the spot for the Club member disappears into the same font color as the rest of the spots, making it more difficult to identify club members (which was the goal of putting their callsign into Special Call signs in the first place). It would be nice if any call listed in Special Callsigns retained a different color or if Leaderboard Worked had a different color than DX Unneeded. Don WB6BEE

Please resend instructions for replacing Primary database because of corruption. I would like to try again, Dave. Thank you, Gerald, WA9GON

Joe, I figured it out. I was trying the create a filter, but Dave had already included it on the Advanced page. I’m slow, but finally see it, most of the time. 73, Bob KB4CL

For me this will mean no more SpotCollector emails to my iPhone via SMS alerting me to a potentially needed and workable spot. OTOH I still get notifications from HamAlert to the HamAlert app on my phone. FYI Jim ab3cv

If I work a number of stations during a contest, but I don’t plan to mail out QSL cards to everybody I worked and I want to change QSL Sent to “N” in one move how do I do it? I know that I go into the DXKeeper Advanced Sorts, Filters & Modifiers. Then create a Filter to isolate them. Finally, under “Modify QSOs in Log Play Display I set QSL_Sent to “N”. The question is what would the filter look like? 73, Bob KB4CL

I wanted to go back and look at my DX Marathon submission for 2024. If I push Alt + Progress, it does not ask me for a year. It only gives me the 2025 report. Thanks 73 Kent N6WT

Hello, I wanted to know if there is a way to copy a profile from 1 computer to another ? I had a crash and lost the laptop. I have a good working install on a desktop. Scott N2SAB

FYI: From: [email protected] [mailto:[email protected]] On Behalf Of Lee Sawkins via groups.io Sent: Tuesday, April 01, 2025 10:25 AM To: [email protected] Subject: Re: [CC-User] Bogus DX Spot Attacks on Clusters What happened this weekend was that tens of thousands of bogus spots were entered into the cluster system. These spots were all for SSB. Since there are no SSB skimmers available yet, all of these spots appeared to be manually entered, but in fact they were generated by a computer. Normally the human entered spots never are more than 60 per minute. During the weekend spots that were bogus were entered at many thousands per minute. These spots were targeting specific active calls. These spots were giving different frequencies on all contest bands for each bogus spot. These spots had same DX call and a different spotter call and different originating cluster call. This caused many nodes to get bogged down trying to process all this data. Some crashed. Others got hopelessly behind and continued sending data to my cluster which dropped the spots because they were too old. Millions of spots were being dropped. My cluster limits the number of spots to 60 per minute. This limited bogus spots but also good spots in each minute. When bogus spots stopped, then all the new good ones got through. Lee VE7CC

I've had one notice of a failed attempt to upload to LotW. I'm thinking that I need to manually upload later. I believe that this notice relates to a single QSO upload from DXLabs. I just don't know which one failed. Is there a DXLab way to find it? I have (accidentally) done my first Sync All. It shows I have work to do, grin. _______________ TQSL error message: TQSL Version 2.7.5 [v2.7.5] Signing using Callsign NU6T, DXCC Entity UNITED STATES OF AMERICA Attempting to upload one QSO C:\DXLab\DXKeeper\LotWUpload.ADI: Unable to connect to the upload site. Please try uploading the Log later. Final Status: LoTW Connection Failed(11) ________________ Thank You Rich, NU6T-- Richard Hill

The short path probability box on the Spotcollector 9.8.3 main panel has no entries, as it used to do. I don't know what I changed to cause this. On the configuration general tab, in the Propagation Prediction panel, the enable SNR box and for all stations boxes are checked. The default required SNR is set to 0 db. PropView 2.0.7 is open. On the config prediction tab, all bands except 60m are selected. The required SNR for CW is 10, for SSB 20, for FT8 -24. What am I missing? 73, Steve K2SN

Using Ver 1.13A of MMSSTV and Ver 6.0 of MMD. The DXKeeper and MMTTY "lamps" light in the MMD pane First problem is there is No 'Setup Logging' in the Option Menu. Thanks Rick - N8XI

+ AA6YQ comments below Dave, you note: “If the PW1 is connected to Commander's Secondary CAT port and no other device, then the only way CI-V collisions can occur is if the PW1 transmit CI-V messages.” Are you saying definitively that the PW1 is never shutting up? Could you can see this in an error log? + Yes, I should be able to do so. You should be able to see it in Commander's Messages window if you uncheck "Capture and display Primary CAT Port Messages" and check " Capture and display Secondary CAT Port Messages". The > and < characters to the immediate right of the timestamp will show whether Commander or the PW1 transmitted each message. 73, Dave, AA6YQ

However, when I turn the I am having trouble setting up my IC-PW1 in DXLabCommander. Please help. I am not good at English. I am writing this with translation software, so sorry if the text is strange. I want to connect IC-PW1 and SteppIR to IC-7600, but the frequency control of IC-PW1 does not work together even if I set DXLabCommander and IcomPW1 control as described in the manual. IC-7600 (Primary CAT Serial Port) is connected to PC (DELL Win11) via USB port (COM X) and IC-PW1 and SteppIR (Secondary CAT Serial Port) are connected via USB interface to the same COM port (COM Y). The IC-7600 is connected to the PC (DELL Win11) via the same COM port (COM Y). After the initial setup, when the IC-7600 and IC-PW1 are turned on, the PW1 alert lights up, and after clicking it, they can be controlled in power off and on again, the AUTO LED on the IC-PW1 is lit, but the PW1 alert on the DXLabCommander is not lit and the frequency control is not linked. Then, when the frequency is changed using the UP or DOWN switch on IC-PW1, the PW1 alert lights up, and when the AUTO LED is turned on again and the PW1 alert is clicked, the frequency control is linked. Also, sometimes, when the power is turned on again, PW1 alert lights up and when clicked, it works correctly. This is the situation. Please let me know how to set it up so that I can control it correctly. Shige:JJ1BCM

For some time now, double clicking on a spot (Spot Collector) doesn't change the frequency of the RTX connected via CAT. Sometimes after 5 or 6 mouse clicks the frequency finally changes but not always. Until some time ago this did not happen and by clicking on each spot the radio immediately QSY. The strange thing is that if I use the QSY function in the menu (using the right mouse button), the Rtx immediately switches to the correct frequency of the spot. Instantly I use a PC with Windows 10 and all DX Lab applications updated to the latest versions. I tried to search through the settings windows to see if there was an item to activate but without luck. Note: DX Lab Commander manages 3 devices (Multiradio) and the problem is present on both radios (1 Icom and 2 Yaesu). Thank you in advance to anyone who wants to give me some suggestions on where to investigate. 73, IZ4MJP Franco

449/5000 Good morning, I have a problem with Pathfinder here. Pathfinder sometimes freezes. Then the only solution is CRTL-ALT-Delete and then force shutdown. and restart again then work pathfinder again. Sometimes it is very fast, other times it takes a little longer. are there more who recognize this problem? And perhaps already have a solution? I work with the complete DXLSuite thanks for the response. greeting Rien, PA7RA Stay Safe!

Perhaps it's just my memory failing or me not reading enough posts here but I see that I have a lot of "C" in the DXView matrix for QSO that are fully verified on LoTW. The QSO in question show up as "Card QSL" in LoTW although that I am positive I have received LoTW confirmations for before applying for credits. Also, clicking "update from lotw" just reports the QSO as "accepted and confirmed" although they are fully verified in my DXCC challenge account. Could this be a side effect of the "emergency repair" done last spring, perhaps? Bj?rn SM7IUN

I've learned much about monitors and graphics cards, and my ignorance remains vast, grin. I've decided to try my existing system with a 2K, QHD, 1440p wide monitor, and go up from there as needed. I'll report more later. I chose to take a too good Amazon deal for $200 on a Spring sale after seeing a very similar model at Best Buy for $280: acer Nitro 31.5" WQHD 2560 x 1440 1500R Curved Gaming Monitor | AMD FreeSync | Up to 180Hz Refresh | 1ms (VRB) | Tilt | 1 x Displayport 1.4 & 2 x HDMI 2.0 | EDA323QU S3bmiiphx https://www.amazon.com/gp/product/B0D9HP796Q/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1 I'm passing this along should others have an interest. I may later decide that I need a second small monitor for maps. I have a 16" portable monitor that may work. YMMV. 73 Rich, NU6T-- Richard Hill

Hi all, Recently started using Spot Collector, and am pleased report that it has already helped collect a few band-specific "new ones". Had a bit of a scare though, LOL - hadn't run it for a few days and yesterday evening and today it wouldn't display any new spots ... which was a bit surprising today given it's the CQ-WPX-SSB weekend. Read various threads on here and went through the suggested troubleshooting steps, but couldn't fix it. Read the error log, which said "program error 3049 in module SpotDatabaseModule.RecordSpot with state = 371: Cannot open database ''. It may not be a database that your application recognizes, or the file may be corrupt" - found the database had grown to 2GB (!) and telling the app to prune the database and compact it (in the Spot Database tab's Size Control panel) ... now the database is only 6MB and spots are coming in. Just thought I'd share that in case someone runs into a similar issue. Anyway, my question is unrelated to that. I have trimmed the number of columns in the main window down to the few I need, but the order they appear in is fixed. Is there some way of re-ordering them so that, for example, I have the "DXCCPrefix" column first on the left, then the "Callsign" column, then the "Frequency", etc? 73, Mike VK2IG

I am happy to announce that Tom NY4I has agreed to provide ongoing support and development for the N1MM-DXKeeper Gateway. I've updated the entry in https://www.dxlabsuite.com/download.htm#Bridges,%20Gateways,%20%20and%20Extenders with the Gateway's new Online Help: https://ny4i.github.io/DxKeeper-UDP-Gateway/ which Tom has already updated to reflect new functionality that he has added. Requests for help, defect reports, and enhancement requests are all still welcome here. Thanks, Tom!!! 73, Dave, AA6YQ