Bil, G4WJS wrote:
Hi Rich,
I'm not sure the behaviour you describe has been implemented since mode
specific working frequencies were introduced several versions back.
* Iagree it is probably desirable behaviour and I have changed WSJT-X
forthe next release such that, only if a working
In the latest version of the QLog program, written so blind hams can use
the WSJT-X digital modes, the MSK144 mode was added. When testing MSK144 I
discovered that when the MSK144 mode was selected while the radio was still
on any HF band, instead of switching to one of the MSK144 VHF/UHF
As I recall in earlier versions of WSJT-X, when in the FT8 mode, when a
user typed a band number followed by the letter "m", such as "20m", in the
Band pulldown menu box, the frequency would change to 14074 KHz. However,
in version 2.2.2 when "20m" is typed into the band box, instead of
switching
In the WSJT-X Band Activity column most of the stations that I have worked
before on the active band have a green background color with a grey
background behind the call letters. However, I've noticed that a number of
stations that have been worked previously on a band do not have the grey
behind
I just downloaded and installed RC3. With the RxFrequency column in focus,
the Erase button works, but with the Band Activity side in focus the Erase
button has no effect. However, using a right click and then selecting
'Erase' does work OK on both sides.
I reloaded RC2 and found that it has the
*Using 2.2.0-rc1, when completing an FT8 QSO and an RR73 is received I send
a 73. However if the station doesn't receive my '73' message, he re-sends
his TX4 RR73 message. When I double click on his first RR73 line, instead
of sending me sending the correct Tx5 '73' message, WSJT-X sends the
2.2.0-rc1 Anomaly responding to MSHV (?) station
This morning, running 2.2.0-rc1, I called ZW5STAYHOME on 30M FT8 with “Auto
Seq” checked. It appears that he was using MSHV or another modified clone
of WSJT-X which allows working on 2 stations at a time, as you can see by
the screen capture
Hi Joe and the WSJT-X Development team.
First, thanks for incorporating the Ctrl-R and ALT-R shortcuts and
other changes into WSJT-X Version 2.2.0-rc1. Adding they will help the
blind and visually impaired Hams as they work FT8 using the QLog program
developed by Sam, W2JDB. I'm looking
Ken,
If you were operating in England, you call would be sent as M/NU0C and
not NU0C/M. If you were operating mobile in England, it probably would be
sent as M/NU0C/M, right?
73,
Rich - K1HTV
= = =
Re: K2H/NAS and GRID SQUARE
From: Kermit Lehman
Date: Sat, 02 May 2020 10:42:41 EDT
Ron,
On the WSJT-X Wide Graph (waterfall) window screen , make sure that the
"Ref Spec" check box in the lower center has not been accidentally checked.
If checked, no signals will be seen on the screen and no WSJT-X signals
will be decoded. This booby trap has caught me a number of times when I
Barry,
An error message when trying to fetch the LOTW CSV file is usually an
indication that you have the wrong version of the SSL library. The correct
one is the 32 or 64 bit version marked as "Light".
The 64 bit version can be downloaded from:
John,
The station may have been using MSHV or one of the other WSJT-X clones
which allows the user to transmit multiple streams. Such stations are not
constrained by having to transmit as a Fox on the even sequence, even
though you may be seeing them transmitting multiple streams. Unlike WSJT-X
Seannon AG0NY ,
The FCC rules regarding 60 Meter channelized operation require that all of
the components of upper sideband voice transmissions remain within the
defined channel.
60 Meter Channel 3, (5357 KHz) is used for FT8 operation in the States and
a number of other countries. The center
,
Rich - K1HTV
= = =
From: Christoph Berg
To: WSJT software development
Cc:
Bcc:
Date: Thu, 20 Feb 2020 16:15:04 +0100
Subject: Re: [wsjt-devel] Band change
Re: Rich Zwirko - K1HTV 2020-02-20 <
cano4n8xl2foairobtzwhsuqsezdrvk688i+aekzzoa9up-j...@mail.gmail.com>
> If you use the "Blank
Uwe,
Remember that for FT8 WSJT-X records a WAV file for 13 seconds then
decodes it. If you switch bands in the middle of the receive cycle, you
will record a mix of stations from both bands into the WAV file. When it is
decoded, you will see a mix of decodes from both bands which you can't
When I started the RTTY RU, the original wsjtx_log.adi file was saved as a
bak file and the Cabrillo file was reset to zero QSOs. Colors were set per
Joe's' suggestion in his January 2019 QST article> All went well for about
2 hours. As stations were worked, when they showed up again in the Band
Hi Joe and thanks for the rapid response to the request of the visually
impaired QLog beta testing team for a shortcut to change the WSJT-X "TX4"
message from RR73 to RRR. The creation of an "ALT+R" shortcut will be
great, but it shouldn't be a toggle function. For some reason, not all of
the
Over a year ago, a call went out on the WSJT-X Development Reflector for a
programmer who could write a piece of software, which would work with
WSJT-X give visually impaired Hams the ability to make contacts using FT8.
A programmer, who spent over 4 decades programming for a number of Wall
Street
Grant,
By any chance could the problem described have been caused because under
Settings, General tab you had the "Disable Tx after sending 73' check box
checked? I don't know if this might be bypassed in the Fox mode. If not, it
should be disabled automatically when the Fox mode is used.
73,
David,
The DXpedition User's Guide, section 11 has the answer to your question. It
says:
"You will need to re-activate Enable Tx (or hit Enter on the keyboard) at
least once every two minutes. (This restriction is to ensure that an
operator is present and paying attention.)".
73,
Rich - K1HTV
=
This morning it took three attempts to finally work ZK3A on 80M FT8 in the
F/H mode. In the first two attempts, after ZK3A answered me, my tone
frequency was moved to their TX tone frequency as was expected. Then for
two transmissions, they sent calls and reports but did not copy the Rogers
and
I know that when using the MSK144 mode, if the green bar in the lower left
corner "Receiving xx%" stays at a low number, the CPU is not being
overworked. We are told that we can leave the 'Tol' setting at the maximum
200 Hz. Using the wider "Tol" setting will allow the decoding of stations
whose
Since it was introduced in 2017, it has been very difficult and nearly
impossible for visually impaired/blind Hams to use WSJT-X and its FT8, and
now FT4 modes. Last year, at the request of some of my visually
impaired/blind friends, I started to search for a programmer who might be
able to create
Thanks to Mike, W9MDB, who suggested to do a frequency reset to resolve the
problem noted in my earlier email (below). All is well again after the
reset.
73,
Rich - K1HTV
= = =
From: Rich Zwirko - K1HTV
To: WSJT
Cc:
Bcc:
Date: Wed, 31 Jul 2019 17:06:42 -0400
Subject: [wsjt-devel] FT8/FT4
Hi Mike,
Good on the note, but I'd correct the last line "73's".
73 means 'Best Regards'.
73's translates to "Best Regards's" (Regardses) 8-).
I know, picky, picky.
Regarding emailing 'educational' notes, I regularly do so to loud locals
who call CQ on 6 Meter FT8 during the 1st & 3rd 15
During this past weekend's CQWW VHF contest I operating on 6 Meters,
primarily using the FT8 and FT4 modes. Of the 312 QSOs made, 212 of them
were on FT8 and 79 on FT4. The other 21 QSOs were on the analog modes.
I ran WSJT-X with N1MM and all worked fine. The best FT4 DX to the east
during the
Laurie,
Your idea of switching from the contest configuration to the one used for
normal operation looks good on paper, but there is a problem. When the
normal configuration comes up, the callsign of the station you were working
is replaced by the call of the last station you worked with the
Your idea of switching from the contest configuration to the one used for
normal operation looks good on paper, but there is a problem. When the
normal configuration comes up, the callsign of the station you were working
is replaced by the call of the last station you worked with the normal
I downloaded and installed the 64 bit version of WSJT-X on my 64 bit
Windows-7 computer.
Changing to the Win64OpenSSL_Light-1.1_0k.exe file has resolved the problem
of receiving an error message when doing a 'Fetch' of the
'lotw-user-activity,csv' file.
However, when I try to bring up Settings,
As some may have heard, a program is being developed which will allow
unsighted Hams to make FT8 QSOs. Today the topic of decoding signals on the
WSJT-X waterfall came up for discussion in the QLog Beta testers group.
I posted this info, which I'd like to share with the many who subscribe to
the
From: Joe Taylor
Sent: 10 July 2019 01:41
To: WSJT software development
Subject: Re: [wsjt-devel] FT8 ghost signals
Hi Conrad,
On 7/8/2019 18:29, Conrad PA5Y wrote:
> In fact Martin, sometimes they clearly AP reflections are but often they
are not. They have no discernible doppler slant at all
Reino,
Yes, the main stronger FT8 signal is the one heard directly. The Doppler
shifted signals, reflected from the direction of a strong Es cloud, are
usually between 40 and over 100 Hz lower, with the average of around -70 Hz.
73,
Rich - K1HTV
= = =
From: Reino Talarmo
To: "'WSJT software
Here in the Mid-Atlantic, a number of 6 Meter FT8 DXers have observed
backscatter signals that appear as a 2nd or even a 3rd signal on the WSJT-X
Wide Graph window. The Doppler shifted frequency is usually lower than the
direct signal. In addition to the directly received FT8 signal appearing on
On Monday, July 1, the Mid-Atlantic had a very long duration opening to
Europe. While I was on the ON4KST IARU Region II chat, I announced that I
was going to call CQ using FT4 on 50.318 MHz. Within a few minutes I worked
F5SDD and IZ8WGU for what may be the first 2-wayTrans-Atlantic FT4
Your suggestion does not work here with Windows 7. I tried simply typing
"ALL.TXT" in the search window but the file, which resides in
AppData/Local/WSJT-X, is not found.
Your suggestion of using "FIND" does not allow the user to easily browse
through the ALL.TXT file, which is what I want to
I often use my Android phone with Real VNC to make FT8 QSOs when I'm not in
the shack. But with its small screen, the WSJT-X screen must be enlarged in
order to read what is on the screen. Its important to know the progress of
the TX/RX sequences. But when zoomed in on the lower right hand of the
Recently, a WSJT-X users asked me how to check if a QSO was actually
completed. He had received a request to confirm a QSO which was not in his
log. I pointed him at the ALL.TXT file. He got back to me later saying that
the file size was enormous and too large for any of his text editors to
read.
Well, the FT4 mode in WSJT-X 2.1.0-rc7 worked great at the K1HTV QTH in
the mock RU test. There were plenty of participants. Here are the totals:
189 QSOs (156 on 20M, 33 on 40M)
26 countries
29 States
4 VE provinces
TX: K3 (70W)
Antennas: A3S at 70ft and ZS6BKW antenna for 40M.
Bill et al,
If stations with non-standard non-compound calls are presently allowed to
skip the TX1 message and start with TX2, will a future release of WSJT-X
inhibit users with such calls from doing the TX1 to TX2 skip?
73,
Rich - K1HTV
= = =
Hi Mike and Jari,
I will qualify that. For
While WSJT-X decoding FT4 stations on 14.080 MHz, the following error
message was received:
“Subprocess error
Sunprocess failed with exit code 2”
Details of the failure:
Running: C:\wsjtx5\bin\jt9 -s WSJT-X -w 1 -m 3 -e C:\wsjtx5\bin -a
C:\Users\k1htv\AppData\Local\WSJT-X -t
communications for the Radio Amateur community.
73,
Rich - K1HTV
= = =
Date: Tue, 23 Apr 2019 02:08:08 +0100
Subject: Re: [wsjt-devel] Program for blind ops needs 2 shortcuts
On 23/04/2019 01:49, Rich Zwirko - K1HTV wrote:
Would it be possible to add the following shortcuts to WSJT-X 2.1.0 rc5
before
WSJT-X Development Team
A year ago I made a request for a software programmer to help develop an
application which would allow our fellow blind Radio Amateurs to make FT8
contacts. When a second request was made a few months ago, Sam Birnbaum,
W2JDB, who developed software for a number of Wall
Mike,
I've been using the free LP-Bridge software with my Windows 7 system for
many years with my Elecraft K3. The K3 is connected to LP-bridge which
creates multiple virtual ports. The K3 can simultaneously connect to
WSJT-X, N1MM, MMTTY, DX Lab suite's Launcher and Commander applications.
I too like the idea of separating the special Fox/Hound frequencies from
the main list and having them activated when that mode is selected. Having
multiple frequencies to choose from in the band list can be confusing,
especially to the new user. A smaller subset, most likely only one per band
Marco,
If you mean tab 3 in the Standard Messages area of the screen, I believe
that Tab 3 is only used by DXpeditions in the Fox/Hound mode. It is not
used in normal operation.
73,
Rich - K1HTV
On Mon, Feb 11, 2019 at 7:51 PM Marco Calistri wrote:
> Yes Rich,
>
> I confirm that TX6 edit
Marco,
Edit your TX6 message to read "CQ OC PY1ZRJ GG87" then try it. It should
work. Do NOT try to modify the TX5 message as it is limited to 13
characters.
73,
Rich - K1HTV
= = =
From: Marco Calistri
To: "'WSJT software development'"
Cc:
Bcc:
Date: Mon, 11 Feb 2019 22:14:29 +
In testing out various keyboard shortcuts which might have to be used by
blind ops when calling a FT8 particular station, I ran into a possible bug
in v2.0.0 . In the sequence tested, for the op to type in a specific call
into the 'DX Call' box, I did the following sequence:
F4 (cleared message
FT8 for the blind?
Over the past year I have received emails from blind Hams wanting to use
the FT8 mode. I posted a note to the WSJT-X Development reflector. The only
comment received was a suggestion that an outside group should develop the
software app needed to accomplish this objective. I
VK2/G3NJV.
Paul,
In addition to being active using WSJT-X v2.0.0 784f75 , I also run a
Redpitaya to decode FT8 stations and feed the FT8 RBN as well as PSK
reporter. My spot of you may also have been from the RP receiver/decoder.
73,
Rich - K1HTV
= = =
From: Paul Randall
To:
FT8 in State QSO Parties?
This year there will be QSO parties for all States except Alaska. Most are
run by individual States, but there are two regional ones (New England QSO
Party and the 7th Call Area QSO Party). At present in WSJT-X V2.0.0 there
isn’t a FT8 ‘Special Operating Activity’
: Bill Somerville
To: wsjt-devel@lists.sourceforge.net
Cc:
Bcc:
Date: Thu, 20 Dec 2018 15:44:52 +
Subject: Re: [wsjt-devel] Wrong band info at times
On 20/12/2018 15:30, Rich Zwirko - K1HTV wrote:
Any idea as to why WSJT-X is responding this way?
Hi Rich,
WSJT-X in FT8 mode is a block message
I noticed during the FT8 RU that the log page, although in UTC, is not in
the 24 hour format but uses the 12 hour plus AM or PM. Who uses UTC in 12
AM/PM format? Almost all Ham logs are in 24 hour format, right?
73,
Rich - K1HTV
___
wsjt-devel mailing
52 matches
Mail list logo
