Log4OM

Hi,
(V. 2.21.1.0)
My "Station Callsign" is set correct in the "Station Configuration", and the profile is active.
However, all QSO logged are marked with LB4MI, instead of JX/LB4MI.

This causes automatic upload to online logbooks to fail, where I have made all separate logbooks for JX/LB4MI.
I need to use "Single field update" manually to change the callsign after QSO's, and then upload.
Has anyone seen this behaviour before? Or has anyone any advice for me?

Thanks
Helge.

Do the online logs have that call registered


Have you used the correct call in the appropriate external services settings user names

You don't state which on line log

Nor do you state the log4om version number

Hi Terry,
thanks for your quick reply.
The version number is in the first line of my original post. Should be the latest version.

So, the problem is not my online logs, sorry if I was unclear. The reason for online logs getting trouble is that LOG4OM is not using my "Station Callsign" from configuration to the ADIF-file. And than later on, the online logs can't upload as I am uploading with LB4MI to all the online logs that are now configured with JX/LB4MI.

Here is a picture of the issue. When I register a QSO, the "Station Callsign" in my ADIF is LB4MI, while in settings it is set as JX/LB4MI. The QSOs underneath is manually changed by myself. The top QSOs are from yesterday, where I have not changed anything afterwards:

Helge,
I tried a variety of prefixes and they are all faithfully reflected in the recorded data, see below.

Please update to the latest Beta release 2.22.0.8 from https://www.log4om.com/download/

Terry,
after more invetigation, I was able to find the problem!
As my new "Subject" indicates...

I am using N1MM for my logging, and the Log4OM gets the data from N1MM.
And, in N1MM i found my callsign being LB4MI only, without JX/....

I didn't think of this, that the "third party" software overrides local Log4OM settings, but I guess now that make sense.

Thanks for your help anyway,
73 from Jan Mayen

LB4MI wrote: 12 May 2022, 07:33 Terry,
after more invetigation, I was able to find the problem!
As my new "Subject" indicates...

I am using N1MM for my logging, and the Log4OM gets the data from N1MM.
And, in N1MM i found my callsign being LB4MI only, without JX/....

I didn't think of this, that the "third party" software overrides local Log4OM settings, but I guess now that make sense.

Thanks for your help anyway,
73 from Jan Mayen

What actually happens is we do not modify incoming data because we have to assume that is what the user is happy with like Name = Bill but update it to the QRZ data which is Name = William Alloush's Mahoney Smith Junior

So similarly we must assume the Station call is correct