Log4OM

Add the grid square directly from wsjt-x/digital software as a lot of the time the grid square logged is incorrect. it is so annoying that your contacts give their grid square but the incorrect one is logged after finding this out recently I now have over 5000 contacts to go through to check and correct

Actually logged incorrectly or displayed in lookup incorrectly?

How are you retrieving qso's from ft8 software?

they are incorrect in the green highlighted box and also if i correct it before its logged it still logs the incorrect grid square

wsjt-x outputs on udp and is picked up by gridtracker then forwarded out to log4om

Your sending the data twice, try unchecked the enable box you show in the jtalert screen shot above and check that logging to log4 on is set in jtalert logging window

The display in log4om is incidental just leave it alone because the udp connection does it all no need for you to do anything in log4om

Since I installed the latest version the the other day, the grid square lookup (from QRZ.com) and (hence) logging has not worked...

G4POP wrote: 26 Jan 2023, 19:44 Your sending the data twice, try unchecked the enable box you show in the jtalert screen shot above and check that logging to log4 on is set in jtalert logging window

The display in log4om is incidental just leave it alone because the udp connection does it all no need for you to do anything in log4om

there isn't a jtalert screenshot there???? the 1st one is log4om then gridtracker

Sorry gridtracker

I have reverted to the previous version 25. The grid square lookup/logging is now working again

It's not working right for me. Log4OM seems to be looking up callsigns somewhere and logging the grid square it gets, not the one that comes from JTDX. Here's an example. D2UY is quite active from Cabinda, Angola, giving his grid square:
195215 -11 0.6 559 ~ CQ D2UY JI64 •Angola
I worked him a couple of times. wsjt_log.adi shows this entry (emphasis added):
<call:4>D2UY <gridsquare:4>JI64 <mode:3>FT8 <rst_sent:3>-06 <rst_rcvd:3>-06 <qso_date:8>20230131 <time_on:6>201130 <qso_date_off:8>20230131 <time_off:6>201214 <band:3>12m <freq:9>24.916122 <station_callsign:4>K1IO <my_gridsquare:4>FN42 <eor>

Now for some reason Log4OM disables the Windows copy function in the Recent QSOs window, but it shows that contact's grid square as JH97, which is somewhere near the centoid of Angola, nowhere near Cabinda (a coastal enclave north of DRCongo).

This is just wrong. Yes, JTDX can look things up too, and fill in the square for stations that don't give it (like when I answer an RR73, not a CQ), but Log4OM shouldn't change it.

For the record, I'm using Log4OM 2.25.0.0.