Hi Joe,
some suggestions:
4.6 Frequency Calibration implies a link to instructions - FMT suite or
a simple example using WWV.
Not sure where this should go, maybe 5 "Transmitter Audio Level"; we
probably should mention the defect with the Windows Vista and later for
the Texas Instruments PCM2900 series CODEC (PCM2904 and below pre-C
revisions). This chip is used in most radios that have built in USB
CODECs as well as other interfaces so it probably effects many WSJT-X
users. The issue is that the device identifies as a microphone despite
being used as a line input. The fix is to set the mic level in the
Recording Device Properties to 0dB which is the correct setting for a
line input level. The defect causes boost of 30dB or more to be added
which severely clips the Tx audio even if the signal is attenuated at
source. http://www.ti.com/lit/an/sbfa020/sbfa020.pdf section 3 details
the issue with the device.
I would like to see 6.3 "Decoding Controls" mention that using "Lock
Tx=Rx" is not recommended since it encourages poor radio etiquette when
running a frequency because your frequency moves around following
callers. Alternatively it might be mentioned at 10.4 "Controls Center"
item 3.
8.2 EME with JT4 para 3: if the band is already in the table the offset
can be edited by double clicking on the offset field itself otherwise a
new band can be added by right clicking in the table and selecting
"Insert ...". Checking this revealed a regression in the drag & drop
behaviour from the working frequencies table view to the station details
table view which I have fixed in r6096.
8.2 EME with JT4 para 4: missing space in sometimesknow.
10.4 Warning: since JT65 maximum SNR value is -1dB it might be better to
say "consider reducing power if your QSO partner reports your signal
above -2dB".
10.6 Status Bar: image is out of date as we now have a progress bar.
10.7.3 View Menu & 10.7.4 Mode Menu: are out of date.
11. Logging: "More elaborate logging capabilities are supported in
cooperation with JT-ALERT-X <http://hamapps.com>, Ham Radio Deluxe
<http://www.hrdsoftwarellc.com/>, or the DX Lab Suite
<http://www.dxlabsuite.com/>." should say something like "More elaborate
logging capabilities are supported by third party applications like
JT-ALERT-X <http://hamapps.com> which can log QSOs automatically to
other applications including Ham Radio Deluxe
<http://www.hrdsoftwarellc.com/>, DX Lab Suite
<http://www.dxlabsuite.com/> and, Log4OM."
14 FAQ item 2: the +2kHz check box no longer exists, instead default JT9
working frequencies are specified in the working frequencies table and
they are automatically selected when switching to JT9 mode.
17: we are also shipping jt4code, jt4sim and, wsprsim.
17: We package rigctl-wsjtx which can be used to send CAT sequences to a
rig before and after running WSJT-X for example in a batch or shell
script file. The version we ship includes the latest Hamlib rig drivers,
as included with WSJT-X itself.
17: We package rigctld-wsjtx which allows other compatible applications
to share a CAT connection to a rig. The version we ship includes the
latest Hamlib rig drivers, as included with WSJT-X itself.
19: Acknowledgements: needs updating, particularly Steve K9AN !!
73
Bill
G4WJS.
------------------------------------------------------------------------------
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
