WSJT-Z Reviews

The new versions of this software are utterly frustrating. Instead of addressing bugs and improving performance, the developers seem to have introduced even more issues. It's as if they've completely forgotten how to code, or perhaps they're simply out of touch with modern practices. Furthermore, they seem oblivious to user feedback, which only exacerbates the users.

I've been running FT8 with WSJT-Z MOD v1.22 for just on 12 months now and find it's wonderful, I'm a happy FOO. I don't walk away from the gear except for a pee, I like to monitor and change filtering to suit the current activity and my aims. I'm not running FT8 to score the numbers, the challenge of running low power, tweaking my antennas for transmission and receiving improvements, and making contacts where a language barrier does not come into play, or a horse voice or keyed-out fingers is just where I want to be, with an easy to use and fun "Z MOD'ed WSJT" to play with. I've been into amateur radio operator since 1977 playing with SSTV, moon bouncing, tracking satellites, ticker tape run Radio Teletype, Slow Scan TV, moon bouncing, Tono keyboards, building an 8080 Acorn computer and tuners, electronic stuff, and lots of experimenting with antennas, and running the Z Modded WSJT-X for me is the next stage for me in amateur radio. Thanks for the 5 Star MODS to WSJT-x. VK4FOO is currently operating WSJT-Z portable highrise rooftops.

I am using version 2.6.1 on macOS, and I have only one word to say to you – congratulations. I have tried other versions of WSJT, but the capabilities of your software surpass all those I have tested. Don't abandon the Mac versions, even if we are fewer than Windows users. And thanks again for your work. Bravo, bravo, bravo. I am waiting the Mac 2.7.0 version Thanks again ! 73 from F6FDY For those wha have some problems to launch WSJT-X on Mac, i wrote this AppleScript to run at each reboot : do shell script "sudo -v" with administrator privileges do shell script "sudo sysctl -w kern.sysv.shmmax=52428800" with administrator privileges do shell script "sudo sysctl -w kern.sysv.shmall=25600" with administrator privileges do shell script "sysctl -a | grep sysv.shm" You just have to give your administrator password at the prompt since Apple not allow any more to automate this step in the latest version of the system.

It's really great software. It would be nice if the transmit digital gain value was displayed to prevent overload.

Ostatnia wersja nie dekoduje ramek MSK144

wsjtz-2.6.1-1.3.3(MAC version ) can't be open on MAC 11.7.3! Please fix it! My email: yst@live.fi

hi dear Om you have done a very excellent job i have a request in your next version if you can add in more detail the scale of the rx scale and if you can put in separate buttons each frequency band and mode thank you for time wait for the next update

My only disappointment is the fact that I can't uncheck the CQ only and Filter boxes while using Auto Call. Sometimes I'm looking for POTA, VOTA, etc., and can't see them while using Auto Call.

Auto CQ does not seem to work. Keeps ignoring callers despite filtering off. Version wsjtz-2.6.1-1.33-win64

I have a question about the automatic logging feature in WSJT-Z. The Northern California Contest Club is sponsoring a new weekly 30 minute FT4 Sprint contest, This contest uses grid square exchange, same as ARRL IDC, with QSOs completed in 2 phases or 15 second. This is done by not transmitting the RR73 or 73 messages, as shown in the table in www.ncccsprint.com/ft4ns.html I understand from europeanft8club.files.wordpress.com/2019/10/ft4_protocol.pdf that FT4 is presently configured so that a station operating in Search-and-Pounce (“S+P”) mode logs a QSO when RR73 is transmitted, and the CQing (“Run”) station logs a QSO when RR73 is received. Can the improved WSJT-Z be configured to automatically log as shown in the table without transmitting or receiving RR73? Clicking "log QSO" is the workaround solution with all the existing FT software, but it is too slow for the FT4 sprint. Looking at the table in ncccsprint.com/ft4ns.html the trigger for "log_QSO" command when in NA VHF or similar "grid-only exchange" contest mode (1) for the runner is the beginning of phase 3 when starting the transmission of "hiscall mycall R mygrid". (2) for the S&Per is at the end of phase 3 when finishing the decoding/receiving of "mycall hiscall R hisgrid" Is it possible to program this? 73, Peter VE7AB

The memory leak in the 1.33 version makes it not possible to use it after a short period of time. In this version, it's also possible to turn on or off the data elements like DXCC, Distance, etc, but the columns are not resizable and not movable. It's not possible to organize them as you want. The font in messages on the right panel is different for different rows, make look ugly. All of that could be OK to accept is the most terrible bug - after some short period of time system stop decoding messages until restarted. Bad build, with too many bugs...

Pour l'avoir utilisé quelques jour, WSJT-Z me plait beaucoup (j'utilisais JTDX qui lui fonctionne toujours) mais alors que je modifiais des paramètres il s'est bloqué. Message d'erreur dès l'ouverture "Sub-process error et Failed to close orphaned jt9 process" puis "Fatal error et Sub-process error". Je l'ai désinstallé puis réinstallé il ne fonctionne toujours pas. Merci d'avance pour les informations que je pourrai recevoir.

prawdopodobnie projekt już nie jest rozwijany, opiera się na starym , z grudnia 2021, WSJT-X v2.5.4, po 3 dniach testu zauważyłem, że nie współpracuje dobrze w funkcji hound z najnowszymi WSJT-X , po prostu używając tego programu z niektórymi stacjami DX nie dokończycie QSO w trybie HOUND, następnym minusem jest Auto Seq umieszczony w zakładce a nie w głównym oknie programu, przełącznik F/H przełącza też częstotliwość na domyślna dla FT8 dla danego pasma, jest jeszcze kilka drobnych niedociągnięć które zauważyłem a były by przydatne użytkownikom, szkoda, że autor tego modu tak to porzucił, bo ta modyfikacja mogła mieć miano najlepszej

Downloaded the software READ the help file studied the the way to use this software, find it is doing exactly as required. Still keep my eye on it but have found no problems so far. Will you be updating your fork to include the latest relase of WSJT-X 6.0

Its works. If I may, I'd like to make a couple of sugestions - When calling auto some station, if that station has a contact in progress, abort inmediatelly. It works sometimes. It would be good some checkbox in settings (abort calling when the other callsign has a contact in progress) - The Wd is erratic when setting to 1 in Ft8. Instead of minutes, it would be very nice if there's an option for 'cycles'. For instance, in FT8, abort if after n cycles completed and no response. Same for FT4 - Add an option in settings, auto call (n) CQ's every x minutes. Actually it can be made when alternating between autoresponse, but I'd like just to call the Cq's after serveral minutes, no alternating responding a calling cq. - Cycle in autorespond in JT9 is not working properly.

Hi, Thanks for the great job, it's fantastic! I'm working around to work my station all on automatic mode, and -Z Is the base! My next idea Is to use All.txt file, in AppData location, read all RX frequencies list and move my TX frequency to be different of them. ( Dark zone in waterfall). Can you have amy suggestioni to do this? Can you please think to implement it in next release? Thank you Giorgio

I am using the last version : mod 0.81 Mostly very usable and easy but there is some simple issues that persist since the first versions. The green color for CQ messages are bugged. If it is set, many other messages that are not CQ , turn green. Other issue is when the autocall is set automatic the program waits one turn to call the station selected from the program. Other thing is that if it is in automode and in autocall, the program should save the stations that called you, to be able to answer then, after some tries to call the station that the autocall selected. One last thing is, that would be nice to be able to unset the "Filtering" and the "CQ only" field when in the autocall mode. I really enjoy watching the decodes all the time in the decode screen. I think it would better be an option instead of mandatory.

v0.81 "Pounce" is not working. v0.74 works. Thanks again, . de JA5FNX

Excellente software, tnx 73 de Felix YV5GRV - 4M5F

Excellent mod to the famous WSJT-X software...it has A LOT of features, but you have to play around with it to get everything setup for your use case. Example and point...I noticed I was calling a station minutes on end with no response, so after looking around in the settings I noticed a watchdog timer that cut TX after quite a few minutes. So I set it to two minutes on FT8 and 1 minutes on FT4, so now if a station doesn't respond during that time frame then I move on. Thank you SQ9FE for your hard work on this. It's much appreciated! Feature additions ideas: -Feature to auto call specific stations calling CQ based on their location, grid square, state, country, etc...I know you can kind of do some of this based on the filter settings, but you can't get very specific from what I can see.

I just downloaded today and I would say FANTASTIC. So far, so good. I let it run in both automatic modes for awhile tonight on 160 FT8. It probably worked around 70-80 USA stations. I have a few questions / perhaps requests that I will address in the coming days. Great job SQ9FVE and a BIG Thank You for your dedication. 73 de Jerry, N9AW

ohhh!!!! LoL TKS TKS TKS TKS MASTER OF MASTER --- LU9DCE 73!!!

I found a problem in WSJT-Z when working in AUTO Call mode. The program ignores the messages of the CQ WW, CQ TEST.

Very nice project. Very good work. 73 DL7TY

version .044 ist great! There are just some "bugs" which pop up all the time on several stns: Rig Failure * Hamlib Error * Communication Bus collission while getting PTT state". This error was observed already some years ago, the disappeared with a new version. Now it's back and consistent. Happens at my stn once within 24h. There's little info interchange on the board? Why? 73's de Stefan DJ5YS/KG2FD