I was away for a while, so I clicked off the [Monitor] in WSJT-X before I left ... with JTalert still open. Came back a couple of hours later, clicked on [Monitor] and waterfall began ... worked a sta

If your pc timing is slightly off it will not decode anything ... I had this the other day ... you have to synch your clock with the atomic clock !! There are several free programs on the net that wil

I have been trying all afternoon to get the "Wanted Callsign" option to change color of the box in the main window ... the option is turned on in the options list, and a half dozen active callsigns ar

OK, after reading a lot of the threads here about slow display of the calls in the main JTalert window, I've finally found a snappy solution ... I'll even share the setting, but first a question ... W

Because it is intermittent, it might well be the CPU is overly busy and doesn't get to the mouse click right away ... I have seen that here, as I am using only a dual-core cpu and with all the databas

imho, it's a neat idea to try to work as many grids as possible, but I'm not inclined to wipe out my work every month ... so I am wanting to do the same thing as K6EU and what I have decided is not pa

#TIP

I would think they would upload the logs ; it's not that much of a task and surely the contacts would count for GRID SQUARES (if there was a way to know in which grid the QSO was made)

seems to me that the grid square info transmitted at the time of the current QSO should over-ride all else... I don't really understand why a previous contact in the log should over-ride current info

I definitely agree !!

I find this with stations that I have worked with WSJT-X _before_ I started using JTalert ... they have not made it into the JTalert database until I work them again ... I've been meaning to ask if th

#FT8

WSJT-X has its own log, and JTalert apparently has its own database for tracking B4s ... what I would like to do is update the JTalert database from the WSJT-X log so they match.

#FT8

actually, it is the other way around ... I was using WSJT-X for FT8 for quite a while before discovering and installing JTalert ... so there are B4s in that which are not in the JTalert, so WSJT-X wil

#FT8

I am using the Standard ADIF File in JTalert ...

#FT8

great !! glad to hear that Mike, and thanks. :))

One of the default macro messages inserts the operator's name in the 73 message ... open the MACRO window, and fill it with the default messages ... then read the help info ...

why don't you just upload the .adi file from WSJT-X FT-8 QSOs ?

Why do you need this when WSJT-X shows it to you for whatever station you click ? It is right under "DX Call" and is labelled Az: meaning Azimuth ... (or beam heading)

MY experience is that you should get the most RAM as you can possibly install on the PC ... 32GB or even 64GB ... what slows down the pc most is not CPU crunch but memory crunch, since everything that

The 'transmitted data' box at the lower left turns BRIGHT RED when the Watchdog has timed out ... surely you know that you have allowed your sequence to repeat over and over, so just glance down at th

if you have an alert set for some special feature, why would you NOT want to know about the alert just because the station is not at the moment calling CQ? wouldn't the early alert give you some time