LOTW issues: County and CQ Zone wrong since Log4OM 2 upgrade
Posted: 05 Oct 2020, 00:44
I just "discovered" that there are errors in my log for the last 3 months. My County was set to USA instead of King. My CQ zone was set to 5 (East Coast US) rather than 3 (West Coast). I believe that the errors began when I upgraded from Log4OM v.1 to v.2. I fixed today's contacts, and they appear to have uploaded to LOTW correctly now.
I upgraded Log4OM to 2.9.0.0 and TQSL to 2.5.5, which fixed the "Invalid Mode FT8" error, which I also got. And to confuse matters even further, I had upgraded my PC from Win7 to Win10 last week.
I've fixed the data with the "QSO Manager." So far so good. What was odd is that my entire log from when I used Log4OM v.1 had the CQ and ITU zones set to zero. I know I set them when I first started because I distinctly remember looking them up. The logs show my county correctly prior to the upgrade. afterwards, each QSO shows "USA" for the county until I fixed them today.
1. Will I have to re-upload these contacts to LOTW and EQSL to avoid issues with confirmation?
2. Are there any other pitfalls with the Log4OM v.1 to v.2 upgrade, or Win7 to Win10, that I may not have noticed?
Thanks!
--Peter, KD7MW
I upgraded Log4OM to 2.9.0.0 and TQSL to 2.5.5, which fixed the "Invalid Mode FT8" error, which I also got. And to confuse matters even further, I had upgraded my PC from Win7 to Win10 last week.
I've fixed the data with the "QSO Manager." So far so good. What was odd is that my entire log from when I used Log4OM v.1 had the CQ and ITU zones set to zero. I know I set them when I first started because I distinctly remember looking them up. The logs show my county correctly prior to the upgrade. afterwards, each QSO shows "USA" for the county until I fixed them today.
1. Will I have to re-upload these contacts to LOTW and EQSL to avoid issues with confirmation?
2. Are there any other pitfalls with the Log4OM v.1 to v.2 upgrade, or Win7 to Win10, that I may not have noticed?
Thanks!
--Peter, KD7MW