Thanks Terry - makes sense.
I'll take care to make sure I always have Log4OM active when I'm using WSJT-X.
73 Gareth G0MFR
Search found 3 matches
- 15 Jan 2021, 15:56
- Forum: User support
- Topic: WSJT-X "Catch up"
- Replies: 4
- Views: 1446
- 15 Jan 2021, 15:15
- Forum: User support
- Topic: WSJT-X "Catch up"
- Replies: 4
- Views: 1446
Re: WSJT-X "Catch up"
Running WSJT with the UDP server on 127.0.0.1 and the port matched in the UDP_INBOUND in Log4OM.
When both are running it works fine.
It's just that if I run WSJT without Log4OM running... when I start log4om later it doesn't pick up the QSOs I made while it was not running.
V1 used to do this ...
When both are running it works fine.
It's just that if I run WSJT without Log4OM running... when I start log4om later it doesn't pick up the QSOs I made while it was not running.
V1 used to do this ...
- 15 Jan 2021, 14:44
- Forum: User support
- Topic: WSJT-X "Catch up"
- Replies: 4
- Views: 1446
WSJT-X "Catch up"
Hello Folks,
I use the WSJT-X -> LOg4OM integration for logging digi contacts.
Since upgrading to V2 it still works but it does not catch up on missed QSOs.
I used to use WSJT-X without log4om running then next time I started log4om it would log all of the QSOs that had happened while it wasn't ...
I use the WSJT-X -> LOg4OM integration for logging digi contacts.
Since upgrading to V2 it still works but it does not catch up on missed QSOs.
I used to use WSJT-X without log4om running then next time I started log4om it would log all of the QSOs that had happened while it wasn't ...
