Actually there is a clearly defined answer in the U.S. http://www.arrl.org/special-event-call-signs The grid alert solution should work as long as they provide a grid. Mike

And with my script it shows 2020-06-06 16:54:52.5217 | Debug | Init

Thank you Joe, 73, OD5KU Elie

There are no dxcc codes for WAE countries. The WAE country is determined by examining the structure of the Callsign and looking for any specific callsign overrides in the cty.dat file.

Make sure your not running WSJT-X with elevated privileges (set to run as Administrator). Also try the latest builds of JTAlert and WSJT-X. WSJT-X is now at 2.2.1 and the latest

Try having the Mac logger listen to the JTAlert resend of WSJT-X UDP traffic. See the Applications -> WSJT-X/JTDX section of the JTAlert settings. de

You messed up (your words, not mine). All Alert color combinations, by default, are unique. There is only one cyan background alert. These ate the colors from a default

Guy, Very good. Glad it worked for you. Yes, I usually have B4 calls displayed also. 73, Jim N6VH

While we are on this topic..... In my copy of WSJT-X, my Alert Color for Wanted Grid is the same as the color for a new callsign, i.e. black text on cyan background. Is this the default for a new

Yes, most likely. You should only use pauses or other commands that require user input when manually testing your scripts then remove them once your satisfied that the script is

OK Laurie - here is the error file - ---------------------------------------------------------------------------------------------------- 2020-06-07 23:26:09.6925 | Error | Error executing

Jim, Showing only CQ calls has done the trick. I do want to see B4 calls but there are not too many of those. Many thanks and stay safe, -- 73 de Guy G4DWV 4X1LT

This general topic is pretty old, but maybe someone has an elegant answer to it by now. I have WSJT-X and JTAlert running on a Win 10Pro computer attached to my Flex 6300. I use MacLoggerDX that is

JTAlert, by design, will not show any console window or similar associated with your script. The output is redirected and recorded in a log file. A planned option to disable that non-display

Make sure you run it by double-clicking from a file browser And that you have the parameters done correctly. Also ensure there are no spaces in the directory/path to the script. If there are you

This is by design. It took me a few minutes to find the relevant entry in the Release notes so your excused from not having seen this, taken from the 2.10.0 (21-JUL-2017)

JTAlert doesn't send Callsign/decode coloring instructions to JTDX simply because the JTDX devs decided to not support that component of the WSJT-X UDP messages api. That is JTDX

Any coded solution has to be flexible enough to take into account the fundamental question "what is a special event Callsign? There is no clearly defined answer, is is subject to the

Read the documentation! Manage Settings -> Logging -> Logging Options scroll down to ""Log seconds in time_on and time_off values" Check the box. 73, ... Joe, W4TV

This is with JTAlert 2.16.6 beta 011 , WSJT-X 2.2.1 and JTDX 2.1.0-rc150.