+ AA6YQ comments below

It just happened. [CC, DXK, PF, DXV] appear in the title bar of SpotCollector, where I double clicked on A75L.

+ Thanks; that shows that SpotCollector is connected to Pathfinder, eliminating one possible cause of the behavior you report.

This shows in the Pathfinder title bar: "Pathfinder 5.3.3 : searching QRZ for K3BB"
I don't recall having double clicking on K3BB previously, but perhaps I did.

+ That implies that Pathfinder was instructed to perform a QRZ search for K3BB, but never received the expected response -- possibly due to the recent changes made to QRZ.com. Please switch to the new version of Pathfinder that I sent you.

73,

Dave, AA6YQ

Dave,

It just happened. [CC, DXK, PF, DXV] appear in the title bar of SpotCollector, where I double clicked on A75L.

This shows in the Pathfinder title bar: "Pathfinder 5.3.3 : searching QRZ for K3BB"
I don't recall having double clicking on K3BB previously, but perhaps I did.
--
Jim McPhee
Placitas, NM
W5ABA

+ AA6YQ comments below

Jim i've seen a similar case.

I use the "Free" version of QRZ.com, not XML. Shurely i was logged in at QRZ.


If PathFinder did not respond to my "Lookup" or " CBA", i just clicked on the <STOP > in upper right corner of QRZ page.

Not closing and reopening PF as you did.


Then i clicked again on the wanted Callsign in SC, hit "lookup"and then PF (QRZ) populated normally.

However, minutes later it happened again,he same way, with the following wanted Callsign. I know Dave is investigating.

+ QRZ recently made changes to QRZ.com that can cause Pathfinder to wait forever for the information it requested -- until you click on its Stop button. I have created a new version of Pathfinder that compensates for these changes; Eddy ON5JK and several other users are testing this new version. I have sent the new version to Jim W5ABA to see if it corrects the behavior he has reported.

73,

Dave, AA6YQ

Thanks Dave. I will do as you suggested the next time it occurs.

--
Jim McPhee
Placitas, NM
W5ABA

Jim i've seen a similar case.

I use the "Free" version of QRZ.com, not XML. Shurely i was logged in at QRZ.

If PathFinder did not respond to my "Lookup" or " CBA", i just clicked on the <STOP > in upper right corner of QRZ page.

Not closing and reopening PF as you did.

Then i clicked again on the wanted Callsign in SC, hit "lookup"and then PF (QRZ) populated normally.

However, minutes later it happened again,he same way, with the following wanted Callsign. I know Dave is investigating.

Eddy ON5JK

+ AA6YQ comments below

This really is not a big deal, but if there is a solution I'd like to implement it.

For several months now when I click on a call sign in Spotcollector or Commander's Bandspread, DXView and DXKeeper Capture windows update to reflect that new call sign, and my TS-890 will immediately QSY, but Pathfinder does not update.

+ Debugging a problem that first appeared months ago is more difficult, because you are unlikely to remember what changes you made to your hardware and software around that time. When incorrect behavior occurs, please report it right away.

I then close and reopen Pathfinder and it works fine, until the next time that it doesn't.

+ The next time this situation occurs, immediately examine the title bar of the DXLab application in which double-clicking a callsign did not trigger a lookup in Pathfinder; what letters appear between the square brackets?

73,

Dave, AA6YQ

This really is not a big deal, but if there is a solution I'd like to implement it.

For several months now when I click on a call sign in Spotcollector or Commander's Bandspread, DXView and DXKeeper Capture windows update to reflect that new call sign, and my TS-890 will immediately QSY, but Pathfinder does not update. I then close and reopen Pathfinder and it works fine, until the next time that it doesn't.

Any idea what could be causing this behavior?

Dave, I emailed the Pathfinder error log to you.
--
Jim McPhee
Placitas, NM
W5ABA