Page 2 of 2
Re: Problems with callsign search and MAP locator is not correct
Posted: 20 Mar 2025, 04:34
by bh2rmx
py8ml wrote: 20 Mar 2025, 02:31
Good evening everyone!
I discovered the "problem" and it was a mistake on my part.
I had changed the login password for the QRZ.com account and did not change it in Log4OM.
So, now everything is fine!
BH2RMX,
Test in LOG4OM if your QRZ password is correct.
In your last "print! I see that you did not mark the QRZ.com option as "Primary Source".
First you must do this, and then enter the login and password information.
To see if everything is correct, after you have done this click on the box to the right of the "QRZ.COM" line and see if the "green check" appears (as it appears in the "HAMQTH" line).
I hope I have contributed and I thank everyone who tried to help me!
Thank you for your reply. I followed your instructions. But the result did not change. Look at my screenshot. In addition, 4-digit and 6-digit grid display, is your display 6-digit? Is your recorded grid data correct? My software shows PN11, which is wrong.
Re: Problems with callsign search and MAP locator is not correct
Posted: 20 Mar 2025, 19:19
by py8ml
Your QRZ account is a "paid" account. If it is not, you will not get the correct information. Oh yes, check QRZ.COM as "Primary source" on the right side of the screen where you marked with the red arrow
Re: Problems with callsign search and MAP locator is not correct
Posted: 21 Mar 2025, 11:54
by py8ml
Hi BH2RMX,
Here's how my screen looks when I enter your Callsign into my log4. Everything is correct.
So this makes me think that what's happening is that your QRZ.COM account is not a paid account and maybe that's why the integration with Log4OM isn't perfect.
Am I correct?
Re: Problems with callsign search and MAP locator is not correct
Posted: 21 Mar 2025, 12:59
by G4POP
Its more likely that the grid reference is being received from an external program like WSJT and we dont change a users incoming data because we consider that that is the information he wants recording.
Its possible that we might overwrite the grid if 'Use external data' is selected in the WSJT UDP connection I dont remember.
However as you displayed Log4OM is providing correct lookup info as long as the user is a paid XML subscriber to QRZ which BH2RMX is NOT, he is a 'Ham member' not XML subscriber.
Re: Problems with callsign search and MAP locator is not correct
Posted: 23 Mar 2025, 08:42
by bh2rmx
py8ml wrote: 21 Mar 2025, 11:54
Hi BH2RMX,
Here's how my screen looks when I enter your Callsign into my log4. Everything is correct.
So this makes me think that what's happening is that your QRZ.COM account is not a paid account and maybe that's why the integration with Log4OM isn't perfect.
Am I correct?
Thanks PY8ML,You made me understand completely
Re: Problems with callsign search and MAP locator is not correct
Posted: 05 May 2025, 03:56
by py8ml
You're welcome!
73!