Log4OM

m0fox

Not sure if this JPG loaded previously

m0fox

For some reason the settings used previously decided NOT to work and as I'd gone back to Win10 and then back to win11 the UDP connections had to be renewed.

So late last night I went back to watching K0PIR videos and used his settings exactly - YESSSSSS success at last, he also made the point of ...

m0fox

I'm just revisiting the group after a year, I'm using log4om, Grid Tracker and WSJTX. All have been running 100% for the last year until several days ago.
After several hours playing FT8 I realised Log4om had stopped logging and hasn't since. Reinstalled it several times, went back to Win10 still ...

m0fox

All sorted now, many thanks for the help Terry.....73 all

m0fox

Can't find you on Skype so I've sent an email from QRZ

Cheers

m0fox

I'm using v2.23.0.0 I have team Viewer installed

m0fox

Hopefully its attached....

: log1.JPG (83.74 KiB) Viewed 1564 times

m0fox

Hi Terry, it's the same standalone as with GT running, everything seems to run OK, logbook updates from GT, just manually entering a call doesn't pick up anything from QRZ, GT collects images & OP details from QRZ, it's the only thing that doesn't work....cheers Paul

m0fox

I am running Log4omV2 with Gridtracker and WSJTX, everything seems to be running fine except the callsign lookup, entering any callsign inc mine does not produce the map, populate any OP fields and QRZ images etc. Its almost like its not connecting to QRZ or Hamqth, am I missing something? cheers Paul

Search found 9 matches

Re: Log4OMV2 2.29.0.0 UDP Coms

Re: Log4OMV2 2.29.0.0 UDP Coms

Re: Log4OMV2 2.29.0.0 UDP Coms

Re: Callsign lookup not working

Re: Callsign lookup not working

Re: Callsign lookup not working

Re: Callsign lookup not working

Re: Callsign lookup not working

Callsign lookup not working