I've noticed a lot of QSO's have their CQ Zone marked as "0" (Zero).
CQ Zone "0"
- G4POP
- Log4OM Alpha Team
- Posts: 10803
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: CQ Zone "0"
Providing you are using version 2.5.0.0
Export the log to ADIF
import the ADIF file with checking enabled (option 1) and with drop old log selected
That will rectify and bad zones
Export the log to ADIF
import the ADIF file with checking enabled (option 1) and with drop old log selected
That will rectify and bad zones
73 Terry G4POP
Re: CQ Zone "0"
Thanks, Terry.
I will do that, but I wonder why so many "Zone 0" suddenly are appearing. Notice my screen snip --- those are all recent QSO's within the last couple of days. Prior to 4/22 I can't find any "Zone 0", now they are commonplace.
I will do that, but I wonder why so many "Zone 0" suddenly are appearing. Notice my screen snip --- those are all recent QSO's within the last couple of days. Prior to 4/22 I can't find any "Zone 0", now they are commonplace.
Re: CQ Zone "0"
OK, I followed your procedure, Terry. (With over 85,000 QSO's in my log, it took a long time!)
It did, in fact, correct the CQ Zone from "0" to whatever was appropriate.
After the procedure was complete, I ran a few more QSO's into the log. Here is a screen clip --- as you can see, the "CQ Zone 0" issue remains.
If it means anything, these Q's were "fed" via UDP to Log4OM (V2.5) from WSJT-x. Also, this is all very recent, maybe since I upgraded to V2.5.
It did, in fact, correct the CQ Zone from "0" to whatever was appropriate.
After the procedure was complete, I ran a few more QSO's into the log. Here is a screen clip --- as you can see, the "CQ Zone 0" issue remains.
If it means anything, these Q's were "fed" via UDP to Log4OM (V2.5) from WSJT-x. Also, this is all very recent, maybe since I upgraded to V2.5.
Re: CQ Zone "0"
Log4OM V2.5.
WSJT-X V2.1
Re: CQ Zone "0"
Here might be another "clue".
When CQ Zone is recorded as "0', AND the contact is a USA station, then the ITU Zone is always recorded as "6".
When CQ Zone is recorded as "0', AND the contact is a USA station, then the ITU Zone is always recorded as "6".
Re: CQ Zone "0"
I also have noticed zone 0 for some ft8 contacts. I checked the wsjt-x log and they are zone 0 there as well. I did the adif export and import and that fixed them.
Harry
W0LS
Harry
W0LS
- DF5WW
- Log4OM Alpha Team
- Posts: 2035
- Joined: 02 May 2013, 09:49
- Location: Kraam, Rhineland Palatinate, Germany
- Contact:
Re: CQ Zone "0"
Having the same with JTDX. After a search for CQ Zone = 0 it shows me 67 of them. All coming from
JTDX via JTalert. Think not JTalert is the problem it´s on WSJT-X/JTDX. Export and import doing
the same for me.
JTDX via JTalert. Think not JTalert is the problem it´s on WSJT-X/JTDX. Export and import doing
the same for me.
73´s .. Juergen ... ALT-512 SDR (10W) , 50 m random wire at SG-211 autotuner, 2 x Xiegu G90 (20W HF TRX) one as portable Radio. Also TS-790E (40 W) for VHF/UHF with X-50 vertical and Duoband 4-Element LPDA.
Re: CQ Zone "0"
FWIW, I use WSJT-X and JTAlert, and I have never had a Zone 0 entered in my log from that combination. I don't normally use lookups from QRZ, HamQTH, etc. Harry, you said your WSJT-X log had some zone 0s in it. What WSJT-X are you looking at? I have looked at both my wsjt-x_log.adi and my wsjtx.log. Neither of those have zone information. If you are logging from JTAlert, I think it uses the lastqso.adi to do the logging. It only contains one QSO at a time. It does contain zone information, both CQ and ITU. Once again, I don't have lookups enabled in JTAlert.
73,
Jim N6VH
73,
Jim N6VH