Greeting to everyone AFTER getting FT8 to run after installing WSJT-X v2.4.0 software, I have discovered a new problem. I call CQ and another station responds. The software runs us thru the contact

Hi Mark, do you have a CAT interface? 73 Bill G4WJS.

Hi Pete, the only serious errors there are a failure to connect to DX Lab Suite Commander, or something that emulates that like the N1MM Logger+ WSJT-X interface module. Are you

Well first off thank everyone for helping me. I have the software running and am copying transmissions on the band. I can double click on CQ’s and if I enable the TX it appears to be sending.

Can anyone help me decipher what the error was and help resolve it? [SYSLOG][2021-08-26 19:36:45.589431][00:00:00.000620][info] Log Start [SYSLOG][2021-08-26

Hi Jim, the decoding effort on all candidate signals is equivalent, obviously some that are easy to decode are processed much more quickly than others. The time offset is only relevant for choosing

Hi Ryan, possibly someone in JO22li square has a call that is a hash collision with yours. As they are sending a 6-character grid they will be sending message pairs with a hash code in the second of

As the maximum system clock error is less than 100 microseconds, I doubt it is a factor. Out of curiosity, how much effort does WSJTX expend on decoding signals more than a couple of hundred

I had the same issue the other day DN90 is correct where did the other grid square come from?

If your antenna system gets worse from loose or wet or corroded connections, you might have more RFI in your shack than you had last week. 73, Willie N1JBJ

Many thanks all for your suggestions I have added 2 clip on ferrites to the usb cable at the scu-17 end and all now appears ok? I have no idea why it should go from being fine to being plagued with

Thanks everyone. This is sort of what I expected. I'll look into the other software mentioned. I guess I have to start actively monitoring the DX expeditions and get serious about

This is one situation where keeping track of spots on clusters really pays off. Someone will likely post any F/H operation. It's difficult otherwise to keep track of all the bands and frequencies as

Greeting to everyone I used Miguel's - ea4bas - suggestions and now WSJT-X v2.4.0 works fine the following settings. Thank you to everyone who has assisted me in solving this problem. 73 Dick -

Not really, although there are some that are frequently used, but to eliminate QRM, most DXPeditions will list on a webpage what frequencies they will be using. Neil, KN3ILZ

It looks like the TNX 2BND 73 message has been coded into a standard <CALL> <CALL> 73 format. WSJT-X is not going to know that it’s not a real call. I don’t know if there’s a way for WSJT-X

I've looked and not found an answer. Is there a common frequency that DX expeditions use for Fox & Hound operations? 73, Norman KC9NVN

perhaps this will have some useful info https://speexpertamps.groups.io/g/main/files/Connecting%20Icom%20Radios%20to%20SPE%20Amplifiers.pdf -ll- Don W6CZ/W6ZBa DM07bk

Here is a screenshot. Thanks, Bob KM4RL

Well I did try selecting the actual device as well but the effect is the same. Default output works fine. It's gotta be an bug on WSJT-X's end because it works fine on the windows version.