: Monday, 17 December 2018 15:38
To: WSJT software development
Cc: Black Michael
Subject: Re: [wsjt-devel] odd behavior
I've had this happen in the middle of a QSO a few times now on V2.
de Mike W9MDB
On Sunday, December 16, 2018, 5:16:36 PM CST, Gary Rogers
mailto:cgaryrogers
I've had this happen in the middle of a QSO a few times now on V2.
de Mike W9MDB
On Sunday, December 16, 2018, 5:16:36 PM CST, Gary Rogers
wrote:
I’ve seen it in previous versions too…It happens when i hit the halt TX button
shortly after the transmit cycle starts…Apparently the
I’ve seen it in previous versions too…It happens when i hit the halt TX button
shortly after the transmit cycle starts…Apparently the software thinks it
should be receiving but the transmitter remains activated...Gary KO3F
> On Dec 16, 2018, at 3:50 PM, Black Michael via wsjt-devel
> wrote:
>
Mike,
Yes, that was it. I changed the rig control program from HRD to Win4Yaesu,
and that required changing the Rig setting in WSJT-X from HRD to Yaesu
FTdx5000. That apparently changed the Split setting and the Bandwidth
setting.
Going back and looking at it, you are also right about the
It sounds like you have File/Settings/Radio/Split Operations set to
"Rig".Rather than saying random freqs it would help if you were explicit about
them.The expected behavior is 500Hz changes every 500Hz of offset.
de Mike W9MDB
On Wednesday, July 11, 2018, 6:25:48 PM CDT, Frank
I was using WSJT-X with no anomalies, making contacts regularly. A few
nights ago, it started doing two strange things.
First, it would transmit on VFO B of my FTdx5000, regardless of how I had
it set, and regardless of the band or frequency of VFO B.
Second, the audio transmit frequency seems
While using MSK144 (r7472) this morning, I noted the following odd
behavior several times that I don't recall seeing before.
1. click radio button TX6 for CQ
2. click [Enable Tx] to begin sending
3. as CQ's are being sent, enter a new DX callsign and grid square
4. click [Generate Std
Not sure if I'm the only one experiencing this, but every once in a while, when
the transmit function will not enable but I'll show a trace and subsequent
decode on the screen that ends up being my CQ... Screen shot attached to show
you what I mean. I've run into this randomly with all builds
