How old is your copy of JTAlert? Fifth from the bottom is "Rebuild Alert Database" de Laurie VK3AMA

#DXLAB

On 20/01/2021 8:34 am, Steve McEdwards wrote: Not sure if I did something wrong , I updated to the latest version of JT Alerts 2.16.17 and everything appears to be OK except when I log a qso and the d

Both those features plus more are already coded in a new Messaging window. It will likely not be in the next public release, but the one after that. It is ~90% feature complete, but has not been seen

JTAlert, by default, considers both the Band and Mode when determining the B4 status. In your example, a 40m FT4 decode would not be considered a B4 if there was a previous 40m FT8 QSO in the log if y

There will likely be something unusual with the ADIF file you used. Send it to me direct and I will test it. Send to vk3ama.ham.apps [at] gmail.com Also , Please use the "Help" -> "Contact Support" me

There will likely be something unusual with the ADIF file you used. Send it to me direct and I will test it. Send to vk3ama.ham.apps [at] gmail.com de Laurie VK3AMA

Short answer... NO Long answer... Any sort of callsign sorting will require that all decodes have been processed and delivered by WSJT-X before JTAlert can produce a sorted display. That could be seve

There are more options, you need to scroll down. Did you miss the highlighted vertical scrollbar (on the right) in my original post?

#DXLAB

de Laurie VK3AMA

In addition, JTAlert has no concept of 'CONTEST_ID' and it is not something conveyed by WSJT-X. You will need to put your logger (DXKeeper) into contest mode prior to logging contest QSOs from WSJT-X/

#DXLAB

JTAlert already logs contest exchanges, but you need to enable that option. Specifically, JTAlert will log 'SRX', 'STX', 'SRX_STRING', 'STX_STRING' if the fields received from WSJT-X contain data de L

#DXLAB

JTAlert-X no longer exists. de Laurie VK3AMA

If the QSOs are getting logged correctly, that indicates that JTAlert is trying to read the wrong log file when it tries to confirm the QSO was written. Very likely you have not set the correct path t

Easy! Just a single mouse-click on the callsign in JTAlert will send it over to WSJT-X which will then set itself up for you to initiate TX. If you don't see the Callsign propagated to the "DX Call" f

You will need to install the latest Callsigns database AFTER installing JTAlert. JTAlert 2.16.17 comes bundled with the 2020-12-06 version of the database which is now superseded by the most recent 20

Switching out a 2 character State with a 4 character grid would not be practical given the size restraints of the current Callsign display area. That would require the user to also decrease the number

You will need to adjust the B4 ignore date to the start of this year if you're pursuing the Marathon. de Laurie VK3AMA

Perhaps TQSL is choking on the zeros for the ITU & CQZones? de Laurie VK3AMA

The 80 character count is correct. There are 72 characters in your sample plus 4 line endings, which on PC are 2 characters (CRLF). 72 + 4*2 = 80. If that ADIF record is not uploading, it wont be beca

Andrew, Sounds like Log4OM is setup to work with wsjtx directly. Check the "Connections" section of the Log4OM Configuration and look for one or more connections set to use the wsjtx udp port, typical