In a nutshell, I opted to drop the W from my call sign to go from MW0KJN to M0KJN, not because im not a proud welshman, but mainly because I do a lot of mobile work, often crossing from Wales to England a few times a week, which meant things like my Fusion transmitted callsign would be wrong, and also my APRS beacon. A simple solution I thought, would be to drop the W and just go about my merry way as M0KJN.
Albeit, maybe a decision taken too lightly without proper thought around consequences.
I understand that now there may be problems with callsign lookups for M0 stations in wales, but what I am seeing is a failure to upload to LOTW because of this. Im trying to work out where the problem lies.
If i work a station and manually enter into my log book on Log4OM, I see things for my callsign correctly, as :
- l4om1.png (173.21 KiB) Viewed 475 times
QSO's that are imported have MY information incorrect, which causes a problem when uploading to LOTW.
An example :
- l4om2.png (212.31 KiB) Viewed 475 times
What i'm trying to work out first, is where its getting that data from, and is there a way I can manually set a call sign in said database to always return, in this example Wales for M0KJN.
Cheers
Kev
