See if this helps
https://groups.io/g/KenwoodTS-2000/message/127
Mike W9MDB
On Wednesday, October 19, 2022 at 06:13:17 PM CDT, Don Hawbaker
wrote:
I have a TS-2000X that I have been using for sometime with WSJT. Works well.
I recently acquired a second TS-2000. I have no tran
On 20/10/2022 12:05 am, Frode Igland via wsjt-devel wrote:
I have used the "Tx power" field in the WSJT-X logging window for most
of my tens of thousands of WSJT-X QSOs. Whether I enter "40 W", "40W"
or "40", it hits my HRD Logbook as "40
Frode,
I recall that you are using JTAlert, is that
Hi Frode
I agree with you that in practice many
applications are tolerant and read non-compliant
ADIF files without errors. However, my report was
actually triggered by a practical problem.
Concretely, I tried to read the ADIF file created
by WSJT-X using the Python library "hamutils".
This
On 19/10/2022 18:24, Barry Jackson via wsjt-devel wrote:
Seems my reply only went to Mike so forwarding to list.
...but no attachments!
Here they are.
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/l
On 17/10/2022 09:24, Uwe, DG2YCB wrote:
Hi Barry,
A couple of days ago, we already made a few minor improvements to the
GUI stretching. It should be better in the next release. However, this
error occurs only under certain conditions (application font, font size,
screen size, style sheet, Qt ver
WSJT-X v2.6.0-rc4, Win 8.1 64 bit.
First run after installation throws a rig control error. Radio is OmniRig Rig1
and Omni-Rig client is already running and connected to TS-590S when WSJT-X
started. Error not seen if WSJT-X closed and re-started.
First run after installation the band selector
Hi, Roman.
My experience is that the ADIF format accepts more than the ADIF
specifications may indicate. I have used the "Tx power" field in the WSJT-X
logging window for most of my tens of thousands of WSJT-X QSOs. Whether I
enter "40 W", "40W" or "40", it hits my HRD Logbook as "40", i.e. a clean
Hi Mike,I wonder if they are running their receive audio level too hot? On
your suggestion my receive level never exceeds 40 dB and I decode flawlessly
with the exception of very weak -20 signals. The other things we found that
can seriously effect decodes are AGC level and any receiver digita
