If you don't want JTAlert performing a DXKeeper lookup (along with DXK filtering) on startup make sure the "DX Call" field in WSJT-X is empty. JTAlert has no way of knowing if that DX Call is a new en

#DXLAB

Name is Mike, You are correct that was the problem all along I dont know how docking got turned on as this was my initial install.The ALT version works best for me. All is well now. Mike C. Boise, ID

#DXLAB

Well, I did some troubleshooting and found that the problem is that JTAlert has stopped sending the DXCC number, CQ zone and ITU zone in the ADIF file it sends to DXKeeper. It sends them as zeros when

#DXLAB

That's correct. I will only add multiple grids per qso support to the Log Scanning function. There is no intention at this time to add multiple grid logging as multiple grids are not conveyed using WS

#DXLAB

Laurie; Thank you for your message. You hit my problem, right on the "head". For some reason I forgot to use the "Log QSO" button. Thank you for taking the time to respond. Mark.

#DXLAB #FT8

"Can it be fixed soon?", NO, there is nothing to fix. Nothing has changed with respect to logging for years now. You need to click the "Log QSO" button... If that is too hard, set WSJT-X to auto-show

#DXLAB

Joe, Good to hear. I don't have an explanation, just real-world experience. Your lucky I saw the reference to DropBox in your JTAlert session data. Which triggered me to make the move it off DropBox s

#DXLAB

Hi Laurie, I followed you suggestion and moved my log file to a different folder (on a different drive and non-dropbox) and all appears to be well. I don't know what happened between versions since it

#DXLAB

Hi Laurie, thank's you for all. Its working as usual. 73 DX.

#DXLAB

Thanks, Laurie. I was off the air for so long there were no useful backups (only one and it was from today!). I started over and it looks to be working now. 73 de K2DT

#DXLAB

Well George, to answer your question. When I got my ticket in 1956, I just plain didn't know abt. GMT. And I don't believe DST was operative in Iowa at the time. In any event, I will follow whatever I

#DXLAB

+ AA6YQ comments below You need to run a JTAlert Scan Log & Rebuild with the Wanted DXCC scan QSL confirmation type(s) set per your requirements for considering a DXCC as no longer needed. Performance

#DXLAB

Thanks for the info to all who posted. Laurie, OK on how the name & QTH is pulled, definitely helps my troubleshooting! Dave, I'll follow the transfer instructions. (Probably going to uninstall everyt

#DXLAB

Jerry, Short Answer... Enable one of the JTAlert XML services. Settings window, "Web Services -> Online XML Callbooks" section. Long Answer... When the DX Call in WSJT-X changes, JTAlert will initiall

#DXLAB

Jim, Currently all decodes are sent to SpotCollector regardless of any filters set within JTAlert. Think of it as a raw data feed. Already on the todo list is to restrict the SpotCollector spots to de

#DXLAB

Walt, Don't worry. It has always been my policy that when new features are added they are optional such that they don't change existing behaviour. de Laurie VK3AMA

#DXLAB

+++ more AA6YQ comments below

#DXLAB

OM, JTAlert Settings, Miscellaneous -> Performance section and increase the QSO check time. Likely DXKeeper is being delayed in writing the QSO to its log file due to uploading the QSO to one or more

#DXLAB

There is *never* any reason to display the WSJT-X/JTAlertX data in DXKeeper's Capture window as that window is not used for logging with JT-Alert. At best Capture provides only a sub-set of the data a

#DXLAB

Neil, That last support email I got from you and your previous post to this group of an image of your Settings shows that you only had the DXKeeper lookup enabled. Your observation confirms that, as t

#DXLAB