my notepad saves as .txt as an extension, but idf you have that option shut off, it may not be showing that is not filename.adi.txt try setting extensions to be seen, and then you just have to rename

#logging

LotW accepts the ADIF as specified. LotW were part of the discussion as were most of the log developers. LotW are only interested in the fact that it was a DATA mode as that’s the category in DXCC awa

#adiFiles #logging #FT4 #FT8

Right now there is a field in the logging form with the option to retain it. For satellite QSO's it would be nice to have a similar field to put the satellite name, retain it and output with ADIF log

#EnhancementReqest #logging

It looks like the TNX 2BND 73 message has been coded into a standard <CALL> <CALL> 73 format. WSJT-X is not going to know that it’s not a real call. I don’t know if there’s a way for WSJT-X to be told

#logging

Bill Thank you for the direction. I had read the section on the site you referenced but in my haste did not comprehend the statement about opening the directory containing the log files. 70 is catchin

#logging

This sounds more like JT-Alert had the 'repeater' setting turned on. That setting had JTAlert repeat the WSJT-X broadcast, and if Log4OM was actively looking at the UDP broadcasts, it would trigger an

#logging

Hi Joe, those that reported this issue before have neglected to use the Log QSO button to log each completed QSO. You can check the "Settings->Reporting->Prompt me to log QSO" option so WSJT-X reminds

#logging

Lately I've been experiencing an issue with B4 contacts. I'm running the latest general release version on both programs on W10. WSJTX will show that the CQ is needed for a new contact but JTALERT wil

#FT8 #FT4 #logging

This will help.... de Mike W9MDB

#logging

Bill, I tried that previously, but because of the use I make of these fields in the status UDP, I want them cleared after logging. I use them to display current contact location in DxAtlas. I'll try a

#IssueReport #logging

Hi Bill, I will check the Log QSO dialog religiously from now on, and conform the QSO data there and then. I hadn’t considered the myriad of use cases that occur and would have to be dealt with. As al

#IssueReport #logging #FT8 #macOS

Hi Mike, Do you mean auto logging -> having QSOs from WSJTX written/synced into Rumlog or manually enter in Rumlog, both is working on my end… If you are on Facebook, better join the Rumlog Group to g

#logging

I used HRD for many years(2010 al;l versions) and had no troubles, and none since logging since adding of WSJT-x FT8 and JTAlert a couple of years ago. Use what you like but avoid trashing others! Bil

#logging

I recently change my logging for DXKeeper, to HRD Logbook. Every thing worked great when I set HRD Logbook to accept UDP from WSJT-X. But when I set JTAlert to log to HRD Logbook, I started getting tr

#logging

To SA5QED. How can I send the .adi file to QRZ.Com and LoTw with a few clicks?

#logging

This is the latest install I have been using since I began using Digital Modes 4 months ago (v2.4 .0 c19d62 Win 64) I use updated Windows 10 and have not gotten this message until 4 days ago. The resu

#logging

Yes, I use Log4OM here at home. N3FJP FD logger is what is used here for FD. Just the way it is ! 73, Jamie WB4YDL

#logging

You're right. There is a configure box for the API interface. I'm not familiar with Aclog , N 3 F J P , yet just evaluating. Been using DX4WIN, looking for something more up to date. Thank you very mu

#logging #help

Log recovered with the help of Paul, G4IJE. Thanks to all who responded.

#IssueReport #logging

I agree. This is specially annoying if I have already double clicked on the next station I want to work. It gets replaced by the one sending 73. The only way I have found to deal with it is to uncheck

#logging