John, First, I suggest upgrading to Log4OM version 2. It first came out in Jan, 2020, and a lot has changed since then. There will be a learning curve, but it will be worth it. Second, Have you checke

If the QSO is being logged in Log4OM, then try changing the time in the Logging / Check QSO Log Record section of the settings. I have attached a picture. In my case, 5 seconds works fine, but try inc

I don't use JTDX, so don't know if this will be useful for you. There is a JTDX forum here: https://jtdx.freeforums.net/ You might try it, and see if it works for you. 73, Jim N6VH

Bob, Since you changed your address with the FCC in Dec, 2022, the GA address would be in the JTAlert callsign database, probably some time in January. Those who are still seeing you in NM haven't upd

Bob, JTAlert shows you in GA. Where are you being shown in NM? 73, Jim N6VH On 4/3/2023 10:18 PM, bob bobholzer.com wrote:

On 3/27/2023 7:38 AM, Arthur Petteway wrote: Art, Since the QSO is being logged in ACLog, then this will probably work for you: Go to Logging section of Settings and increase the time under "Check QSO

#FT8

Mike, You said you updated some programs. Which programs did you update? What were the previous versions and what are the new versions? Are you running the DESKTOP version of .NET 6, as specified near

On 3/11/2023 11:30 AM, Jim N6VH wrote: That got sent before I had finished. My fault, sorry. Ignore the statement about three ways to do it. The method listed above is probably the easiest. Another wa

On 3/11/2023 8:06 AM, bozovich@... wrote: There are three ways to do this. 1. Just reinstall JTAlert 2,60.5, and tell it to create the shortcut you want. No need to uninstall JTAlert, just insta

I under stand typos very well. I make them from time to time. As a matter of fact, I made one in my previous post on this subject. I wrote "tiles" instead of "times". 73, Jim N6VH

On 3/8/2023 2:38 PM, JTAlert Support (VK3AMA) wrote: The thing is, Rich said he had never worked that particular station before, so that would not apply in this case. Yes, that's why I have the "Do no

Rich, In an earlier post, you had a picture showing an incorrect grid in JTAlert. I can't explain how that got there, My thought is that the grid shown in JTAlert should be the one sent by the other s

On 2/19/2023 8:48 AM, Joe WC4R wrote: Joe, While I normally use Log4OM, I tested with ACLog. I had a QSO using WSJT-X and JTalert, and the QSO went to both logging programs, no problem. Here is a scre

#FT8

Jim, In the main JTAlert window, go to Settings / Alerts /Filters. Then check "Do not show Worked Before (B4) Callsigns". For checking propagation, use these two sites: For a tabular display of calls

Joe, Yes, that's true. One problem is when someone is operating portable (POTA, for example), he might not be in his home state. And, as you say, what gets uploaded isn't always the same as where he w

The only location info that JTAlert gets from a CQ is the grid square, and that isn't always a reliable indication of the state. A number of grids include more than one state. For example, DM25 includ

Paul, Yes, there shouldn't be any problem running JTAlert and Grid Tracker at the same time. I don't normally run GT, but I have once in awhile, just to see what it does. My thought would be to have J

Glenn, Why go to the extra trouble? Why not just let JTAlert do the logging? That way, you won't have to go through the extra steps that you mentioned. 73, Jim N6VH

Paul, If you don't have JTAlert log to HRD, then JTAlert wont give you any alerts, B4, etc. Also, it isn't a good idea to have both programs doing the logging, because you will end up with duplicate Q

In the JTAlert main screen, go to Settings/Rebuild Alert Database. Check to make sure the settings in this window are what you want. Then click Rebuild All (enabled). 73, Jim N6VH