开云体育

I'm using a single monitor and can't take it anymore. I'm adding a second monitor. I have a question that maybe someone can answer. I do most of my operating from a remote PC, using Windows Remote Desktop to access my shack PC. If I add a second monitor in the shack and configure DXlab to use two monitors, what happens if I remote in with a Remote Desktop session that is set up for a single monitor. Does DXlab detect a single monitor state and move everything back to that desktop, or will I miss seeing everything that the local desktop has on the second monitor? 73, Dean W8ZF

Hello, a couple of days ago I noticed uploading to Club Log timed out. This started with QSO's from 5/25/2025. I am using DXKeeper latest version 18.1.4. Below is information from the error log when attempted to upload a QSO to club log. Any thoughts LOTW auto upload is working as expected thanks K4JKB 2025-05-26 10:26:35.817 > ClubLogModule.SendQSO: begin 2025-05-26 10:26:35.823 > ClubLogModule.SendQSO: initiating upload to https://clublog.org/realtime.php 2025-05-26 10:26:35.830 > Params = False 2025-05-26 10:26:35.837 > ClubLogModule.SendQSO: upload initiated 2025-05-26 10:26:35.845 > ClubLogModule.HandleInetStateChange, theState = 3(Connecting), OperationCompleted = False 2025-05-26 10:26:35.851 > ClubLogModule.HandleInetStateChange: connecting to Club Log host 2025-05-26 10:26:35.916 > ClubLogModule.HandleInetStateChange, theState = 4(Connected), OperationCompleted = False 2025-05-26 10:26:35.924 > ClubLogModule.HandleInetStateChange: connected to Club Log host 2025-05-26 10:26:36.003 > ClubLogModule.HandleInetStateChange, theState = 5(Requesting), OperationCompleted = False 2025-05-26 10:26:36.013 > ClubLogModule.HandleInetStateChange: sending request to Club Log 2025-05-26 10:26:36.020 > ClubLogModule.HandleInetStateChange, theState = 6(Request Sent), OperationCompleted = False 2025-05-26 10:26:36.026 > ClubLogModule.HandleInetStateChange: successfully sent request to Club Log 2025-05-26 10:26:36.034 > ClubLogModule.HandleInetStateChange, theState = 7(Receiving Response), OperationCompleted = False 2025-05-26 10:26:36.041 > ClubLogModule.HandleInetStateChange: receiving response from Club Log 2025-05-26 10:26:36.088 > ClubLogModule.HandleInetStateChange, theState = 8(Response Received), OperationCompleted = False 2025-05-26 10:26:36.096 > ClubLogModule.HandleInetStateChange icResponseReceived: still executing 2025-05-26 10:26:36.103 > ClubLogModule.HandleInetStateChange: received response from Club Log 2025-05-26 10:26:36.111 > ClubLogModule.HandleInetStateChange, theState = 12(Response Completed), OperationCompleted = False 2025-05-26 10:26:36.118 > ClubLogModule.HandleInetStateChange: response completed 2025-05-26 10:26:36.495 > DXLogMain.LogGrid_FetchCellTips, RowIndex = 8, ColIndex = 0, DXLogSetup.TooltipsCheckbox.Value = 1 2025-05-26 10:26:36.504 > theColName = BAND 2025-05-26 10:26:36.510 > Callsign = KC3OL, CellContents = 20M 2025-05-26 10:26:36.516 > DXLogMain.LogGrid_FetchCellTips complete, CellTip = +celltip 2025-05-26 10:26:36.855 > DXLogMain.LogGrid_FetchCellTips, RowIndex = 8, ColIndex = 0, DXLogSetup.TooltipsCheckbox.Value = 1 2025-05-26 10:26:36.863 > theColName = BAND 2025-05-26 10:26:36.871 > Callsign = KC3OL, CellContents = 20M 2025-05-26 10:26:36.877 > DXLogMain.LogGrid_FetchCellTips complete, CellTip = +celltip 2025-05-26 10:26:38.445 > DXLogMain.LogGrid_FetchCellTips, RowIndex = 8, ColIndex = 0, DXLogSetup.TooltipsCheckbox.Value = 1 2025-05-26 10:26:38.455 > theColName = BAND 2025-05-26 10:26:38.461 > Callsign = KC3OL, CellContents = 20M 2025-05-26 10:26:38.467 > DXLogMain.LogGrid_FetchCellTips complete, CellTip = +celltip 2025-05-26 10:26:39.261 > DXLogMain.LogGrid_FetchCellTips, RowIndex = 2, ColIndex = 19, DXLogSetup.TooltipsCheckbox.Value = 1 2025-05-26 10:26:39.269 > theColName = QSO_BEGIN 2025-05-26 10:26:39.277 > Callsign = CO8ZZ, CellContents = 5/23/2025 01:11 2025-05-26 10:26:39.283 > DXLogMain.LogGrid_FetchCellTips complete, CellTip = +celltip 2025-05-26 10:27:36.099 > ClubLogModule.DownloadTimedOut 2025-05-26 10:27:36.110 > ClubLogModule.SendQSO: upload aborted after 4connection retries 2025-05-26 10:27:36.118 > Message.DisplayMessage: Title: DXKeeper Club Log Upload, Message = Upload QSO to Club Log timed out 2025-05-26 10:27:36.144 > DXLogMain.popClubLogUpload_Click: complete 2025-05-26 10:27:36.154 > DXLogMain.LogGrid_Click, ClickCallsign = KF8CGR, ClickAbsolute = 63987 2025-05-26 10:27:36.161 > DXLogMain.LogGrid_Click: complete 2025-05-26 10:27:36.396 > DXLogMain.RowChangeLookupTimer_Timer 2025-05-26 10:27:36.405 > DXLogModule.UpdateFieldVisibility, DXCCID = 291 2025-05-26 10:27

Is there some way of filtering out (from Spot Collector) the so-called spots begging a DX station something like "15m pse"? I really don't need to have this pop up in Spot Collector and try to find him, just to find out it's someone BEGGING the DX to go to 15 meters on a medium most DX stations don't see anyway. Thanks, Earl / KD5XB DM84 e e Sent with Proton Mail secure email.

Different ham radio computer logging programs appear to have different degrees of ADIF support, and I'm interested in understanding the impact of those differences in a number of areas: - data transfer between ham logging applications - QSL'ing and award tracking - use of application-defined fields I'm looking for a list of ADIF field names supported by DXKeeper. I found this cross-reference of DXKeeper Log Items with ADIF field names: https://www.dxlabsuite.com/dxkeeper/Help/Items.htm#QSO%20items Does that include all of the supported ADIF field names? Steve, N5EP

Can I utilize User Defined Controls in Commander to control an SPE amplifier driven by a Flex 3000 run by PowerSDR software? The SPE amp is on COM17. I want to be able to change from Antenna 1 to Antenna 2 on the SPE amplifier. I already have a Kenwood receiver tracking with the main radio as the Secondary. Also, in a Multi radio setting I have a yaesu FTDX101D set as radio #2. The SPE command set is 0x04

Every time DXLab Suite starts, I get the message "A new TQSL (V2.8.1) is available". I am already running that version. Any suggstions as to how to address this? Thanks, Roger EI8KN.

will dxlab support the new ftx-1? thanks Reggie k6xr

I'm getting the message: Disabled QSL Queue entry for JH8ISO on 2025-05-25 at 13:04:38 - station location "Home" specified in QSO's QTHID item "bakersfield" doesn't match station location "Bakersfield" selected on the QSL Configuration window's LotW tab There was report of the same issue on March 14th and I followed those directions. myQTHs Tab has Bakersfield QSL Tab LoTW Operation has Bakersfield TQSL Has Bakersfield What am I missing? This was a new build and new TQSL certs because I totally lost a drive with no backup other than my logbook on a different drive. Greg NZ6E

I have observed this behavior while never noticing it before. My transceiver is an IC7300. I am on FT8 with WSJT. A CW DX spot comes out, and I double-click in spot collector. Commander changes to the correct frequency, mode, and filter bandwidth. (It seem sometimes I have to stop monitoring on WSJT, and sometimes not, or it will grab me back to the FT8 frequency, but that's not what this is about). When I return to FT8 by re-enabling the monitor in WSJT, I see that the bandwidth is 2.7 kHz. Before that, it was 3+ kHz on the waterfall. I then change the Filters Group setting back to Normal (or Wide), and the bandwith goes back to the 3+ kHz. But now, the Group bandwidth display periodic bounces from normal to narrow, about 1 to 2 times per second. I can change the filter to wide, same bouncing. I can change it to narrow (where it was on CW immediately prior to coming back to FT8), and there is no bounce. There is some kind of polling going on and the state it keeps trying is Narrow. I don't hear any bandwidth changes on the radio while this is going on, and I don't see any change in the WSJT spectrum. Once I shut down commander and restart, this behavior disappears and "normal" is the constant state of the filter group. Any ideas what's going on? 73, Dean W8ZF

When I post to the Cluster (using SpotCollector) the audio alarm readout says "Grid Square FO93" included in the announcement. First of all: 1. F093 is wrong, and no matter what Call is Spotted, the same Grid Square is announced. 2. Even in Spots announced by other stations, the Grid Square FO93 is announced. What is the source of this and how can I turn it off? SC 9.9.2 73, N0AN, Hasan

A new poll has been created: Do you pursue POTA and/or SOTA awards? 1. I'm pursuing POTA awards but not SOTA awards 2. I'm pursuing SOTA awards but not POTA awards 3. I'm pursuing both POTA and SOTA awards Click Here To Vote Do not reply to this message to vote in the poll. You can vote in polls only through the group's website.

Greetings to the Group, Two days ago, I did a PC reboot to capture the latest Windows update. Like dozens of times before I did not see any issue. To be candid I'm not sure this update and reboot is related to the problem I'm seeing. After the update when everything was up and running, I launched Commander, DXKeeper, DXView, and Spotcollector. Several hours later I noticed spots were not showing up in the band spread window and not on my FLEX6400 display. The Spotcollector window was not capturing new spots. It is displaying the last spots captured before the Windows update on 5/21 @ 1413z. Symptoms include, I can initiate and send a spot to the DXcluster but it would not be captured in the Spotcollector screen or the bandspread etc. Going into the individual cluster windows, I see that Spots are coming in from the clusters I monitor, but nothing "new" was showing in the spotcollector window. SH/DX inquiries to the clusters stream the latest spots right back. I tried doing a restore to Spotcollector but that did not change anything. I'm not sure what else to try. Thoughts and/or suggestions would be appreciated. Thanks, Mike K9MK PS: PC is a i9 gaming platform running W10_Pro.

So it's 0715Z, I just woke up and checked Spot Collector. I'm receiving about 37 spots per minute with all skimmers turned off. Is this normal? Seems kinda low. Spot sources are: n6ws.ddns.net lu9da.no-ip.org 7N4TWL.HOMEIP.NET DX.HAMNET.NETWORK Thanks, Earl / KD5XB GN e e Sent with Proton Mail secure email.

Some time ago I started using log4om. bad move. I want to switch back to dxl. When importing the adif is there a way to append the dxl database and avoid duplicate entries? -- 73, Greg - AB7R Flex 8600 PGXL & TGXL AG

For MONTHS now, I've been having an on-again off-again problem. If I let my spot database get too large (around 10,000 entries is when I start noticing it), it gets slower & slower processing spots, until it finally just stops doing ANYTHING and I usually have to use Task Manager to kill the program before staring over. Well, this morning, it happened again. I had let it run overnight, and the database had around 20,000 entries, and when I first came into the radio room this morning, the Q said 842 and was just sitting there, not processing. Once I got it going again, I started going through ALL the config settings in Spot Collector, one-by-one like a checklist. I had a hit on the first one! Apparently, some time in the past, I meant to set "Maximum Separation in Time) to 60, which is reasonable, but I found it set to 600!!! My finger must have bounced on the 0 key and I never noticed. Spot |Collector sure seems to run better now that it's changed to 60, with my current database at ~11,300 and all Telnet sources are turned on with skimmer turned on throughout. Oops, now we're at ~11,350... A fat-fingered wrod ot teh wsie... Vy 7 3 Earl / KD5XB DM84 e e Sent with Proton Mail secure email.

HI THERE, I AM USING DXLAB FROM 2007 AND IT IS FOR ME THE BEST. A FEW DAYS AGO AND I AM NOT SURE IF IT WAS AFTER THE INSTALATION OF THE LATEST VERSION OF DXKEEPER 18.1.4 DXKEEPER STARTED DOING THIS, AND IT DRIVES ME NUTS. THIS IS HAPPENING IS WHEN I CONCLUDE A QSO ONLY FROM WSJT-X RUNNING FT8 OR FT4. WHEN I ENTER A CALLSIGN AT THE DXKEEPERS CAPTURE WINDOW AND PRESS LOG ALL THE DATA ARE THERE. BUT NOT FROM WSJT-X. IT IS NOT FILLING UP (THE QTH TAB THE TX FREQUENCY TAB THE ADDRESS TAB THE CONTINENT TAB CQ TAB ITU TAB) WHAT IS CAUSING THAT I HAD NO PROBLEM BEFORE IT STARTEDBAS I SAID A FEW DAYS AGO. YOUR HELP WILL BE GREATLY APPRECIATED.

I was trying to figure out why, when I turn skimmer on, none of the entries in Spot Collector show the # as they did on my old computer. Still looking on that one. However, using https://www.dxlabsuite.com/RBN/index.htm , the link for DX Summit (toward the top of this page) gave me a 404 error. Specifically, the link goes to http://www.dxsummit.fi/Default.aspx and gives a 404. I did notice that http://www.dxsummit.fi goes to http://www.dxsummit.fi/#/ and apparently gives a page of DX spots. (Spot Collector has spoiled me, I don't remember how to use http://www.dxsummit.fi/#/ ! LOL!) Vy 7 3 Earl / KD5XB e e Sent with Proton Mail secure email.

Hello all, have a Question is there a way on the Qsl card you design that you can move the Qso report grid lines further up or down by itself or it always have to move together with the Station Callsign ? Thanks Jose NK4L -- jose gonzalez

I'm back in business. Yesterday I mentioned there were no other symptoms. Later I noticed that hyperlinks in Thunderbird emails did not work all of a sudden, though they still worked in Outlook. This morning, after a couple more PC re-boots, Thunderbird hyperlinks started working again. Probably no connection, but when I went back to DXL Launcher, things looked better - the Launcher config button now looked normal. But most of the apps, on the Launcher config page, looked as if they had never been installed. When I tried to install DXKeeper, there was a continuus hourglass, as if waiting for a response from me. And it was! When I held down alt-tab I saw a window asking if I want to install DXK, but I couldn't hit Yes cuz the window wouldn't cooperate and stay on the screen when I released the ALT key. Double checked that I had never set up a 2nd monitor...check Then I remembered about the Reset button in Launcher Config - that did the trick. Installed DXK, which is mostly the only DXL app I use, and noted that my 175k qso's are there! The issue seems to be solved. I'll note that my comdlg32.ocx file still has a creation date in 2004. Thanks Dave for DXL. While I'm not a heavy user, this was the 1st issue I've had in many years. I'll probably never know what the original cause was.... -Steve K8LX On 05/19/25 5:47 PM, Dave AA6YQ wrote:

running spot collector with 3 sources and after a while the scrolling stops but i see the queue counting down. the fix for me is to compact the database and all scrolling restarts. wish there was a setting to periodically compact the database . i do have periodic pruning turned on but it doesnt help the scrolling issue