Please excuse the late response.
Perhaps your
DXAtlas issue is actually you monitor’s configuration—too many pixels per inch..
This article may help.
?
73,
Dave, w6de
?
toggle quoted message
Show quoted text
From: [email protected]
<[email protected]> On Behalf Of Craig via groups.io
Sent: 12 February, 2025 16:01
To: [email protected]
Subject: [DXLab] DXAtlas Enhancements
?
All.. is anyone aware of enhancements from DXLab / DXView to enhance DXAtlas.? For example, the QSO path on DXAtlas is hard to view with a higher resolution monitor being able to adjust the color and increase path density would be nice.?
Thanks for letting me know...? ?
|
I wouldn't want to disable that double-click - it's the quickest way to restore that progress bar window.? The real question is why does it end up ultra-minimized down in the corner of the screen in the first place, all without me moving it or doing anything else to it?? It's not off-screen, just really tiny and jammed into the lower left corner.? Its normal position, and the position it returns to after double-clicking, is near the center of the screen.
?
73,
Chris, W2PA
|
Re: QSO Path in DX Atlas?
+ AA6YQ Comments belo-w
My installation of DX Atlas v2.41 is not showing anything when running WSJTX. It is not showing the qso path. In an earlier thread on Grid Tracker, you posted a link to a screenshot of what appeared to be worked grids- I am also not seeing of my worked grids.
Is it possible I have not made the proper settings - somewhere in DXLab? or specifically in DXView? Or are there corresponding settings that have to be made in DX Atlas.
So far I haven't seen any of what others see in the? DX Atlas/WSJTX pairing.
+ There is no "DX Atlas /WSJTX pairing". + DXView can interoperate with SpotCollector to display the locations of stations in its Spot Database and the stations that spotted those stations. If you have enabled interoperation between DXLab and WSJT-X, then the Spot Database will include stations decoded by WSJT-X: https://www.dxlabsuite.com/dxlabwiki/GettingStartedwithK1JTModes + You can configure DXView to display the locations of these stations and their spotters on its built-in world map, on Google Earth, or by following these instructions to display them on the DX Atlas map: + You can configure DXView to display the locations of your logged QSOs, either on its built-in world map or by following these instructions to display them on the DX Atlas map: + You can configure DXView to display your worked and confirmed grid squares on the DX Atlas map by following these instructions: + All of the above articles are accessible by searching + for DX Atlas. ? ? ?73, ? ? ? ? ? ? ?Dave,; AA6YQ
?
|
Re: Cannot get Commander to Connect to SDR
+ AA6YQ comments below
PS Similarly, I can not click on spots in SC and it automatically changes the frequency on the Flex and of course the mode.
+ Are active callsigns displayed on SmartSDR's Spectrum-Waterfall? ? ? ? 73, ? ? ? ? ? ? ?Dave, AA6YQ
|
Re: QSO Path in DX Atlas?
Paul, in DX Altas are you telling it to show grids? ?There is a menu item that looks like this: #. ?Click it and a drop-down will appear with the option to show grids.
toggle quoted message
Show quoted text
On Feb 15, 2025, at 07:29, w2eck via groups.io <eckerpw@...> wrote:
My installation of DX Atlas v2.41 is not showing anything when running WSJTX. It is not showing the qso path. In an earlier thread on Grid Tracker, you posted a link to a screenshot of what appeared to be worked grids- I am also not seeing of my worked grids.
Is it possible I have not made the proper settings - somewhere in DXLab? or specifically in DXView? Or are there corresponding settings that have to be made in DX Atlas.
So far I haven't seen any of what others see in the? DX Atlas/WSJTX pairing.
?
73 and tnx
?
Paul w2eck
|
Re: QSO Path in DX Atlas?
My installation of DX Atlas v2.41 is not showing anything when running WSJTX. It is not showing the qso path. In an earlier thread on Grid Tracker, you posted a link to a screenshot of what appeared to be worked grids- I am also not seeing of my worked grids.
Is it possible I have not made the proper settings - somewhere in DXLab? or specifically in DXView? Or are there corresponding settings that have to be made in DX Atlas.
So far I haven't seen any of what others see in the? DX Atlas/WSJTX pairing.
?
73 and tnx
?
Paul w2eck
|
Re: Cannot get Commander to Connect to SDR
It does, that is Smartlink provides a secure way to connect Smart SDR to a remote Flex Signature transceiver….the solution to our problem was to connect DX Commander by CAT and not by IP address and Port….duh, just as the instructions say to do…All is solved. ?TY all for your help...
toggle quoted message
Show quoted text
On Feb 14, 2025, at 11:22?PM, Dave AA6YQ via groups.io <aa6yq@...> wrote:
+ AA6YQ comments below
This is an alternative method that uses Flex SmartSDR CAT and is therefore more secure.?
+ If Commander is controlling a Flex Signature transceiver via "SmartSDR CAT", it's treating the transceiver functionality as if it were? Kenwood TS-2000. For example, active callsigns reported by SpotCollector or decoded by WSJT-X will not appear on the SmartSDR's spectrum-waterfall display. + I had assumed that SmartLink provides a secure way to connect SmartSDR to a remote Flex Signature transceiver, which would provide full functionality in a secure manner. Is this not the case? ? ? 73, ? ? ? ? ? ? ? Dave, AA6YQ ? ? ?
|
Re: Cannot get Commander to Connect to SDR
PS Similarly, I can not click on spots in SC and it automatically changes the frequency on the Flex and of course the mode. ?Also, I am now able on FT8 to work a station, and click on a pop up to log it, and it is directly logged into DX Keeper! ?Life is good again!
Mark
toggle quoted message
Show quoted text
On Feb 15, 2025, at 7:41?AM, Mark Wohlschlegel <mvwohlschlegel@...> wrote:
Larry, got it working perfect through CAT connection exactly per Dave’s instructions, duh!
Start?SmartSDR Start?SmartSDR CAT configure it as described in its? - note the virtual serial COM port that it creates?
select an available Flex Signature transceiver, and click the green?Connect?button? in the small?SmartSDR CAT?window that appears, select the entry for the Serial port created in the previous step?
In the?Primary CAT Serial Port?panel on the?Ports?tab of Commander's Commander's Configuration window,? set the?Port?selector to the virtual COM port created by?SmartSDR CAT?in step 2a above? set the?Baud?selector to?57600 set the?Word?selector to?8 set the?Parity?selector to?none set the?Stop?selector to?2 set the?DTR?selector to?Off set the?RTS?selector to?Off
On the?General?tab of Commander's Configuration window,? set the?Radio?panel's?Model?selector to?FlexCAT?(near the bottom of the list of available models)? set the?Command interval?to?50 check the?Interrogation?box?
On Feb 14, 2025, at 7:42?PM, Larry Benoit via groups.io <lbenoit@...> wrote:
Mark,
?
Using SmartSDR CAT to obtain band data is secure via SmartLink? for remote ops, while port forwarding is by default insecure as the open port is not protected. However, you can configure your router's firewall to allow access to a specific port or range of ports only for the specific IP address or subnet assigned to your remote router.?
?
Alternatively, when I've used port forwarding for remote ops, I've usually logged into my home router to enable the external port and then disabled it when done operating.?
?
Good luck and 73,
Larry KB1VFU
?
?
?
?
?
|
Re: Cannot get Commander to Connect to SDR
Larry, got it working perfect through CAT connection exactly per Dave’s instructions, duh!
Start?SmartSDR Start?SmartSDR CAT configure it as described in its? - note the virtual serial COM port that it creates?
select an available Flex Signature transceiver, and click the green?Connect?button? in the small?SmartSDR CAT?window that appears, select the entry for the Serial port created in the previous step?
In the?Primary CAT Serial Port?panel on the?Ports?tab of Commander's Commander's Configuration window,? set the?Port?selector to the virtual COM port created by?SmartSDR CAT?in step 2a above? set the?Baud?selector to?57600 set the?Word?selector to?8 set the?Parity?selector to?none set the?Stop?selector to?2 set the?DTR?selector to?Off set the?RTS?selector to?Off
On the?General?tab of Commander's Configuration window,? set the?Radio?panel's?Model?selector to?FlexCAT?(near the bottom of the list of available models)? set the?Command interval?to?50 check the?Interrogation?box?
toggle quoted message
Show quoted text
On Feb 14, 2025, at 7:42?PM, Larry Benoit via groups.io <lbenoit@...> wrote:
Mark,
?
Using SmartSDR CAT to obtain band data is secure via SmartLink? for remote ops, while port forwarding is by default insecure as the open port is not protected. However, you can configure your router's firewall to allow access to a specific port or range of ports only for the specific IP address or subnet assigned to your remote router.?
?
Alternatively, when I've used port forwarding for remote ops, I've usually logged into my home router to enable the external port and then disabled it when done operating.?
?
Good luck and 73,
Larry KB1VFU
?
?
?
?
?
|
Re: Cannot get Commander to Connect to SDR
+ AA6YQ comments below
This is an alternative method that uses Flex SmartSDR CAT and is therefore more secure.?
+ If Commander is controlling a Flex Signature transceiver via "SmartSDR CAT", it's treating the transceiver functionality as if it were? Kenwood TS-2000. For example, active callsigns reported by SpotCollector or decoded by WSJT-X will not appear on the SmartSDR's spectrum-waterfall display. + I had assumed that SmartLink provides a secure way to connect SmartSDR to a remote Flex Signature transceiver, which would provide full functionality in a secure manner. Is this not the case? ? ? 73, ? ? ? ? ? ? ? Dave, AA6YQ ? ? ?
|
there's a defect in the Mixed section of the DX Marathon Progress Report
If you have the Mixed box checked in the "Marathon Bands & Modes" panel on the Configuration window's Awards tab, then the Progress
report generated when you click the Progress button in the "DX Marathon Challenge" panel on the Main window's "Check Progress" tab
will contain a section entitled "Mixed Analysis", with 3 subsections:
- Mixed Countries by Continent
- Mixed Score by Band
- Mixed Score by Mode
The first time you generate a DX Marathon progress report after starting DXKeeper, the analysis in all 3 sections will be correct.
However, if you generate one or more additional DX Marathon progress reports, the analyses in the "Mixed Score by Band" and "Mixed
Score by Mode" sections will be incorrect. Terminating and restarting DXKeeper will enable you to generate DX Marathon progress
report with accurate "Mixed Analysis".
The responsible defect has no adverse impact on DX Marathon submission generation. This defect has been corrected in the next
version of DXKeeper, which is in the hands of the users who reported the defect.
73,
Dave, AA6YQ
|
Re: Cannot get Commander to Connect to SDR
Mark,
?
Using SmartSDR CAT to obtain band data is secure via SmartLink? for remote ops, while port forwarding is by default insecure as the open port is not protected. However, you can configure your router's firewall to allow access to a specific port or range of ports only for the specific IP address or subnet assigned to your remote router.?
?
Alternatively, when I've used port forwarding for remote ops, I've usually logged into my home router to enable the external port and then disabled it when done operating.?
?
Good luck and 73,
Larry KB1VFU
?
?
?
?
?
|
Re: Cannot get Commander to Connect to SDR
Larry, after reading this I think I failed to mention to you that we actually have a VPN in place between home and remote site…so the router does not need any port forwarding. ?
We now have commander working one direction if you can believe that…what that means is that when I change the frequency on the flex, commander changes the frequency and tracks it. ?If I go to spot collector, and click on a spot, the commander window changes to that stations frequency and mode…HOWEVER, what we don’t have is the propogation of that information back to the radio. ?Go figure…so information from commander, or spotter does not flow back to the radio…
toggle quoted message
Show quoted text
On Feb 14, 2025, at 12:25?PM, Larry Benoit via groups.io <lbenoit@...> wrote:
Mark,
?
You said: "I have configured the General Tab within Commander Configuration with the IP Address of my home computer, and listed the IP Port as 4992." ?
?
If you operate remote this won’t work because there is no valid routing information for DX Commander to connect to the radio.? If you want to establish a direct connection to the 6500 without using SmartSDR CAT you need to enable port forwarding on your home router per this article as Dave noted:
?
Also, you need a fixed public IP address for your home router and a fixed IP address for your 6500. With this method you can specify WSJTX Radio to DX Lab Suite Commander or configure to connect to a SmartSDR CAT serial port per my previous post.?
?
Here is yet another method for remote ops:
?
1) Create a new TCP port for SmartSDR CAT (for example port 60000)
2) Configure WSJTX Radio to Flex6xxx
3) Configure WSJTX Network Server to: 127.0.0.1:60000
4) Configure DX Commander Radio to FLEXCAT (essentially the same as KENWOOD) and set Primary CAT Serial Port to a valid SmartSDR CAT port number.
?
Alternatively, I've tried setting DX Commander to a Flex 6600 and the IP address to the localhost IP address: 127.0.0.1 and the IP Port number to a valid SmartSDR CAT TCP port number, but that doesn't work. But,? it doesn't need to work, because other methods work flawlessly.?
?
73,
Larry KB1VFU
?
|
Re: QSO Path in DX Atlas?
+ AA6YQ comments below
2.41 is not a new version, it was released a year ago.
+ It's new for Paul W2ECK, as he reported in /g/DXLab/message/227832? ? ?73, ? ? ? ? ? ?Dave, AA6YQ
|
Re: QSO Path in DX Atlas?
2.41 is not a new version, it was released a year ago.
Alex
toggle quoted message
Show quoted text
On 2025-02-14 18:53, Dave AA6YQ wrote: + AA6YQ comments below
When using DXView World Map the WSJTX FT8 qso path is plotted correctly. If i enable DX Atlas map instead of the World Map, the qso path is not plotted. Is it possible to have the qso path shown in DX Atlas?
+ I just confirmed that DX Atlas version 2.3 correctly plots the QSO path.
+ Earlier, you reported here that you've just upgraded to DX Atlas version 2.41; perhaps there's been a regression in this new version.
73,
Dave, AA6YQ
|
Re: QSO Path in DX Atlas?
+ AA6YQ comments below
When using DXView World Map the WSJTX FT8 qso path is plotted correctly. If i enable DX Atlas map instead of the World Map, the qso path is not plotted. Is it possible to have the qso path shown in DX Atlas?
+ I just confirmed that DX Atlas version 2.3 correctly plots the QSO path.
+ Earlier, you reported here that you've just upgraded to DX Atlas version 2.41; perhaps there's been a regression in this new version.
73,
Dave, AA6YQ
|
+ AA6YQ comments below
When I use the 'Sync All" button on the QSL tab the resulting date and time of the LOTW QSL and QSO sync does not update to the same. The resulting report says that both were updated together. If I do them individually the dates and times will match. Is this normal or an issue?
+ The dates shown beneath the "Sync LoTW QSOs" and "Sync LoTW QSLs" buttons are unrelated: + The date shown beneath the "Sync LoTW QSOs" button is the date on which LoTW last accepted one of your QSOs, as reported the last time you invoked "Sync LoTW QSOs". + The date shown beneath the "Sync LoTW QSLs" button is the date on which LoTW last confirmed one of your QSOs, as reported the last time you invoked "Sync LoTW QSLs". ? ? ?73, ? ? ? ? ? ? Dave, AA6YQ
|
When I use the 'Sync All" button on the QSL tab the resulting date and time of the LOTW QSL and QSO sync does not update to the same. The resulting report says that both were updated together. If I do them individually the dates and times will match. Is this normal or an issue?
|
+ AA6YQ comments below
Yes I get the same behavior - I hadn't tried this before. If I double click on the tiny window the normal size window pops up with the status bar as before. It must be a Windows 11 thing.
+ Windows 10 and Windows 11 will attempt to fully expand a window if you move it too close to a border of your screen. Perhaps the behavior you report is related to that. I don't know whether it can be de-activated.
73,
Dave, AA6YQ
|
Re: Reasonable call prefilter
There have been discussions in this group about the 13 character
limitation. The supported maximum callsign length can vary in
Amateur Radio software.? However, there are known callsigns (with
and without modifiers) that are longer than 13 characters; if you
have Microsoft Access, they can easily be seen in the LoTW and eQSL
Access databases supplied in DXLabs.? The maximum size of the
Callsign field in the appropriate table (Callsigns table in LoTW,
AGCallsigns table in eQSL) is 16 characters.?
These are present in the LoTW Access database table:
EA9/EA7KMZ/QRP, JK3HFN/SO2005/3, JK3HFN/SO2005/4, VI2020STAYHOME
All 4 entries have uploaded QSO's into LoTW.? VI2020STAYHOME is a
searchable callsign on QRZ.com.
By the way, states
TQSL supports a maximum callsign length of 20 characters.?
The eQSL Access database table has more entries >= 14 characters,
several /QRP style calls, along with dual calls (call/special event
call), and several entries that would not be considered valid.?
Callsigns in the eQSL Access database look to be truncated to a
maximum 15 characters (this does not appear to be the case in the
LoTW Access database).? Take for example "EA8/OE7WGT/p/QR".? This
should be EA8/OE7WGT/p/QRP.? On the eQSL.cc web page, I can only
type up to EA8/OE7WGT/p/Q (14 characters) in the search field.? If
you enter the URL ,
and click on "See if cards waiting", you'll see several cards
waiting to be retrieved.? Therefore, eQSL supports uploading QSO's
with callsigns up to 16 characters.
The takeaway is that hams have uploaded QSO's to LoTW and eQSL with
callsigns longer than 13 characters.? It remains to be seen if there
is enough demand to increase the callsign length support in
DXKeeper.
73,
Bill
WB2RIS
On 2/11/2025 2:36 AM, Bj?rn SM7IUN
wrote:
13 seems to be a de facto standard.?
The callsign field in the Cabrillo standard is 13
characters wide.
Contest loggers like Win-Test and DXLog have the same.
Bj?rn SM7IUN
+
AA6YQ comments below
The ITU has fairly clear regulations on valid amateur
callsigns
<>
essentially limiting callsigns to Letter-number (e.g. W1, G5,
F2, etc.), Letter-letter-number (e.g., WA1, KH6, PY3, VE2,
etc.), Letter-number-number (e.g. A61, C53, E77, etc.) or
Number-letter-number (e.g., 2E1, 3B8, 4L1, 4X4, 5A1, etc.)
followed by up to four characters the last of which must be a
letter *except* in the case of half series assignments
(3DA-3DM Eswatani, 3DN-3DZ Fiji, SSA-SSM Egypt, and SSN-SSZ
Sudan) where the prefix should be *three* characters followed
by a number then a maximum of *three* characters the last of
which must be a letter.
*However* Article 19, section 3 includes language that permits
the use of callsigns with more than four characters in the
suffix "On special occasions, for temporary use".
DXKeeper permits logging callsigns of up to 13 characters (to
handle up to 7 character callsigns with a "portable" prefix or
suffix).? I could not find a reference to maximum callsign
size for SpotCollector.
For those who chase Special Event operations, what is a
reasonable
(practical) limit for the length of special event (special
occasion, temporary use) callsigns that one might encounter on
the air or see via the cluster network?? Is the 13 character
limit in DXKeeper workable (assuming there is no need for a
"portable" modifier to an already jumbo sized callsign
<G>)?
+ There have been no complaints posted here about DXKeeper's
13-character limit on callsigns.
+ SpotCollector also imposes a 13-character limit on
callsigns.
? ? ? ?73,
? ? ? ? ? ? ? Dave, AA6YQ
|
wc3w
Alex, VE3NEA
n4qwf .