Page 1 of 1

QSO info from qrz.com

Posted: Wed 7. Oct 2020, 10:06
by James
Hello,

With version 5:

1.- When supplementing QSO data with information from qrz.com, the information is confusing. At least 2 lines appear for each contact, many times in red.

2.- In the station information window, the information often does not appear if you retrieve information from qrz.com. This I cannot reproduce because at the moment it does not happen to me, it is random.
I thought that all this was a specific problem of qrz.com and I have waited 1 day to report it, but it remains the same.
It happens to me since I installed version 5 of RumlogNG.
Does it happen to someone else?

Attached screenshots of point 1.
A screenshot is about a single callsign and what happens is that a first line with the callsign only appears and the other line appears the data Ok.
and the other screenshot is a 4 callsign query.

By the way, a very good option that the QSOs are incorporated automatically from N1MM.
I have tested it and it will really be a very useful help for large contests.
Captura-1.png
Captura-2.png
73,

Re: QSO info from qrz.com

Posted: Wed 7. Oct 2020, 13:44
by DL2RUM
1.- When supplementing QSO data with information from qrz.com, the information is confusing.
Confirmed. Looks really crazy, I have to check. It seems HamQTH is not affected.

Re: QSO info from qrz.com

Posted: Wed 7. Oct 2020, 13:54
by James
No, QTH seems not to be affected, check it out.

Thank you,

Re: QSO info from qrz.com

Posted: Wed 7. Oct 2020, 14:38
by DL2RUM

Re: QSO info from qrz.com

Posted: Wed 7. Oct 2020, 14:57
by James
Perfect and fast, now yes.

----------------------------------------------------------------------------

By the way, "QSO upload utility" has stopped working for me.
I always have "Listen to UDP N1MM contact" activated and I update perfectly in qrz, HRDlog and Hamqth (Clublog and eQSL performed directly in RumlogNG).
I thought it was because I have the RumlogNG option "QSO received from N1MM" activated, but it has nothing to do with it, I think.


Thanks.