Re: [wsjt-devel] Band box bug?

[Rich Zwirko - K1HTV]

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 frequency for the
currentselected mode and IARU region is available, will it accept a
wavelengthentry in the working frequency drop-down entry field, and in that
caseit will select the lowest working frequency for the currently
selectedIARU region and mode for that band.*

73
Bill
G4WJS.

= = =
Thanks Bill. Sorry I called it a bug. I should have better called it a
perceived anomaly. Thanks for planning to make the change in the next
release. It will be very helpful to our fellow blind and visually impaired
Hams who are using WSJT-X with QLog. Thanks again to you, Joe, Steve and
the rest of the WSJT-X Development team for all the work you have done.

73,
Rich - K1HTV
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Bug when using MSK144?

[Rich Zwirko - K1HTV]

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
frequencies, the radio remained on the same HF band that my K3 was set to
before the mode switch was made.

This means that if the user accidentally called CQ, the transmission would
be made on an HF band, where the MSK144 is not legal, in many countries.
What should happen is that when the MSK144 mode is selected, the band box
should switch to the lowest frequency on the VHF/UHF pulldown menu list and
CAT control should switch the radio to that frequency.

I hope that this issue can be resolved in the next release of WSJT-X.
Thanks.

73,
Rich - K1HTV

*PS*
If you know of any blind or visually impaired Hams who you want to help get
started in the world of FT8, FT4  and MSK144, send an email to:
*qlogusers+subscr...@groups.io  *
to join the QLog Users Group. In the "Files" section are the QLog.exe
program, the Initial Setup Manual for sighted helpers, the QLog Users
Manual as well as other support files and programs.
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Band box bug?

[Rich Zwirko - K1HTV]

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 to the 14074 KHz FT8 frequency, it switches to the 14.0966 WSPR
frequency. No matter what band number plus the letter "m" is typed into the
band box.WSJT-X always switches to the WSPR frequency used on that band. It
does this when any other mode (FT4, FT8, JT65, etc.) is the currently
selected mode.

The QLog program, written by Sam, W2JDB is used by many blind Hams around
the world to make digital QSOs with WSJT-X. QLog's ALT+B shortcut addresses
the band box and allows the user to type in a band number plus "m" to
quickly move to the correct frequency on that band for the
currently selected mode. It used to work correctly in earlier versions of
WSJT-X.

Typing the band + "m" in the WSJT-X band box should change the correct
frequency for the current digital mode.I hope that this bug can be
corrected in the next version of WSJT-X.
Thanks.

73,
Rich - K1HTV
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Rescan ADIF log

[Rich Zwirko - K1HTV]

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 the callsigns when they call CQ on that band This is the case,for
example, with the 8P6PE, whom I've worked on 40M FT8. His CQs are not
flagged with a gray background behind his callsign.

Since the flag colors are derived from data in the "wjst_log.adi" file, I
checked it and found a 40M FT8 QSO with 8P6PE made a few months ago.

I clicked on the "Rescan ADIF log" button located at  the "Settings/Colors"
in hopes that it would resolve the problem. Unlike other buttons that are
clicked, when I click on the "Rescan ADIF log" button, there is no sign
that any action was taken. I expected that subsequent decoded 40M FT8 CQs
from 8P6PE would be flagged with a grey background behind the callsign.
Instead, his CQs continued to produce a full green background without the
grey. Any idea as to why this is happening?

It appears that the "Rescan ADIF log" feature may not be working.

73,
Rich - K1HTV
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] RC3 Erase button bug

[Rich Zwirko - K1HTV]

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 same bug. Is it my system or are
others seeing this anomaly?

73,
Rich - K1HTV
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Clicking on RR73 produced wrong TX response msg

[Rich Zwirko - K1HTV]

*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
incorrect response of a  'Tx3' message of calls and roger report. *

*Is this a bug or a 'feature' to keep us on our toes?*

*73,*
*Rich - K1HTV*
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] 2.2.0-rc1 Anomaly responding to MSHV (?) station

[Rich Zwirko - K1HTV]

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 below.

After calling the ZW5 station, he responded with calls and a report. But
instead of my 2.2.0-rc1 version responding with a Tx3 message of Calls and
Report, it continued to send the Tx1 calls and grid message. For my next 15
second TX sequence I manually forced the Tx3 message to send the ZW5 Calls
and Report. As you can see, the ZW5 responded with his “RR73” message, but
instead of my responding with a TX5 “73” message, I continued to send my
Tx3 message of Calls and report. My auto sequencing was not working at all
for this QSO.

095200 6 0.2 566 ~ JI1CNA RR73; JA7FHL  -26

095230 8 0.2 566 ~ JA7FHL  -25

095245 Tx 510 ~  K1HTV FM18

095300 9 0.2 566 ~ JA7FHL RR73; K1HTV  -26

095315 Tx 510 ~  K1HTV FM18

095330 9 0.2 566 ~ K1HTV  -25

095345 Tx 510 ~  K1HTV R+09

095400 10 0.2 566 ~ K1HTV RR73 J

095415 Tx 510 ~  K1HTV R+09





I tried to initiate a second QSO with the ZW5 station, starting with a Tx1
message and when the ZW6 answered my call again, I got the same results of
my Auto Seq not automatically responding as it should have to the ZW5
messages.

I have not yet run across other station with a non-standard callsign using
the multi simultaneous QSO capability of their software to see if I get the
same results.

73,

Rich – K1HTV
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] DB.EXE attachment?

[Rich Zwirko - K1HTV]

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 forward to testing RC1 when it comes
out next Monday.

At the end of your recent announcement message I noticed a box with
"db.exe shared in drive" was included, a 64KB file. I was wonder what it is.

Joe, thanks for your efforts to get 4U1UN on the air. They sure are
creating some big pileups when they get on the air on FT8.

Although I'm still working plenty of DX with my 75 Watts (4U1UN was FT8
DXCC entity #271). I'm sure that you all have noticed the increased QRM and
greater competition from some pretty strong QRO signals. It is becoming
more and more difficult for many FT8 users to work DX. Both the 20M and 40M
FT8 frequencies, as you have seen, are really over packed at times. I
wonder if it may be time to start talking about the creation of well
defined, and agreed upon, secondary FT8 frequencies, at least on 20 & 40
Meters.

Hope you are all well in these crazy COVID-19 times. Thanks again to
the WSJT-X Development Team for making WSJT-X an even greater communication
tool than ever for its many users.

73,
Rich - K1HTV
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] K2H/NAS and GRID SQUARE

[Rich Zwirko - K1HTV]

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

Then don't ever operate as NU0C/M (UK-England).  Or /MM (UK-Scotland) or
/AM (Spain).
73,Ken, AB1J
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] No Signal IN

[Rich Zwirko - K1HTV]

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
accidentally checked it while using my Android phone to remotely use WSJT-X
via VNC.

I wish the "Ref Spec" check box would be removed in a future release of
WSJT-X as it is NOT needed by 99.99% or more of WSJT-X users.

73 & QWH, the newly adopted Q signal for "Wash Your Hands: :-)
Rich - K1HTV
= = =
From: Ron W2RAL 
   Date: Sun, 26 Apr 2020 13:12:31 EDT

Thanks Marty,

Checked Audio Midi, and nothing is muted the I can see.  This is what the
midi is showing me now,

USB Audio Codec 1  Output   /left and right bars showing blue
USB Audio Codec 2  Input / left and right bars are blank

Any clues??
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Lost red Lotw user in band activity

[Rich Zwirko - K1HTV]

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:
https://slproweb.com/download/Win64OpenSSL_Light-1_0_2u.exe

The 32 bit version can be downloaded from:
https://slproweb.com/download/Win32OpenSSL_Light-1_0_2u.exe

73 & QWH (Q-signal for "Wash your Hands")
Rich - K1HTV
= = =
From: Barry Bowman <77bow...@charter.net>
To: WSJT software development 
Cc:
Bcc:
Date: Wed, 1 Apr 2020 18:36:05 -0400
Subject: Re: [wsjt-devel] Lost red Lotw user in band activity

Hi Neil

Tried and got error. Is this something you could log in and correct. I’m
home for the next 2 weeks.

Thanks

Barry



Sent from Mail  for Windows
10



*From: *Neil Zampella 
*Sent: *Wednesday, April 1, 2020 9:26 AM
*To: *wsjt-devel@lists.sourceforge.net
*Subject: *Re: [wsjt-devel] Lost red Lotw user in band activity



Head back to the COLORS setting tab, and click on the FETCH NOW to update
the LoTW user file.  Close then open the program.

Should fix this.

Neil, KN3ILZ
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] F/H with the DX calling on 2nd (odd)

[Rich Zwirko - K1HTV]

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
which requires Hounds to call using tones above 1000 Hz, the cloned
versions will respond to stations in the entire passband.

So, when you come across these stations, turn off the Hound option and
respond as you would when making contacts in the normal FT8 way.

73,
Rich - K1HTV
= = =
NA6L wrote:

 F/H with the DX calling on 2nd (odd)
   From: John V 
   Date: Sat, 14 Mar 2020 11:15:14 EDT

Last night there was a DX station on 160m FT8 FH that I needed. The problem
was that he was calling on 2nd sequence (odd) and answering on 1st (even)
rather that 1st sequence. He seemed to be working stations but I never
figured it out. Other that getting him to change sequence is there away to
"fool" FT8 FH on my end? Was he using a program other than WSJT-X FT8 FH
that would allow the Caller to use odd for innating calls?

Thanks, John NA6L
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] 60 meters

[Rich Zwirko - K1HTV]

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 frequency for that channel is
5358.5 KHz.  A normal Upper Sideband , passing through a transmitter’s TX
filter will pass audio signals between 200 and 2800 Hz.  With a user’s VFO
set to 5357 KHz, audio components of a USB signal will occupy between
5357.2 and 5360 KHz.

A 50 Hz wide FT8 signal, using the same VFO setting and a tone between  200
Hz and 2750 Hz, will also remain within that channel.  A Pactor signal will
occupy between 5357 and 5359.4 KHz, a whole lot more than a 50 Hz FT8
signal. Expecting all FT8 signals to transmit exactly 1500 Hz, no more, no
less, above the 5357 KHz is ridiculous. It simple won’t happen.

I don’t know of any FCC actions on any complaints of FT8 interference to
any other services occupying the 60 Meter FT8 frequency of 5357 KHz.

73,

Rich – K1HTV

AG0NY wrote:
>> >
>> > 9. Under the existing rules, only upper sideband voice transmissions
>> are permitted in the 60 meter band. In the NPRM, the Commission proposed
to
>> authorize the use of three additional emission designators in the band:
CW
>> emission 150HA1A, which is Morse telegraphy by means of on-off keying,
and
>> data emissions 2K80J2D and 60H0J2B. In § 97.307(f)(14)(i) of the proposed
>> rules, the Commission restricts emission designator 2K80J2D to data using
>> PACTOR-III technique and emission designator 60H0J2B to data using PSK31
>> technique. The Commission also sought comment on whether amateur stations
>> could be permitted to transmit emission types in addition to those
>> requested by ARRL in the 60 meter band without increasing the likelihood
of
>> interference to primary users.
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Band change

[Rich Zwirko - K1HTV]

Christoph ,
  Do we know for a fact that band change decodes (those following a dashed
line w/o a band indicated) are actually submitted to PSKReporter?  Maybe
one of the Development Group can verify this. If this is actually
happening, it should be corrected in a future update of WSJT-X.

73,
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 lines between decode period" option,disregard the
> data below the separating dashed line which does NOT show the band on the
> right side of the line.

The point is, if wsjtx knows there was a band change with possibly
mixed decodes, why does it still submit that data to pskreporter?

Christoph
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Band change

[Rich Zwirko - K1HTV]

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 rely
on being accurate.

If you use the "Blank lines between decode period" option,disregard the
data below the separating dashed line which does NOT show the band on the
right side of the line.

That's just the way it is, nothing to be concerned about.

73,
Rich - K1HTV



From: "DG2YCB, Uwe" 
To: 
Cc:
Bcc:
Date: Thu, 20 Feb 2020 11:19:51 +0100
Subject: [wsjt-devel] Band change @ wsjt-x: decodes of old cycle falsely
detected/reported as from new band

Hi Joe, Steve, Bill et al.,

I don't know if it's already known: At WSJT-X v2.1.2 0068f9 after changing
the band, remaining decodes of the old cycle are still falsely detected as
from the new band. And likely, these decodes are then also reported to PSK
Reporter or HamSpots for the wrong band. Would be great if that will be
corrected in one of the future releases.

73 de Uwe, DG2YCB
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Some RU Stations not worked show as gray

[Rich Zwirko - K1HTV]

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
Activity window, their calls were marked with a gray background color.  But
then I started noticing a number of stations, than I didn't recall as being
worked in the RU, marked gray, as if I had already worked then. I checked
my DXKeeper log and verified that many of those calls marked gray by WSJT-X
as being worked, were in fact, not yet worked on any band in the contest.
As of this point, 3 hours into the RTTY RU, all 170+ QSOs were made using
the FT4 mode, using WSJT-X, JTAlert and DX Lab Suite's DX Keeper logging
program without N1MM.

Regarding problem being reported of occasional missing data in the "Rcvd"
field, that field will remain blank when the expected RTTY RU report is not
received. When the station you are working sends a dB report, and NOT the
expected RST plus State, Province or in the case of DX, a serial number,
the result will be that the "Rcvd" field in the WSJT-X Log window will
remain blank.

As others have noted, I have also occasionally experienced a blank "Rcvd"
field even though a station being worked actually sent the proper RTTY RU
report. I estimate that this anomaly has occurred in about 10% of the QSOs.

73,
Rich - K1HTV
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Shortcut for switching TX4 message

[Rich Zwirko - K1HTV]

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 screen readers used by the visually impaired can read the WSJT-X
message boxes, so they have no way to read the contents of the TX4 message
field to tell if it is set for RRR or RR73. It appears that "CTRL+R" is not
on the current list of WSJT-X shortcuts. If possible, assigning "CTRL+R" to
switch the TX4 message to the RR73 option would be very helpful.

Thanks again for considering this matter and we look forward in the new
shortcut(s) being included in  future release of WSJT-X.

73,
Rich - K1HTV

= = =

Hi Rich,

> So here is the question of the WSJT-X Development Group.  Is there a way
> that a blind Ham could make the required TX4 switch? There are 41 known
> WSJT-X shortcuts, but a shortcut to toggle TX4 from RR73 to RRR does not
> exist. Your consideration of this matter would be greatly appreciated.

Sure, we could do that.  How about "Alt+R" ??

-- Joe
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Shortcut for switching TX4 message

[Rich Zwirko - K1HTV]

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 financial firms, answered the call and accepted the challenge.  He
had already developed a logging program called QLog.

 After months of work modifying and adding a voice to the program, QLog for
the visually impaired was ready for testing. A team of blind beta testers
was recruited. For many months, they have been working with the developer
of QLog to tailor the program to the point where it’s now ready for use by
our fellow visually impaired Hams.

Configuration of QLog by a blind Ham, is relatively easy, however some of
the configuration changes to WSJT-X have been difficult, if not impossible
for the blind. I’d like to address one of them in hopes that the WSJT-X
Development team can come up with a solution.

The QLog program, using UDP data from WSJT-X, can initiate a CQ or answer a
CQ from a list of decoded stations. In the process, depending on the
message received, QLog announces the status of each step in the QSO
process.  In order for QLog to proceed in an orderly manner to the
completion and logging of a QSO, the TX4 message of WSJT-X must be set to
calls and RRR and NOT calls and RR73. A sighted op can easily toggle
between the two messages by double clicking the TX4 button or the TX4
bullet. A visually handicapped operator cannot do this. Attempts to make
the change using NVDA, Window-Eyes and JAWS screen readers have been
unsuccessful.

Switching the TX4 message from RR73 to RRR message could be done by editing
the WSJT-X.INI file. The “\RR73=true” would have to be changed to
“RR73=false” for each configuration in the INI file. But as we know,
editing an INI file can be dangerous for a sighted person and probably even
more so for a blind Ham using a screen reader.

So here is the question of the WSJT-X Development Group.  Is there a way
that a blind Ham could make the required TX4 switch? There are 41 known
WSJT-X shortcuts, but a shortcut to toggle TX4 from RR73 to RRR does not
exist. Your consideration of this matter would be greatly appreciated.

In closing, if you know of a visually impaired Ham who is interested in
diving into the world of FT8, FT4,  MSK144, etc., a new group called
QLogusers has been created. Once a member of that group, a user can
download the qlog.exe program as well as the “QLog Initial Setup Manual”
for sighted helpers as well as the “QLog Users Manual”.
You can subscribe at:  qlogusers+subscr...@groups.io
73,
Rich – K1HTV
PS: Two of the QLog Beta Testers already have worked over 100 FT8 DXCC
countries….. QLog works!
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FT8 Fox and Hound Mode - FOX Mode Operator enhancement

[Rich Zwirko - K1HTV]

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,
Rich - K1HTV

= = =

VK5GR wrote:

2.   Secondly, and this was a MOST frustrating aspect of using the
software. No matter what we did we couldn’t seem to find any settings that
would stop the “Enable TX” button from being cancelled *every time* the FOX
sent RR73 on any channel. Now it appears as though this is by design
although I hope it is in fact a bug. Our view is that if the FOX operator
had made the deliberate effort to load a station into the calling queue
then *the enable TX button should remain active until the last station
leaves the calling queue.*
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] F/H stops calling after 5 cycles

[Rich Zwirko - K1HTV]

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

= = =

K2DBK wrote:
From: K2DBK-WSJT 
To: "'WSJT software development'" 
Cc:
Bcc:
Date: Mon, 7 Oct 2019 21:28:24 -0400
Subject: [wsjt-devel] F/H stops calling after 5 cycles

I’ve noticed that in F/H mode after I call 5 times Enable Tx will turn off,
similar to what happens in non F/H mode when the Tx watchdog expires.
However, unlike in that case, there’s no red indicator in the lower left
corner, it just stops sending. I’ve confirmed that my watchdog timer is set
higher than that (just in case) and it’s set to 6 minutes. The number of
cycles seems to be consistent, and I’ve got no issue in other modes, ruling
out something like RF causing an issue. I’ve looked through the
documentation and couldn’t find any reference to maximum number of calls
before it will stop on its own.  I’m not transmitting on top of the Fox,
I’ve seen this both with and without “Rx All Freqs” set. One thing I’ve
noticed is that just before Enable Tx turns off, the Decode button will
flicker very briefly, something I don’t see at any other time. Also, even
though it seems to be on the 5th transmit cycle, it looks like sometimes
the Enable Tx button will turn off just as a transmission is starting, and
sometimes immediately after it’s finished. I’m baffled.



I’m running v2.1.0 on Windows 10 1903 build 18362. I’ve got Save All
checked in case those files would be of any use in diagnosing this.



73,

David, K2DBK
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Fox Hound question

[Rich Zwirko - 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 report that I sent each time. After not acknowledging my second "ZK3A
K1HTV R-01" report I noticed that WSJT-X had shifted my tone frequency to
around 600 Hz. The first time this happened, I did not decode ZK3A's
transmission immediately following my second report transmission. After
sending an number of calls and reports to ZK3A with teh 600 H tone, I
restarted from scratch, calling ZK3A with the TX1 message using a tone
frequency above 1000 HZ.

The second time ZK3A answered, again  I called twice with no RR73 from them
and again was shifted by WSJT-X to a 600 Hz tone. This time I did copy the
ZK3A transmission which showed them calling other stations, apparently
giving up on my call again.

Fortunately my third try was a charm and I did finally receive a RR73 from
ZK3A for my 80M country #121 with 75 Watts.

My questions are:
1) After two unsuccessful attempts to receive calls and reports from a
Hound that the Fox has answered, when the WSJT-X moves the TX tone of that
Hound to 600 Hz, does it mean that the Fox has given up on that Hound?

2) If the Hound continues to call on the 600 Hz tone frequency, will the
Fox ever respond. If not, the Hound needs to restart the calling process
with a TX tone greater than 1000 Hz.

73,
Rich - K1HTV
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] WSJT-X MSK144 'Tol' question

[Rich Zwirko - K1HTV]

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 frequency accuracy is less than accurate, but still better than +/-
200 Hz.

But what if the initial decode of a station indicates a DF of less than 20
Hz? Is there any improvement in MSK144 decode sensitivity by tightening the
"Tol" setting to 20 Hz?

73,
Rich - K1HTV
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Visually impaired Hams to use FT8/FT4. Help needed.

[Rich Zwirko - K1HTV]

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 the software needed so that they could easily operate these
new digital modes.



Earlier this year Sam, W2JDB, volunteered to take on the task. He had
created a logging program that already interfaced to WSJT-X called *Quick
Log* or* QLog*. He has since modified the program by providing voice
assistance so the visually impaired/blind ops can set up WSJT-X and *QLog*
thereby enabling them to make FT8 contacts by answering stations that are
calling CQ. The program is currently being used by a group of visually
impaired/blind beta testers, who have successfully made hundreds of FT8
contacts as well as enabling them to participate in the 2019 Field Day
event.



As you probably can imagine, it can be difficult for many of the visually
impaired/blind Hams to get WSJT-X up and running with their radios and
computers. Because of this, there is a need for sighted Hams, who are
familiar with WSJT-X, to help them get their hardware and software
configured and operating.



If you know of a visually impaired/blind Ham who is interested in working
FT8/FT4 and are willing to help that person get started, please contact me.
I will provide all the information on how to download the latest version of
*QLog* and all the documentation needed for the sighted ham to setup WSJT-X
and *QLog* as well as documentation on the use of *QLog* for the visually
impaired/blind ham.



*73,*

*Rich – K1HTV*
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FT8/FT4 frequency change bug?

[Rich Zwirko - K1HTV]

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 frequency change bug?
I noticed that while using the FT8 mode on a standard FT8 frequency, when
when the FT4 mode is selected from the "Mode" pull down list, the frequency
is changed to the correct  FT4 frequency for that band.

However, after using FT4, when the user selects the FT8 mode from the
"Mode" pull down menu, the mode changes, but WSJT-X does NOT change to the
correct FT8 frequency for that band. It remains on the FT4 frequency. This
holds true for all bands.

Bug??

73,
Rich - K1HTV
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Lid operators or bad design?

[Rich Zwirko - K1HTV]

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 second sequences when
the band is open to Europe and Africa.

A TX sequencing convention for openings to Europe/Africa, has been agreed
upon by the majority of 6M DXers. NA stations call CQ only during the 2nd &
4th sequences (Tx even/1st check box UNCHECKED). Very strong out of
sequence stations cause the receiver's AGC to push very weak DX further
into the noise. When all 6M DXers in the region are all using the same Tx
sequence, we all have a better chance to decode weak DX signals.

Later in the day, when it looks like we have possible SSSP propagation to
Japan, the sequencing convention is reversed. North American stations call
CQ during the 1st & 3rd (Even) sequence. JA DXers religiously adhere to
transmitting 2&4 to NA and 1&3 (Even) to Europe.

73,
Rich - K1HTV

= = =
On 7/28/2019 11:01 AM, Black Michael via wsjt-devel wrote:

Attribute it to inexperienceyou should contact them and help to
politely educate them.

Something like

 Hi there OM,

Saw you in a QSO with  and after the QSO was complete you called CQ on
the same offset.
You should consider working people in split by choosing a Tx offset that is
clear of other signals (shift click will do that) in the waterfall and
checking "Hold Tx Freq" to keep your offset constant.
Of course I'm sure you know that calling CQ on somebody else's frequency is
a no-no.
73's
..

de Mike W9MDB
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] No WSJT-X "ALL.TXT" decodes with N1MM?

[Rich Zwirko - K1HTV]

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 contest was EA8DBM in IL18 and the farther to the west was W7MEM
in DN17 in Idaho. On Saturday evening around 22:40Z here in VA (FM18ap) I
decoded a number of FT8 stations from Japan. According to PSK Reporter I
was decoded by 4 JA stations. I worked one of them, JG1TSG in QM05.

After the contest was oven, I wanted to check to see if any other JA
stations were decoded during that SSSP opening. But, to my disappointment,
the ALL.TXT file did not archive any decodes during the contest while
WSJT-X was running with N1MM. I checked the computer but could not find a
similar 'ALL.TXT' file that N1MM may have saved.

Would there be a way, when WSJT-X is in used with N1MM, that WSJT-X could
continue archiving all decodes? I would have loved to analyze the decodes
made on both FT8 and FT4 modes during the contest.

73,
Rich - K1HTV
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Contest confusion

[Rich Zwirko - K1HTV]

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 normal
operating configuration. None of the message boxes will have the callsign
of the station your were just working.  And I'll bet a doughnut that most
guys won't remember who they were working after switching to the 'Normal'
WSJT-X configuration.

If after 2 or 3 repeats from the other station, the best thing to do is to
switch sequences and start calling CQ. If you stay in the same sequence and
call CQ, you will end up responding again with calls and report to that
same station, unless he aborts the QSO.

73,
Rich - K1HTV

= = =

From:   Laurie, VK3AMA

Simple and only requires a single mouse click. Setup two configurations
in WSJT-X, one for you desired contest and the other non-contest. Once
setup, it is a single click using the "Configuration" menu to switch
between contest and non-contest.

de Laurie VK3AMA
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Contest confusion

[Rich Zwirko - K1HTV]

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
operating configuration. None of the message boxes will have the callsign
of the station your were just working.  And I'll bet a doughnut that most
guys won't remember who they were working after switching to the 'Normal'
WSJT-X configuration.

If after 2 or 3 repeats from the other station, the best thing to do is to
switch sequences and start calling CQ. If you stay in the same sequence and
call CQ, you will end up responding again with calls and report to that
same station, unless he aborts the QSO.

73,
Rich - K1HTV

= = =

From:   Laurie, VK3AMA <_vk3a...@vkdxer.net>

Simple and only requires a single mouse click. Setup two configurations
in WSJT-X, one for you desired contest and the other non-contest. Once
setup, it is a single click using the "Configuration" menu to switch
between contest and non-contest.

de Laurie VK3AMA
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Please read: Windows users installing the latest v2.1.0 GA 64-bit version

[Rich Zwirko - K1HTV]

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, either using  File, Settings or
the F2 key, the result is still a blank settings screen.

I'm back to using the 32 bit version of WSJT-X v2.1.0-GA until the problem
has been resolved.

73,
Rich - K1HTV

= = =

From: Greg Beam 
To: wsjt-devel@lists.sourceforge.net
Cc:
Bcc:
Date: Thu, 18 Jul 2019 02:06:16 -0600
Subject: Re: [wsjt-devel] Please read: Windows users installing the latest
v2.1.0 GA 64-bit version
It's on the Same page:

https://slproweb.com/products/Win32OpenSSL.html

Link: https://slproweb.com/download/Win64OpenSSL_Light-1_1_0k.exe

73's
Greg, KI7MT
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Decoding ALL FT8 signals

[Rich Zwirko - K1HTV]

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 WSJT-X Development Group reflector. Unless you have read the WSJT-X
manual, you might not be aware that only signals in the displayed frequency
range of the Wide Graph or the waterfall as many call it, will be decoded.

Most know that the lowest frequency decoded is set by changing the value in
'Start XXX Hz' box.  However, many do NOT know that the highest frequency
decoded is affected by the box titled "Bins/Pixel". If you have set the
'Start Frequency' to zero Hertz and set the 'Bins/Pixel' to 1, the highest
frequency decoded will only be 1000 Hz. If you increase the 'Bins/Pixel'
value to 2, signals will be only be decoded from 0 to 2000 Hz. Since many
FT8 signals use tones above 2000 Hz, the minimum "Bins/Pixel" setting
should be 3. However, the full 3000 Hz can only be decoded if the right
wall of the Wide Graph window is fully widened to actually display out to
3000 Hz. Beware that even if the 'Bins/Pixel' is set to 3, if the far right
wall of the Wide Graph window wall is dragged to the left so the Wide Graph
displays only  0 to 1000 Hz is shown, only signals in that range will be
decoded.

The bottom line is that unless the full range of frequencies is displayed
in the Wide Graph, you will not decode all stations transmitting in the
full FT8 channel. And don't forget that using the high and low DSP roll off
controls on your radio will also limit the audio frequencies that WSJT-X
can decode.

73,
Rich - K1HTV
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FT8 ghost signals

[Rich Zwirko - K1HTV]

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 and appear to be a
fixed offset and have me completely puzzled. I regularly see 2 or 3 'ghost'
signals between 6 and 20dB lower in amplitude than the main signal on 2m
from stations with 100W to a 9ele or more. Stations can be several hundred
km away from me. The offsets vary between 70-150 Hz and can be positive or
negative.  In order to have a doppler shift something must be moving and
with an offset of 100Hz or more quite quickly. You would think therefore
that the frequency offset would change and it often does not but remains
static for several periods and then just disappears. How on earth can this
happen? I have no reasonable explanation for it but I assure you it is real.
>
> Aircraft scatter on 6m occurs of course but not so often, however during
intense Es events sure enough I also see these ghosts on 6m and again no
shift. It really is very puzzling indeed.

Evidently what's puzzling you is Doppler shifts that remain nearly constant
for a minute or so.  Aircraft at 10,000 meters can be line-of-sight visible
at distances up to several hundred km.  With typical aircraft speeds, in
such cases the geometry for bi-static reflections will not change much over
a minute.  So the Doppler shift can remain nearly constant.  Does this not
make sense?

-- Joe, K1JT

= = =
Joe, I understand why we can see and decode one Doppler shifted signal, but
how do you explain 2 or 3 extra Doppler reflections from the same station?

BTW, congrats on working 5T5PA on 50.323 F/H. Johannes peaked at +11 at
16:36Z when I worked him and more than an hour later he is still at a
steady +4 to +6 dB here in VA. I chatted w/him using JTAlert and he said he
is having lots of fun working so much 6M DX in the F/H mode.

73,
Rich - K1HTV
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FT8 ghost signals

[Rich Zwirko - K1HTV]

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 development'" 
Cc:
Bcc:
Date: Sun, 7 Jul 2019 11:10:57 +0300
Subject: Re: [wsjt-devel] FT8 ghost signals

Hi All,

Perhaps this a wrong forum, but still I like to ask how you explain ghost
signals with varying frequency offset? Do you have both a direct signal and
an ES reflection from a moving cloud?

73, Reino oh3ma
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] FT8 ghost signals

[Rich Zwirko - K1HTV]

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
the waterfall display, at times both direct signal as well as one or more
of the reflected backscatter Doppler shifted signals can be decoded. The DF
between the main and ghost signals is usually between 40 and 130 Hz. The
average appears to be around negative 70 Hz.

When these ghost signals are observed, they are usually noted on multi-KW
FT8 signals produced by stations in the Mid-Atlantic region that are
beaming towards highly ionization Es regions. These extra waterfall signals
can last a few minutes then quickly disappear. I have not observed them
when there is no Es opening. They don't appear to be the result of signals
being reflected off aircraft.

73,
Rich - K1HTV

= = =

From: Jim Brown [mailto:k...@audiosystemsgroup.com]
Sent: 6. heinäkuuta 2019 9:28
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] 60 Hz + harmonics sidebands on FT8 signals?

There are two common causes of sidebands with a station that is properly
adjusted and uses good equipment.

1) The best gear (Elecraft K3, K3S, or a Flex 6000-series), and a first
class power amp) have sidebands roughly 40 dB down on both sides of their
signal due to IM distortion in the RF stages. These sidebands are generally
symmetrical, and the total -40 dB bandwidth is about 680 Hz.

2) Doppler shift produced by reflections from aircraft. These sidebands are
generally asymmetrical (that is, on one side or the other of the main
signal). Here in the SF Bay Area, which includes Silicon Valley and extends
down along the Monterey Bay, we have glide paths for major airports in San
Jose and San Francisco.

There are roughly a dozen or so locals running 500W with gear like this,
and we all regularly experience what you're seeing.

73, Jim K9YC
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] 1st Trans-Atlantic FT4 on 6M?

[Rich Zwirko - K1HTV]

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
contacts. It sure was FAST!

FT4 has the potential of harvesting those very short duration multi-hop Es
openings to distance lands, openings which definitely are too short to
complete JT65 (remember?) or FT8 QSOs.

73,
Rich - K1HTV
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Monthly ALL.TXT archives

[Rich Zwirko - K1HTV]

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 be able to do and can do
easily in the monthly files that I manually archive. What good is a
humongous ALL.TXT file to a WSJT-X user if he can't easily browse through
it?

I was told by another local FT8 user that JTDX does what I have requested,
that is archiving ALL.TXT files in separate monthly files. He also informed
me that my other request that Red/Green colors be used in the 15 second
count up bar also already exists in the JTDX software.

73,
Rich - K1HTV

= = =

From: Black Michael 
To: WSJT 
Cc:
Bcc:
Date: Tue, 25 Jun 2019 14:05:11 + (UTC)
Subject: Re: [wsjt-devel] Monthly ALL.TXT archives
On Windows:

find "K1HTV" ALL.TXT | find "S92HP"
190611_06190014.074 Rx FT8-17  0.1 2393 S92HP K1HTV -11
190611_06203014.074 Rx FT8-15  0.1 1106 S92HP K1HTV -11
190611_06210014.074 Rx FT8-17  0.4 1107 S92HP K1HTV -11
190611_06214514.074 Rx FT8-17  0.4 1106 S92HP K1HTV -11
190611_06220014.074 Rx FT8-15  0.4 1107 S92HP K1HTV RR73
190611_06223014.074 Rx FT8-15  0.4 1107 S92HP K1HTV RR73

On Linux
grep "K1HTV" ALL.TXT | grep "S92HP"

de Mike W9MDB
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Receiving/Transmitting colored indicator

[Rich Zwirko - K1HTV]

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
WSJT-X screen, there is no easy way to tell if I'm in the TX or RX
sequence. The colored "Receiving/Transmitting" bar in the lower left corner
or the screen can not be seen unless the focus is moved to the left with
the touch screen.

A suggestion to consider regarding the WSJT-X screen:
Change the color of the 12 segment progress bar on the lower right side of
the screen from always blue to alternating between *Green* when receiving, *Red
*when the user is transmitting, and gray or blue when the program is
processing data or when monitoring has been turned off.

Another request is to move the Date/Time clock to the right of its present
position. This also would help the folks who use small phones or tablets
which require zooming in to view.

73,
Rich - K1HTV
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Monthly ALL.TXT archives

[Rich Zwirko - K1HTV]

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.

Monthly, I edit my ALL.TXT file and manually archive the decoded data for
future use. These files have been used a number of times to confirm QSOs
when a station that I work, usually a DXpedition, says I'm not in the log
and I know that it was a solid QSO. I excerpt the decodes, showing
responses to me and others, attaching the info to an email that is sent to
him.

Unless it is kept to a reasonable size, the ALL.TXT will be useless to most
WSJT-X ops who want to check it. Why not archive the lines of decoded data
into a file with a file name reflecting the month that the data was
decoded, such as:

2019-06ALL.TXT

I believe that this change should be seriously considered in a future
release of WSJT-X.

73,
Rich - K1HTV
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Mock RU test results

[Rich Zwirko - K1HTV]

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.



Looks like RC7 is a keeper, as far as performance, with no problems at all.
A tip of the hat to the WSJT-X Development team for their work to get the
new FT4 mode working so well.



73,

Rich – K1HTV
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Call sign error

[Rich Zwirko - K1HTV]

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 compound calls the above is true but for other
non-standard calls it is not. There is a defect that causes the option to
skip Tx1 to be allowed for non-standard non-compound calls, in that case a
double-click of a CQ decode will incorrectly send Tx2. Despite that users
with non-standard non-compound calls still need to understand the
implications and should not select the option to skip Tx1.

73
Bill
G4WJS.
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] WSJT-X rc5 Subprocess error

[Rich Zwirko - K1HTV]

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
C:\Users\k1htv\AppData\Local\Temp\WSJT-X

At line 41 of file C:\Users\bill\src\k1jt\wsjtx\lib\ft4\ft4_downsample.f90

Fortran runtime error: Index '-2147483648' of dimension 1 of array 'cx'
below lower bound of 0



Error termination. Backtrace:



Could not print backtrace: libbacktrace could not find executable to open

#0 0x

#1 0x

#2 0x

#3 0x

#4 0x

#5 0x

#6 0x

#7 0x

#8 0x

#9 0x

#10 0x

#11 0x

#12 0x

#13 0x



 = = = =

73,

Rich - K1HTV
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Program for blind ops needs 2 shortcuts

[Rich Zwirko - K1HTV]

Bill,
  Thanks for your reply and suggestion about using the Qt Accessibility
interface. Sam, W2JDB, who has been working on the QLog (QuickLog) program
says that he will get up to speed on its use. He released QLog Version 157
today for testing by our 5 visually impaired QLog beta testers.

I'm looking forward to talking with Joe, who will be giving a presentation
Saturday at the VHF Super Conference at the Dulles Airport Holiday Inn. I'm
sure that FT4 will be a hot topic of discussion.

Thanks for all the work that you and the WSJT-X Development Team continue
to do to enhance digital 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 it is released so the new application for blind Hams would be able
to:

1)  Address the Tx Tone box

2)  Enable and Disable “Hold Tx frequency"

Rich,

as already noted, these controls are available programmatically using the
standard Qt Accessibility interface (MSAA on MS Windows, macOS
accessibility on macOS, and Unix/X11 AT-SPI on Linux). On Windows
instantiating the IAccessible2 API allows any process to access a Qt
application by enumerating and controlling its UI control elements.

Rather than extending WSJT-X to do specific control extensions on a case by
case basis thus duplicating existing functionality, it should be much more
efficient to adjust the control names and assistive text descriptions, if
necessary, so that any accessibility tool can make use of them.

73
Bill
G4WJS.
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Program for blind ops needs 2 shortcuts

[Rich Zwirko - K1HTV]

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 Street financial firms
for many decades, volunteered to take on the task.  Sam developed a program
which is now being beta tested by me and a team of 5 visually impaired
Hams.

Using voice announcements to aid the blind ops, the application can now
answer FT8 stations calling CQ. The software is able to find clear
frequencies on which the blind ops can call CQ, but because there is no way
to send a command from the app to WSJT-X, to change the transmit tone to a
clear frequency, this capability cannot be implemented.

Would it be possible to add the following shortcuts to WSJT-X 2.1.0 rc5
before it is released so the new application for blind Hams would be able
to:

1)  Address the Tx Tone box

2)  Enable and Disable “Hold Tx frequency"

The addition of these two shortcuts to WSJT-X for use with the FT8 mode
would be greatly appreciated.

73,

Rich – K1HTV
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Reading SWR from rig

[Rich Zwirko - K1HTV]

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.

For non-K3 radios, you can use LPB2. I understand that both LP Bridge and
LPB2 also works with Windows 8. I read that they can be used with Windows
10 but not with Ham radio Deluxe (HRD) software, which uses Unicode.

You can read more about LP Bridge and LPB2 at:
http://www.telepostinc.com/LPB.html

73,
Rich - K1HTV

= = =

From: "Deisher, Michael" 
To: WSJT software development 
Cc:
Bcc:
Date: Thu, 7 Mar 2019 17:37:01 +
Subject: Re: [wsjt-devel] Reading SWR from rig
Thanks for the quick reply, Bill.  Do you (or any others on the list) have
any recommendations for implementing this "below" wsjtx?  In my current
setup, wsjtx seems to "lock" the serial device so that other apps (e.g.,
flrig) cannot access it.  It makes sense, but I remember reading about
people experimenting with virtual serial devices and such that allow
multiple applications to share the rig.  This seems a bit fraught with
potential issues (e.g., two masters with conflicting commands) but could
allow simple things like reading/displaying status information.

73, Mike KK7ER
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Separate F/H freq list

[Rich Zwirko - K1HTV]

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
would simplify things in the Fox/Hound mode.

Completely locking out the use of standard frequencies while in the F/H
mode would stop DX stations who use WSJT-X and feel that they deserve to
use the F/H mode. But the clones of WSJT-X would probably continue to be
used by these 'special' DX stations on normal FT8 frequencies.

73,
Rich - K1HTV
= = = = =

From: Mark James 

I like the idea of custom frequency lists.

I realize this would be more elaborate in terms of code changes, but it
would be nice to be able to have a separate list of Fox/Hound frequencies
that could be customized, and would switch into place in that mode.

While it isn't hard to add custom frequencies, this might help popularize
Fox/Hound and make it clear that custom frequencies are needed,
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Sorry to ask here!

[Rich Zwirko - K1HTV]

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 field is working correctly but I was asking
> about the CQ presets in the "CQ button" into label 3, which already
> contains several CQ preset:
>
> CQ
> CQ AF
> CQ AN
> CQ AS
> CQ EU
> CQ NA
> CQ OC
> CQ SA
>
> These are not working, at least with my attempts.
>
> Please reply directly to me in order to avoid to fill the list if you
> think this topic is not related to the list scope.
>
> --
>
> 73 de Marco, PY1ZRJ
>
>
> > 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 mailto:py1...@outlook.com>>
> > To: "'WSJT software development'"  > >
> > Cc:
> > Bcc:
> > Date: Mon, 11 Feb 2019 22:14:29 +
> > Subject: [wsjt-devel] Sorry to ask here!
> > I forgot how to call CQ for a specific country.
> > I tried several presets in WSJTX as "CQ OC" but the standard format "CQ
> > PY1ZRJ GG87" is always the one being sent.
> >
> > TKS and regards,
> > --
> >
> > 73 de Marco, PY1ZRJ
>
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Sorry to ask here!

[Rich Zwirko - K1HTV]

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 +
Subject: [wsjt-devel] Sorry to ask here!
I forgot how to call CQ for a specific country.
I tried several presets in WSJTX as "CQ OC" but the standard format "CQ
PY1ZRJ GG87" is always the one being sent.

TKS and regards,
-- 

73 de Marco, PY1ZRJ
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] ALT+G anomaly?

[Rich Zwirko - K1HTV]

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 boxes and placed cursor in 'DX Call' box). So far, so
good.
Type in call
Type ALT+G (hold ALT key the hit 'G' key. This should populate the message
boxes.

When I do this I get the call sign that I typed, but with the letter 'G'
after it and standard message boxes remain empty.

So I tried again:
F4
Type in call
Hit the TAB key to move cursor our of the 'DX Call' box and into the 'DX
Grid' box.
Try ALT+G again.
Now the 'DX Grid' box has the letter 'G' in it and still no standard
messages.

It isn't until the cursor is in neither box will the ALT+G populate the
standard message boxes. The op should be able to hit the ALT+G after the
last letter of the call sign is entered into the 'DX Call' box to make it
happen, right?

73,
Rich - K1HTV
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] FT8 for the blind?

[Rich Zwirko - K1HTV]

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 understand that back
then that FT8 was in its infancy, requiring the prime focus of the WSJT-X
Development team. More recently,  V2.0.0 has required the majority of time
being spent by the team.


Now, with FT8 being so widely accepted and running so well, we can step
back a few feet, take a deep breath and smile. There are now many tens of
thousands of happy FT8 users. Unfortunately our fellow blind Hams are NOT
in that group as they are still unable to effectively use FT8.


Does anyone of the Development team know of any software developers that
might want to tackle the task of developing an FT8 interface which would
allow the many unsighted Hams to enjoy this great new digital mode?


73,

Rich – K1HTV
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] (no subject)

[Rich Zwirko - K1HTV]

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: "wsjt-devel@lists.sourceforge.net" 
Cc:
Bcc:
Date: Thu, 24 Jan 2019 01:50:04 +
Subject: [wsjt-devel]  WSJT Reporting to PSK Reporter

 Hi, I got this address from the WSJT website. I am new to this
group and not sure of the protocols. I tried emailing yesterday but am
unsure if this was received.



I am operating as VK2/G3NJV. After upgrading to v2.0.0 I found reports of
my transmissions almost disappeared from PSK Reporter. I now get just a
handful of reports all from stations NOT using WSJT. Most of these come
from stations using “Red Pitaya FT8 TRX 1.0”. I spoke to Philip Gladstone
about this and he told me that WSJT does not send reception reports to PSK
Reporter unless it receives callsign and locator in a single message. It is
impossible for me to transmit a message like this. Because I have a type B
callsign, all that will fit in a single message is “CQ VK2/G3NJV”



This seems a particularly harsh outcome for type B callsign holders
upgrading to v2.0.0. who, like me, are often operating portable stations
with makeshift antennas where reception reports are extremely valuable. The
reports from stations using a Red Pitaya are perfectly acceptable and I’m
not sure of the reasoning behind the current WSJT “callsign + QRA” rule.
Would it be possible to modify this to allow reception reports for type B
callsigns received without a QRA?



Many thanks for your attention.

Paul Randall

G3NJV



PS After completing this email I checked the PSK Reporter website again.
Sure enough there were just 5 reception reports, four from monitors using
Red Pitaya but also a single report from K1HTV  using WSJT-X v2.0.0 784f75.
This is the only WSJT reception report seen since 10 December so now I’m
not sure what is going on!
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] FT8 in State QSO Parties?

[Rich Zwirko - K1HTV]

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’ module for these very popular
operating events.

My son Andy, K1RA & I have been discussing how we might implement the use
of FT8 in the upcoming VA QSO Party, scheduled for March 16 & 17 this
year.  The various QSO Parties around the USA require stations in the *host*
State to send one of these 5 exchange formats:

·  RST+County (total  6 or 7 characters)

·  or Serial number+County (up to 4 digit SN)  +( 3 or 4 char. for
County)

·  or  State+County (5 or 6 characters)

·  or County+State (5 or 6 characters)

·  or the ops Name+County (limit the name length?) + (3 or 4 for
County)

 One idea considered for the VQP, using the presently available V2.0.0, was
to have all participants use the RTTY RU module and set the callsign to,
for example, K1HTV/CUL (Culpeper County).  But that format doesn’t fit the
present FT8 format for compound calls.  Sending a sequential QSO number
could be achieved if Stateside stations were able to flag themselves as
‘DX’….but there isn’t any way at present to do so in V2.0.0 . So what, if
anything, can be done to incorporate FT8 into future State QSO Parties?

If an FT8 “State QSO Party” module were to be added to the present WSJT-X
code, it should:

1)  Allow for 3 or 4 character county abbreviations to be sent.  In the
case of the 7 land and New England QSO parties, allow for a 5 character
combined State and County code to be sent by stations in New England & W7
land States.

2)  Allow all to send either an RST,  or a sequential number,  or their
name.

3)  As required by the QSO Party rules, allow out-of-State participants
to send their State, or VE province abbreviation,  or in the case of DX
stations, to send ““DX”.

4)  Allow for a special QSO Party CQ message to stick, such as “CQ VQP
K1HTV” or “CQ 7QP W7XX ”.

In the VQP, K1RA in Fauquier County might send “K1JT 002 FAU” and Joe would
respond with “K1RA 599 NJ”. If possible, both calls should be sent.


In the 7 land QSO Party, W7CT in Davis County, UT , would send, for
example, “JA4BUA 599 UTDAV” and JA4BUA  would respond with “W7CT 599 DX”.
Again, send both calls if possible. There would be no requirement to send a
real signal report. Who ever does in contests? Its 59 or 599, right?


I wouldn’t worry about WSJT-X having to proof the State or County info. I’d
leave it up to the op to verify that the data received is in the proper
format for submission to the QSO Party administrators.


What is needed are boxes in the WSJT-X “Advanced Settings” for participants
to check off to properly format the QSO Party exchange that they will be
sending to stations being worked in that QSO Party. Of course, exchanges
sent would have to meet line length limits.


What say WSJT-X Development team?  Can do ? Comments by others?



73,

Rich – K1HTV
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Wrong band info at times

[Rich Zwirko - K1HTV]

Bill,
 Tnx for the suggestion. The BAT file presently is started 1 second BEFORE
the start of a decode period. I will switch it at least 5 seconds after the
normal :00 seconds start time. Since the first decode after a band switch
is normally flagged with a band switch, the late start won't hurt anything.

The K3 band switching, which also controls which antenna is used, was
mainly done to supply the optimum antenna to the Redpitaya 8 band FT8
decoder. It feeds the FT8 RBN. One of the nodes that propagates FT8 spots
is:dxc.w9pa.net:7374

I had been using the K3 to decode old V1.9.1 users spots, but the switch
over has been so good that I'm only decoding V2.0.0 stations. Congrats to
the whole crew and thanks to you for all of your contributions to the code
and for helping out so many users as they face pilot errors and the
occasional new bug.

73,
Rich  - K1HTV






= = =
From: 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 decoder, messages are accumulated
throughout the whole Rx period and decoded afterwards, no attempt is made
to attribute decodes to a previous band if the frequency is switched part
way through a period.

Your solution is simple, time your band changes to be within the first half
of a receive period. Near enough to the start of period to ensure no
decodes of the old band are possible (in the first half will assure that)
but long enough after the start to ensure that decoding and spotting is
compete for the old band, that depends on your system speed. For FT8 I
would try switching at start of period plus 5 seconds. Doing so earlier
will get more decodes for the new band on the switch over period if your
system is fast enough.

73
Bill
G4WJS.
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] UTC time in contest log page

[Rich Zwirko - K1HTV]

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 list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel