Is use:
Windows 10, WSJT-X 1.7 RC2, JTAlert 2.8.4, LOG4OM v1.26.0.0
I have sometimes problems with the logging from JTAlert to LOG4om.
With several qso's everything works perfect, but sometime's i get a failure and i have to log the qso manual.
Failure: QSO not logged!
ERROR Message: LOG4OM file: unable to confirm QSO logged
NOTE: The QSO is still saved to the WSJT-X Log file
Someone recognize this problem?
JTAlert logging
- DF5WW
- Log4OM Alpha Team
- Posts: 2035
- Joined: 02 May 2013, 09:49
- Location: Kraam, Rhineland Palatinate, Germany
- Contact:
Re: JTAlert logging
This is a known Errormessge but normally all QSO will be logged in Log4OM by JTAlert. Before you log manually try a refresh in the Log4OM Recent QSO Window (F8) to see the contact is logged or not. There is no automatted refresh
73´s .. Juergen ... ALT-512 SDR (10W) , 50 m random wire at SG-211 autotuner, 2 x Xiegu G90 (20W HF TRX) one as portable Radio. Also TS-790E (40 W) for VHF/UHF with X-50 vertical and Duoband 4-Element LPDA.
Re: JTAlert logging
In JTAlert, go to Settings/Miscellaneous/Performance. Under Check QSO Log Record, increase the time. I have mine set at 10 seconds. Hope this helps.
Re: JTAlert logging
Problem solved:
Solution:
I did a fresh Windows 10 install.
Solution:
I did a fresh Windows 10 install.