Page 1 of 1

Configuration Error

Posted: 17 Jan 2025, 13:24
by g3psm
Hi,

I am a new user of LOG4OM and slowly getting my head around it.

One problem I am getting is in the configuration menu. As an example External services/ LOTW tab. I can enter User, Password, TQSL path, Temporary path without any problem, however when I enter my callsign in the Station ID it is not accepted and I I get "Please complete required information" error.

Is this something I have overlooked ?

Station is a K3 running WSJT via HamLib.

73

Colin, G3PSM

Re: Configuration Error

Posted: 17 Jan 2025, 14:34
by g3psm
Never mind...I think I've cracked it.

73

Colin, G3PSM

Re: Configuration Error

Posted: 17 Jan 2025, 17:42
by KI5IO
g3psm wrote: 17 Jan 2025, 14:34 Never mind...I think I've cracked it.

73

Colin, G3PSM
Collin,

Sharing your solution would be helpful for other OMs who might experience the same as you have.

Glad you got it sorted.

Re: Configuration Error

Posted: 18 Jan 2025, 14:03
by G4POP
KI5IO wrote: 17 Jan 2025, 17:42
g3psm wrote: 17 Jan 2025, 14:34 Never mind...I think I've cracked it.

73

Colin, G3PSM
Collin,

Sharing your solution would be helpful for other OMs who might experience the same as you have.

Glad you got it sorted.

Yes it would help others

Re: Configuration Error

Posted: 19 Jan 2025, 15:32
by g3psm
Guys, it was operator error on my part. I omitted to open the folder associated with the Station ID tab.

Having moved QTH 10 years ago there are two location profiles listed in TQSL and these are listed in this folder. I selected the current location and all was well.

Now back to sorting out an apparent CAT port conflict between LOG4OM and WSJT-X.

73

Colin, G3PSM

Re: Configuration Error

Posted: 19 Jan 2025, 16:50
by G4POP
Not a conflict I suspect that either your not using omnirig or in WSJT you selected your radio instead of omnirig rig 1 or 2

See user guide

Re: Configuration Error

Posted: 20 Jan 2025, 17:44
by g3psm
Yes Terry correct. I had WSJT set on Hamlib instead of Omnirig but I got there in the end.

All working now, thanks.

Colin, G3PSM