Log4OM

HB9BRJ wrote: 24 Apr 2018, 19:10

G4POP wrote: 19 Apr 2018, 20:21Hi Marcus,
We are working with Stephen the author of GridTracker and as a result you will see some new features in GridTracker for the next release, including a worked before warning based on the imported Log4om adif file.

Hi Terry,
RST sent/rcvd are consistently written into RST rcvd/sent on the Log4OM side.

I have notified Stephen

Some countries are not identified and left blank, e.g. 2I0GFR (Northern Ireland).

Are you sure the call was not recorded as twenty one zero GFR?

Hi Terry,

The missing country issue also happens with "common" countries like Germany. Yesterday I logged several QSOs with German stations. In all but one cases, the country was correctly added.

The cause of the RST mix up error is on the GridTracker side: Checked Log4OMs Communicator activity log which clearly shows that RST sent and RST rcvd are already mixed up in this line:
TCPManagement: Incoming QSO from TCP Connection (ADD) <BAND:3>30m...
In very rare cases however GridTracker provides correct RST reports. Strange.

73, Markus HB9BRJ

I have tried GridTracker. However, having used and configured JTAlert to my requirements, GridTracker would have to come up with something really special to make me switch.

From what I have seen that "something" is not there yet.

I am open to persuasion in case I may have missed anything.

Guy G4DWV 4X1LT