My Location is Incorrect

K2GT
Novice Class
Posts: 9
Joined: 13 Jun 2020, 04:11

My Location is Incorrect

Post by K2GT »

I have spent much time trying to determine why I cannot auto upload or manually upload to LOTW and have figured out the problem, but not the answer. The problem lies in my location. I am in Hawaii. If I manually enter a QSO through the add button, SSB for example, Log4OM records my location as Hawaii. However, if a contact is entered directly from WSJT-X, JTDX, or through JTAlert, my location becomes United States. When this is uploaded to LOTW, the contacts are rejected as not having a valid callsign certificate because my callsign certificate says I am in Hawaii. The only way I have found to solve the upload problem is to manually go to QSO manager, open each contact, click the My QTH tab, go to the dropdown menu, manually change the location to Hawaii and save it. Obviously with a few dozen FT8 contacts at a sitting, this is impractical. Any suggestions would be appreciated.
User avatar
G4POP
Log4OM Alpha Team
Posts: 11585
Joined: 21 Jan 2013, 14:55
Location: Burnham on Crouch, Essex UK

Re: My Location is Incorrect

Post by G4POP »

Station info and set location correctly
73 Terry G4POP
K2GT
Novice Class
Posts: 9
Joined: 13 Jun 2020, 04:11

Re: My Location is Incorrect

Post by K2GT »

Yes, station information is correct. If it were not, then I would think that all QSO's would be wrong, not just the ones entered automatically.
73,
Gus K2GT
User avatar
G4POP
Log4OM Alpha Team
Posts: 11585
Joined: 21 Jan 2013, 14:55
Location: Burnham on Crouch, Essex UK

Re: My Location is Incorrect

Post by G4POP »

Then its the program sending the data to Log4OM - We dont change existing incoming data from other programs

Check with the other developer and ask why its wrong
73 Terry G4POP
K2GT
Novice Class
Posts: 9
Joined: 13 Jun 2020, 04:11

Re: My Location is Incorrect

Post by K2GT »

Hi Terry,

I have more than one program that has this problem. It is evident in JTDX,WSJT-X and JTAlert. The attached file shows a random import to Log4OM which shows that MY State is indeed being changed.n Although the screen does not show what it is being changed to, using QSO manager shows my location as United States instead of Hawaii.
Attachments
Log4OM Import.png
Log4OM Import.png (50.64 KiB) Viewed 3057 times
User avatar
G4POP
Log4OM Alpha Team
Posts: 11585
Joined: 21 Jan 2013, 14:55
Location: Burnham on Crouch, Essex UK

Re: My Location is Incorrect

Post by G4POP »

Your confusing an ADIF import with data sent directly from an external program, different process

Do as I suggested and check your settings in the other software or contact their developers
73 Terry G4POP
nk9n
New user
Posts: 1
Joined: 23 Dec 2022, 17:30

Re: My Location is Incorrect

Post by nk9n »

whatever callsign I enter into the log, it tells my "callsign does not appear to be valid, proceed anyway?"
User avatar
G4POP
Log4OM Alpha Team
Posts: 11585
Joined: 21 Jan 2013, 14:55
Location: Burnham on Crouch, Essex UK

Re: My Location is Incorrect

Post by G4POP »

That is usually caused by typing an I instead of a one or an O instead of zero

Was it working and has suddenly stopped working

Again the inevitable question what version of Log4OM are you using - see help/about
73 Terry G4POP
kp4tr
Novice Class
Posts: 4
Joined: 02 Jan 2022, 13:02

Re: My Location is Incorrect

Post by kp4tr »

I am having exact same issue.

I live in Florida. But my callsign is from Puerto Rico. WSJT send contact to LOG4OM, but in LOG4OM the "country" is set to Puerto Rico, even though city and state is correct (Seffner, Florida).

If I enter it manually, it saves it correctly. I have to manually fix all my FT8 QSO's "mycountry" by hand.

The "Station Information" is correct. This only happens when log entry comes via WSJT-X.
User avatar
G4POP
Log4OM Alpha Team
Posts: 11585
Joined: 21 Jan 2013, 14:55
Location: Burnham on Crouch, Essex UK

Re: My Location is Incorrect

Post by G4POP »

The problem is caused by WSJT assigning the data to the QSO like the country etc.

We dont change incoming data because we expect the user to want that information, hence the problem.

Speak to WSJT if you can!
73 Terry G4POP
Post Reply