Same callsign appears in logging

[HS0ZQG]

Hi

I have an annoying issue that I cant resolve ... everytime I start Log4OM and /or change bands , the same Callsign appears in my logging Page ? I started noticing it after upgrading to new version some time back in May 2023 ?? thats when I seem to have logged this station on my log , I know its not normal as I have worked other stations Log4om and never seen this happen ? ... not only is it annoying it also slows the loading of Log4om until it has all the info for this user displayed ... whats the solution ?

regards
Russell E21AZ .. HS0ZQG

[KI5IO]

Hi

I have an annoying issue that I cant resolve ... everytime I start Log4OM and /or change bands , the same Callsign appears in my logging Page ? I started noticing it after upgrading to new version some time back in May 2023 ?? thats when I seem to have logged this station on my log , I know its not normal as I have worked other stations Log4om and never seen this happen ? ... not only is it annoying it also slows the loading of Log4om until it has all the info for this user displayed ... whats the solution ?

regards
Russell E21AZ .. HS0ZQG

Russell,

Do you also have the 3rd party FTxx APPs running when you turn on Log4OM?

If you do ... turn them all OFF and turn on Log4OM without any other 3rd party APPs involved and see if the same condition persists.

[HS0ZQG]

Nolan

yes I have wsjtx and Gridtracker operating only prior to starting Log4OM ... however I need to have them operating first as Log4om want connect if I start it first with OMNIRIG

[HS0ZQG]

Nolan

Ok I did not start WSJTX and Gridtracker and YES it did not bring up the stubborn callsign all appears ok .. BUT I have to sequence as follows WST|JTX first ... Gridtracker second and then Log4OM last for everything to work correctly

[HS0ZQG]

Nolan

I see with your suggestion its actually wsjtx creating the issue .... There appears nothing obvious or anything that resembles that callsign in the fields that would send it to Log4OM .. on startup ... Maybe , I need to uninstall and reinstall wsjtx ... to see if it clears ... let me do that and Ill report back any luck

regards
russell

[KI5IO]

Nolan

I see with your suggestion its actually wsjtx creating the issue .... There appears nothing obvious or anything that resembles that callsign in the fields that would send it to Log4OM .. on startup ... Maybe , I need to uninstall and reinstall wsjtx ... to see if it clears ... let me do that and Ill report back any luck

regards
russell

Russell,

Actually it is an option setting in WSTJx that is causing the 'last QSO' made in WSJTx to again appear in Log4OM.

Has been discussed here on the Forum in the past.

In the WSJTx "Settings / Reporting" tab be sure that you have selected "Clear DX Call and Grid After Logging"

That might clear the last data out of WSJTx and thus then not appear in Log4OM.

Be sure that your don't have two sources sending logging data into Log4OM. As I recall you do not need to have ADIF Monitoring of the WSJTx feed enabled.