"Both Windows 7 or 8.x version support will not be available for Qt 6.
Microsoft discontinued the support for both Windows versions some time ago, and
as a vendor, we can no longer maintain support for these windows versions in Qt
6. Windows 7 (both 32bit and 64bit) was supported as a target in
"I have been using WSJT-X since before version 1.0 was released. I have never
heard WSJT-X produce an alert sound."
Never mind, I see it is an option that have not enabled. I use JTAlert.
73
Andy, k3wyc
___
wsjt-devel mailing list
wsjt-devel@list
" Currently, WSJT-X uses the system’s default audio output to play alert
sounds."
I have been using WSJT-X since before version 1.0 was released. I have never
heard WSJT-X produce an alert sound.
What WSJT-X alert sounds are you hearing/transmitting?
The usual problem is that the operator con
re fix for 2.8.0. improved with Win 8.1 -
"WSJT-X rig control will now work until WSJT-X is closed"
Rig control fails as soon as TX is made so, although stable for band change and
frequency change in band, fix is no use for operating.
73,
Andy, k3wyc
April 16th I reported that I was having issues with ver 2.8.0 -
"Changing band on WSJT-X changes the "dial" frequency displayed my WSJT-X but
does not change the frequency of my TS-590S. I revert to devel 240721 improved
PLUS and rig control works."
Uwe, DG2YCB and Roger, W3SZ spent a lot of t
"2.8.0 improved, when used with OnmiRig, does not control rig frequency when
Mode = None. It does control rig frequency when Mode = USB."
A bit more experimenting with 2.8.0. showed MODE=USB was a necessary but not
sufficient condition. Rig control only seemed to work if Split operation was
c
I am using OmniRig 1.20 as downloaded from DX Atlas site.
Would anyone who is using OmniRig with 2.8.0 improved please send me a screen
shot of their Settings/Radio. If my address is not visible here it is good on
QRZ.
It is obvious that some aspect of the OmiRig interface was changed between
Since OmniRig works for other users I tried to find out what configuration
difference could account for my problem.
I have always used Mode = None because I want to take responsibility for my rig
configuration.
2.8.0 improved, when used with OnmiRig, does not control rig frequency when
Mode =
Is anyone else seeing problems with 2.8.0 250314 improved PLUS when using
OmniRig?
Changing band on WSJT-X changes the "dial" frequency displayed my WSJT-X but
does not change the frequency of my TS-590S. I revert to devel 240721 improved
PLUS and rig control works. WSJT-X "dial" does not disp
"I don't have to ever touch the radio dial, Andy. If SpotCollector shows a
spot, I double click on it and it moves me to the mode and exact freq for
the qso. (DXLabs Spot Collector). It's true for cw/ssb/digital."
You don't appear to understand that, if you do this and the frequency of the
spot
"Just remember: don't touch the radio vfo! If you make all changes in
frequency thru WSJT-X alone, then you will never have a problem."
give up the ability to click tune DX spots - No thanks
give up the ability to click on HDSDR activity - No thanks
I want to spot the frequency to which I decid
This was documented in detail in the thread "ALL.TXT RX freq is not RX DIAL
freq" July 2024.
https://tinyurl.com/ynajnra7
Read it all to find out how the developers responded.
Andy, k3wyc
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge
"In the 2.7 releases the rig moves to the correct frequency but the SteppIR
does not. "
How is your SteppIR controller connected so that rig frequency is available to
it? There are many different ways of configuring this interface and it doubt
it would be possible to investigate your problem w
WSJT-X v2.7.1 devel 240721
Win 8.1
I called Z22AO with F/H selected.
He answered with a report of -09.
I replied with his report of R-16 but saw no RR73
I exited F/H mode but the TX cursor stayed where it was (no problem with that).
I sent my report again on the next cycle.
I saw the reply K3WYC R
From: Joseph Taylor
Sent: Wednesday, July 31, 2024 6:58 AM
To: WSJT software development
Cc: Andy Durbin
Subject: Re: [wsjt-devel] ALL.TXT RX freq is not RX DIAL freq (Reino Talarmo)
On 7/31/2024 9:32 AM, Andy Durbin via wsjt-devel wrote:
> The problem I reported can be fixed either by us
"May I conclude that we want to report the actual
(correct) transmit frequency at all wsjt-x modes (by
definition the lowest FSK tone)."
I had intended to leave this discussion but, since you asked a direct question,
I shall answer it.
My preference is for ALL.TXT, PSKReporter, and logging to us
"All one has to do is enter or select the drop down freq...CAT will change
the VFO, the resulting passband will be 0 - 3000 Hz or whatever your rx
supports..and the signals will be there."
Where in the user guide does it say that these are the only methods of tuning
the rig that are acceptable?
"Digital -- we need need the "real" transmit frequency -- i.e. the tone offset."
When I spot an FT8 station with manual entry to DXSummit.fi I always enter the
suppressed carrier frequency. If you check there you will see that most
spotters do the same.
When I use DXKeeper to make a spot it u
"So for computer control, it is much better to not include the offset in the
frequency in the spot...so you don't have to do math in your head or guess
at the offsets, for your vfo to be set to the proper freq.
73, N0AN"
I am in complete agreement with this.
I would also add that it is not corre
;
if (m_lastBand != band_name)
On Sunday, July 28, 2024 at 11:55:46 AM CDT, Andy Durbin via wsjt-devel
wrote:
"What rig do you have that WSJT-X does not follow rig freq changes?
Mike W9MDB"
I have no such rig. WSJT-X follows my rig frequency with 1 Hz resolution as
indicated i
"What rig do you have that WSJT-X does not follow rig freq changes?
Mike W9MDB"
I have no such rig. WSJT-X follows my rig frequency with 1 Hz resolution as
indicated in the draft paper.
The issue is not that WSJT-X does not follow the rig frequency. The issue is
that WSJT-X knows the rig fr
I made a few minor corrections to draft 1 and draft 2 is available at
https://tinyurl.com/2s3drdra
For those that don't wish to follow links I have reproduced the conclusions and
the proposal below. I don't have the skill or knowledge to code this but I am
willing to test if anyone else decid
I ran some tests and documented the results. I made a proposal that HF
operators, particularly those chasing DXpeditions, may find useful.
A first draft is available on dropbox here - https://tinyurl.com/2p9pyds7
Comments are welcome.
73,
Andy, k3wyc
From: Andy
Joe,
Thanks for taking the time to improve my understanding of how WSJT-X frequency
control and reporting is designed to work. The design may be intuitive for a
VHF/UHF operator but it certainly was not for me as someone who only works HF
and 6 m chasing DX.
I think what I'd like to do is run
Joe,
Thanks for your reply and the explanation to the way the reported frequency is
intended to work.
I have quite often worked FT8 DXpeditions by observing them on my HDSDR
panadapter and clicking on the appropriate frequency. The rig changes to the
intended frequency, WSJT-X main window dis
"Turn your waterfall gain down (top left slider) and it will clean it up
mostly. I have a +20 dB SNR file and it is awful looking until you turn the
gain of the waterfall down."
Thanks for the tip. I have viewed many much stronger signals using the same
waterfall setting and have not seen simil
"I still don't understand why 21.091 was recorded correctly but 14.091 was not.
I'll continue to monitor unless the development team indicates the problem is
understood."
I ran a simple test and it appears the RX frequency recorded in ALL.TX is not
the current rig dial frequency (TS-590S with
"I'm decoding K8R on 18.090 with S/N varying beween +6 and +9."
Sorry, should have typed 18.095.
Andy, k3wyc
From: Andy Durbin
Sent: Monday, July 22, 2024 11:04 AM
To: wsjt-devel@lists.sourceforge.net
Subject: SF rc6 TX signal "fuzz"
I'm decoding K8R on 18.090
I'm decoding K8R on 18.090 with S/N varying beween +6 and +9. The tones are
clearly visible on widegraph and for most transmissions the signal appears to
be clean. Some transmissions have "fuzz" or spead on the individual tones but
the signal still decodes ok.
I experimented with different AG
RX frequency was correctly logged to ALL.TXT when tuned to 21.091. Neither
21.091, nor 14.091, was included in my frequency table.
The advantages that I know for having a frequency entered in the table are:
1.
The frequency is available for selection from the pull down list
2.
The frequenc
I'm decoding K8R at -9 for all stations in the decode but, on wide graph, only
the sync tone is visible (barely visible). The relationship between visible
signal strength and reported S/N seems to be very different from baseline FT8
or previous F/H.
Is that normal and expected or are the repor
In -rc6 the ALL.TXT decodes appear to be recorded correctly but the RX
frequency is still incorrect. For this report I was receiving K8R with dial
frequency 14.091.
240719_17423014.074 Rx FT8_SH -12 0.3 737 DK7DU K8R RR73
240719_17423014.074 Rx FT8_SH -12 0.3 737 DL1DUO K8R RR73
240
I have noticed when monitoring K8R that the message "K8R verified" is not
always displayed. The variation seems to depend on the number of encodes in
the tranmission. E.g.:
20m
131200 6 0.4 683K1VC K8R RR73
131200 6 0.4 683W4DID K8R RR73
13
WIn 64 bit, OS Win 8.1
ALL.TX log does not correctly record the decode window text and the QSO
frequency: -
Decode window:
181330 -1 0.2 730 K3WYC K8R RR73
181330 -1 0.2 730OZ3AEV K8R RR73
181330 -1 0.2 730G4WFQ K8R -18
181330 -1 0.2 730KA6RWL K8R -12
181330 -1 0.2 730
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,
Andy
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 2.6
shot, 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 scr
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 c
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 then
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 cycl
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 not
" 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 bac
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 H
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 t
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 size/position
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 audio
m/db/DG2YCB<http://www.qrz.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 t
the connection to OmniRig. But
that has since 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
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
Om
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
they
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 shu
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 o
63 matches
Mail list logo
