I am translating the v2.3.1 User Guide. In section 17.2.10, Table 7 quotes the FST4-15 Keying rate (Baud) to 16.67 baud, whilst the Bandwidth is quoted as 67.6 Hz. Should that be (16.67 x 4 =) 66.7 Hz

#FST4

The User Guide is generally mentioned as the first and foremost go-to reference for all WSJT-X questions, and obviously is an important tool in using and understanding the finer details of WSJT-X. I p

#QSO_practices #GeneralGroupInfo

Thanks for version 2.4.0-rc3. In the v2.4.0-rc3 User Guide, the illustration of section 10.1.5 Mode Menu shows the v2.3.0 Mode Menu, including QRA64 and ISCAT, both to be deprecated in v2.4.0. I guess

#mainscreen #FST4 #Q65

Thanks, Bill, for a swift response, as always. I will also update the Norwegian translation accordingly, and send a new edition to Joe for publishing. 73, Frode LA6VQ

#linux

When translating the WSJT-X 2.3.0 User Manual into Norwegian (sent to Joe yesterday for publication), I noticed that there are no instructions/code for uninstalling Debian on amd64. For installation t

#linux

Checking or unchecking "Disable Tx after sending 73" has no effect in popular modes like FT8 and FT4. It only works in modes where it is expected to have to repeat your 73 message many times in order

Re the 500 Hz "error" when using "Split" or "Fake it". The purpose of those two settings is to make sure that the FT8/FT4 audio signal stays between 1500 and 2000 Hz (to avoid the risk of intermodulat

From: VE3KTN Date: Sun, 21 Jun 2020 09:21:10 PDT ... It's too bad the logic is set up to detect the "73" string instead of just whether TX4 is being sent, as I've pointed out in a similar parallel thr

Bob G8HGN has an excellent memory. I copy an e-mail from Bill G4WJS dated 21 June 2018, settling the case: auto-tx after sending a 73 message is disabled when you have "Call 1st" checked, this is a de

+ AA6YQ comments below x LA6VQ comments below How do you see it possible that logged times can be consistent, when there is no agreed reference?LoTW serves its purpose, other online QSL/matching servi

Kai KE4PT, How do you see it possible that logged times can be consistent, when there is no agreed reference?LoTW serves its purpose, other online QSL/matching services serve their purposes, and conte

The standard format for contest logging is Cabrillo, which permits only one item for time. Therefore the contest adjudicators will never see more than one time in a contest log, so they will never hav

Running WSJT-X 2.1.2 on Win10 64bit Dell laptop with i7 processor, 8 GB RAM A while ago the automatic update of the LoTW-user-activity.csv file in Settings | Colors - [Fetch Now] button quit working,

Hi, Bob. This "operational inconvenience" is caused by the RR73 "convenient QSO completion procedure" when the conditions are good enough for RR73. It is easy to solve. First of all, follow the User G

Will it be Monday 11th or Sunday 10th? Frode LA6VQ

Checking or unchecking the "Disable Tx after sending 73" checkbox in Settings - General - Behavior has no effect in FT8 and FT4, as disabling Tx is the hardcoded default overriding the "Enable Tx" but

Darl, you may have found the answer, but I didn't see any response to your message. You are correct about the alternate F1 - F6 functions not being explained in the User Guide. In the WSJT-X main wind

Chuck and Thomas, I believe the original problem of RR73 or RRR in FT4 and FT8 was linked to contest modes. In ordinary operation, if I close WSJT-X with FT4 as mode and RRR in Tx4, QSJT-X will open w