开云体育

ctrl + shift + ? for shortcuts
© 2025 开云体育

Re: Verified vs Confirmed on LoTW

 

Hi Bj?rn
I'm not what the problem is you are trying to solve? Is it that your DXCC Challenge numbers shown on LOTW don't match what is reported in in your DXCC report in DXKeeper? If so, you should use the 'Compare' button in the DXCC progress section of DXK as a starting point.

Also what is the "the DXView matrix" you are referring to?

73, Chuck KM3V


Re: Verified vs Confirmed on LoTW

 

+ AA6YQ comments below

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?

+ Are you referring to the ARRL's "system disruption" caused by its failure to maintain immutable backups and a tested disaster recovery plan? If so, no one knows what changes were made. What is known is that the same developer who released LoTW in 2003 with little testing and no end-user documentation has been making changes.

73,

Dave, AA6YQ


Re: Verified vs Confirmed on LoTW

 

Perhaps it is an LOTW bug after all. If I pick one of the?"strange" QSO which show up as C rather than V in?
spite of being verified I see that if I look up the QSO in "My QSO" and click on its QSL link, I get a full LOTW?
confirmation with time of confirmation, grid, etc. but if I go to "Awards" and click my way to my Challenge account?
and click that same QSO in the matrix, I get a "card" type confirmation without date, etc.

If I go into my application history and look up the QSO, it also shows up as a "full" LOTW digital QSL.

I cannot see it any?other way than?that this is a bug in LOTW.

Bj?rn SM7IUN

On Thu, Mar 27, 2025 at 11:38?PM Bj?rn SM7IUN via <bjorn=[email protected]> wrote:
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


Verified vs Confirmed on LoTW

 

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


Re: Graphics cards and Monitors for the shack/ DXLab

 

开云体育

Perplexity offers this comment about Graphics card memory and system memory:

?

A graphics card primarily uses its own dedicated memory, known as Video RAM (VRAM), for handling graphics-related tasks such as storing textures, shaders, and rendered images

However, in certain situations, a graphics card can utilize the motherboard's system RAM, but this is not a standard or preferred method for several reasons:

--Integrated Graphics: When a system uses integrated graphics (i.e., graphics processing capabilities built into the CPU or motherboard), it relies on system RAM for graphics processing. This is because integrated graphics do not have their own dedicated VRAM

--Shared Memory: Some systems, particularly those with integrated graphics, allow for a portion of system RAM to be allocated as shared memory for graphics processing. This is more common in laptops or systems without a dedicated graphics card

--PCIe Bandwidth: Modern graphics cards can access system RAM via the PCIe interface, but this is generally slower than using VRAM. The PCIe bus allows for data transfer between the GPU and system memory, but it is not typically used for primary graphics rendering due to bandwidth limitations

--Outsourcing to System RAM: In cases where a GPU runs out of VRAM, it might use system RAM as a fallback, but this is inefficient and can lead to performance drops

?

In summary, while a graphics card can technically use motherboard memory under specific conditions, it primarily relies on its own VRAM for optimal performance.? While a GPU cannot directly use system RAM as a substitute for VRAM, system RAM can be utilized in specific contexts through software management or when using integrated graphics. The performance impact of relying on system RAM for graphics tasks is generally significant due to slower access speeds compared to dedicated VRAM.

------------------------------------------------------------------------------------End of Perplexity quote--------------------------------------------------------------

?

In my shack computer I have an old graphics card with 4 Gig of memory.? That amount of memory is not enough to store the images on my 3440 X 1400, 34” monitor (DXLab + WSJTX improved)? and my 21”, 1920 x 1080monitor (DXAtlas + DXMaps).? So, when my video system goes to sleep, upon wake up, it takes an annoying amount of time to refresh the two screens.?

?

On my house office computer, I have a video card with 16 Gig of video memory.? I have a 27”, 2560 x 1440 monitor (4,816,000 pixels) , on that video system, when awakened from sleep the previous images instantly pops up.? I can’t afford the card that has enough video memory to pop-up that many pixels—nor would I buy the computer case big enough to fit that card.

?

When running DXLab and associated Amateur Radio related software, we have a lot of pixels loaded with useful images and text, the rate of change of those pixels is quite slow in comparison to design tools and gaming.

?

Display pop up time is not a meaningful measure.? But it does show the relative speed of update from video memory vs mother-board memory.

?

73,

Dave, w6de

?

From: [email protected] <[email protected]> On Behalf Of Richard Hill via groups.io
Sent: 27 March, 2025 18:10
To: [email protected]
Subject: Re: [DXLab] Graphics cards and Monitors for the shack/ DXLab

?

Regarding Spot collector hardware needs, I think they relate to the motherboard hardware and not to the graphics card unless the graphics card uses motherboard resources and then a limitation in resources could affect the graphics system and display capabilities (probably on low end systems) when under heavy loads.??

?

Yes?

?

Rich, NU6T

?

On Thu, Mar 27, 2025 at 10:49?AM Dave AA6YQ via <aa6yq=[email protected]> wrote:

+ AA6YQ comments below

is SpotCollector multi-processor or multi-core aware?

+ I did not design SpotCollector or any other DXLab component to detect and exploit the presence of multiple cores. However, testing revealed that SpotCollector's performance does increase if 2 or 3 cores are assigned - likely due to parallelism in the Jet database engine. If you have SpotCollector configured to direct PropView to generate a propagation forecast for each new Spot Database Entry, then assigning PropView to a core would likely also improve performance,?

+ See the Hardware Capabilities section of



? ? ?73,

? ? ? ? ? ? Dave, AA6YQ


?

--

Richard Hill


Re: Graphics cards and Monitors for the shack/ DXLab

 

+ AA6YQ comments below
I'm continuing to try to define the graphics card requirements?for ham radio work specifically like the DXLab suite, N1MM, WSJT-X and such
+ Any interface from a reputable supplier that supports your chosen monitor's resolution, refresh rate, and video connector (HDMI or DisplayPort) will be fine.?

? ? ? ?73,

? ? ? ? ? ? ? Dave, AA6YQ


Re: Graphics cards and Monitors for the shack/ DXLab

 

I'm continuing to try to define the graphics card requirements?for ham radio work specifically like the DXLab suite, N1MM, WSJT-X and such.? I am wondering whether a 2D system like AutoCAD might reflect the basic requirements. I plan to use the information below to understand mid level graphics cards through the G2D performance charts on the Video Benchmark site:



For 2026, AutoCAD (Computer Aided Design) recognizes a Basic system as 2 GB GPU with 29 GB/S Bandwidth and Direct X 11 compliance.? A recommended system is 8 GB GPU with 1066 GB/s bandwidth and Direct X 12 compliant.


I've been exploring my Dell 8950.? If you type "dxdiag" into the search bar of the Win 11 Start page, you will get a DirectX Diagnostic tool that shows some of your graphics card's capabilities.? My Intel UHD Graphics 730 "basic" card has Direct X 12, and has a 4GB?total memory..

I needed more information to understand whether this GPU meets the AutoCAD recommendations.? I downloaded a free tool called GPU-Z.? ?It shows me that I have Direct X 12 (2_1), a 128 bit bandwidth?and 140.5 GB/s bandwidth.? I did a Google search to find GPU-Z.


That tells me that my low end GPU meets the Basic requirements for AutoCAD and more, but not the full recommended requirements.? This set of tools could be used to help understand what your system has available.

I don't know if the AutoCAD requirements are relevant to ham radio needs, but it is the best that I have so far.? CAD is heavily 2D and very little?3D.? AutoCAD's minimum resolution requirement is 1080p but higher resolution is desired.? There are additional requirements depending on the variation of AutoCAD.

73
Rich, NU6T


On Tue, Mar 25, 2025 at 11:13?PM Dave AA6YQ via <aa6yq=[email protected]> wrote:
+ AA6YQ comments below

An important distinction is that most of the features of these performance graphics cards are not going to be used at all with typical ham applications.? Almost nothing in the ham application use 3D graphics.? Instead, it's the 2D rendering performance that is key but it's not talked about at all in most card reviews.? This is especially important because there is a complete and total mess in the higher end graphics market now which may confused and scare away hams from picking up a very fine graphics card that would meet their needs.

Fortunately there is a web page that will help guide relative speeds of graphic cards, both old and newer ones.?



Take note at the G2D column, and sort from highest to lowest.? Then just go down that list and check whatever graphic card you have an interest in.

Notice that the fastest card on the list is about 1000 in the 2D speed.? The card I have in my main PC (GTX 1060) scores 770 - a card that must be at least 5 years old.? It runs a trio of UHD monitors here in the shack.? And you can get a similar one for under $100 on ebay.

I'm not advocating this card, rather mentioning that whatever card you are thinking of buying can be judged on it's speed by consulting this list.? And anything that's on the top half (500 or more) will most certainly be completely fine for ham applications.

+ It would be nice to have a "Selecting a Video Card" article in the DXLab Wiki to go with the "Selecting a Monitor" article developed by Dave W6DE:



+ The above guidance regarding 2-dimensional rendering performance would certainly be included in "Selecting a Video Card", but there are additional considerations:

- resolution

- refresh rate

- power consumption

- physical size

- monitor connectivity (HDMI, DisplayPort, etc.)

- motherboard compatibility

+ Would someone like to take a crack at this?

? ? ? ?73,

? ? ? ? ? ? ?Dave, AA6YQ









--
Richard Hill


Re: Graphics cards and Monitors for the shack/ DXLab

 

+ AA6YQ comments below

Regarding Spot collector hardware needs, I think they relate to the motherboard hardware and not to the graphics card unless the graphics card uses motherboard resources and then a limitation in resources could affect the graphics system and display capabilities (probably on low end systems) when under heavy loads.

+ Neither SpotCollector nor any other DXLab application directly utilize graphics card resources. They rely on Windows to display their windows using whatever hardware is provided for that purpose.

73,

Dave, AA6YQ


Re: Error log Text

 

+ AA6YQ comments below

I keep getting this error message in DXKeeper.

2025-03-26 23:37:04.549 > Common.Terminate: DXKeeper shutdown
2025-03-27 12:48:23 > DXKeeper version 17.9.9
2025-03-27 12:48:23 > App.Path : C:\DXLab\DXKeeper
2025-03-27 12:48:23 > App.exe : DXKeeper
2025-03-27 12:48:23 > Module : C:\DXLab\DXKeeper\DXKeeper.exe
2025-03-27 12:48:23 > Operating System : Windows 10 Home (64-bit) build 19045
2025-03-27 12:48:23 > Locale ID : 1033 (0x409)
2025-03-27 12:48:23 > ANSI CodePage : 1252
2025-03-27 12:48:23 > OEM CodePage : 437
2025-03-27 12:48:23 > Country : United States
2025-03-27 12:48:23 > Language : English
2025-03-27 12:48:23 > DecimalSeparator : . <46><0>
2025-03-27 12:48:23 > ThousandSeparator : , <44><0>
2025-03-27 12:48:23 > DXLab Apps : [CC,DXV]
2025-03-27 17:55:07 > Monitors : 1
2025-03-27 17:55:07 > Monitor 1
2025-03-27 17:55:07 > width : 1920
2025-03-27 17:55:07 > height : 1080
2025-03-27 17:55:07 > dimensions : (0, 0)-(1920, 1080)
2025-03-27 17:55:07.212 > program error 3078 in module DXLogModule.OpenSubdivisionPrimary theDXCC = 118: The Microsoft Jet database engine cannot find the input table or query 'Primary_118'. Make sure it exists and that its name is spelled correctly.

Is there anything I need to check or do to keep it from appearing?


+ That error message indicates that DXKeeper's Primary Subdivision Database has been corrupted. Since DXKeeper only reads from this database -- it never makes changes -- this can only be the result of a failure in your system.

+ To obtain a fresh copy of the Primary Subdivision Database,

1. terminate DXKeeper

2. in DXKeeper's Databases folder, delete the file

PrimarySubdivisionDatabase.mdb

3. download the self-extracting executable from



and run it; direct it to extract its contents - the file

PrimarySubdivisionDatabase.mdb

into DXKeeper's Databases folder

4. start DXKeeper

73,

Dave, AA6YQ


Re: Graphics cards and Monitors for the shack/ DXLab

 

Regarding Spot collector hardware needs, I think they relate to the motherboard hardware and not to the graphics card unless the graphics card uses motherboard resources and then a limitation in resources could affect the graphics system and display capabilities (probably on low end systems) when under heavy loads.??

Yes?

Rich, NU6T


On Thu, Mar 27, 2025 at 10:49?AM Dave AA6YQ via <aa6yq=[email protected]> wrote:
+ AA6YQ comments below
is SpotCollector multi-processor or multi-core aware?
+ I did not design SpotCollector or any other DXLab component to detect and exploit the presence of multiple cores. However, testing revealed that SpotCollector's performance does increase if 2 or 3 cores are assigned - likely due to parallelism in the Jet database engine. If you have SpotCollector configured to direct PropView to generate a propagation forecast for each new Spot Database Entry, then assigning PropView to a core would likely also improve performance,?

+ See the Hardware Capabilities section of



? ? ?73,

? ? ? ? ? ? Dave, AA6YQ



--
Richard Hill


Error log Text

 

I keep getting this error message in DXKeeper.
?
2025-03-26 23:37:04.549 > Common.Terminate: DXKeeper shutdown
2025-03-27 12:48:23 ? ? > DXKeeper version 17.9.9
2025-03-27 12:48:23 ? ? > App.Path ? ? ? ? ?: C:\DXLab\DXKeeper
2025-03-27 12:48:23 ? ? > App.exe ? ? ? ? ? : DXKeeper
2025-03-27 12:48:23 ? ? > Module ? ? ? ? ? ?: C:\DXLab\DXKeeper\DXKeeper.exe
2025-03-27 12:48:23 ? ? > Operating System ?: Windows 10 Home (64-bit) build 19045
2025-03-27 12:48:23 ? ? > Locale ID ? ? ? ? : 1033 (0x409)
2025-03-27 12:48:23 ? ? > ANSI CodePage ? ? : 1252
2025-03-27 12:48:23 ? ? > OEM CodePage ? ? ?: 437
2025-03-27 12:48:23 ? ? > Country ? ? ? ? ? : United States
2025-03-27 12:48:23 ? ? > Language ? ? ? ? ?: English
2025-03-27 12:48:23 ? ? > DecimalSeparator ?: . <46><0>
2025-03-27 12:48:23 ? ? > ThousandSeparator : , <44><0>
2025-03-27 12:48:23 ? ? > DXLab Apps ? ? ? ?: [CC,DXV]
2025-03-27 17:55:07 ? ? > Monitors ? ? ? ? ?: 1
2025-03-27 17:55:07 ? ? > Monitor 1
2025-03-27 17:55:07 ? ? > ? ?width ? ? ? ? ?: 1920
2025-03-27 17:55:07 ? ? > ? ?height ? ? ? ? : 1080
2025-03-27 17:55:07 ? ? > ? ?dimensions ? ? : (0, 0)-(1920, 1080)
2025-03-27 17:55:07.212 > program error 3078 in module DXLogModule.OpenSubdivisionPrimary theDXCC = 118: The Microsoft Jet database engine cannot find the input table or query 'Primary_118'. ?Make sure it exists and that its name is spelled correctly.
?
Is there anything I need to check or do to keep it from appearing?
?
Thanks,
?
Gerald, WA9GON


Re: Graphics cards and Monitors for the shack/ DXLab

 

+ AA6YQ comments below
is SpotCollector multi-processor or multi-core aware?
+ I did not design SpotCollector or any other DXLab component to detect and exploit the presence of multiple cores. However, testing revealed that SpotCollector's performance does increase if 2 or 3 cores are assigned - likely due to parallelism in the Jet database engine. If you have SpotCollector configured to direct PropView to generate a propagation forecast for each new Spot Database Entry, then assigning PropView to a core would likely also improve performance,?

+ See the Hardware Capabilities section of



? ? ?73,

? ? ? ? ? ? Dave, AA6YQ


Re: LotW/eQSL

 

+ AA6YQ comments below
It seem the if I use the Capture window in DXK the LoTW and eQSL colors come across fine.? However, if the QSO is entered vie WSJT-X the colors are ignored and remain white.
+ There are two supported forms of interoperation between WSJT-X and DXLab: direct, and via JTAlert. Both forms provide options that direct DXKeeper to perform eQSL and LoTW database lookups when logging a new QSO. See



? ? ?73,

? ? ? ? ? ? ?Dave, AA6YQ


Re: LotW/eQSL

 

I might have spoken prematurely.


It seem the if I use the Capture window in DXK the LoTW and eQSL colors come across fine.? However, if the QSO is entered vie WSJT-X the colors are ignored and remain white.


-Kurt, KR2C

On 3/25/2025 10:20 AM, Kurt Cathcart wrote:
Thanks Dave


It was the databases in DXView the caused the problem.


-Kurt, KR2C

On 3/24/2025 9:04 PM, Dave AA6YQ wrote:
+ AA6YQ comments below

That's ticked,? Any other suggestions?

+ Yes: click the Colors button in the same pane and confirm that the Log Page Display background colors are set correctly.

+ Also visit DXView's Databases tab to confirm that you have the eQSL and LoTW databases loaded.

????? 73,

???????????? Dave, AA6YQ








Re: Tom NY4I is the new steward of the N1MM-DXKeeper Gateway

 

So Tom, a related question.? What about the case where I would like log requests going to DXKeeper on one machine to also be logged in the database of a primary copy of DXKeeper on another? In this case, you'd need to intercept a request to log directed at DXKeeper and redirect or copy it to another instance of DXKeeper on another computer.? IS this possible?? I wrote a quick and dirty Python program to harvest additions to the WSJTX adi file on the second computer and send that (UDP command request) to the primary DXKeeper, but that seems a bit hokey and is limited to WSJTX QSOs.? What I would like is to have the appearance of a single database on one machine with updates from other machines running in parallel.
?
Thoughts?
?
Joe/WQ6Q


Re: Tom NY4I is the new steward of the N1MM-DXKeeper Gateway

 

Use port 12060 and the latest gateway.

Tom NY4I
813-205-6388
ny4i@...


Re: Graphics cards and Monitors for the shack/ DXLab

 

moreover, I have seen that all running processes have affinity set to all CPUs.

73 de
Salvatore (I4FYV)


Re: Graphics cards and Monitors for the shack/ DXLab

 

correction:

the Task Manager still has the Affinity option, but it is accessible only in "Details" view.

Sorry.

73 de
Salvatore (I4FYV)


Re: Graphics cards and Monitors for the shack/ DXLab

 

hello,

SpotCollector alone can make good use of 3 cores
is SpotCollector multi-processor or multi-core aware?

I have found a link on a very old article here,



where the author writes:

"However, we have run into a few instances where 32-bit applications run with no issues on single processor systems, but fail to run, or perform poorly on multiprocessor systems."

I don't know if this assumption could still be valid. And unfortunately, Microsoft has removed the "Affinity" option in Windows 10 and 11 task manager.

73 de
Salvatore (I4FYV)


Re: Graphics cards and Monitors for the shack/ DXLab

 

I'm reviewing various graphics cards and seeing many costing well over $300-400.? I'm also seeing various 4K NUC mini computers?with 3-4 video outputs (HDMI) that are apparently 4K or even 8K and advertised?for video production or high end gaming.? Upgrading may not be cost effective, grin.

Rich, NU6T

On Wed, Mar 26, 2025 at 5:00?PM Joe Subich, W4TV via <lists=[email protected]> wrote:

The other argument against buying the absolute high end CPU (more CPU
than necessary for the purpose) is that Moore's Law still holds when
it comes to CPU performance vs. price.? By the time the user's needs
even come close to the capability of the CPU the price of that CPU
will drop significantly or newer CPUs will be available with major
advances in capability.

A typical lifetime of computer technology is something on the order
of six years - or perhaps two major versions of Windows.? Purchasing
capability beyond that lifetime is a waste of time.? At every 6-8
year point I have replaced computers with new systems having four
times the performance (MOps/Sec, RAM, etc.) the previous system at
half the cost of the "obsolete" system.

Today, with systems featuring CPUs at the median ~24,000 CPU Mark
level available for between $350 and $500, it makes no sense to
pay three to four times as much for the highest performance CPUs
that show CPU Marks of ~28,000-29,000.

73,

? ? ... Joe, W4TV

On 2025-03-26 5:57 PM, Dave AA6YQ wrote:
> + AA6YQ comments below
>
>>
>> I've followed this thread with some interest. It seems to me that an
>> important feature of computer, monitor, and graphics cards purchases is
>> missing.
>>
>> I believe one should attempt purchases that reflect more what demands on
>> these devices are likely to be in the future than what they might be in
>> the present. While the future is unknown, it seems very likely that
>> demands for more memory, more sophisticated and faster processors will be
>> the future as they have been in the past. High-end graphics cards are a
>> requirement in the AI world we'll be living in well before you will want
>> to retire today's computer purchase.
>>
>> Even if you can afford a computer used exclusively for amateur radio you
>> are likely to benefit from buying the? most powerful hardware you can
>> afford rather than buying what's needed for using the software hams are
>> using today.
>
> + That's a slippery slope:
>
> 1. It's not clear that high-end graphics cards will be a requirement for using AI. Yes, the development and training of Large Language Models (LLMs) currently involves the heavy use of graphics processing units (GPUs) because GPUs can rapidly execute the matrix multiplication operations employed in neural networks. However, exploiting LLMs - which is what hams would likely do - does not require such computation. Furthermore, the DeepSeek LLM demonstrates that the race for market share led many LLM developers to forgo optimizations that enable training with significantly less computation.
>
> 2. With respect to CPUs, plotting available CPU models on a price vs. performance graph generally reveals a suite spot. At the high end, paying an extra 25% to get 10% more performance makes little sense.? Larger CPU caches are worthwhile. More CPU cores will definitely make DXLab applications run faster. As described in the "Hardware Capabilities" section of
>
>
>
> SpotCollector alone can make good use of 3 cores. One core for each additional application you expect to consume CPU cycles in parallel is a reasonable rule of thumb. Don't count the DXLab Launcher, as it only consumes significant cycles during upgrades. You won't need 256 cores unless you're going into weather forecasting.
>
> 3. With respect to RAM, more is always better. While 32 GB may be more than sufficient today, a motherboard with 32GB that is expandible to 64GB when you need it would be preferable.
>
> 4. Secondary storage - whether solid state or rotating - is easy to expand as your needs evolve. The 4 terabyte rotating drive I use for local backup connects to my laptop via USB 3.2 and cost $112! No, it won't meet my needs if I start DXing for dark matter and begin recording and analyzing data from radio telescopes, but likely other upgrades will be required if I head in that direction.
>
> 73,
>
> Dave, AA6YQ
>









--
Richard Hill