+ AA6YQ comments below

I noticed exactly the same thing on May 15th as you described above.
Nothing was changed in the DXL settings.
Even more, PV was difficult because <> was not reachable (now, that happens more often).

+ Make sure that your anti-malware is configured to enable PropView to access the internet.

This morning (May 16th) still the same problems. Tonight 17:00 UTC) everything seems to be normal. Hopefully for you too.
On May 14th I did see a cumulative update for my W10 22H2 x64 (KB5058379) but that will not be the cause I think.

Sometimes the problems are solved by themselves: we have to be patient...

+ I strongly prefer that users immediately report problematic behavior, rather than wait on the infinitesimally small chance that the problem will solve itself. Waiting to report a problem can deprive us of critical evidence needed to identify the root cause of the misbehavior.

73,

Dave, AA6YQ

+ AA6YQ comments below

This on a new Win11 PC with a new installation of DXLabs software.

+ So both your hardware and you software changed.

+ To enable me to see what's going on, please do the following:

1. on Pathfinder's Configuration window, check the "Log debugging info" box

2. terminate Pathfinder

3. start Pathfinder, and wait for it to initiate

4. direct Pathfinder to lookup my callsign in QRZ

5. on Pathfinder's Configuration window, uncheck the "Log debugging info" box

6. attach the errorlog.txt file from your Pathfinder folder to an email message, and send that message to me via

aa6yq (at) ambersoft.com

73,

Dave, AA6YQ

I have tested the S50CLX POTA/SOTA cluster describe below with SpotCollector, and confirmed that POTA tags are correctly captured. There were no SOTA tags spotted during my test.

73,

Dave, AA6YQ

Maybe it would be interesting for users of your programme to improve the reception of telnet DXCluster spots for interested group of users of POTA and SOTA programme. On the S50CLX DXCluster I have implemented the integration of spots that are not part of the classical telnet DXCluster network. More in my note below. The user of your programme would thus have the possibility to select in the programme the reception of specific spots via a button, with predefined commands to be sent to the S50CLX DXCluster after a successful connection. Sorting, searching by reference ... etc is a matter of implementing such spots into DXLab software. The idea for the buttons are:

1. POTA ONLY spots -> command executed: ACC/SPOTS INFO -POTA-

2. SOTA ONLY spots -> command executed: ACC/SPOTS INFO -SOTA-

3. BOTH POTA&SOTA spots -> command executed: ACC/SPOTS INFO -POTA- OR INFO -SOTA-

4. S50CLX CLUSTER DEFAULT (all spots) -> command executed: CLEAR/SPOTS ALL

A connection via telnet protocol to S50CLX s50clx.infrax.si:41112 which is a completely free service is required to receive such tagged POTA/SOTA spots.


Good luck,

73s Dan S50U


**
POTA and SOTA enthusiasts!

POTA (Parks On The Air) and SOTA (Summits On The Air) are internationally renowned programmes. They encourage licensed radio amateurs to operate outdoors in nature parks or on mountain peaks. Operators making contacts in parks or on summits are called activators, and the other operators who contact them are hunters.

On the S50CLX telnet DXCluster I implemented the collection of spots from POTA and SOTA that are not part of the classical telnet DXCluster network (potaapp and sotawatch). Such spots are tagged with [-POTA-] and [-SOTA-] respectively. In the comment field a spot tagged as such carries:

POTA:
- International POTA reference number, example: SI-0831
- Mode of operation, example: CW
- POTA reference name, example: Preval Vrh Ravni

SOTA:
- International SOTA peak reference number; example: S5/CP-002
- Mode of operation; example: SSB
- SOTA summit name, altitude, points; example: Porezen, 1630m, 8 points

With the right settings, the exact DX spots you want can be received and this is achieved using the filters below. To change an existing filter, simply overwrite it with a new command. Each command (BOLD formatted text) must be entered on a new line, confirm the entry by pressing ENTER.

- for receiving only POTA spots, command: ACC/SPOTS INFO -POTA-

- for receive only SOTA spots, command: ACC/SPOTS INFO -SOTA-

- for receiving POTA and SOTA spots, command: ACC/SPOTS INFO -POTA- OR INFO -SOTA-

The CLEAR/SPOTS ALL command removes all set filters and the S50CLX passes us all SOTA, POTA, DXCluster and optionally RBN (SET/SKIMMER <mode>) spots.

In cases where you do not want to receive POTA and SOTA spots e.g. in a contests, use the command as the first filter before all others REJ/SPOTS 1 INFO -POTA- OR INFO -SOTA-

Spot forwarding is based on the DXSpider DXCluster software validation and normalisation algorithm, rejecting duplicates spots and ensuring quality spots in the face of increasingly frequent malicious attacks on global amateur radio DXCluster network.

The S50CLX DXCluster can be reached via telnet at: s50clx.infrax.si port 41112

My small contribution to the promotion of outdoor activities in POTA and SOTA hamradio programmes. :-)

Spread the news, thanks
73 Danilo S50U sys S50CLX DXCluster

p.s.
The information is also published on the Radioklub Cerkno S50E website


--
S50CLX DX Cluster <>

开云体育

Dave,
This on a new Win11 PC with a new installation of DXLabs software.? I followed the wiki to move my setup to the new computer and everything is working except for callsign lookup.? I checked the Pathfinder settings on my old computer and they are the same as on the new computer.
George, W2GS

开云体育

When I use Pathfinder to lookup a callsign I get the Pathfinder not logged into QRZ.? But I have verified that I am logged in.? I can click on the Pathfinder icon in the Tray and it opens and when I click on QRZ it looks up the callsign.? My password and Automatic look up filled in and checked.? Any recommendations?



73, George
W2GS

Thank you. Problem solved.

+ How did you solve it?

73,

Dave, AA6YQ