Log4OM

I have discovered if my CQ or ITU zones are different in JTAlert than in Log4OM and I log a contact from JTAlert, Log4OM changes my station setup to the CQ and ITU zones that come in the JTAlert logging "transaction". I know these fields should never be different between the two programs but if it happens that they are, I can understand that the log of that QSO might have these different myzone values but it doesn't seem that the station setup values should be changed automatically and without warning. Bug?

Log4OM ver 2.5
WSJT-X ver 2.1.2
JTAlert ver 2.16.5

There is a 4/5 page long topic on this forum about this, please refer.

Resolved in next release

G4POP wrote: ↑13 May 2020, 06:26 There is a 4/5 page long topic on this forum about this, please refer.

Resolved in next release

Terry,
If you are referring to the CQ Zone "0" issue, I'm well aware of that and have contributed to that discussion. This is a different problem. It seems Log4OM automatically changes my Station Information in setup when a logging "transaction" comes through that contains CQ and/or ITU zone information. If the values in the transaction are the same as in Log4OM, no harm done but if they are different, Log4OM station setup is changed to the different values. I don't know if this is also being addressed but it is not the same problem.

Are you referring to your own zone info in the program config

If so what must be happening is that WSJT etc are using incorrect info for YOUR zones, of course when we receive that information as part of the incoming data we don't change or check it

Use the UDP monitor to watch the incoming data from WSJT if it contains wrong data for YOUR station contact Joe Taylor

It's the same as any import if it says your /P we record it as such etc

G4POP wrote: ↑13 May 2020, 12:26 Are you referring to your own zone info in the program config

If so what must be happening is that WSJT etc are using incorrect info for YOUR zones, of course when we receive that information as part of the incoming data we don't change or check it

Use the UDP monitor to watch the incoming data from WSJT if it contains wrong data for YOUR station contact Joe Taylor

It's the same as any import if it says your /P we record it as such etc

Terry,
Yes, I am referring to my own zone info in the program config. A picture is worth .....

My station setup JTAlert setup. Yes, I know it is wrong, guilty as charged! My setup after logging a contact The log for this QSO shows the wrong My CQ Zone and My ITU Zone which seems reasonable. After all, it came with the logging transaction and as you point out, you are not going to change it. However, I would not expect it to change my station setup. This is not a WSJT or JTAlert issue, it wouldn't matter what software sent the logging transaction.

I hope this clears up what issue I am trying to describe.

phew... seems really strange as there are no data writers to this field in the whole code but...
i'm investigating

Pretty sure we identified the issue and our Alpha team are testing now.

Thank you for reporting this

Team,

Just checked this out in 2.6.1 and FIXED! That's like record time. Great job.