This continues to be a problem at my station and it has the potential to damage
my equipment as the spurious TX starts before my SteppIR has changed to the new
band.
Shouldn't WSJT-X clear out all generated messages on band change or, at a
minimum, flag that F/H QSO attempt has ended.
73,
Several times I have completed an FT8 F/H QSO on one band then changed to
another band with Hound mode still active. "Enable TX" is not active and no
intended transmissions have yet been made on the newly selected band. However,
WSJT-X starts a new transmission to the fox that had been worked
"I have noticed the same thing at times while running as Hound in F/H where
the report from the Fox will appear in the Band Activity column but not in
the Rx Frequency column. I am presently running the "WSJT-X V2.7.1 devel
231031 Improved PLUS" version."
I think I have seen this once with ver
I’d like to
follow up to understand this situation better.
Thanks,
-Brian N9ADG
Sent via iPhone
On Jan 24, 2024, at 7:16 AM, Andy Durbin via wsjt-devel
wrote:
As implemented in WSJT-X ver 2.6.1 the hound is able to select TX3 as their
first transmission. One user has posted a screen s
As implemented in WSJT-X ver 2.6.1 the hound is able to select TX3 as their
first transmission. One user has posted a screen shot showing that fox replied
with a signal report but the QSO could not be completed.
Since new WSJT-X ops seem reluctant to read the instructions would the
developers
It turns out that this problem is very easy to reproduce. First some
background on my configuration.
The TS-590S has both a USB port and a traditional RS-232 COM port. The USB
port connects to an internal USB hub which, in turn, connects to a USB UART for
CAT and a PCM2903B USB Audio CODEC.
I have it working again.
I had disconnected all cables from the laptop to access the battery. When I put
it all back together I had swapped the cables for the TS-590S USB port and a 10
port USB hub. I only realized this error when WSJT-X did not see my TS-590S
USB audio CODEC.
When I put the
I'm using WSJT-X ver 2.6.1 on a Win 8.1 laptop. I have been using OmniRig as
my radio interface for many months and the only issue has been that first start
after a new installation WSJT-X will fail to connect to OmniRig. It always
connected ok for second and subsequent starts.
Now I cannot
After a review of ALL.TXT I no longer think this was related to prior use of
F/H mode. I had set TX5 to a "CQ DX message" and that was auto sequenced after
RR73 was received.
I'll need to be careful to ensure TX5 is set correctly when in QSO.
73,
Andy, k3wyc
WSJT-X ver 2.6.1, Win 8.1.
I have observed several times that I could not complete a QSO by sending 73
after I had received an RR73. This is expected operation with F/H active but
not when F/H is not active. I suspect that something is latched in software if
F/H mode has been used but is
I worked 3Y0J 17 m FT8 February 11 at 1603 UTC. At that time they were
transmitting "even" and had a clock error of 0.4 seconds. F/H hound mode
worked as expected and moved me from 2579 to 256.
I was very surprised to hear the reports of a large clock error causing their
TX on the wrong
Also seen in 2.6.0.
Good to hear a fix has been coded. I was delaying making a report until after
Bouvet QRT.
73,
Andy, k3wyc
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
I made a copy of the ini file for the condition that connects to Omni-Rig and a
separate ini file copy for the configuration that does not connect to Omni-Rig.
I compared the files using WinMerge. I see no obvious difference that would
explain why one works with Omni-Rig and the other does
" https://wsjtx.groups.io/g/main/message/40301 "
Thanks for that link Martin.
I attempted to change to a previously saved Fox/Hound configuration that worked
fine in ver 2.3.0. It not only came up with a zero and red frequency box but
it also failed to connect to Omni-Rig.
When I switched
The -rc5 release notes say:
- When in Hound mode and click the "H" button again, the frequency
is now kept. This gives the user the following two options to return
to normal FT8 mode:
- Click the "H" button again. Then you will stay on the QRG.
- Click the "FT8" button (or use the
If WSJT-X 2.6.0-rc5 is closed with FT8 active and Hound not selected it
restarts with standard frequencies available in the frequency selector.
If Hound is selected the standard frequencies remain in the frequency selector.
If WSJT-X is closed and re-started then it opens with Hound active and
More detail on "Main window size/position is not remembered through shutdown
re-start. (previously reported and seems to be in all versions since 2.3.0)"
In addition to the previously reported issue that width and right edge position
are not restored -
With main window dragged to minimum width
"Do you have split mode turned on?
Does it behave if split mode is turned off?
Mike W9MDB"
Split was "Rig". No obvious difference with Split "None". Hang was not
associated with crossing a 500 Hz boundary.
Wide Graph hang can also be induced if the TX cursor is repeatedly moved within
a 500
WSJT-X ver 2.6.0-rc5 64 bit. Windows 8.1. TS-590S with Omni-Rig.
I frequently slew the TX frequency cursor by clicking on the TX frequency box
and using my mouse wheel. When I do that in 2.6.0-rc5 the wide graph pauses
and may hang for a second. Sometimes the TX cursor has a delayed response
WSJT-X v2.6.0-rc5, Win 8.1 64 bit. TS-590S with OmniRig 1.19.
When first opened after starting the band selector pull down list is abnormally
wide. Normal width seen after selector closed and re-opened. (previously
reported and seems to be in all versions since 2.3.0)
Main window
More detail on "Main window size/position is not remembered through shutdown
re-start. (previously reported and seems to be in all versions since 2.3.0)"
I'm running a laptop PC with an additional monitor. I have the WSJT-X main
window positioned in the lower right corner of the laptop screen.
WSJT-X versions 2.3.0, 2.5.4, and 2.6.0 rc4 do not display the correct audio
device names if the names have been changed. Other apps, such as Soundcard
Scope, show the current device name.
E.g. I change my TS-590S audio CODEC name from "microphone" to "TS-590 RX".
That name shows in the
com/db/DG2YCB>
Am 26.11.2022 um 17:56 schrieb Andy Durbin via wsjt-devel:
I have been running various versions of WSJ-X with Omni-Rig for many years.
After having my station shut down for about a week I can no longer run WSJT-X
with Omni-Rig. Error "Failed to start OmniRig COM server&
e resolved itself for me.
73 de DG2YCB,
Uwe
German Amateur Radio Station DG2YCB
Dr. Uwe Risse
eMail: dg2...@gmx.de<mailto:dg2...@gmx.de>
Info: www.qrz.com/db/DG2YCB<http://www.qrz.com/db/DG2YCB>
Am 26.11.2022 um 17:56 schrieb Andy Durbin via w
I have been running various versions of WSJ-X with Omni-Rig for many years.
After having my station shut down for about a week I can no longer run WSJT-X
with Omni-Rig. Error "Failed to start OmniRig COM server".
If I run Omni-Rig client it connects to my TS-590S with no issue. If I close
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
I seem to be having a bad day. I upgraded from 2.3.0 to 2.5.4. I have never
downloaded or installed 2.5.0.
So my revised report is:
I updated from WSJT-X ver 2.3.0 to ver 2.5.4 both Win 64 bit and I noticed the
following changes. I used the term regressions in the title because I think
I updated from WSJT-X ver 2.3.0 to ver 2.5.0 both Win 64 bit and I noticed the
following changes. I used the term regressions in the title because I think
they are. The developers may not agree that this characterization is correct.
1. Main window size is no longer remembered through a
re - Interaction with JTAlert has changed for single clicked callsigns. In
2.3.0 any decoded call would move the RX frequency cursor and populate the
Received frequency pane with the decode. In 2.5.0 only a subset of decoded
calls is responsive. (See HamApps thread "No click response if CQ
29 matches
Mail list logo
