Keyboard Shortcuts
Likes
- DXLab
- Messages
Search
Re: Dxkeeper and Spotcollector - no text displayed
+ AA6YQ comments below
Dxkeeper and Spotcollector - no text displayed DXKeeper errorlog 2025-04-24 09:44:11.987 > I = 126 2025-04-24 09:44:11.987 > DXLogMain.LogGrid.Columns.Count = 126 2025-04-24 09:44:47.012 > program error -2147221164 in module DXLogModule.InitializeLogLayout, State = 2: Class not registered 2025-04-24 09:44:49.137 > program error -2147221164 in module DXLogModule.FormatLogGrid, State = 2: Class not registered + "Class not registered" means that your DXKeeper installation has been corrupted. To repair it, 1. make sure you have a backup of your log stored elsewhere. Don't delete anything. 2. terminate all applications except the Launcher 3. direct the Launcher to create a new Workspace, and populate it with DXKeeper's settings 4. terminate the Launcher 5. reboot Windows 6. using the Windows Control Panel's "Uninstall an program" function, direct Windows to uninstall DXKeeper 7. start the Launcher, and direct it to install DXKeeper 8. start DXKeeper; if DXKeeper's settings are missing, terminate DXKeeper, direct the Launcher to recover DXKeeper's settings from the Workspace you created in step 3, and then restart DXKeeper 73, Dave, AA6YQ |
Re: Display more memories
Dave's Commander manual says (and maybe this can help you): To help keep track of each memory's purpose,? you can record notes that pop up whenever the mouse cursor hovers over the memory's Sel button. To record such notes,? depress the Ctrl key while clicking the Sel button; Commander will display a Memory Notes Editor window that allows you to capture notes:
You can direct Commander to display each memory's notes in place of its frequency, mode, and filter -- simply click the command button captioned ~ in the upper right corner of the memory bank panel. To return to a display of memory frequency, mode, and filter, click the ~ button again. |
Re: discrepancy between LOTW and DXKeeper QSO totals
On 2025-04-24 10:25 AM, W0MU wrote:
Is the 100k that LOTW states include other calls I have used such asDoes the 100k match the number in the header (lower right) of the LotW "My QSOs" page? It is likely, unless you have specified a single callsign in QSL Config -> LotW -> "Limit Sync operations to this station callsign" that the number includes all callsigns in your DXCC/LotW account. Do you know what the contact was - callsign at least? If so use theI was trying to recover a LOTW confirmation on a single contact. LotW "My QSOs" page, search for that callsign and enter the data manually. 73, ... Joe, W4TV On 2025-04-24 10:25 AM, W0MU wrote: I was trying to recover a LOTW confirmation on a single contact.? I did the CTRL sync QSO's and LOTW is reporting over 100k qso's. DXK log says 76k.Is the 100k that LOTW? states include other calls I have used such as DXpeditions?? I am unsure where I would have made 30k qsos that got uploaded to LOTW without using DXK. |
discrepancy between LOTW and DXKeeper QSO totals
I was trying to recover a LOTW confirmation on a single contact. I did the CTRL sync QSO's and LOTW is reporting over 100k qso's. DXK log says 76k.Is the 100k that LOTW? states include other calls I have used such as DXpeditions?? I am unsure where I would have made 30k qsos that got uploaded to LOTW without using DXK. I believe I can create a blank new log and then import from LOTW and find out? BTW inspecting 100k qsos takes a very long time. Mike W0MU |
Re: Importing issues
It was the grid square.
toggle quoted message
Show quoted text
Thanks. On 4/23/2025 8:08 PM, Dave AA6YQ wrote:
+ AA6YQ comments below |
Dxkeeper and Spotcollector - no text displayed
Dxkeeper and Spotcollector - no text displayed
?
DXKeeper errorlog
2025-04-24 09:44:11.987 > ? ?I = 126
2025-04-24 09:44:11.987 > ? DXLogMain.LogGrid.Columns.Count = 126 2025-04-24 09:44:47.012 > program error -2147221164 in module DXLogModule.InitializeLogLayout, State = 2: Class not registered 2025-04-24 09:44:49.137 > program error -2147221164 in module DXLogModule.FormatLogGrid, State = 2: Class not registered
|
Re: DXKeeper Command line import support
+ AA6YQ comments below
I've done some of my own "scripts" scanning WSJT-X adi files (creating import *.adif-files) and I have a wish that that I could import those in DXKeeper from directly via a command line instead via DXKeeper menus (works fine..). It would be a another interface to communicate with DXKeeper... like cmd: DXKImport.exe /f adif-file [optional parameters]. If this is doable I would be a lucky guy ! + You can start DXKeeper with a single command line argument: the full pathname of the log file you wish DXKeeper to open. There are no command line switches or other arguments, so you cannot specify an ADIF file to be imported. + Are you aware that QSOs logged via WSJT-X can be directly conveyed to DXKeeper without the need to import an ADIF file? See 73, Dave AA6YQ |
DXKeeper Command line import support
Hi DXLab,
?
I've done some of my own "scripts" scanning WSJT-X adi files (creating import *.adif-files) and I have? a wish that? that I could import those in DXKeeper from directly
via a command line instead via DXKeeper menus (works fine..). It would be a another interface to communicate with DXKeeper... like cmd: DXKImport.exe /f adif-file [optional parameters]. If this is doable I would be a lucky guy !
?
Best rgds/73
SM0FGT - Keijo? |
Re: Importing issues
+ AA6YQ comments below
I am importing logs from wsjtx, jtdx, mshv etc. Most of the time I use jtalert to log to DXK at the same time but occasionally their are hiccups. When I do an import I usually get an unaccepted number of dupes. I am not sure what boxes to check for a cleaner import. I am using check duplicates on import +/- 10 mins and merge info. I might of had consider grid squares checked. Maybe I need to increase the minute range. + Choose a duplicate QSO that was imported. Compare it to the original QSO that was already present. The comparison will reveal the changes to make in the "Duplicate checking" panel on the Main window's "Import QSOs" tab. 73, Dave, AA6YQ |
Importing issues
I am importing logs from wsjtx, jtdx, mshv etc.? Most of the time I use jtalert to log to DXK? at the same time but occasionally their are hiccups.? When I do an import I usually get an unaccepted number of dupes.? I am not sure what boxes to check for a cleaner? import.? I am using check duplicates on import +/- 10 mins and merge info.? I might of had consider grid squares checked.? Maybe I need to increase the? minute range.
Mike W0MU |
Re: [cwops] [DXLab] Importing N1MM+ and/or WSJT-X logs
¿ªÔÆÌåÓýThanks, but I just wanted to say how well the gateway program works and how it can save users time and effort.
Jim N7US
Sent from my Verizon, Samsung Galaxy smartphone
-------- Original message --------
From: Gerald Buglione <kd2fsh@...>
Date: 4/23/25 17:56 (GMT-06:00)
To: Jim McDonald <jim@...>
Subject: Re: [cwops] [DXLab] Importing N1MM+ and/or WSJT-X logs
You are the best Jim de KD2FSH Jerry # 1918 On Wed, Apr 23, 2025, 4:44?PM Jim N7US #486 via
<jim=[email protected]> wrote:
|
Re: Display more memories
+ AA6YQ comments below
Is there a way to display more than the 10 memories per bank?? I would love to see two bank or 20 memories or have this customizable if possible.+ The limit is 10 memories per bank. Ten banks of 10 memories each are provided; you can switch from one bank to another with one mouse click. ? ? ? 73, ? ? ? ? ? ? Dave, AA6YQ |
Re: SP Prob & LP Prob
+ AA6YQ comments below
+ Older propagation prediction engines may support a wider frequency range, but they are inferior to VOACAP on HF bands. SpotCollector directs PropView to use VOACAP; I'm not planning to enable the use of older inferior propagation engines even if doing so would yield forecasts on 160m and 6m. ? ? ? 73, ? ? ? ? ? ? ?Dave, AA6YQ |
Re: SP Prob & LP Prob
¿ªÔÆÌåÓýThere is almost no way to predict (ES) e-skip propagation on 6m and even F2 openings seem to make no sense at times.? Your best bet is to watch dx maps and be in the ON4KST chat if you are a serious 6m op. W0MU On 4/23/2025 3:01 PM, Earl Needham via
groups.io wrote:
|
Re: SP Prob & LP Prob
Thanks again, Dave. I've been wondering about this for some time, since in the config, on the Prediction panel, both of these bands are included.? It would definitely be a help if either one or both was available. What if I used the ICEPAC LUF & MUF instead?? (I admit, I don't know much about these engines...) Earl
Sent with secure email.
On Wednesday, April 23rd, 2025 at 3:20 PM, Dave AA6YQ <aa6yq@...> wrote:
|
Re: SP Prob & LP Prob
+ AA6YQ comments below
Should I be seeing SP Probability and LP Probability on 6 meters, or is this strictly 10-80 meters?+ "when checked,??1.8.7 or later can be directed to generate Signal-to-Noise Ratio (SNR) and Probability predictions for Spot Database Entries whose frequencies are in the range of 2 Mhz to 30 Mhz." + That range excludes 160m and 6m; it's a limit of the VOACAP propagation prediction engine. ? ? ?73, ?
? ? ? ? ? ?Dave, AA6YQ |