after upgrading from 2.24 to 2.27 something is wrong:
the [lastqso.adi] - file has all the right data, including State en CQzone.
When importing (UDP) the CQzone is set to default value instead of the
CQzone that is imported from [lastqso.adi].
Examples:
VK6xx CQzone 29 is written as CQzone30 (default for VK)
(W7xx CQzone 03 is written as CQzone 5 (default for W)
Same for all other multi-zone countries like VE and RA9.
When entering a QSO manually the CQzone is auto-populated
correctly by use of lookup in QRZ.
This problem did NOT occur with previous versions I used...
Do I overlook an obvious setting or is this a bug?
73 PA3BUD
v2.27 autopopulates wrong CQZ
Re: v2.27 autopopulates wrong CQZ
Bud,
Check your QRZ.com membership level. You need to at least have an XML Data membership to get the 'detailed' information from QRZ.com ... Looking at your QRZ page it does not indicate that you currently have any QRZ level of membership.
Or you could try HamQTH which is free of charge.
Check your QRZ.com membership level. You need to at least have an XML Data membership to get the 'detailed' information from QRZ.com ... Looking at your QRZ page it does not indicate that you currently have any QRZ level of membership.
Or you could try HamQTH which is free of charge.
73 - Nolan Kienitz - KI5IO
Plano, TX
Plano, TX
Re: v2.27 autopopulates wrong CQZ
Nolan,
Thanks for replying.
If that is the case: how come that in previous versions
(last one used was 2.24) everything was just working fine?
And yes: I have a membership at QRZ.com…
73 Bud
Thanks for replying.
If that is the case: how come that in previous versions
(last one used was 2.24) everything was just working fine?
And yes: I have a membership at QRZ.com…
73 Bud
Re: v2.27 autopopulates wrong CQZ
Bud,
If you have a QRZ.com membership (at least XML) then all the data is available to you. It's just that when I looked your callsign up on QRZ your profile page usually has some banner indicating your QRZ membership level. I'm guessing something is amiss at QRZ with respect to that.
Now ... to your issue I was again reading your original post and you noted you were doing UDP imports.
From that comment I'm guessing those inputs are from WSJTx, JTDX, JTAlert, or Griditracker ???
So -- Data coming in via UDP is not correct, but if you enter the same call "manually" the data is correct?
Assuming that is mostly a correct view of your experience I'm going to guess that you did not thoroughly read the Release Notes for the new update. Those Release Notes have stated that you have to DELETE all your current UDP Incoming Settings and BUILD new ones. You cannot simply make changes to what you have installed. You have to delete them and then rebuild them.
Lele put in a whole new process that handles the UDP situation much better.
Making those changes will resolve your data difference issues between UDP incoming and manual entry.
I've linked a PDF that Lele has also posted elsewhere on the Forum that may also help.
https://www.log4om.com/l4ong/usermanual ... ith_JT.pdf
Here is a link that addresses the requirement to Delete and Rebuilt the UDP Inbound Connections:
https://forum.log4om.com/viewtopic.php?p=43147#p43147
If you have a QRZ.com membership (at least XML) then all the data is available to you. It's just that when I looked your callsign up on QRZ your profile page usually has some banner indicating your QRZ membership level. I'm guessing something is amiss at QRZ with respect to that.
Now ... to your issue I was again reading your original post and you noted you were doing UDP imports.
From that comment I'm guessing those inputs are from WSJTx, JTDX, JTAlert, or Griditracker ???
So -- Data coming in via UDP is not correct, but if you enter the same call "manually" the data is correct?
Assuming that is mostly a correct view of your experience I'm going to guess that you did not thoroughly read the Release Notes for the new update. Those Release Notes have stated that you have to DELETE all your current UDP Incoming Settings and BUILD new ones. You cannot simply make changes to what you have installed. You have to delete them and then rebuild them.
Lele put in a whole new process that handles the UDP situation much better.
Making those changes will resolve your data difference issues between UDP incoming and manual entry.
I've linked a PDF that Lele has also posted elsewhere on the Forum that may also help.
https://www.log4om.com/l4ong/usermanual ... ith_JT.pdf
Here is a link that addresses the requirement to Delete and Rebuilt the UDP Inbound Connections:
https://forum.log4om.com/viewtopic.php?p=43147#p43147
73 - Nolan Kienitz - KI5IO
Plano, TX
Plano, TX
Re: v2.27 autopopulates wrong CQZ
Nolan,
You might be spot on… As I said: I probably overlooked
something simple. Like “not reading all relevant info”
and just do an upgrade like so many times before.
Case #2 in the forwarded PDF holds the clue I think.
When back home am gonna rebuild the UDP-structure.
Thanks for putting me on the right track!
73 PA3BUD
You might be spot on… As I said: I probably overlooked
something simple. Like “not reading all relevant info”
and just do an upgrade like so many times before.
Case #2 in the forwarded PDF holds the clue I think.
When back home am gonna rebuild the UDP-structure.
Thanks for putting me on the right track!
73 PA3BUD