Jim, you are amazing. You must monitor this group pretty closely. Thank you for your quick response. I hope others who take the plunge and get a new M1 Mac will see this solution. I have only one

Aside from FALSE DECODES, it has happened to me on 6m because WSJT-X is uploading my decodes to PSK Reporter. So sometimes people see that they probably have propagation to me, and that my rig is

That's happened to me as well. I assumed they were monitoring pskreporter. One, during the ARRL Grid Chase, was so soon after I changed bands and before I'd transmitted that I assume it was an

Ken - bring up a terminal session and run the following two commands. You will probably be asked for your password after entering the first one: sudo sysctl -w kern.sysv.shmmax=104857600

Hello everyone, After 30 years without a mac - my last and only one was the Mac SE - I took the leap and bought the Mac M1 Mini. I am proficient at running wsjt-x on Windows and Linux. I cannot get

Hi Phil, that's not correct, there's no use of previously decoded callsigns in the decoder. You may be recalling that some messages have calls substituted with hash codes, which

I though I read once that WSJT-X tries and correlate what it can’t quite decode with calls it’s seen before. This is obviously gibberish, as the grid-square is in the middle of the south pacific,

Hi Dave, this happens because of AP decoding techniques, it is a false decode. In this case a priori decoding postulates that you might be being called as a result of calling CQ and, by assuming

Actually it's valid. It's a new "feature" in the contest modes of the WSJTx v2.3.0 rcx they are testing. It will more fully look like a CW or RTTY contest contact might. -- 73's George -

I run WSJT-X (2.2.2) and JTAlert (2.16.15). Recently I have spent quite a lot of time just monitoring 15m, and never transmitting. I have noticed several times that I get called by a "station" with

Works perfectly. I finally figured out how to get this issue resolved. The problem was neither the radio or the computer, just a misunderstanding on my part to get the unzipped files working as they

Hi Bill, That helped and the GUI is now looking good. But now it's not transmitting anymore. I try to figure it out, and if I don't find a solution, I will open a new topic here. 73 Reiner DH9FAX

First, if this is a known problem, sorry for the repeat. I looked a little bit but could not find this problem reported. With WSJT-X, I use the 'worked before' feature to help me spot new contacts.

Jtalert will close if you check the appropriate boxes.

That’s a false decode. They can be ignored.

I keep seeing messages like this. Is this a secret coded message or what ? This was on 160m FT8, but I see like messages on other bands also. TU; 6S7MON DY7MVD 599 1924

Hey Bill.. is it possible that I am looking for the wrong information output? I got the impression from one of the texts that I should get something like: SLope .046 +/- .004 ppm intercept: -.065 +/-

I have been opening directory using the file menu item but when I run \tools\solve for calibration parameters I still get the same error message. and just for information the fmt.all does not have a

Hi Jim, that's fine, just be sure to use the "Menu->File->Open log directory" to locate the right files for each WSJT-X instance. 73 Bill G4WJS.

Hi Jim, that looks fine, I suspect it is an old file from a previous run. If you are running on Windows then make sure your fmt.all file that you cleaned up has the right file name