Incorrect USA CQ Zones
Posted: 03 Jan 2024, 17:19
Hi
Using 2.30.1 build on several machines, several callsigns
CQ Zones appear to be getting logged incorrectly, compared with QRZ as an example
KN6QJW Log4Om as Zone 5 QRZ Zone 4 Screen shot attached
As it was an event call I did not have Info providers set and running with Monitor Adif file
I am running Adif monitor for the event call and normally use this in my call
In offline testing when I logged the same calls or similar calls it logged in Log4OM incorrect Zone, this was tried with several calls from several USA zones, I then added QRZ to my info providers and also using UDP 2237 and update info from external and this logged Zone correctly, but if update CQ-ITU zone is not selected the incorrect zone is logged.
I created different instances, new database and the same occured
I cannot remember this being an issue in previous builds, this was noticed as Dx marathon Zones were checked and observation
Anyone else seeing this issue?
Have a great night
Using 2.30.1 build on several machines, several callsigns
CQ Zones appear to be getting logged incorrectly, compared with QRZ as an example
KN6QJW Log4Om as Zone 5 QRZ Zone 4 Screen shot attached
As it was an event call I did not have Info providers set and running with Monitor Adif file
I am running Adif monitor for the event call and normally use this in my call
In offline testing when I logged the same calls or similar calls it logged in Log4OM incorrect Zone, this was tried with several calls from several USA zones, I then added QRZ to my info providers and also using UDP 2237 and update info from external and this logged Zone correctly, but if update CQ-ITU zone is not selected the incorrect zone is logged.
I created different instances, new database and the same occured
I cannot remember this being an issue in previous builds, this was noticed as Dx marathon Zones were checked and observation
Anyone else seeing this issue?
Have a great night