Re: [wsjt-devel] Bug Report WSJT-X 2.0 - QSY QRG on MSK144

[Joe Taylor]

Hi Alex,

On 12/12/2018 8:37 AM, DL1KDA Alex wrote:

I noticed one bug in the latest Version (2.0.0)

On MSK144 i can enter any "TX CQ ***" number in ***  but allways when i 
check to turn it on in the TX5 field appears "CQ 150 DL1KDA JO30"


You are observing the expected behavior.  Use of the "CQ nnn ..." 
feature is described in Section 10.4 of the WSJT-X 2.0 User Guide:


http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-2.0.0.html#CONTROLS_CENTER

... or page 53 of the German translation:

http://physics.princeton.edu/pulsar/k1jt/wsjtx-doc/wsjtx-main-2.0.0_de.pdf

To use this feature you must be using CAT control

Set your dial frequency to the one on which you wish to conduct a QSO, 
say 144.370.  (You can enter "370k" in the drop-down band selector box.)
Set the spinner control TX CQ to the kHz portion of the frequency on 
which you wish to call CQ, say "360".  Now while calling CQ you will 
transmit on 144.360 and receive on 144.170.  When someone answers you 
will continue the QSO on 144.370.


-- 73, Joe, K1JT


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

Re: [wsjt-devel] Rx Frequency doesn't move to QSO partner frequency.

[Joe Taylor]

Hi Neil,

On 12/11/2018 11:46 PM, Neil Zampella KN3ILZ wrote:

I was calling CQ with the Hold Tx Freq set.  I has just finished an QSO 
with a station, and someone replied to a CQ call a minute later.  The 
Auto Sequence kicked in fine, and the QSO was completed properly. 
However, when I looked back on the exchange in the Rx Frequency window, 
I noticed that I was getting decodes in that window from my previous QSO 
partner.


Looking at the waterfall, I saw that the Rx Green Bracket had not moved 
to the new QSO partner's frequency, but stayed with the old one.  I have 
an attachment, not sure which is better keep the screen cap as an 
attachment or as an inline picture.


Looks perfectly normal to me.  The "Rx Frequency" window gets anything 
decoded within a few Hz of Rx Freq and anything containing your own 
call.  The green goal posts did not move to your new QSO partner's 
frequency because you did not double-click on his call to start the QSO. 
 You had "Call 1st" enabled, so the QSO started automatically when he 
replied to your CQ.


-- 73, Joe, K1JT


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

Re: [wsjt-devel] Bug Report

[Joe Taylor]

Hi John,

False decodes are rare, but their frequency is not zero -- especially if 
you have checked "Decode | Enable AP".


Please read Section 12.1 of the User Guide, "AP Decoding":
http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-2.0.0.html

-- 73, Joe, K1JT

On 12/11/2018 9:56 PM, John LeRoy via wsjt-devel wrote:

  *

Program version: wsjt-x   v2.0.0

  *

Operating system:    Debian Stretch 64 bit Kernel Linux
4.9.0-8-amd64 x86_64 w/ MATE 1.16.2 desktop and libraries from
Debian Sid required for install of .deb package from wsjtx-x web
site (fortran and qt5).

  *

Concise description of the problem: I had just completed a QSO with
WA1GPO and was doing something else on the computer unrelated to
wsjt-x when this entry popped up in both panes. I stopped the
decoding so I could take a screen shot.

  *

Exact sequence of steps required to reproduce the problem: can't
reproduce, although I should note that the QSO required ten
transactions to complete - there was deep fading occurring.

73,

John W4JKL




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




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

Re: [wsjt-devel] wsjt-devel Digest, Vol 58, Issue 190

[Joe Taylor]

On 12/11/2018 3:55 PM, Lahra Svare KT9X wrote:

I signed up for the digest version of this list, yet I’m getting 10-20 emails a 
day each with 4 to 5 emails in each one. Is there anyway to get ONE daily 
digest? I hate to unsubscribe, I love the information - but there’s quite a 
volume of individual emails, even for the digest version.  Thanks for any 
information any of you can share.

Lahra


As far as I am aware, the "digest" option on this list works properly.

Every email from the list contains this link at the bottom:

https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Please go there, scroll down nesr the bottom, and check the status of 
your options to be sure Set Digest Mode is ON.


-- Joe, K1JT


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

Re: [wsjt-devel] compound callsigns and grid square

[Joe Taylor]

Hi Bill, and Mike,

good questions. For the first I need to check message source encoding 
routine, it may be that /P is allowed, it appears to be so although I 
have not tested it end to end.


"/P" is allowed with a grid because it is a valid message format for EU 
VHF Contest purposes.  See User Guide Section 7.4, "Contest Messages",


http://physics.princeton.edu/pulsar/k1jt/wsjtx-doc/wsjtx-main-2.0.0.html#_contest_messages

under the heading *EU VHF Contest*


It's not a good idea to use this format for standard HF operating.

-- Joe


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

Re: [wsjt-devel] compound callsigns and grid square

[Joe Taylor]

Mike --

On 12/11/2018 2:41 PM, Mike Maynard wrote:

Ok, so explain to me why K2GC/P formats properly?


Compound callsigns and their usage is described here:
http://physics.princeton.edu/pulsar/k1jt/wsjtx-doc/wsjtx-main-2.0.0.html#COMP-CALL

I could certainly understand the issue more if my callsign were 
longer...   but with such a short callsign I am not sure why all this 
'making it fit' comes into play.


Callsigns are not encoded on a character-by-character basis.  Every 
standard callsign uses exactly 28 bits.


furthermore,  so how is one supposed to operate?   do I just call cq 
with no grid, 


Yes.


and the software will out it in the exchange later?


I'm not sure what this means.

You can tell the other buy your grid, in the way that Bill already 
described for you.


-- Joe, K1JT


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

Re: [wsjt-devel] Error Loading LotW Users Data

[Joe Taylor]

On 12/11/2018 2:25 PM, Greg Gilbert KN4APC wrote:

What is the fix for this?

Thanks,
Greg KN4APC


New Year's Resolution:

"Before posting a question on setup or usage of WSJT-X I will check the 
WSJT-X 2.0 User Guide and look for similar queries on the same reflector."


In this particular case, an installation problem under Windows, try 
looking at Section 3.1, "Installation: Windows":


http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-2.0.0.html#INSTALL

--Joe, K1JT


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

[wsjt-devel] Good News on WSJT-X 2.0

[Joe Taylor]

Hi all,

My office is close to home, so I went home today over the lunch hour.

Monitoring 20 meters just 3 hours after WSJT-X 2.0 had been released, I 
found that nearly half of the active stations were already using it.  I 
made 18 QSOs in about half an hour.


According to PSK Reporter statistics, at least 1620 callsigns have been 
making QSOs with the new version.  This is now ~7.5 hours after the v2.0 
GA release.


Many thanks to all those who have upgraded to WSJT-X 2.0 quickly! 
Please help us to spread the word that upgrading is painless, and highly 
desirable.


-- 73, Joe, K1JT


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

Re: [wsjt-devel] Documentation Suggestion

[Joe Taylor]

Hi Rick,

My suggestion is to add a sentence or two under each of the settings tab 
screen shots with a BRIEF description for each of the features on that 
tab ... such as:


"Label and decode Fonts may be changed in the Display section as shown 
above."


Good suggestion.  In fact, such a "ToDo" has been on our priority list 
for a long time; it just hasn't reached the top, hi.


Further attention will definitely be paid to the WSJT-X 2.0 User Guide, 
in coming weeks.


-- 73, Joe, K1JT


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

Re: [wsjt-devel] 200 or 2000 Hz

[Joe Taylor]

Hi Bill,

On 12/10/2018 1:20 PM, Bill Mullin AA4M wrote:

I asked this question on another list but did not get a usable answer:

With 1.9.1 we were told to use 200 HZ to Start and change this to 2000 
Hz for RC5.  Which should we use for the 2.0.0 GA version?  Is there 
some frequency that may be better than 200 or 2000?


From the release announcement:

"We now recommend using WSJT-X 2.0 anywhere in the conventional FT8 and 
MSK144 sub-bands.  Everyone should upgrade to v2.0 by no later than 
January 1, 2019."


-- 73, Joe, K1JT


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

[wsjt-devel] WSJT-X 2.0.0: GA release

[Joe Taylor]

The WSJT Development Group is pleased to announce the general 
availability (GA) release of WSJT-X Version 2.0.0.


If you have been using version 1.9.1 or earlier, or one of the candidate 
releases v2.0.0-rc#, it's important to upgrade now.  The original 
protocols for FT8 and MSK144 are no longer supported.  With v1.9.1 and 
earlier you cannot communicate with WSJT-X 2.0 using these modes.


We now recommend using WSJT-X 2.0 anywhere in the conventional FT8 and 
MSK144 sub-bands.  Everyone should upgrade to v2.0 by no later than 
January 1, 2019.


NEW FEATURES IN WSJT-X 2.0
--

1. Compound and nonstandard callsigns are automatically recognized and 
handled using new FT8 and MSK144 message formats.


2. The new FT8 protocol provides optimized message formats for North 
American VHF contests, European VHF contests, ARRL Field Day, and ARRL 
RTTY Roundup.  Similarly, the new MSK144 protocol provides optimized 
message formats for North American VHF and European VHF contests.  Full 
support is provided for "/R" and "/P" calls in the relevant contests.


3. The new protocols provide nearly equal (or better) sensitivity 
compared to the old ones, and lower false decode rates.


4. New logging features are provided for contesting and for "Fox" 
(DXpedition) mode.  Logging is optionally integrated with N1MM Logger+ 
and WriteLog.


5. Color highlighting of decoded messages provides worked-before status 
for callsigns, grid locators, DXCC entities, continents, CQ Zones, and 
ITU zones on a “by band” and “by mode” basis, and for stations that have 
uploaded their logs to Logbook of the World (LoTW) within a specified 
time interval.


6. The WSPR decoder now achieves decodes down to S/N = -31 dB.  For the 
particular benefit of LF/MF users, an option "No own call decodes" has 
been added.


7. The UDP messages sent to companion programs have been expanded and 
improved.


A more detailed list of program changes can be found in the cumulative 
Release Notes:

http://physics.princeton.edu/pulsar/k1jt/Release_Notes.txt

Upgrading from earlier versions of WSJT-X should be seamless.  There is 
no need to uninstall a previous version or move any files.


Please do not continue to use any release candidate -- that is, any beta 
release with "-rc#" in the version name.


Links to installation packages for Windows, Linux, and Macintosh are 
available here:

http://physics.princeton.edu/pulsar/k1jt/wsjtx.html

You can also download the packages from our SourceForge site:
https://sourceforge.net/projects/wsjt/files/
It may take a short time for the SourceForge site to be updated.

We hope you will enjoy using WSJT-X Version 2.0.0.

 -- 73, Joe, K1JT, for the WSJT Development Group


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

Re: [wsjt-devel] Clear guidance - Development Environment

[Joe Taylor]

Steve --

On 12/7/2018 5:32 AM, Stephen Ireland VK3VM wrote:

 From comments passing it appeared that Greg Beam’s brilliant JTSDK was 
not being used as the central environ; with great difficulty I also 
gathered from responses that base development is performed under Linux 
and that Windows versions are cross-compiled from Linux. 


That's not correct.  We develop in Windows, Linux, or even macOS as 
needed and as convenient.  In general we don't cross-compile.


Likewise I drew 
conclusions that development from XCode was based upon Linux-lines. Can 
this please be confirmed?


I'll just speak for myself:  I don't use XCode, and I don't know what's 
meant by "Linux-lines".


As for your other requests: I'm currently using Qt5.5, MinGW, g++ gcc 
gfortran 4.9.2.  More recent Qt versions are probably OK too.  You can 
certainly start with Greg's JTSDK, if you choose that approach, 
modifying its scripts to your own particular needs.


-- 73, Joe, K1JT


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

Re: [wsjt-devel] Specification for side band attenuation

[Joe Taylor]

Hi Simon, Richard, and all,

As Bill stated, the phase of an FT8 signal is continuous.  The first 
derivative of phase (i.e., the frequency) has discontinuous steps at 
symbol boundaries.


The attached plot shows the average spectrum of ten simulated FT8 
signals carrying different messages.  Small details will be different 
for different messages, but the broad outline is always the same.


The ITU occupied bandwidth containing 99% of the power is 52 Hz.  Skirts 
extend farther outward, of course.  The signal is 65 Hz wide at -20 dB,

102 Hz at -30 dB, and 195 Hz at -40 dB.

We could, of course, apply a digital filter to the generated audio 
signal to reduce power in the wings of the spectrum.  The filtered 
signal would no longer have a constant envelope.


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

Re: [wsjt-devel] 2.0.0 rc5 JT65 bw looks like JT9

[Joe Taylor]

Hi Wolfgang,

On 12/7/2018 3:56 AM, Wagner Wolfgang OE1WWL wrote:


When I change the mode from FT8 to JT65 (today not via JT9) the red and
green markers have a smaller bandwidth than before. It appears like the
bandwidth of JT9.


This problem was identified and fixed about a week ago.  It will be 
correct in WSJT-X 2.0.


With RC5 release candidate "RC5", the workaround it to switch 
temporarily to JT9+JT65 mode, then back to JT65 mode.


-- 73, Joe, K1JT


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

Re: [wsjt-devel] WSJT-X 2.0.0-rc5

[Joe Taylor]

Hi Shel,

If you are going back and forth between 1.9.1 and 2.0-rc5, that is 
expected behavior.  Use of 1.9.1 will erase your colors saved from v2.0 
and require you to reset.


After GA is available, next week, don't use v1.9.1 any more!

-- Joe, K1JT

On 12/6/2018 3:30 PM, Shel KF0UR wrote:

Hi,

I just downloaded and started using the subject release and came up with 
one issue having to do with Colors.


I changed the “my call” color just a little, unchecked a few boxes, and 
saved it.   That worked fine.  I then closed the WSJT-X program.


When re-opened, all of the colors are now missing (see screenshot 
below), and I have to click on “Reset Highlighting” to restore the 
original colors.   I was able to repeat this multiple times.


I’m running on a PC, Windows 10.   Version 1.9.1 is also installed (in a 
separate directory) and has been in use.


Let me know if you need any more info.

73 and tnx for all the nice work.

Shel KF0UR



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




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

Re: [wsjt-devel] Average DT Time

[Joe Taylor]

Hi all,

A number of comments and questions have appeared here recently 
concerning the parameter DT displayed by the WSJT-X decoders.


K6AVP:

Only a few have posted what range of DT’s they mostly see ...


K9YC:

My memory is routinely seeing DTs in the range of +/_ 200msec, with occasional 
outliers up to 2 sec or so.


AI4FU:
I would be most interested to hear if you tried pushing the limits of how far out of sync you could push things and still manage decodes. 


NX6D:

I see “DT” values that range from about 0.0 to about 0.5 in my system.


... etc.

Positive DT means that a signal arrived late according to your 
computer's clock.  For example: if the computer clocks at both ends of 
an EME QSO are bang on, the decoded EME signals will show DT = 2.5 s, 
because the EME path delay is 2.5 s.  Terrestrial propagation delays are 
a few tens of ms or less, so the DT values most of us see in HF 
operating are caused by latencies in our audio systems, context 
switching delays in our operating systems, and -- most importantly -- 
clock errors in one or both computers.


Because people have been asking about it, I compiled histograms of the 
distribution of DT values extracted from decodes in my ALL.TXT file from 
two recent dates.  The first was a few weeks ago, using WSJT-X v1.9.1. 
The second was during the FT8 Roundup, last weekend, using WSJT-X 
2.0-RC5.   I limited the time ranges so that each data set had exactly 
the same total number of decodes, 65010.


The distribution of DT values for these two data sets are shown by red 
and purple curves in the attached plot.  Most decodes have DT in the 
range 0.0 to 0.3 s.  The bug in RC5 that eliminated decodes with 
negative DT is clearly evident in the plot: the purple line cuts off to 
zero to the left of DT=0.


I operated in the FT8 Roundup with "Save all" checked, so it was easy to 
reprocess all of those saved files with the soon-to-be-released
WSJT-X 2.0.  This produced another 5290 good decodes -- essentially the 
previously missing ones that have negative DTs.


The FT8 decoder tests for DT values from -2.5 to +2.5 s.  As these 
results show, most FT8 users keep their computers "on time" to within a 
few tenths of a second.


-- 73, Joe, K1JT

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

Re: [wsjt-devel] Previously saved Wave files no longer processing with rc4 & rc5

[Joe Taylor]

Hi Sandro,

Yes, we know that the sample files need to be replaced.  Also a few 
files named in the User Guide need to be updated.


Thanks, as always, for your attention to such details!  It's a big help 
for us.

-- Joe

On 12/5/2018 2:05 PM, Alessandro Gorobey via wsjt-devel wrote:

Hi Joe,

perfectly understood.

But the sample downloaded in help-->Download samples.. are to be updated
C:\Users\Sandro\AppData\Local\WSJT-X\save\samples\MSK144
C:\Users\Sandro\AppData\Local\WSJT-X\save\samples\FT8

Compliments for the big work

Il 05/12/2018 00:31, Joe Taylor ha scritto:

Hi Laurie,

Probably you figured this out, already.  Any revision later than 
2.0-rc3 cannot decode the old FT8 protocol.  It's an inevitable 
consequence of the forced shift to a better protocol.


 -- Joe, K1JT

On 12/4/2018 17:09, Laurie, VK3AMA wrote:
Since rc4, opening previously saved wave files are no longer showing 
decodes. There is a brief change in the Decode button color, but no 
decodes shown. Same wave files work with rc3.


I have many previously recorded wave files I use for testing purposes 
that no longer produce decodes under rc4 & rc5.


Is this a defect?

de Laurie VK3AMA



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





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

Re: [wsjt-devel] what is rtty mode?

[Joe Taylor]

Dave --

On 12/1/2018 2:07 PM, Dale Wheeler via wsjt-devel wrote:

Using win 10
Running ver. 2.0 rc5

I have received the same pop-up 3 times. It asks if I want to RTTY 
contest mode (see attached picture). I looked but don't understand the 
documentation. Am I doing something wrong or is this a bug?


Your screen shot shows that you have decoded several messages of tyhe 
form "CQ RU ...", the CQ message used in the FT8 Roundup, ARRL RTTY 
Roundup, and similar contests.


From the Quick Start Guide to WSJT-X 2.0, page 5:

"Casual operators who decode a contest-type message formatted for ARRL 
Field Day or ARRL RTTY Roundup will be prompted to check the relevant 
box so that they can transmit the required exchanges."


These guys just forgot to change their CQ message.  Just click OK and 
ignore the message box.


-- 73, Joe, K1JT


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

Re: [wsjt-devel] Previously saved Wave files no longer processing with rc4 & rc5

[Joe Taylor]

Hi Laurie,

Probably you figured this out, already.  Any revision later than 2.0-rc3 
cannot decode the old FT8 protocol.  It's an inevitable consequence of 
the forced shift to a better protocol.


-- Joe, K1JT

On 12/4/2018 17:09, Laurie, VK3AMA wrote:
Since rc4, opening previously saved wave files are no longer showing 
decodes. There is a brief change in the Decode button color, but no 
decodes shown. Same wave files work with rc3.


I have many previously recorded wave files I use for testing purposes 
that no longer produce decodes under rc4 & rc5.


Is this a defect?

de Laurie VK3AMA



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

[wsjt-devel] WSJT-X 2.0 User Guide

[Joe Taylor]

Hi all,

I have posted what I'm calling a "minimally acceptable" WSJT-X 2.0 User 
Guide on the WSJT web site:


http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-2.0.0.html

It's what will come up in your browser when you click *Online User 
Guide" from the Help menu in RC4, RC5, or the soon-to-be posted GA 
release of WSJT-X 2.0.


Like previous User Guides, tis one will continue to evolve as we make 
additions and corrections.  If you find things missing or wrong, please 
let us know!


-- 73, Joe, K1JT


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

Re: [wsjt-devel] FT8 Roundup Cabrillo

[Joe Taylor]

Hi Dave,

On 12/3/2018 19:25, Dave Hachadorian K6LL wrote:

There were major issues with RST not getting filled in, both sent and 
received.  I’ve got about 200 dupes in my Cabrillo because one line has 
no RST, and the next line has the RST typed in manually.  It was a major 
pain during the contest.  While filling in the data manually, 
Transmitting is disabled, so it further slows down the RATE.
Also, when you get a repeat of the exchange, as frequently happens, the 
RST can change, so there may be a discrepancy between two logs, 
depending on which version of the RST was logged.  If I were the 
software programmer, I would make everybody 599 in contest mode, just as 
God intended.
It is interesting that it was only the sent/received RST that acted this 
way.  States/provinces and serial numbers were solid.

Dave Hachadorian, K6LL
Yuma, AZ


I have 638 QSOs in my log and only 14 dues.  I think all of these (or 
maybe all but one?) were "legitimate" dupes, by which I mean the same 
guy called me again, on the same band.  I had only a handful of 
semi-broken QSOs that required intervention to fill in a part of the 
exchange.  In no case was RST missing from information send to N1MM+.


If we are to help you diagnose what created your problem, we'll need 
more information about how you operated.  Could your SO2R operating 
technique have contributed that many Op errors?


Be aware: As clearly stated in the "Quick-Start Guide to WSJT-X 2.0", 
existing features for contesting are no more than a starting point.

So far we have given zero thought to conveniences for SO2R operating.
As usual, any and all suggestions for improvement are welcome.

-- 73, Joe, K1JT


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

Re: [wsjt-devel] WSJT-X 2.0 RC5 -- difference from 1.9.1

[Joe Taylor]

Larry --

On 12/3/2018 16:50, Larry Banks W1DYJ wrote:


I have just switched to 2.0 RC5.  I use it mainly for HF/FT8.
With FT8 and when at my 2nd home in Maine, I usually change my TX6 -- 
the autoloaded /_*CQ W1DYJ FN43*_/ -- to /_*CQ W1DYJ /ME*_/ as Maine is 
far more important info than just FN43 (v1.9.1).  NOW, it won’t take the 
/ME (v2.0 RC5). When I try, it just sends */_CQ W1DYJ_/*.  I did not 
find anything in the Quick Guide, etc., that helped me make this work as 
it used to.  (I also tried _CQ W1DYJ ME_.)
Have you deleted the “free form” 13-character CQ?  Is this no longer 
allowed?


73 -- Larry -- W1DYJ


No, but your particular message is a pathological case that won't work. 
Your inclusion of "/" in a CQ message has told the source encoder to 
expect a compound callsign.  Then, you do something else that is not a 
compound callsign.


FT8 (and nearly all of the WSJT-X modes) use carefully optimized 
structured messages to gain both content and sensitivity.  Better stick 
with the grid locator, that's what the optimized message wants.  It's 
also what your QSO partner's software (and the partner him/herself) will 
understand.


-- 73, Joe, K1JT


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

Re: [wsjt-devel] Delay in outgoing Tx5 Message

[Joe Taylor]

Hi Dave,

This is a known problem.  We will address it ASAP.

-- Joe, K1JT

On 12/3/2018 12:59 PM, Dave Hachadorian wrote:
I operated in the FT8 Roundup this past weekend, using two computers in 
SO2R.  Both computers logged about 450 QSO’s each.
One of the computers used a relatively slow CPU – An Athlon II X 2 220 
at 2.8 GHz, with a Passmark Score of 1621.  That computer has 12 GB of 
RAM.  Toward the end of the contest, there was a noticeable delay in my 
outgoing Tx5 message, while the computer seemed to be tied up putting 
the QSO into the log.  At the end, it was using up about 3 seconds of my 
transmit period before transmission began, and I was afraid the message 
would not get through.
The other computer had a speedy i5-8300H CPU with a Passmark Score of 
9465 and, while there was still a perceptible delay in updating the log, 
there was no delay to the outgoing message.
The slow computer exceeded the specs of the WSJT-X User’s Guide, so 
maybe there is a process that could be optimized a bit.

Thanks.
Dave Hachadorian, K6LL
Yuma, AZ

.


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




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

Re: [wsjt-devel] TX # spinner in RU Contest mode

[Joe Taylor]

On 12/1/2018 12:33, G3WDG char...@sucklingfamily.free-online.co.uk wrote:

Just wondering what the TX # spinner is used for (located to right of RX
freq combo box) on mainwindow GUI?


For non US/Canada stations, the contest exchange is signal report and 
QSO serial number.


-- Joe, K1JT


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

[wsjt-devel] Fwd: "FT8 Roundup" mock contest

[Joe Taylor]

Reminder: Another FT8 Roundup practice session starts about 3.4 hours 
from now.  See below.


The real FT8 Roundup starts in about 19.4 hours.  See 
https://www.rttycontesting.com/ft8-roundup/


See you in one or both events!  Be sure to use RC5 and to read the docs.

-- 73, Joe, K1JT

 Forwarded Message 
Subject: [wsjt-devel] "FT8 Roundup" mock contest
Date: Mon, 26 Nov 2018 16:55:00 -0500
From: Joe Taylor 
Reply-To: WSJT software development 
To: WSJT software development 

Hi all,

Another one-hour "practice contest" is scheduled for Saturday, December 
1, 0200-0300 UTC (that's Friday evening, Nov 30, NA time).  This session 
will serve as a final tune-up opportunity for those planning to operate 
in the "FT8 Roundup" on December 1-2 (more details below).


DIAL FREQUENCIES


The practice event will use dial frequencies 7.080-7.100 and 
14.130-14.150 MHz in 2 kHz increments -- the same as recommended for the 
FT8 Roundup and the ARRL RTTY Roundup (January 5-6, 2019).  Start at the 
low end, dial frequency 7.080 or 14.130.  If/when the lower sub-bands 
fill up, QSY upward in 2 kHz increments (7.082, 7.084, etc.).  (Use 
keyboard shortcuts Ctrl+Shift+F11 and Ctrl+Shift+F12 to move dial 
frequency down/up by 2 kHz.)


Everyone works everyone.  Do not use a compound or nonstandard callsign 
in this event.


To participate you must use WSJT-X 2.0 RC5 (or RC4, but RC5 is 
preferred).  Installation packages for RC5 in Windows, Linux, and macOS 
can be found near the bottom of this web page:

https://physics.princeton.edu/pulsar/k1jt/wsjtx.html

A revised "Quick-Start Guide to WSJT-X 2.0" for RC5 is posted here:
https://physics.princeton.edu/pulsar/k1jt/Quick_Start_WSJT-X_2.0.pdf
Be sure to read this entire document before using WSJT-X 2.0.

PREPARATION FOR THE MOCK CONTEST


Detailed setup instructions for the FT8 Roundup are posted here:
https://www.rttycontesting.com/ft8-roundup/preparation/
They serve equally well for the practice session.

Rules for the FT8 Roundup specify 100 W maximum power output.  We 
recommend the same limit for the practice session.


OPERATING PROCEDURES


Best operating practices for FT8 in contests will surely evolve as users 
gain experience.  As initial suggestions we recommend procedures 
slightly different from those used for everyday FT8 operation.  CQing 
stations ("Run" stations) should check TX EVEN/1ST and HOLD TX FREQ, and 
select audio Tx frequencies 200, 400, 600, ..., integral multiples of 
200 Hz. Search-and-pounce (S+P) stations should uncheck TX EVEN/1ST and 
HOLD TX FREQ and should call a CQing station at 0, 60, or 120 Hz above 
the CQ frequency.  These procedures should help to contain the 
mini-pileups around Run stations to relatively small frequency ranges. 
S+P stations can use Shift+F11 and Shift+F12 to move their Tx frequency 
down/up by 60 Hz.


If a 2 kHz segment becomes too full of stations, users should QSY upward 
in 2 kHz increments, thus establishing new operating sub-bands.  Again, 
you can use Ctrl+Shift+F11 and Ctrl+Shift+F12 to QSY between 
dial-frequency sub-bands.


THE FT8 ROUNDUP, DECEMBER 1-2
-

The FT8 Roundup starts at 1800 UTC on Saturday, December 1 and ends at 
2359 UTC on Sunday, December 2, 2018.  Power limit is 100 W output: no 
high-power amplifiers!  Full contest rules are posted at 
https://www.rttycontesting.com/ft8-roundup/ .


LOOKING TWO WEEKS AHEAD
---

We are planning to make the full General Availability (GA) release of 
WSJT-X 2.0 on or before December 10, 2018.  The necessary transition 
from from WSJT-X v1.9.1 to WSJT-X v2.0 protocols for FT8 and MSK144 
should take place by the end of calendar year 2018.


THEREFORE: As soon as possible after December 10, and certainly by 
January 1, 2019, everyone should be using WSJT-X 2.0 or a compatible 
v2.0 version of derivative programs such as JTDX or MSHV.  As of today, 
PSKreporter statistics show roughly 3000 users of WSJT-X versions older 
than v1.9.1, 9500 users of v1.9.1, and 3000 users of v2.0-rc#.  Please, 
everyone, help us to spread the word that upgrading to v2.0 after 
December 10 is very important.  There will be no looking back!


-- 73, Joe, K1JT


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


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

Re: [wsjt-devel] v2.0.0-rc5 - JT65 has disappeared

[Joe Taylor]

On 11/30/2018 5:06 PM, Jim Shorney NU0C wrote:
FWIW I have always used JT9+JT65 as opposed to plain JT65 mode. 


So did I.  Emphasis on past tense.  It was convenient and did a lot to 
encourage use of JT9 when it was a new mode.



Why would one not?


If one is involved in writing and maintaining code for this highly 
complex program, and if one pays any attention to the ways JT9 and JT65 
are actually used in late 2018, the choice is clear.  There is little 
(if any) reason to maintain a combo-mode.


-- 73, Joe, K1JT



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

Re: [wsjt-devel] v2.0.0-rc5 - JT65 has disappeared

[Joe Taylor]

Hi Sandro,

Thanks for reporting this defect.  It has been fixed, and will be OK in 
the GA release.


In the meantime, the workaround is essentially the same as I reported 
earlier: Switch to JT9+JT65 mode, toggle the button above "Hold Tx Freq" 
to show "Tx JT9 #", then return to JT9 mode.


We will probably do away with JT9+JT65 mode, some time soon.  It is no 
longer useful, and it complicated the code in a number of ways.


-- 73, Joe, K1JT

On 11/30/2018 3:32 PM, Alessandro Gorobey via wsjt-devel wrote:

Hi Joe,

I have similar problem switching from FT8 to JT9

- frequency 14.078 (registered in frequency table)
- switch from FT8 to JT9
- VHF/UHF functions are disabled
- standard message is "CQ IW3RAB JN65"

RX seem to be JT9, TX is fixed to FT8

Thank in advance

exceptional work

I hope the transition period for additional bits will last as little as 
possible



Il 29/11/2018 22:36, Martin Davies G0HDB ha scritto:

On 29 Nov 2018 at 16:06, Joe Taylor wrote:


Hi Martin,

Thanks for your report.  This bug was identified and fixed several days
ago.  It will not be present in the GA release.

The workaround in the RC5 release is simple.  Switch to JT9+JT65 mode,
toggle the button above "Hold Tx Freq" to show "Tx JT65 #", then return
to JT65 mode.

-- 73, Joe, K1JT


Hi Joe, many thanks.  Glad to hear the bug has already been fixed.

I'm looking forward to the GA release after which there'll 
(hopefully!) be more stations than at

present using 77-bit FT8!

On a largely unrelated topic, here's a few suggestions for 
incorporation into the GUI at some

point in time (not necessarily for the upcoming GA release)...

1.  It would be useful to be able to bring up the 'Configurations' 
menu without having to
 enable all the menu options by ticking the 'Menus' box.  It would 
make switching

 between different configurations slightly easier and quicker.

2.  It would be useful to have a keyboard shortcut, for example Alt-A, 
for adding a DX
 call and their grid to the database.  There's already a shortcut 
(Ctrl-L) for looking up a

 callsign, so why not have one for adding a callsign?

3.  When operating in DXpedition 'Hound' mode, it might be helpful if 
the frequency scale
 across the top of the Wide Graph windows was colour-coded red 
below 1000Hz and
 green above 1000Hz.  It might make it a bit more obvious to users 
that they shouldn't

 be calling the Fox below 1000Hz.

My thanks go to you, Bill and everyone else in the development team 
for all your hard work
and dedication to evolving and improving the software - your efforts 
have transformed

operating for many, many amateurs around the world.

--
73, Martin G0HDB


---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus



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






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

Re: [wsjt-devel] Which FREQS for 1-2 Dec Roundup?

[Joe Taylor]

On 11/30/2018 10:49 AM, DAMIJAN ŠKVARČ S58G wrote:
Sorry, maybe I have overlooked in the rules: Which exact frequencies 
will be used in 1-2 December Roundup?


J. Taylor wrote for mock test:
<<>>

But what about for 80, 15 and 10 M please?


Go here for FT8 Roundup Rules and related advice:

https://www.rttycontesting.com/ft8-roundup/rules/

You will find the following text:

"Suggested frequencies are 3.590-3.600, 7.080-7.100, 14.130-14.150, 
21.130-21.150 and 28.160-28.200 MHz. Set the WSJT-X dial frequency to a 
multiple of 2 kHz, for example 7.082 MHz. (Note from Japan: For JA-JA 
and JA-DX contacts, use 3.523, 7.033, 14.082, 21.082 and 28.082 MHz.)"


-- 73, Joe, K1JT


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

Re: [wsjt-devel] v2.0.0-rc5 - JT65 has disappeared

[Joe Taylor]

Hi Martin,

On 11/29/2018 3:44 PM, Martin Davies G0HDB wrote:


Using the 'Default' configuration in v2.0.0-rc5, I've just been invoking and 
trying all the various
modes that I'm likely to use, and JT65 seems to have disappeared.



In the process of trying each mode in turn I've found that even though I select 
JT65 from the
'Modes' menu I get JT9 - the 'goalposts' above the waterfall stay at the JT9 
width and when I
transmit a signal all I get are the JT9 tones.


Thanks for your report.  This bug was identified and fixed several days 
ago.  It will not be present in the GA release.


The workaround in the RC5 release is simple.  Switch to JT9+JT65 mode, 
toggle the button above "Hold Tx Freq" to show "Tx JT65 #", then return 
to JT65 mode.


-- 73, Joe, K1JT


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

Re: [wsjt-devel] FT8 Roundup practice session

[Joe Taylor]

On 11/29/2018 11:03 AM, Stephen Ireland VK3VM/VK3SIR wrote:

Any chance of coordinating a better time/band for testing?

The times selected (0200 GMT) are the worst possible times for 
long-haul, cross-equatorial propagation from your parts on 40m under 
current solar conditions. 0500 on 20m may provide better results for 
both you and us south of the equator.


Thanks and 73
Steve I
VK3VM/VK3SIR


Of course we know that any time selected will be less than ideal in some 
parts of the world.  The hour-long practice sessions promoted by the 
WSJT Development Group were scheduled after we requested input from 
subscribers to wsjt-devel.  We went with the advice received (which, as 
I recall, came almost entirely from NA and EU).  Our main goal -- the 
developers, that is -- was to test the program's operational and 
user-convenience features.


Please feel free to define and promote any practice session(s) that make 
sense for you.  W0YK did just that for the session last evening.  At 
least 73 people showed up, we had fun, and it provided useful input for 
future programming enhancements.


-- Joe


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

[wsjt-devel] FT8 Roundup practice session

[Joe Taylor]

Hi all,

I was on 40 meters for the FT8 Roundup practice session last evening (NA 
time).


Operating time: 0200 to 0259 UTC
Program: WSJT-X 2.0 RC5
Dial frequency 7.080
Power: 100 Watts
Antenna: Dipole at 50 ft

I operated as a Run station, calling CQ at audio Tx frequency 1000 Hz.
There are 240 15-second intervals in an hour, and I transmitted in half 
of them, using "Tx First/even".


In the 120 Rx intervals I decoded 1766 transmissions: an average of 14.7 
decodes per Rx interval.  These transmissions came from 73 different 
stations.  This was reasonably good turnout for a weekday evening, 
especially given the very short notice.  I logged 38 QSOs, including 2 
dupes.


I made notes of various things that can be made better in the WSJT-X 
user interface for contesting.  We'll get to these as time permits -- 
but for most of them probably not in time for the GA release of WSJT-X 
2.0 planned for December 10.  The current interface requires careful 
operator attention and some practice.


I'll plan to be on again for the next practice session: Saturday, 
December 1, 0200-0300 UTC (that's Friday evening, Nov 30, NA time).
Also for the first FT8 Roundup, starting the next day.  Contest rules 
are posted at https://www.rttycontesting.com/ft8-roundup/ .


-- 73, Joe, K1JT


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

Re: [wsjt-devel] ISCAT Problem?

[Joe Taylor]

On 11/27/2018 10:20 AM, Rory Bowers K5CKS wrote:
Is there a chance you will change that to a double click Joe?  


No.  ISCAT uses free-form messages.  It's totally unsuited to 
double-clicking or Auto-Sequencing logic.


I think 
ISCAT could be a LOT of fun.  I was amazed at the sensitivity!!


It can be a lot of fun.  But most QSOs you can make with ISCAT, you can 
also make with MSK144, probably even easier.  There is a fairly narrow 
range of circumstances in which ISCAT is, or should be, the preferred mode.

-- Joe, K1JT


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

Re: [wsjt-devel] [RTTY] "FT8 Roundup" mock contest [Two Sessions]

[Joe Taylor]

Hi Phil and Ed,

Thanks for sharing your views.

We thought long and hard about backward-compatibility issues before 
concluding that a change in the FT8 protocol was highly desirable.


Among the most important motivations were these:

1. Message formats optimized for North American VHF contests, European 
VHF contests, RTTY contests, and ARRL Field Day have been frequently 
requested by users.


2. Nonstandard and compound callsigns were a perpetual nuisance with the 
older protocols.  The new capabilities make them a breeze.


Neither of these objectives could be met with the original FT8 and 
MSK144 message payloads.


Our planned changes were publicized well in advance.  We sent internal 
details and source code to developers of the derivative programs JTDX 
and MSHV well in advance.  These guys are fully on board with the changes.


A number of other relevant considerations were spelled out very 
effectively by Ed, W0YK, in a previous message.


Upgrading to WSJT-X 2.0 will not be a big imposition.  Download, click 
to install over your older version, read and pay attention to the 
Release Notes, and away you go.


-- 73, Joe, K1JT

On 11/28/2018 2:37 PM, Ed Muns wrote:

Hi Phil.

This question is really for the WSJT development team to address.  But, my
personal opinion as a user differs a bit from yours.  I'll offer it here as
another perspective.

In general, I agree with your stated principle of backward compatibility.
At the same time I tolerate breaking the principle for good reason.  And, in
this case, I believe there is good reason.

First of all, WSJT-X is not a commercial product and the developers aren't
compensated much (tongue-in-cheek) for their tremendous efforts.  Second,
this mode was invented 1-1/2 years ago and should rationally be considered
as still in development.  Third, the use cases for this wonderful mode are
very diverse so a lot of conflicting requirements are being juggled.
Fourth, the WSJT-X source code is fully open for others to use.  There is no
monopoly.

I am delighted to be able to participate as a user in this state-of-the-art
development and believe the developers try hard to maintain backward
compatibility when they can.  The exception we're traversing now is
acceptable to me, even though it is a bit inconvenient and perhaps even
annoying to some.

When I start using a mode that is still being actively developed, my
expectation is that there well could be migration bumps and other
inconveniences.  That's been my frequent experience when I choose to be an
early adopter.  My alternative would be to stick with a digital mode like
RTTY that is unlikely to have backward compatibility issues.

I think the FT8 backward compatibility issue is exacerbated by the explosive
popularity of the mode on HF.  I'm sure the WSJT-X developers understand
this reality and respect user convenience balanced with striving to make FT8
the best it can be.

Ed W0YK

-Original Message-
From: Phil Sussman [mailto:psuss...@pactor.com]
Sent: 28 November, 2018 03:09
To: Ed W0YK
Cc: 'WSJT software development'; r...@groups.io; 'NCCC Reflector'
Subject: Re: [RTTY] "FT8 Roundup" mock contest [Two Sessions]
Importance: High

I am concerned that transition to Ver. 2.0 without backwards compatibility
to
previous versions is a serious shortfall. I do NOT plan to change because of
the lack of compatibility. There is a principle involved.

Not everyone is going to make the transition and I've spoken to others who
feel WSJT software is trying to monopolize the mode. (Those using JTDX and
some others.) Personally I don't care; however, as I mentioned backwards
compatibility is a must. Complexities aside, it's a basic concept that
should
be respected.

As someone who works with commercial software (e.g. Motorola, Harris, etc.)
all can be upgraded, but is always backwards compatible. Of course, that
makes future software revisions more complex, the price of maintaining a
base
of satisfied users who rely on support.

Thanks for reading and understanding.

73 de Phil - N8PS

---

Quoting Ed W0YK :


In addition to this practice contest just prior to the actual FT8 Roundup
next weekend, there will be an identical practice on Wednesday evening NA
time (0200-0300 UTC Thursday, 29 November).

Don and I feel another practice will be useful since we all need to ensure
we have installed and configured WSJT-X 2.0, rc5 correctly.  (rc4 will

also

work, but rc5 is preferred since it has improvements and bug fixes beyond
rc4.)

73,
Ed W0YK
Don AA5AU

-Original Message-----
From: Joe Taylor [mailto:j...@princeton.edu]
Sent: 26 November, 2018 13:55
To: WSJT software development
Subject: [wsjt-devel] "FT8 Roundup" mock contest

Hi all,

Another one-hour "practice contest" is scheduled for Saturday, December
1, 0200-0300 UTC (that's Friday evening, Nov 30, NA time).  This session
will serve as a final tune-up opportunity for those planning to operate
in the "FT8 Rou

Re: [wsjt-devel] LoTW / No LoTW

[Joe Taylor]

Lee --

On 11/28/2018 10:27 AM, Lee. KX4TT via wsjt-devel wrote:
It also does not work well with the green highlighting for those who are 
color-blind; People with either protanomaly  or deuteranomaly may have 
problems in this case. The result for red lettering on a green 
background can be two indistinct non-contrasting grays………..I would 
actually suggest not using red at all for this.


73 de Lee KX4TT


You have complete freedom to set the colors as you wish.

-- Joe, K1JT


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

Re: [wsjt-devel] WSJT-X 2.0 rc5: Open list problem

[Joe Taylor]

Hi John,


Would it not be better if files were always numbered with 6 time digits insted 
of a mix of 4 and 6 digits, then the list would be ordered in a squential 
manner?


Possibly, but that's not the way we've done it.  Labeling files with 
4-digit times makes good sense for the modes with 60 s T/R sequences, 
and we've labeled them that way for nearly 20 years now.


-- Joe, K1JT


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

Re: [wsjt-devel] Quick-Start Guide to WSJT-X 2.0

[Joe Taylor]

Hi Eugene,

On 11/27/2018 2:26 PM, Eugene UA1NAN wrote:

Hi friends!
I can send a translation (not machine) into Russian of the article
"Quick-Start Guide to WSJT-X 2.0" from Joe Taylor, K1JT.
  73, Eugene, UA1NAN.


Thanks for this offer!  I will be happy to post your translation on the 
WSJT web site.


-- 73, Joe, K1JT


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

Re: [wsjt-devel] WSJT-X rc5 hard crash

[Joe Taylor]

Hi Steve,

Thanks for the report.  You do know that ""W6XX W7WM RR73 TNX" is not a 
legal FT8 message, right?


Nevertheless, the program should not crash when it's given a bad 
message.  This defect will be fixed in the 2.0 GA release.


-- Joe, K1JT

On 11/27/2018 2:19 PM, Steve Boone W7WM wrote:
Sorry, I didn't report this during RC4 but I accidentally discovered 
this unusual behavior with WSJT-X just before RC5 was released. This 
also happens in RC5.


While in QSO at transmitting step TX1, TX2 or TX3
I manually change TX4 to "W6xx W7WM RR73 TNX"  [1 or 2 extra characters 
does not fail)

Click on TX4 (while TX1 is still transmitting)

WSJT-X 2.0 rc5 aborts:
WSJT-X screen disappears, wsjtx.exe task disappears (jt9.exe is still 
active-see note below)

transceiver hangs in transmit mode (PTT)

On restart of WSJT-X
Popup:
       Killing JT9.exe Process
       KilByName return code: 602

OK continues WSJT-X as normal

On initial startup, wsjt.exe has 3 sub-tasks:
wsjtx.exe
jt9.exe
console window host
I have mode = FT8

Windows 10 Pro 1803





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




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

Re: [wsjt-devel] RC5 error in JT65

[Joe Taylor]

On 11/27/2018 12:07 PM, Jari A wrote:
... I work several qsos with RC5 on FT8, then got silent with FT8, so I 
change to JT65 as I saw traffic on it.


I also note, that after I change from JT65 to JT9, RC5 keeps tx on FT8, 
even JT9 is indicated below date/ time window.


Aaah!  Now I understand what you did.  These are defects, and they will 
be fixed.


-- 73, Joe, K1JT


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

Re: [wsjt-devel] RC5 error in JT65

[Joe Taylor]

Hi Charlie, Jari, and all,

Thanks for your reports -- they are much appreciated.  I'm sure you 
understand that our recent work has mostly been related to HF interests 
-- in particular, the new 77-bit protocols for FT8 and MSK144, and new 
special messages for contesting.


We are certainly not forgetting about VHF+, JT65, QRA64, etc.  Some 
remaining issues, and perhaps some recently introduced ones, will be 
addressed as soon as we can.  This could be in time for the WSJT-X 2.0 
release in two weeks; if that's not possible, we will work with you to 
address them soon after that.


-- 73, Joe, K1JT


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

Re: [wsjt-devel] wsjt-x 2.0.0-rc5 right click on waterfall not as documented

[Joe Taylor]

On 11/27/2018 12:52 PM, Paul Kube K6PO wrote:

wsjt-x 2.0.0-rc5
Windows 10 Pro x64 Version10.0.17134 Build 17134

Position the mouse cursor in the waterfall window.
Right click.
A small dialog pops up announcing "Set Rx and Tx Offset".
The Rx and Tx offsets themselves are not affected.

However, the WSJT-x Special Mouse Commands documentation displayed with 
F5 says:

Ctrl-click or Right-click to set Rx and Tx frequencies


When the popup context menu appears you must select the desired action. 
Move the mouse pointer into the popup box and click there.



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

Re: [wsjt-devel] ISCAT Problem?

[Joe Taylor]

On 11/27/2018 9:54 AM, Rory Bowers wrote:
I installed rc5 this morning and ran ISCAT B on 6M.  I got two calls 
from my CQ.  When I tried to double click on one of them the program 
said "Double Click Not Available for ISCAT Mode".  How do you answer a 
call in ISCAT Mode??

Thanks,
Rory, K5CKS


Enter DxCall (and DxGrid, if desired).  Click Generate Std Msgs.  Select 
the desired message, e.g., Tx2, Tx2, etc.  Enable Tx.  Advance to 
subsequent messages as your QSO progresses.



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

[wsjt-devel] "FT8 Roundup" mock contest

[Joe Taylor]

Hi all,

Another one-hour "practice contest" is scheduled for Saturday, December 
1, 0200-0300 UTC (that's Friday evening, Nov 30, NA time).  This session 
will serve as a final tune-up opportunity for those planning to operate 
in the "FT8 Roundup" on December 1-2 (more details below).


DIAL FREQUENCIES


The practice event will use dial frequencies 7.080-7.100 and 
14.130-14.150 MHz in 2 kHz increments -- the same as recommended for the 
FT8 Roundup and the ARRL RTTY Roundup (January 5-6, 2019).  Start at the 
low end, dial frequency 7.080 or 14.130.  If/when the lower sub-bands 
fill up, QSY upward in 2 kHz increments (7.082, 7.084, etc.).  (Use 
keyboard shortcuts Ctrl+Shift+F11 and Ctrl+Shift+F12 to move dial 
frequency down/up by 2 kHz.)


Everyone works everyone.  Do not use a compound or nonstandard callsign 
in this event.


To participate you must use WSJT-X 2.0 RC5 (or RC4, but RC5 is 
preferred).  Installation packages for RC5 in Windows, Linux, and macOS 
can be found near the bottom of this web page:

https://physics.princeton.edu/pulsar/k1jt/wsjtx.html

A revised "Quick-Start Guide to WSJT-X 2.0" for RC5 is posted here:
https://physics.princeton.edu/pulsar/k1jt/Quick_Start_WSJT-X_2.0.pdf
Be sure to read this entire document before using WSJT-X 2.0.

PREPARATION FOR THE MOCK CONTEST


Detailed setup instructions for the FT8 Roundup are posted here:
https://www.rttycontesting.com/ft8-roundup/preparation/
They serve equally well for the practice session.

Rules for the FT8 Roundup specify 100 W maximum power output.  We 
recommend the same limit for the practice session.


OPERATING PROCEDURES


Best operating practices for FT8 in contests will surely evolve as users 
gain experience.  As initial suggestions we recommend procedures 
slightly different from those used for everyday FT8 operation.  CQing 
stations ("Run" stations) should check TX EVEN/1ST and HOLD TX FREQ, and 
select audio Tx frequencies 200, 400, 600, ..., integral multiples of 
200 Hz. Search-and-pounce (S+P) stations should uncheck TX EVEN/1ST and 
HOLD TX FREQ and should call a CQing station at 0, 60, or 120 Hz above 
the CQ frequency.  These procedures should help to contain the 
mini-pileups around Run stations to relatively small frequency ranges. 
S+P stations can use Shift+F11 and Shift+F12 to move their Tx frequency 
down/up by 60 Hz.


If a 2 kHz segment becomes too full of stations, users should QSY upward 
in 2 kHz increments, thus establishing new operating sub-bands.  Again, 
you can use Ctrl+Shift+F11 and Ctrl+Shift+F12 to QSY between 
dial-frequency sub-bands.


THE FT8 ROUNDUP, DECEMBER 1-2
-

The FT8 Roundup starts at 1800 UTC on Saturday, December 1 and ends at 
2359 UTC on Sunday, December 2, 2018.  Power limit is 100 W output: no 
high-power amplifiers!  Full contest rules are posted at 
https://www.rttycontesting.com/ft8-roundup/ .


LOOKING TWO WEEKS AHEAD
---

We are planning to make the full General Availability (GA) release of 
WSJT-X 2.0 on or before December 10, 2018.  The necessary transition 
from from WSJT-X v1.9.1 to WSJT-X v2.0 protocols for FT8 and MSK144 
should take place by the end of calendar year 2018.


THEREFORE: As soon as possible after December 10, and certainly by 
January 1, 2019, everyone should be using WSJT-X 2.0 or a compatible 
v2.0 version of derivative programs such as JTDX or MSHV.  As of today, 
PSKreporter statistics show roughly 3000 users of WSJT-X versions older 
than v1.9.1, 9500 users of v1.9.1, and 3000 users of v2.0-rc#.  Please, 
everyone, help us to spread the word that upgrading to v2.0 after 
December 10 is very important.  There will be no looking back!


-- 73, Joe, K1JT


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

[wsjt-devel] Candidate release WSJT-X 2.0.0-rc5

[Joe Taylor]

A fifth candidate release ("RC5") of WSJT-X 2.0 is now available for 
download and use by beta testers.  RC5 is stable, works well, and fixes 
the known problems in RC4.  It is likely that the General Availability 
(GA) release of WSJT-X 2.0, scheduled for two weeks from today, will be 
nearly identical to RC5.


Changes in RC5 relative to RC4 include the following:

 -  Make the "Auto Seq" checkbox sticky, again
 -  Remove the 5-minute mouse timer
 -  Correct the "worked before" logic for color highlighting
 -  Add "No own call decodes" checkbox in WSPR mode
 -  Display and log UTC (not local time) in contest operations
 -  Validate contest QSO details before allowing logging
 -  Force Aqua theme on macOS to avoid issues with Mojave dark theme
 -  Move Fox log Reset action to Fox log window context menu
 -  Improve layout of Working Frequencies and Station Information tables
 -  Allow deletes and editing in Fox and Contest log windows
 -  Add Tool Tips for Fox and Contest log windows
 -  Fix a bug causing false AP decodes in JT65 VHF+ operation
 -  Fix a bug that could switch unexpectedly from JT65 to JT9 mode

You may need to invoke "Settings | General | Colors | Reset 
Highlighting" on your first program start with this version.


The "Quick-Start Guide to WSJT-X 2.0" has been updated. Be sure to read 
this entire guide before using RC5:

http://physics.princeton.edu/pulsar/k1jt/Quick_Start_WSJT-X_2.0.pdf

We recommend using RC5 (and therefore the v2.0 FT8 protocol) in the 
conventional FT8 sub-bands at audio Tx frequencies 2000 Hz and higher. 
Inevitably the necessary transition from v1.x to v2.0 protocols for FT8 
and MSK144 will cause some confusion and cross-protocol interference. 
Users of v1.9.1 and earlier are unable to decode transmissions from 
users of RC4 and later, and vice-versa.


As more users upgrade their software to WSJT-X 2.0 -- and particularly 
after the General Availability (GA) release on December 10 -- the new 
protocol should start to dominate the conventional FT8 sub-bands.  As 
soon as possible after December 10, everyone should upgrade to WSJT-X 2.0.


Download links for RC5 on Windows, Linux, and macOS can be found on the 
WSJT-X web page http://physics.princeton.edu/pulsar/k1jt/wsjtx.html


A final FT8 "practice contest" will be held on Saturday, December 1, 
0200-0300 UTC (that's Friday evening, Nov 30, NA time).  Watch for a 
separate announcement with more details.


If you find any unexpected behavior with WSJT-X 2.0-rc5, please send a 
detailed report to the wsjt-devel email list,
wsjt-devel@lists.sourceforge.net. You must subscribe to the list in 
order to post there.


The first serious FT8 contest is scheduled for the weekend of December 
1-2.  See https://www.rttycontesting.com/ft8-roundup/ for full details 
and contest rules.  The ARRL RTTY Roundup (January 5-6, 2019) permits 
and encourages FT8 as well as traditional RTTY operation.



ONCE MORE: As soon as possible after December 10, and certainly by 
January 1, 2019, everyone should be using WSJT-X 2.0 or a compatible 
v2.0 version of derivative programs such as JTDX or MSHV.  As of today, 
PSKreporter statistics show roughly 3000 users of WSJT-X versions older 
than v1.9.1, 9500 users of v1.9.1, and 3000 users of v2.0-rc#.  Please, 
everyone, help us to spread the word that upgrading to v2.0 after 
December 10 is very important.  There will be no looking back!


-- 73, Joe, K1JT (for the WSJT Development Group)


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

Re: [wsjt-devel] Error loading LotW Users data

[Joe Taylor]

Hi Gorm,

On 11/26/2018 2:10 PM, Gorm Helt-Hansen OZ6GH wrote:


Windows 10 64 bit - WSJT-X RC4.

When starting I get the error msg: Error Loading LotW Users Data Network 
Error - SSL/TLS support not installed, cannot fetch: 
"https://lotw.arrl.org/lotw-user-activity.csv;


This error msg came between RC2 and RC3. In RC2 it worked fine.


Yes.  It has been mentioned about 999 times on this email list, along 
with reasons and work-around.  Lots of places to go for help.  You did 
read the Quick-Start Guide, right?

https://physics.princeton.edu/pulsar/k1jt/Quick_Start_WSJT-X_2.0.pdf
See under LoTW Download Errors on page 5.

-- 73, Joe, K1JT


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

Re: [wsjt-devel] DXPedition changes?

[Joe Taylor]

On 11/21/2018 12:08 AM, jarmo OH1MRR wrote:


Some months ago we said "The existing FT8 DXpedition mode will still
be supported, and a more powerful DXpedition mode may be offered as
well." We have not yet done serious work on the potentially "more
powerful mode". -- Joe, K1JT


As during VP6D, was seen, that they used 9 slots! 


As far as I know, VP6D used WSJT-X v1.9.1.  The maximum number of slots 
is 5.



When they CQ'ed, using
only one signal, signal was example -7, great, send my call, next lost
them totally, because they answered to 9 stations. I saw only slot
frames, but no decoding information. Someone, who had better antennas,
told me, that they are answering to me, no see...
I could copy, when they answered with 4 slots and fortunately got
qso. 


So, maybe limiting slots to some lower or to documentation some
words for dx, when propagation is bad, don't use more than 3-4 slots
max.


It's easy for Fox to limit the number of slots in use, and good 
operators quickly learn when to do this.


-- 73, Joe, K1JT


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

Re: [wsjt-devel] DXPedition changes?

[Joe Taylor]

Hi Mike,

On 11/20/2018 11:51 AM, Black Michael via wsjt-devel wrote:
It was mentioned a while ago that changes would be made to the Fox mode 
to avoid the power loss for multiple QSOs going on.


Has this been done?  rc4 still points to the old DXpedition guide.


The only change made to FT8 DXpedition Mode is to upgrade it to using 
77-bit messages.  User operation for both Fox and Hound is unchanged.


Some months ago we said "The existing FT8 DXpedition mode will still be 
supported, and a more powerful DXpedition mode may be offered as well."

We have not yet done serious work on the potentially "more powerful mode".
-- Joe, K1JT


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

Re: [wsjt-devel] RTTY roundup dups

[Joe Taylor]

Hi Dave and all,

On 11/20/2018 11:11 AM, David Kjellquist WB5NHL wrote:
Has anyone come up with ideas for avoiding dups when using FT8 in a 
large contest? JTAlert checks B4 but its display matrix is limited and 
not really designed for contest use. N1MM log integration works well but 
I don't see that it checks for dups prior actual log entry (not much 
help). But, I'm not really N1MM literate so I may be missing something.


JTAlert does preload a call into AClog but I can't check N3FJP contest 
logs since N3FJP integration is AClog only.


This is already taken care of in RC5 (which is not yet released).  In 
RC5 the color highlighting is (finally!) working properly.  See the 
screen shot that I posted to this reflector a couple of hours ago.


Steve, K9AN, and I both used RC5 last night, and we found it highly 
effective.  We'll do our best to make RC5 (or the full v2.0 release) 
available in plenty of time for the December 1-2 "FT8 Roundup".


One other point of interest.  Steve and I were paying particular 
attention to performance of the 77-bit decoder in a crowded band.  The 
mock contest provided an excellent indication of what it will be like 
when everyone upgrades to using the v2.0 protocols.  Decoding 
performance was uniformly excellent -- including the frequent copy of 2 
or even 3 overlapping signals.  THanks mostly to Steve's efforts, the 
77-bit decoder has some significant improvements over the older 75-bit one.

-- 73, Joe, K1JT


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

Re: [wsjt-devel] RC4 Mock

[Joe Taylor]

Hi Julian,

On 11/19/2018 9:46 PM, Julian VK4CMV wrote:
I've noticed that WSJT-X logging thinks it's on local time - see the 
Contest Log - the QSOs do make it in Z time to my HRD log via JTAlert 
though. (We are +10hrs on UTC)


There are some signals at 14.078 that I can't decode in RC4 or 1.9.1 - 
which is a bit of a mystery (they were there before the 'contest' began).


Thanks for your report.  Those undecodable signals are JS8, aka JS8CALL, 
formerly known as FT8CALL -- a mode based loosely on the old FT8, but 
using different sync information.


-- Joe, K1JT


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

Re: [wsjt-devel] Potential RC4 bug ? Auto Seq setting not sticky

[Joe Taylor]

On 11/19/2018 7:16 PM, Mark Spencer VE7AFZ wrote:


I downloaded and installed a fresh copy of RC-4 onto a different computer (a 
laptop running Windows 10 pro) a noticed the same behaviour.

While running FT8 if I select auto sequence and then re start the application 
auto sequence is not enabled.  I hope this information is of some use.


It would be, except that it has already been mentioned at least umpteen 
times on this reflector and on wsjtgroup.  We have stated that it's 
known, unintended, and long-since fixed.


-- Joe, K1JT


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

[wsjt-devel] Reminder: FT8 mock contest tomorrow

[Joe Taylor]

A one-hour "practice contest" will be held tomorrow using the FT8 mode 
and the ARRL RTTY Roundup rules.


Tuesday, November 20, 0200-0300 UTC (Monday evening, NA time)

Dial frequency 7.078 MHz (and higher, in 2 kHz increments, if too much 
QRM).  Secondary dial frequency, especially for those in other parts of 
the world: 14.078 MHz.


Everyone works everyone.

To participate you must use WSJT-X 2.0.0-rc4.  Installation packages for 
Windows, Linux, and macOS can be found near the bottom of this web page:

https://physics.princeton.edu/pulsar/k1jt/wsjtx.html

Note that this Release Candidate 4 ("RC4") is a beta-test version.  A 
full release of WSJT-X 2.0 is targeted for release on December 10, 2018.


A revised Quick-Start Guide to WSJT-X 2.0 for RC4 is posted here:
https://physics.princeton.edu/pulsar/k1jt/Quick_Start_WSJT-X_2.0.pdf

Be sure to read this entire document before using WSJT-X 2.0.  There 
have been many changes since RC3.


IMPORTANT FOR THE MOCK CONTEST:

1. On the *Settings | Advanced* tab, be sure to check the
*Special operating activity* and *ARRL RTTY Roundup* options.  In the 
field labeled "Exch" enter the 2- or 3-letter abbreviation for your 
state or province (US/Canadian stations) or DX if you are not in the US 
or Canada.


2. Be sure that 7.078 and 14.078 appear in your drop-down frequency list 
for FT8 mode.  You might need to do a *Reset* on the *Settings | 
Frequencies* tab.  If the sub-band starting at 7.078 becomes 
over-crowded we suggest moving to higher dial frequencies in 2 kHz 
increments: 7.080, 7.082, etc.  Type Ctrl+Shift+F12 to move up by 2 kHz, 
Ctrl+Shift+F11 to move down by 2 kHz.  You might want to change 
Bins/Pixel or adjust the width of the Wide Graph so as to limit the 
range of frequencies displayed to 0 - 2000 Hz.


3. Do not use a compound or nonstandard callsign in this event.

Note that planning is underway for other FT8 contests to be held in the 
next few months.


FT8 Roundup: December 1-2, 2018, see
https://www.rttycontesting.com/ft8-roundup/rules/ for detsils.

The ARRL RTTY Roundup, January 5-6 2018: FT8 is encouraged, as well as RTTY

Post results and comments here so we can all learn from an actual FT8 
contest-like experience.  If you are not already subscribed, you may 
wish to join the email list wsjt-devel:

https://sourceforge.net/p/wsjt/mailman/?source=navbar
That list is the best way to communicate directly with the WSJT 
Development Group.


-- 73, Joe, K1JT


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

Re: [wsjt-devel] 5 minute mouse timeout

[Joe Taylor]

Hi all,

Please!  No need for any more comments about a 5 minute mouse-movement 
timeout!  This feature was never intended to be a permanent addition. 
It had to do only with preventing trivial robotic use of WSJT-X during a

digi-mode contest.

Evidently it was a bad idea.  Already, several days ago, it was 
committed to the dustbin of history.


-- Joe, K1JT


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

Re: [wsjt-devel] Problems with RC4

[Joe Taylor]

Hi Giuseppe

On 11/16/2018 12:38 PM, Giuseppe Molinaro KE8FT via wsjt-devel wrote:
I would like to bring to your attention that I had to reinstate version 
RC3 because for some unknown reason the RX sensitivity is extremely low 
when using RC4 (about 90% less station decoded as compared to version 
RC3) on a Icom 7300 transceiver.


I reinstalled RC4 twice with identical results both times


There is nothing wrong with the sensitivity of RC4.

We assume that people using our beta releases will read and understand 
the Release Notes and Quick-Start Guides for the releases they are testing.


Release candidate RC4 decodes and transmits only 77-bit messages.  It 
will not (and is not supposed to) decode the 75-bit messages transmitted 
by WSJT-X v1.9.1 or earlier.  By default, release candidates RC1, RC2, 
and RC3 also transmits 75-bit messages.


-- 73, Joe, K1JT


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

Re: [wsjt-devel] I do not receive

[Joe Taylor]

Hi Paolo,

On 11/16/2018 12:16 PM, iw2etr Paolo Fiorelli IW2ETR wrote:
Hello everyone, can anyone understand why installing the rc4 I do not 
receive the station? with 1.9.1 everything is ok.


We assume that people using our beta releases will read and understand 
the Release Notes and Quick-Start Guides for the releases they are testing.


Release candidates RC1, RC2, and RC3 had decoders for both 75-bit and 
77-bit messages.  As described in the documentation, RC4 decodes and 
transmits only 77-bit messages.


-- 73, Joe, K1JT


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

Re: [wsjt-devel] So far, so good

[Joe Taylor]

Hi Chris and all,

On 11/16/2018 10:43 AM, Chris Schulz wrote:
I just started using the RC4 this morning. I had a strong signal on the 
waterfall trying to come back to me and never got a decode. So a local 
ham and myself went to 10m to test this. He was running RC3 and I ran 
RC4. He decoded my signal, I could not decode his reply. 


This is exactly as expected.

Please remember: RC3 and earlier versions had decoders for both 75-bit 
and 77-bit messages.  But unless you checked "Always generate 77-bit 
messages", standard messages for non-contest modes would be sent as 
75-bit messages.  These cannot be decoded by RC4.


-- 73, Joe, K1JT


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

Re: [wsjt-devel] So far, so good

[Joe Taylor]

Hi Gary,

Thanks for the report from down under.

On 11/16/2018 3:18 AM, Gary Hinson wrote:

RC4 works down here on the Far Side, albeit upside-down.

There are not too many RC4 stations to work, yet, but enough to know it works.

I believe I've been called several times today by 75-bit users (often on 'my' frequency above 2000) that I 
can't decode so I've been alternating between the standard CQ message and free-text messages along the lines 
of "WSJTX RC4", "77 BITS ONLY" and "NO CPY 75 BITS" in the hope that some of 
the undecodables will understand why I seem to be so rudely ignoring them.


You're doing exactly the right thing: encourage others to install RC4 
and use 77-bit messages.



I will persist in using 77 bit RC4, partly so others who are just trying it out 
have someone to copy and hopefully work.  I'm not worried about duplicates, so 
please don't hesitate to call me again.  Observers on the side will see 2x77 
bit QSOs in progress and might just be persuaded to upgrade to RC4.

Tomorrow, I'll take advantage of the extra bits by calling "CQ RC4 ZL2IFB RF80" or 
"CQ 77BT ZL2IFB RF80".


However... You will soon discover that these particular messages won't 
work as expected.  After the CQ you can insert 1-4 LETTERS.  Not "1-4 
characters".


-- 73, Joe, K1JT


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

Re: [wsjt-devel] Hide own call in WSPR decodes

[Joe Taylor]

Hi Paul,

Welcome to wsjt-devel, and thanks for the suggestion.  It would not be 
very difficult to implement something along these lines.  We'll put it 
on the ToDo list, for when time is available.


-- 73, Joe, K1JT

On 11/16/2018 7:01 AM, N1BUG wrote:

Hi,

This my first post here.

Some time ago there was brief discussion in the user forum about
hiding one's own call sign so it doesn't show up in the WSPR
decodes. I just installed RC4 and don't see this option implemented.
Could this be put on the list for consideration please?

Explanation:

My situation is not unique. I use WSPR extensively on 2200 meters
and sometimes 630 meters to study propagation. I use separate
receiver and transmitter which is common on these bands. Decodes of
my own WSPR transmissions (sent from a stand-alone hardware box, the
QRP Labs Ultimate 3S) showing in WSJT-X is a distraction. I would
prefer not to see decodes of myself as it serves no useful purpose
and means I need to scroll back constantly to see what interesting
DX I may have caught.

To make matters worse, I and others often see two decodes of our own
transmissions. 120 Hz sidebands are very common on these bands. Even
when they are down enough to be legal and not a problem to anyone
else, the incredible WSPR decoder decodes them! I usually transmit
on 137437 and see myself decoded on 137437 and 137557 every time.

Having the ability to not display WSPR decodes of one's own call
sign would, in my opinion, be very useful.

73,
Paul N1BUG


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




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

Re: [wsjt-devel] FT8 Roundup, 1-2 December 2018

[Joe Taylor]

Hi Ed,

On 11/15/2018 12:48 AM, Ed Muns wrote:

Don AA5AU and I are pleased to announce the FT8 Roundup to be held on 1-2
December 2019.  Rules, tutorials and other information can be found at:

https://www.rttycontesting.com/ft8-roundup/ 
...


One further suggestion, in addition to changing "December 2019" to 
"December 2018" in line 2 of your announcement.  There may be later 
release(s) of WSJT-X 2.0 before December 1.  Therefore your Rule 1 
should read as follows:


1.  FT8 mode only.  Must use WSJT-X 2.0, rc4 or later

-- 73, Joe, K1JT


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

Re: [wsjt-devel] recent_calls bug?

[Joe Taylor]

On 11/15/2018 9:17 AM, Black Michael via wsjt-devel wrote:

Was checking out the recent_calls hash and noticed this:

mskrtd.f90:   recent_calls(i)(1:13)=' '

But recent_calls is char*12.


Not correct.  See at top of packjt77.f90:

##
module packjt77

! These variables are accessible from outside via "use packjt77":
  parameter (MAXHASH=1000,MAXRECENT=10)
  character*13 callsign(MAXHASH)
  integer ihash10(MAXHASH),ihash12(MAXHASH),ihash22(MAXHASH)
  integer n28a,n28b,nzhash
  character*13 recent_calls(MAXRECENT)

  contains
...
##

-- 73, Joe, K1JT


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

Re: [wsjt-devel] WSJT-X 2.0.0-rc4

[Joe Taylor]

Hi Svend,

On 11/14/2018 12:00 PM, Svend Aage Jessen LA6YJA wrote:

The option of LOTW is giving me an error.
I do not use LOTW. Is there an option of turning it off?


Please follow instructions in the "Quick-Start Guide to WSJT-X 2.0",
https://physics.princeton.edu/pulsar/k1jt/Quick_Start_WSJT-X_2.0.pdf

 on page 5 under "LoTW Download Errors".

In Norwegian:

http://physics.princeton.edu/pulsar/k1jt/WSJT-X_2.0_no.pdf

-- 73, Joe, K1JT


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

Re: [wsjt-devel] Inconsistency in color scheme logic - PSE name it "Worked before" instead of "New Call"

[Joe Taylor]

Uwe --

On 11/14/2018 6:29 AM, DG2YCB, Uwe wrote:

*And PLEASE FIX ALL COLOR SCHEME BUGS BEFORE THE GA VERSION IS 
ANNOUNCED!!! *I don’t want to be impolite, but we have been discussing 
the color scheme issues at least for one and a half months now and rc4 
is still full of bugs ...


There is no need to SHOUT at us.

In case you haven't noticed, there has been significant effort toward an 
efficient and flexible color-highlighting scheme.  This feature is 
closely connected to the logging scheme, which also has evolved 
significantly owing to the program's new support for contesting.  Bugs 
will be fixed.


-- 73, Joe, K1JT


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

Re: [wsjt-devel] Candidate release WSJT-X 2.0.0-rc4

[Joe Taylor]

Hi Jim,

On 11/14/2018 12:54 AM, Jim Shorney NU0C wrote:


The only little nit I have os Operator call isn't sticky in the logging box.
Not that big a deal since I rarely do mutli-op, but I like to fill it in for
completeness if it is there and having to enter if for each QSO gets old. Am I
missing something? I've searched the settings.


Did your search include the Upper-right of the Settings | Reporting tab?

-- 73, Joe, K1JT


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

[wsjt-devel] "FT8 Roundup" mock contest

[Joe Taylor]

A one-hour "practice contest" will be held next week using the FT8 mode 
and the ARRL RTTY Roundup rules.


Tuesday, November 20, 0200-0300 UTC (Monday evening, NA time)

Dial frequency 7.078 (and higher, in 2 kHz increments, if too much QRM). 
 Everyone works everyone.


To participate you must use WSJT-X 2.0.0-rc4.  Installation packages for 
Windows, Linux, and macOS can be found near the bottom of this web page:

https://physics.princeton.edu/pulsar/k1jt/wsjtx.html

Note that this Release Candidate 4 ("RC4") is a beta-test version.  A 
full release of WSJT-X 2.0 is targeted for release on December 10, 2018.


A revised Quick-Start Guide to WSJT-X 2.0 for RC4 is posted here:
https://physics.princeton.edu/pulsar/k1jt/Quick_Start_WSJT-X_2.0.pdf

Be sure to read this entire document before using WSJT-X 2.0.  You will 
find many changes since RC3.


IMPORTANT FOR THE MOCK CONTEST:

1. On the *Settings | Advanced* tab, be sure to check the
*Special operating activity* and *ARRL RTTY Roundup* options.  In the 
field labeled "Exch" enter the 2- or 3-letter abbreviation for your 
state or province (US/Canadian stations) or DX if you are not in the US 
or Canada.


2. Be sure that 7.078 appears in your drop-down frequency list for FT8 
mode.  You might need to do a *Reset* on the *Settings | Frequencies* 
tab.  If the sub-band starting at 7.078 becomes over-crowded we suggest 
moving to higher dial frequencies in 2 kHz increments: 7.080, 7.082, 
etc.  Type Ctrl+Shift+F12 to move up by 2 kHz, Ctrl+Shift+F11 to move 
down by 2 kHz.  You might want to change Bins/Pixel or adjust the width 
of the Wide Graph so as to limit the range of frequencies displayed to 0 
- 2000 Hz.


3. Do not use a compound or nonstandard callsign in this event.

Note that planning is underway for one or more dedicated FT8 contests to 
be held in the next few months. The ARRL RTTY Roundup, January 5-6 2018, 
encourages FT8 as well as RTTY participation.


Post results and comments here so we can all learn from an actual FT8 
contest-like experience.


If you are not already subscribed, you may wish to join the email list 
wsjt-devel:

https://sourceforge.net/p/wsjt/mailman/?source=navbar
That list is the best way to communicate directly with the WSJT 
Development Group.


-- 73, Joe, K1JT


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

Re: [wsjt-devel] RC 4 not setting auto seq to on

[Joe Taylor]

Hi all,

Please read the posts by others and remember that a problem needs to be 
reported only once.


You may rest assured that we already know that the state of the "Auto 
Seq" box is not being remembered on program restart.


-- &3, Joe, K1JT


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

Re: [wsjt-devel] Candidate release WSJT-X 2.0.0-rc4

[Joe Taylor]

Thanks to all who have installed RC4, read the new Quick-Start Guide, 
and proceeded to make QSOs using the new FT8 protocol.


Transition to the v2.0 protocol seems to be going smoothly.  Most people 
with RC4 are using the standard FT8 dial frequencies and remembering to 
transmit above Tx Freq 2000 Hz.


I just used the RC4 release to make 20 QSOs in about 25 minutes, on 20m. 
 I QSYed to 40m and I'm finding plenty to work there, as well.


Please send reports of any problems to wsjt-devel.

-- 73, Joe, K1JT


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

Re: [wsjt-devel] New release RC-4 not decoding anything.

[Joe Taylor]

Tnx Ed, that's very helpful.  More will get the picture, soon.

-- 73, Joe, K1JT

On 11/13/2018 10:48 AM, Ed Wilson via wsjt-devel wrote:

Working great for me...made several contacts above 2000 Hz.

Ed, K0KC



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

Re: [wsjt-devel] New release RC-4 not decoding anything.

[Joe Taylor]

On 11/13/2018 10:28 AM, Bob via wsjt-devel wrote:
Just downloaded the new Beta RC4 and no signals are showing decoded.  
Answer?


Bob AA7CT


Please follow instructions and "Be sure to read this entire guide before 
using RC4:

http://physics.princeton.edu/pulsar/k1jt/Quick_Start_WSJT-X_2.0.pdf "

Pay attention to the third paragraph on page 1.

Try calling CQ for a while at a Tx Freq above 2000 Hz.

-- 73, Joe, K1JT


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

[wsjt-devel] Candidate release WSJT-X 2.0.0-rc4

[Joe Taylor]

A fourth candidate release ("RC4") of WSJT-X 2.0 is now available for 
download and use by beta testers.


Changes in RC4 relative to RC3 include the following:

 -  Fix the "cannot open file fort.81" bug
 -  Avoid too many redirect loops related to openSSL support
 -  Fix the auto-generated messages for nonstandard callsigns
 -  Remove all support for the legacy FT8 protocol
 -  Disallow selecting MSK144 with RTTY or Field Day messages active
 -  Correct and expand support for color highlighting decoded messages
 -  ESC key aborts a QSO, clears DX Call, and selects Tx6
 -  Disable "nextCall" procedure for RTTY contest; it still needs work
 -  Correct a flaw in handling MSK144 Sh messages
 -  Prevent Fox from inadvertently toggling Tx 1st/Even
 -  Re-organize the Fox/Hound/Contest selection boxes
 -  Improve the validators for contest exchange boxes
 -  Disable Tx after 5 minutes of no mouse movement
 -  Remove end-of-line AP info when using contest messages
 -  Fix the Sent and Rcvd exchanges sent to N1MM+ and ADIF log
 -  Don't auto-log a QSO with incomplete exchange info
 -  Fix two sequencing flaws after double-clicks on a decoded msg
 -  New facilities for Contest and Fox-mode logging

Be sure to invoke "Settings | General | Colors | Reset Highlighting"
on your first program start with this version.

The "Quick-Start Guide to WSJT-X 2.0" has been revised and extended.  If 
Be sure to read this entire guide before using RC4:

http://physics.princeton.edu/pulsar/k1jt/Quick_Start_WSJT-X_2.0.pdf

As described in the Quick-Start Guide, at this time we recommend moving 
MSK144 activity back to the standard 6-meter working frequencies: 50.360 
MHz in IARU Region 1, 50.260 in Regions 2 and 3. We recommend also 
starting to use the v2.0 FT8 protocol in the conventional FT8 sub-bands 
— for example, dial frequencies 7.074 and 14.074 MHz on 40 and 20 
meters. Inevitably this will cause some initial confusion: users of 
v1.9.1 and earlier will be unable to decode transmissions from users of 
v2.0.0-rc4, and vice-versa. To minimize this cross-protocol interference 
we suggest initially using the RC4 release at audio Tx frequencies 2000 
Hz and higher. As more users upgrade their software to RC4 or later, 
activity can gradually move downward in audio frequency. By December 10 
or very soon afterward, everyone should upgrade to the full WSJT-X 2.0 
general availability (GA) release.


Download links for RC4 on Windows, Linux, and macOS can be found on the 
WSJT-X web page http://physics.princeton.edu/pulsar/k1jt/wsjtx.html


A one-hour "FT8 mock contest" will be held next week: November 20, 
0200-0300 UTC (that's Monday evening, Nov 19, NA time).  Watch for a 
separate announcement with more details.


We look forward to your feedback on WSJT-X 2.0-rc4.  Reports should be 
sent to the wsjt-devel email list, wsjt-devel@lists.sourceforge.net. You 
must subscribe to the list in order to post there.


-- 73, Joe, K1JT (for the WSJT Development Group)



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

Re: [wsjt-devel] Returning from Hound to normal mode.

[Joe Taylor]

Hi Dave,

On 11/9/2018 2:05 PM, David Gould wrote:
I see the following which has been has been present for some time, I 
thought it might have changed in RC3 but it has not.


I am not sure it is a bug, but a design perhaps limitation.

I always have Hold TX freq checked.
When change to Hound mode it obviously has to be unset.
When change back from Hound mode to normal mode it remains unset.
Although I know it happens I keep getting caught out by it.

Is it possible to either:-
1) return to what it was set originally
2) have the default as to always set it as checked (good practice)


This sort of question has been discussed here many times.  One of them 
was earlier today.


WSJT-X faithfully remembers user settings on program exit and restart. 
For many reasons it does not guarantee doing so after a user-initiated 
change followed by a reverse change.


If you have more than one favored setups use the Configuration menu. 
Make separate Configurations for "FT8" and "FT8 Hound" (say) , 
configured the way you like, and then switch between them by switching 
Configurations.


-- 73, Joe, K1JT


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

Re: [wsjt-devel] Auto Seq hic-cup

[Joe Taylor]

Hi Russ,

On 11/8/2018 7:59 PM, Russ wrote:
Hi All. Want to report some problems.Maybe they have been reported 
before but it takes too long to go through all the messages on this forum.


I’m running RC3 on a windows 10 system.

 1. I’m on MSK144 and have FTOL set to 200.I go to JT65 and set FTOL to
50.I return to MSK144 and FTOL there is now at 50.It took me quite a
while to discover why I was not decoding pings on MSK144…


WSJT-X faithfully remembers user settings on program exit and restart. 
For many reasons it does not guarantee doing so after a mode switch 
followed by return to the original mode.


If you want such behavior, use the Configuration menu.  Make separate 
Configurations for MSK144 and JT65, set up the way you like, and then 
switch modes by switching Configurations.



 2. On both of the above modes the SH and Auto Sequence checkboxes keep
getting unchecked.This is particularly true in JT65 mode, but it
happens in MSK as well.They get unchecked while using the program
(don’t have a tested scenario), and they sometimes do not stay
checked after a restart.


I have not seen such behavior, and have not received any similar 
reports.  Please document a situation in which an unexpected change 
occurs for you.



 3. In JT65 mode the auto sequencing does not work right.For example,
when a station answers by sending calls and an OOO report, the next
sequence for me would be to send just RO (when SH is checked).But
the program starts sending calls and OOO report instead.Then when
advancing from RO to 73, it just continues sending RO.


Auto-sequencing is designed for the 15-second modes FT8 and MSK144. 
It's normally quite necessary for 60-second modes like JT65.  However, 
as a favor to some microwave EME Ops we tentatively activated it for use 
when they are kept very busy with antenna pointing, etc.  They don't 
normally use Sh messages, and I do not think we have ever tested 
auto-sequencing in JT65 with Sh messages.  If you think it's important, 
we could look into it.



 4. Periodically WSJT-X stops receiving.Everything seems to work, and
the noise level is still there, but the waterfall or graph does not
advance, and no signals are found.The program must be restarted to
get it working again.This has been happening even with 1.9 and 1.8
versions, and on multiple computers.(I would guess that one of the
program threads is dying.)


This does not sound like a WSJT-X issue. ???


 5. Sometimes, in JT65 (and maybe in MSK144), the ability to double
click on a received call and have the messages auto generate stops
working.


Please provide example(s).

-- 73, Joe, K1JT


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

Re: [wsjt-devel] FT8 RU Test #2 Observations

[Joe Taylor]

On 10/25/2018 9:27 AM, Joe WB8SBD wrote:


where does the exported cabrillo get saved?


Use the command "File -> Export Cabrillo log".  You can save it wherever you 
choose.

Thats what I thought would happen. But after the test last night I did 
do that sequence, and the usual popup asking where to save it never 
appeared. So I thought it just does it to some default location.


You need to click the "Save As" button.

-- Joe, K1JT


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

[wsjt-devel] Mock FT8 Roundup Observations

[Joe Taylor]

Everyone seems to have had fun exercising the RTTY RU features in 
WSJT-X.  I did, too, making 37 QSOs in a little over an hour using 100 W 
and a dipole.


I found more things wrong than others have reported, so far.  I will 
document them carefully and report here more fully in a little over a 
week.  (I will be busy with other commitments from Oct 26 through Nov 1.)


Bottom line, as I see it today:

It's clear that the new FT8 message formats can work well for RTTY 
contesting.  We still have work to do on improving the contest-oriented 
user convenience features.


-- 73, Joe, K1JT


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

Re: [wsjt-devel] FT8 RU Test #2 Observations

[Joe Taylor]

On 10/25/2018 8:32 AM, Joe WB9SBD wrote:

where does the exported cabrillo get saved?


Use the command "File -> Export Cabrillo log".  You can save it wherever 
you choose.

-- Joe, K1JT




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

[wsjt-devel] Reminder: Mock "FT8 Roundup" Contest is tomorrow

[Joe Taylor]

A one-hour "practice contest" will be held tomorrow (Wednesday evening, 
NA time) using the FT8 mode and the ARRL RTTY Roundup rules.


Date and time: Thursday, 25 October 0200-0300 UTC

Dial frequency 7.078 (and higher, in 2 kHz increments, if too much QRM). 
 Everyone works everyone.


To participate you must use WSJT-X 2.0.0-rc3.  Installation packages for 
Windows, Linux, and macOS can be found near the bottom of this web page:

https://physics.princeton.edu/pulsar/k1jt/wsjtx.html
Note that this Release Candidate 3 ("RC3") is a beta-test version.  A 
full release of WSJT-X 2.0 is targeted for release on December 10, 2018.


A revised Quick-Start Guide to WSJT-X 2.0 for RC3 is posted here:
https://physics.princeton.edu/pulsar/k1jt/Quick_Start_WSJT-X_2.0.pdf
Be sure to read this entire document before using WSJT-X 2.0.  Changes 
in RC3 relative to RC2 are described starting on page 7.


If you have not already used RC3, and especially if you will use Linux 
of macOS, be sure to read this message containing work-arounds for known 
issues:


https://sourceforge.net/p/wsjt/mailman/wsjt-devel/thread/ca07c870-e48d-1a7d-9183-0c40afb2ebf9%40princeton.edu/#msg36444674


IMPORTANT FOR THE MOCK CONTEST:

1. On the *Settings | Advanced* tab, be sure to check the boxes
*Always generate 77-bit messages*, *Decode only 77-bit messages*, and
*ARRL RTTY Roundup*.  In the field labeled "Exch" enter the 2- or 
3-letter abbreviation for your state or province (US/Canadian stations) 
or DX if you are not in the US or Canada.


2. Be sure that 7.078 appears in your drop-down frequency list for FT8 
mode.  You might need to do a *Reset* on the *Settings | Frequencies* 
tab.  If the sub-band starting at 7.078 becomes over-crowded we suggest 
moving to higher dial frequencies in 2 kHz increments: 7.080, 7.082, 
etc.  Type Ctrl+Shift+F12 to move up by 2 kHz, Ctrl+Shift+F11 to move 
down by 2 kHz.


3. Do not use a compound or nonstandard callsign in this event.


Note that planning is underway for one or more dedicated FT8 contests to 
be held in the next few months. The ARRL RTTY Roundup, January 5-6 2018, 
is explicitly encouraging FT8 as well as RTTY participation.


If you are not already subscribed, you may wish to join the email list 
wsjt-devel:

https://sourceforge.net/p/wsjt/mailman/?source=navbar
That list is the best way to communicate directly with the WSJT 
Development Group.


Post results and comments here so we can all learn from an actual FT8 
contest-like experience.


-- 73, Joe, K1JT


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

Re: [wsjt-devel] Major Crash with Ver 2.0.0-rc3

[Joe Taylor]

Tom --

Your problem has been described a number of times already on this email 
list.  The work-around solution is simple: run the program from a 
command-prompt window.


-- 73, Joe, K1JT

On 10/22/2018 5:40 PM, Tom Harson wrote:

Hello

I am experiencing a program crash with RC3 (*This does not happen in RC2*)

Also this does not happen when running wsjt alone.


System / Operating information

Using Mint linux ver. 19.0

wsjtx ver. 2.0.0-rc3_amd64.deb

Logging Program - CQRLOG

The program crashes upon DECODE


Here's the Dump


Running: /usr/bin/jt9 -s WSJT-X -w 1 -m 3 -e /usr/bin -a 
/home/tom/.local/share/WSJT-X -t /tmp/WSJT-X
At line 145 of file /home/bill/wsjtx-prefix/src/lib/ft8_decode.f90 (unit 
= 81)

Fortran runtime error: Cannot open file 'fort.81': Permission denied

Error termination. Backtrace:
#0  0x7f1513f8d31a
#1  0x7f1513f8dec5
#2  0x7f1513f8e68d
#3  0x7f1514100c3d
#4  0x7f151410796c
#5  0x5562ffd3fb80
#6  0x5562ffd33d79
#7  0x5562ffd2c565
#8  0x5562ffd2b2a8
#9  0x5562ffd29bde
#10  0x7f1513034b96
#11  0x5562ffd29cd9
#12  0x


Thanks de Tom K5VJZ






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




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

Re: [wsjt-devel] possible MSK144 auto sequencing issue v2.0 rc-3 ?

[Joe Taylor]

Hi Mark,

On 10/21/2018 2:07 PM, Mark Spencer VE7AFZ wrote:

Hi.   Was running with another station on MSK144.   I was in NA contest mode (but I 
believe the other station wasn't as they were not calling me with my "/R" call.)

Things seemed to be working until another Station sent "TU JOHN 73"  this 
caused my station to advance to TX5 even though the message wasn't directed to me.  I was 
also prompted to log the QSO (even though the QSO wasn't complete.).  Is this normal ?


Your QSO should look like the one shown for NA VHF Contest on page 4 of
https://physics.princeton.edu/pulsar/k1jt/Quick_Start_WSJT-X_2.0.pdf

You'll need to find out why he did not call VE7AFZ/R.  If he 
double-clicked on your "CQ VE7AFZ/R CN89", he would have used the /R.


Your QSO is obviously complete -- he sent you 73.  Auto-sequencing 
cannot work with free-form text messages, so you need to intervene at 
that point.


-- 73, Joe, K1JT


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

Re: [wsjt-devel] WSJT-X 2.0.0. rc3 and LotW

[Joe Taylor]

Gorm --

On 10/21/2018 6:31 AM, Gorm Helt-Hansen OZ6GH wrote:

Hi.

WSJT-X 2.0.0.-rc3
Windows 10

When starting WSJT-X I receive the error msg:

'Error loading LotW Users Data.

Network Error - Too many redirects: 
'https://lotw.arrl.org/lotw-user-activity.csv'


And no LotW colours in WSJT-X


Discussed many times here before.  Please see (for example) the thread 
with subject line "Summary of early results with WSJT-X 2.0-RC3".


-- 73, Joe, K1JT


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

Re: [wsjt-devel] Possible bug (?) 1.9.1 with numeric msg

[Joe Taylor]

Hi Paul,

On 10/20/2018 11:04 AM, Paul Bramscher KD0KZE wrote:
Running WSJT-X 1.9.1 r8747 compiled on Debian (AMD64) Linux.   A couple 
days ago an operator on 20M FT8 was calling CQ 052 {his call | his 
grid}.  Out of curiosity I clicked his message in the band activity 
pane.  My radio then switched to 14.052 MHz and the freq. pane turned 
red (indicating a non-standard FT8 freq.) .  In the Rx Frequency pane, I 
got purple messages stating "QSY 14.052".


Is this a bug or a feature that I've not seen yet?


Please refer to the WSJT-X User Guide here (scroll down a page or so), 
look for "CQ nnn":

https://physics.princeton.edu/pulsar/k1jt/wsjtx-doc/wsjtx-main-1.9.1.html#CONTROLS_CENTER

This behavior is motivated for and intended mainly for use with meteor 
scatter on VHF bands, where in busy periods there may be a "callign 
frequency" for CQs, and QSOs are completed on other frequencies.


-- 73, Joe, K1JT


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

Re: [wsjt-devel] Delay when receiving multible answer from DX

[Joe Taylor]

Hi Gorm,

On 10/20/2018 5:33 AM, Gorm Helt-Hansen OZ6GH wrote:

Fox - Hound mode. Qso with ZL7X.

I noticed WSJT-X had a delay when receiving answer from DX. I received a 
multible callsign answer from DX. WSJT-X continued sending call. When 
receiving a specific answer from DX, WSJT-X changed to sending report. 
See the photo, pse.


I see nothing wrong the sequence of messages in your screen shot.

07:28:30 - ZL7X called you with report "-11"
07:28:45 - You sent report "R-05"
07:29:00 - He calls you again, report "-13"
07:29:15 - You send report "R-11"

ZL7X did not send RR73, so there is no QSO.



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

Re: [wsjt-devel] Improving S/N

[Joe Taylor]

Hi Frank,

On 10/19/2018 9:47 AM, Frank Kirschner KF6E wrote:
One thing I haven't seen discussed on this reflector is improving the 
S/N by narrowing the receiver bandwidth. It is no surprise that 
decreasing the bandwidth received increases the S/N, by 10 to 15 dB, 
sometimes more. When I see a station I want calling at -24 or so, I can 
narrow the BW and get solid communications. This is very easy with the 
graphical presentation and digital filtering of the Flex 6600, but with 
a little practice, could be done on any modern receiver.


This means that, if we knew where the stations were calling at -30 or 
so, we could focus on them and bring them up to the point of making 
contact. Since you can't decode stations at that S/N, it would have to 
be done "out of band." Is there any thought being given to setting up an 
FT8-only DX cluster with exact frequencies?


What a fascinating hobby!


Desirable settings for received bandwidth are discussed in the WSJT-X 
User Guide here:


http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-1.9.1.html#TRANSCEIVER

There is NO decoding advantage to setting a narrow received bandwidth, 
(for example, 500 or even 200 Hz) centered on a desired weak signal.


Why not?  Because the WSJT-X decoders already filter the data in 
software, down to a detection bandwidth equal to the keying rate (6.25 
Hz for FT8, 2.69 Hz for JT65, 1.74 Hz for JT9, etc.  A narrow receiver 
bandpass setting will only serve to confuse the decoder and bias its 
measurement of S/N, producing unreliable values.


-- 73, Joe, K1JT


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

Re: [wsjt-devel] Red 'indicators' not showing on main window in MSK144 mode when ARRL Field Day or ARRL RTTY Roundup selected

[Joe Taylor]

On 10/18/2018 6:36 PM, K5GZR - Rick wrote:
In FT8 mode, selection of any one of the ‘Special operating activity’ 
options causes a red background ‘flag’ to appear on the WSJT-X main 
window just to the right of the large date and time box, indicating 
which activity has been selected.


However,

In MSK144 mode, the red background ‘flag’ appears only for NA VHF and EU 
VHF, and not for ARRL Field Day and ARRL RTTY Roundup.   If those are 
valid ‘special operating activities’ for MSK144 mode, then the ‘flags’ 
should be shown.  If the activities are not valid for MSK144 then they 
should be either greyed out or omitted on the Settings-Advanced window.


From the Quick-Start Guide to WSJT-X 2.0, top of page 10:

"MSK144 cannot be used with the ARRL Field Day or ARRL RTTY Roundup 
message formats."


This restriction is, of course, by design.  MSK144 is forbidden at HF, 
so useless in the RTTY Roundup; and why would anyone want to use MSK144 
for Field Day?


-- 73, Joe, K1JT


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

Re: [wsjt-devel] Hound 77-bit

[Joe Taylor]

On 10/18/2018 6:06 PM, Black Michael via wsjt-devel wrote:

Seems it's not possible to turn off 77-bit messages when Hound is selected?
As soon as I save it and come back in they're checked again.


From the Quick-Start Guide to WSJT-X 2.0:

"FT8 DXpedition Mode: Starting with release candidate RC3 the “Fox and 
Hound” operating mode will always transmit and receive using only the 
new 77-bit messages."


From the RC# release announcement:

"13. Convert DXpedition mode to always use 77-bit messages"

-- 73, Joe, K1JT


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

[wsjt-devel] Summary of early results with WSJT-X 2.0-RC3

[Joe Taylor]

Hi all,

According to PSK Reporter statistics, more than 650 users are busy 
making QSOs with WSJT-C 2.0-RC3.  This is good!


Nearly all of the early reports are related to one of two issues:

1. Some Windows users receive error messages related to downloading the 
ARRL's LoTW status file.  Messages like "Too many redirects", or "SSL 
handshake failed".


These will be easy to fix.  In the meantime, here's a work-around:

Download the OpenSSL installer for Windows from here:
https://slproweb.com/products/Win32OpenSSL.html ,
specifically the "Win32 OpenSSL v1.0.2p Light" version. Note that this 
is the right version even if you are running 64-bit Windows. Download 
link is

https://slproweb.com/download/Win32OpenSSL_Light-1_0_2p.exe .

Run the downloaded installer using default options and accept the
option to install the libraries into the Windows system directory.

Alternatively, you can fetch the file manually from 
https://lotw.arrl.org/lotw-user-activity.csv
and put it into your WSJT-X log file directory ("Menu->File->Open log 
directory").


2. macOS users get an error message "Subprocess failed with exit code 
2", caused by an attempt to write diagnostic information to file fort.81 
in a write-protected directory.


You can work around the issue by starting the application from the 
command line rather than the application bundle. Do something like this 
from a command-prompt window:


cd /Applications/WSJT-X/Contents/MacOS
./wsjtx

You may have to install the application away from the /Applications 
directory as well, you can drag'n'drop it onto the desktop for example.


3. A few people have complained that color-highlighting does not work as 
expected.  Most of these can be traced back to not having used the 
available configuration options.


Please note that the sense of the LotW highlighting has been changed 
such that highlighting is on for known LotW users. This is mainly to be 
consistent with other applications that do similar highlighting. You now 
can also turn the highlighting on and off as well as set the minimum 
number of days since last upload that characterizes a call as a LotW 
user. See the "Settings->Colors" panel for the controls. You also have 
"Menu->View->Color highlighting scheme" as an on-screen reminder.


A future release will allow changing the relative priorities of New 
call, New grid, New DXCC, etc.


-- 73, Joe, K1JT


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

Re: [wsjt-devel] MyCall cut when calling special station

[Joe Taylor]

Hi Attila,

A program bug causes your Tx1 message to be auto-generated incorrectly 
when you double-click on a nonstandard callsign.  As a temporary 
work-around, when working a station such as CR140AA disable Tx1 by 
double-clicking on the Tx1 button (or radio Button) first, so that you 
will call with your Tx2.


-- 73, Joe, K1JT


On 10/18/2018 10:35 AM, Attila Kocis wrote:

Hi

Using RC3 on Win10 Pro x64 v1803

CR140AA calling CQ in 77 bit mode.

My Settings: 77bit tx and rx checked.

When I try to call him, it cuts my callsign DL1NUX tu DL1NU

So I quit calling him, because „DL1NU“ also exists 

73 de dl1nux





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




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

Re: [wsjt-devel] RC3 sequence problem

[Joe Taylor]

Mike --

On 10/17/2018 5:22 PM, Black Michael via wsjt-devel wrote:

Was working a QSO...logged him during the 73 being sent from me.
He came back with another RRR and the autosequence then sent R+00 
instead of 73.  Had to turn off autoseq to finish the QSO.


This is another example of why we need to relax the sequencing with the 
patch I provided before.


Unfortunately, I can't make sense of your message.  Please explain 
exactly what sequence of messages took place, and what is the "patch you 
provided before".  When?  Against what source code?


-- Joe, K1JT


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

Re: [wsjt-devel] Candidate release WSJT-X 2.0.0-rc3

[Joe Taylor]

Hi Glen,

On 10/17/2018 1:02 PM, Glen Brown wrote:

Joe and the Team,
It might be helpful if you clarify for everyone that the Ducie 
expedition expects everyone to use 1.9.1.  This is even more important 
now that rc3 forces 77 bit encoding for Expedition mode.


73,
Glen W6GJB


From the "Quick-Start Guide to WSJT-X 2.0", posted here
http://physics.princeton.edu/pulsar/k1jt/Quick_Start_WSJT-X_2.0.pdf

At the bottom of page 2:

"We recommend that any serious use of DXpedition mode should use
WSJT-X v1.9.1 until December 10, 2018, and WSJT-X 2.0 thereafter."

This applies equally to both Fox and Hound.

-- 73, Joe, K1JT


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

[wsjt-devel] Mock "FT8 Roundup" Contest

[Joe Taylor]

A one-hour "practice contest" will be held next week using the FT8 mode 
and the ARRL RTTY Roundup rules.


Thursday, 25 October 0200-0300 UTC (Wednesday evening, NA time)

Dial frequency 7.078 (and higher, in 2 kHz increments, if too much QRM). 
 Everyone works everyone.


To participate you must use WSJT-X 2.0.0-rc3.  Installation packages for 
Windows, Linux, and macOS can be found near the bottom of this web page:

https://physics.princeton.edu/pulsar/k1jt/wsjtx.html
Note that this Release Candidate 3 ("RC3") is a beta-test version.  A 
full release of WSJT-X 2.0 is targeted for release on December 10, 2018.


A revised Quick-Start Guide to WSJT-X 2.0 for RC3 is posted here:
https://physics.princeton.edu/pulsar/k1jt/Quick_Start_WSJT-X_2.0.pdf
Be sure to read this entire document before using WSJT-X 2.0.  Changes 
in RC3 relative to RC2 are described starting on page 7.


IMPORTANT FOR THE MOCK CONTEST:

1. On the *Settings | Advanced* tab, be sure to check the boxes *Always 
generate 77-bit messages*, *Decode only 77-bit messages*, and *ARRL RTTY 
Roundup*.  In the field labeled "Exch" enter the 2- or 3-letter 
abbreviation for your state or province (US/Canadian stations) or DX if 
you are not in the US or Canada.


2. Be sure that 7.078 appears in your drop-down frequency list for FT8 
mode.  You might need to do a *Reset* on the *Settings | Frequencies* 
tab.  If the sub-band starting at 7.078 becomes over-crowded we suggest 
moving to higher dial frequencies in 2 kHz increments: 7.080, 7.082, 
etc.  Type Ctrl+Shift+F12 to move up by 2 kHz, Ctrl+Shift+F11 to move 
down by 2 kHz.


3. Do not use a compound or nonstandard callsign in this event.


Note that planning is underway for one or more dedicated FT8 contests to 
be held in the next few months. The ARRL RTTY Roundup, January 5-6 2018, 
encourages FT8 as well as RTTY participation.


Post results and comments here so we can all learn from an actual FT8 
contest-like experience.


If you are not already subscribed, you may wish to join the email list 
wsjt-devel:

https://sourceforge.net/p/wsjt/mailman/?source=navbar
That list is the best way to communicate directly with the WSJT 
Development Group.


-- 73, Joe, K1JT


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

[wsjt-devel] Candidate release WSJT-X 2.0.0-rc3

[Joe Taylor]

A third candidate release ("RC3") of WSJT-X 2.0 is now available for 
download and use by beta testers.


Changes in RC3 relative to RC2 include the following:

1   Improved SNR calculation for FT8
2   Test grid4 (not grid6) for matches in ADIF log
3   Auto-generate 77-bit messages for callsigns with /R or /P
4   Fix auto-sequencing for "CQ ABC ...", "CQ ABCD ...", etc.
5   Fix the "CQ RU RU ..." bug
6   Implement AP decoding for contest messages and for Hound
7   Check Field Day and RTTY Roundup exchanges for validity
8   Implement "Select next caller" and use of the "TU; ..." messages
9   Option to "Auto Log" in contests
10  Real-time display of contest log
11  Contest exchanges sent to the ADIF log and N1MM+
12  Function to export a Cabrillo log, ready for submission
13  Convert DXpedition mode to always use 77-bit messages
14  Fix bug associated with opening file "houndcallers.txt"
15  Remove end-of-line numbers from MSK144 decodes
16  Finish MSK144 encoding/decoding for Sh msgs and nonstandard calls
17  Halt Tx before resetting power after Tune
18  Auto update of LoTW info, and faster program startup

The "Quick-Start Guide to WSJT-X 2.0" has been updated and extended.  If 
you plan to use the beta-test release candidate RC3, be sure to read 
this entire guide first:

http://physics.princeton.edu/pulsar/k1jt/Quick_Start_WSJT-X_2.0.pdf

Changes in RC3 relative to RC2 are described in a new section starting 
on page 7.


Download links for RC3 on Windows, Linux, and macOS can be found on the 
WSJT-X web site

http://physics.princeton.edu/pulsar/k1jt/wsjtx.html

A one-hour "FT8 mock contest" will be held next week: Thursday, October 
25, 0200-0300 UTC (that's Wednesday evening, NA time).  Watch for a 
separate announcement with more details.


We look forward to your feedback on WSJT-X 2.0-rc3.  Please help us by 
testing all new features, including especially the contest-oriented 
messages and the new MSK144 protocol. Reports should be sent to the 
wsjt-devel email list, wsjt-devel@lists.sourceforge.net. You must 
subscribe to the list in order to post there.


-- 73, Joe, K1JT (for the WSJT Development Group)


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

Re: [wsjt-devel] Rc2 ft8 72 bit vs 77 bit?

[Joe Taylor]

On 10/8/2018 6:15 PM, Bill Pence KI4US wrote:

Ok. I tried some tests.
I do decode both 77 bit and old messages
I had a buddy send an old cq and 77 bit cq.
I decided both.

But  I did not select the always generate 77 bit messages so I expected 
to answer with the format I decoded.  That was not the case ???


No.  As described in the "Quick-Start Guide to WSJT-X 2.0" (page 1):

"The new v2.0 message formats are recognized automatically and 
transmitted using the new protocol. You can check *Always generate 
77-bit messages* to force all transmissions to use the new protocol..."


If you have not ticked the *Always generate 77-bit messages* box, and 
your message can be transmitted using the v1.x protocol, that's how it 
will be done.


-- 73, Joe, K1JT


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

Re: [wsjt-devel] TX 2.0 Not Resetting Properly

[Joe Taylor]

John --

On 10/4/2018 5:23 PM, John Kludt K4SQC wrote:
In  to  and checked NA VHF Contest - on main page TX 
2.0 NA VHF verbage appeared in Red Bar.  Generated messages as 
expected.  TX1 grayed out.  Went back to  checked ARRL FD and 
filled in exchange.  Back on main page Red Bar TX 2.0 now reads ARRL 
FD.  Generated appropriate messages.  TX 1 grayed out.  Went back to 
 and checked .  Red bar persists reading TX 2.0 with no 
appended text.  TX1 still grayed out and unable to access TX1.


I was only able to clear by shutting down and restarting WSJT-X 2.0.  
With no contest selected system TX1 no longer grayed out however Red Bar 
TX2.0  seems to now be permanently displayed on main page.


Win 7.0 WSJT-X 2.0-rc2


In normal mode (not using contest messages) you have full control over 
whether Tx1 is grayed out, or not.  Double-click on Tx1 (Next or Now) to 
toggle between the two possibilities.


-- Joe, K1JT



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

Re: [wsjt-devel] Free text problem

[Joe Taylor]

Keijo --

There is no reason to jump between Tab 1 and Tab 2.  Free text messages 
can be sent perfectly well from Tab 1.  You can enter a free-text 
message in any Tx# box, and transmit it from there.  More conveniently, 
you can enter and save Free Text messages in Tx5.


I believe you have several callsigns.  Using a nonstandard callsign like 
OG55W for "everyday" purposes necessarily limits your ability to use the 
features provided by the various modes in WSJT-X, including FT8.


-- 73, Joe, K1JT

On 10/1/2018 11:02 AM, OG55W wrote:

Yes I am jumping between 1 and 2 as I do not understand any other way.
I start CQ with label 1 Tx6.
As the TX6 is not given the locator I go also to free text to give as 
stations are asking it.


But I think that the problem was in Windpws update..

73 Keijo OG55W

-Alkuperäinen viesti----- From: Joe Taylor
Sent: Monday, October 1, 2018 5:50 PM
To: WSJT software development
Subject: Re: [wsjt-devel] Free text problem

Keijo,

On 10/1/2018 10:31 AM, OG55W wrote:

1. Start WSJT-X 2.0-rc2 with "MyCall" = OG55W
2. CQ OG55W in Tx6
3. Select a free text message in Tx6  "RC2 PSE"
4. After transmission finishes, select General message
5.QSY to label 1 Std Messages
6. Try to CQ again, but do not get Enable TX red.
7. Close the WSJT-X
8. Open WSJT-X and everything is working again.


I assume your step 2 means that you allow the program to transmit a CQ
message using message field Tx6 on Tab 1.

Your step 3 says "select a free text message in Tx6".  The only TX#
message field that allows "selecting" a pre-stored message is Tx 5.  So
I don't know what you did here.  Did you menually enter "RC2 PSE" in
Tx6?  Or select a pre-stored "RC2 PSE" inn Tx5?  Or something else?

Your step 4 says "select General message".  This appears to be a
reference to the "Gen msg" entry field of Tab 2?  Are you really
changing between Tab 1 and Tab 2?  If so, why?  Users are assumed to use
either Tab 1 or Tab 2, but not both in the same QSO.

When you write "QSY to label 1 Std Messages", do you mean that you
selected Tab 1 and then clicked "Generate Std Msgs" ??

I am baffled.  I can't make the program do what you say it does for you.

-- Joe, K1JT


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


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



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

Re: [wsjt-devel] Free text problem

[Joe Taylor]

Keijo,

On 10/1/2018 10:31 AM, OG55W wrote:

1. Start WSJT-X 2.0-rc2 with "MyCall" = OG55W
2. CQ OG55W in Tx6
3. Select a free text message in Tx6  "RC2 PSE"
4. After transmission finishes, select General message
5.QSY to label 1 Std Messages
6. Try to CQ again, but do not get Enable TX red.
7. Close the WSJT-X
8. Open WSJT-X and everything is working again.


I assume your step 2 means that you allow the program to transmit a CQ 
message using message field Tx6 on Tab 1.


Your step 3 says "select a free text message in Tx6".  The only TX# 
message field that allows "selecting" a pre-stored message is Tx 5.  So 
I don't know what you did here.  Did you menually enter "RC2 PSE" in 
Tx6?  Or select a pre-stored "RC2 PSE" inn Tx5?  Or something else?


Your step 4 says "select General message".  This appears to be a 
reference to the "Gen msg" entry field of Tab 2?  Are you really 
changing between Tab 1 and Tab 2?  If so, why?  Users are assumed to use 
either Tab 1 or Tab 2, but not both in the same QSO.


When you write "QSY to label 1 Std Messages", do you mean that you 
selected Tab 1 and then clicked "Generate Std Msgs" ??


I am baffled.  I can't make the program do what you say it does for you.

-- Joe, K1JT


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

Re: [wsjt-devel] Free text problem

[Joe Taylor]

Keijo --

On 10/1/2018 9:30 AM, OG55W wrote:

- Program version WSJT-X v2.0.0-rc2 cc148d
- Windows 10, latest update yesterday
- I need to tell to other stations with free text that they can not get 
the QSO with me with RC1. RC2 is working OK
- When I come back from free text to standard text ENABLE TX will not 
turn to red, but when I close the program and open it again, everything 
is OK again.
Free text I need also for longer call signs QSOs like OE100 and 
OE1000-calls..


As I Wrote before, I cannot reproduce the problem you describe.

The attached screen shot shows my attempt to follow your minimal 
instructions.


I transmitted the free text message "RC2 NOT RC1", followed by two 
standard, structured, FT8 messages that include your nonstandard 
callsign OG55W.  The "Enable Tx" button stays active (red), the entire 
time.  It can be toggled On/Off, as usual, at any time.


So, once again: please provide a sequence of steps that will reproduce 
the undesired behavior you describe?  For example:


1. Start WSJT-X 2.0-rc2 with "MyCall" = OG55W
2. Select a free text message in Tx5, and select Tx5 under "Next".
3. Toggle "Enable Tx" to On (red).
4. After transmission finishes, select Tx1 under "Next" (or perhaps
   something else ???)
5. ... etc.

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

Re: [wsjt-devel] FT8 Mock Contest Findings

[Joe Taylor]

Dave --

Please use the original (or at least an informative) subject line rather 
than allowing your email client to insert something like

"Re: [wsjt-devel] wsjt-devel Digest, Vol 55, Issue 106".

As best I can infer from information you've provided, you must not have 
had a valid entry in the "Exch" field.  Presumably this should have been 
"ON" (for Ontario) -- nothing more, nothing less.  Are you sure this was 
true?  Have you repeated the test to be extra sure?


-- 73, Joe, K1JT

On 9/27/2018 4:26 PM, Jeff Wilson VE3CV wrote:

Hi Dave and Joe

Yes, I had the truncated message thing going on and could not figure it 
out.  I spent the afternoon before the constest using V2.0 in the normal 
FT8 mode and was busy DXing on 40 and 20 with no problem.  During the 
contests I made 1 QSO  (K5CM) with difficulty and then nothing as I 
noticed my messages were severely truncated.


All was set up with correct checks on the Advanced Tab and the Red 
Notice on the main window.  But I still could only transmit 13 
characters.  If a 6 character call, they only got  KX1XXX_VE3CV_  (=13) 
   when I called them...no report at all.


If a 5 letter call they got KX1XX_ VE3CV_ 5_   (=13)

I tried all permutations of checks on the Advanced Tab. With the 
Exchange left blank I was able to send 23 or 25 characters when I used 
the Free Message entry window.  Eg.,  KX1XXX_VE3CV_539_ONS_0001 ...or 
something like that.


Loved the program and the contest,  and glad (sad) to see I wasn't the 
only only suffering the truncated message error.


Hope this helps

73

Jeff VE3CV

On 27 Sep 2018 10:06, Dave wrote:

First off, Joe and team thank you for this great software.  Also to 
Don for confirming what I saw here.  I can only assume that I have 
something set incorrectly but it's actually rather simple to go from 
normal mode to RTTY RU mode.



From: "Don Hill AA5AU" mailto:aa...@bellsouth.net>>
To: "'WSJT software development'"
mailto:wsjt-devel@lists.sourceforge.net>>

3. I had two stations (W3DLQ and VE3CV) call me where it appears their
message wasn't fully sent (see screenshot below for W3DLQ
example). W3DLQ
answered me with "AA5AU W3DLQ 5" and VE3CV did the same thing
"AA5AU VE3CV
5". I'm guessing they didn't have something set up correctly on
their end?


I'm using V2.0 rc-2.  I have used this version to make contacts with 
no contest selected so I know it is working properly. I cloned my 
normal operating configuration and renamed the clone to RTTY RU.  When 
setting up for the ARRL RTTY Roundup I have that ticked and have 
entered MDC in the Exch: box.  I have "FT8 message types" *Always 
generate* and *Decode only 77-bit messages* ticked.  Everything else 
is the same except I cleared all default frequencies and added only 
7.078 and 14.078.


As soon as I click on OK the messages are converted to RTTY RU  mode.  
e.g.  AA5AU W3DLQ 539 MDC and Tx2.0 RTTY is highlighted in a red box 
on the main screen.  This also works when I enter a callsign in the DX 
Call box and click "Generate Std Msgs"  When I clicked on a CQ message 
the messages are changed to that caller.


When I clicked on a CQ in the Band Activity window, the messages 
changed, and TX started.  However, in the Rx Frequency window my 
messages are truncated to *AA5AU W3DLQ 5.*  This also shows in the 
last message sent TX box.


This occurs if either I send a CQ and the program answers and sends 
the response message, I click on a CQ message or I click on a message 
sent to me.  In the exchange with AA5AU I clicked on his call to me.


I also clicked on a call *CQ RU K9OM EN65.*  My response TX to him 
was*K9OM W3DLQ 55.*

**
In summary, any TX I make is truncated.  I think I'm set up correctly 
or there is something strange in my set up which is Windows 10 with a 
FLEX-6500.  I was running two slices last evening, one for 20M and the 
other for 40M.  Nothing on 20M but many on 40M were decoded.


Looked like fun but after I saw what was happening when I transmitted 
I stopped participating.  I didn't want to get flamed for not reading 
the FTM, not following Joe's directions for setting up the program or 
other smarta$$ comments.  Comments like Don's are appreciated.  He 
made no accusations and merely stated the facts.

Dave W3DLQ






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




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

Re: [wsjt-devel] Special callsigns triggering endless loop

[Joe Taylor]

Hi Andy,

If you have read and understood the documentation distributed with 
WSJT-X 2.0-rc1 and -rc2, you must understand that there is no room in a 
77-bit message for two nonstandard calls and a signal report, even if 
one of the nonstandard calls is encoded as a hash code.


-- Joe, K1JT

On 9/27/2018 3:41 PM, m_andi wrote:

Hello everybody,

I was trying to contact the special callsign OG55W with my callsign 
OE100DMB. The qso ended up in an endless loop as nobody transmitted a 
report. See screenshot attached.


Is it a bug or is it just not intended to be used for contacts between 
two stations with special callsigns?


I was using rc2 in 77 Bit mode under win10.

73s de Andy OE3DMB from Austria




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




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

[wsjt-devel] FT8 Mock Contest Findings

[Joe Taylor]

Thanks to all who reported on experiences during the FT8 mock contest 
last evening.  Reports are still coming in, but this seems like a good 
time to summarize some basic conclusions.


Beta-testing of software is done to help identify problems including 
programming errors, missing or broken features, and undesired behavior 
that might be caused by unexpected user actions.  Last evening's mock 
contest was an effort to exercise the new "RTTY Roundup" message format 
in WSJT-X 2.0, under conditions that might be similar to those in a real 
RTTY-style contest.


Documentation provided with WSJT-X 2.0-rc1 and -rc2 made it clear that 
many features important for contest operating such as dupe checking, 
stacked queuing of calls to be worked, display of QSO rate, multipliers, 
cumulative score, etc., have not yet been implemented. Moreover, 
complete logging when using contest-like messages is limited to a file 
"cabrillo.txt".  In the -rc1 and -rc2 releases, neither the ADIF log nor 
logging information sent to N1MM+, or through JTAlert to DXKeeper, etc., 
would include signal reports, grid locators, or the like.


With these preliminaries out of the way, here's a brief  summary list of 
findings:


1. Operators who read and followed the instructions had few problems 
when working others who had read and followed the instructions.


2. Valid QSOs were properly logged to file cabrillo.log.

3. Manual editing of the CQ ("Tx6") message could produce an improperly 
formatted message starting with "CQ RU RU ..." rather than "CQ RU ...". 
The program generates the correct message automatically. It was not 
intended that anyone should edit the Tx6 message, but the improper 
result is a program defect.  This bug has been fixed, and it will not 
appear in the -rc3 release.


4. Of course the default color-highlighting scheme for decoded messages 
is not useful.  In a contest we care only about dupes, and maybe 
multipliers.  Suitable color-highlighting for contesting has not yet 
been implemented.


5. Double-clicking on a decoded message could result in setting the Tx 
message to Tx2 rather than the correct Tx3.  We will look carefully at 
the cause, and correct it as necessary.


6. Most of us received messages decoded as "<...>", or perhaps something 
like "<...> W/".  These were caused by another operator having 
selected RTTY Roundup messages without also setting a valid exchange 
(state, province, or "DX").  We were aware that a suitable validator for 
"Exch" entries is needed, but we have not yet found time to implement it.


7. Transmitting RTTY Roundup messages with a bad or missing "Exch" entry 
also puts faulty information in the QSO partner's cabrillo.log, as in 
this example:


 QSO: 14078 RY 2018-09-27 0257 XE1MEX  569 0001  VK7XX  VK7XX RR73


8. At present list of valid state/province/DX abbreviations is as follows:

   "AL ","AK ","AZ ","AR ","CA ","CO ","CT ","DE ","FL ","GA ",
   "HI ","ID ","IL ","IN ","IA ","KS ","KY ","LA ","ME ","MD ",
   "MA ","MI ","MN ","MS ","MO ","MT ","NE ","NV ","NH ","NJ ",
   "NM ","NY ","NC ","ND ","OH ","OK ","OR ","PA ","RI ","SC ",
   "SD ","TN ","TX ","UT ","VT ","VA ","WA ","WV ","WI ","WY ",
   "NB ","NS ","QC ","ON ","MB ","SK ","AB ","BC ","NWT","NF ",
   "LB ","NU ","VT ","PEI","DC "

Thus, MD, DE, and DC are allowed, but MDC (which at least one operator 
used) is not.


Rule 5.2 of rules for the ARRL RTTY Roundup reads as follows:

"5.2. Multipliers: Each US state (except KH6 and KL7) plus the District 
of Columbia (DC), Canadian provinces/territories: NB (VE1, 9), NS (VE1), 
QC (VE2), ON (VE3), MB (VE4), SK (VE5), AB (VE6), BC (VE7), NWT (VE8), 
NF (VO1), LB (VO2), NU (VYØ), YT (VY1), PEI (VY2) and each DXCC country. 
KH6 and KL7 count only as separate DXCC entities."


9. Upon program restart, at least one user had trouble resetting the QSO 
serial number to the proper number.


10. Users were warned not to use a compound or nonstandard callsign 
during the mock contest.  At least one user tried, nevertheless, with 
predictably bad results.



I operated for a little over an hour during the test.  I made 31 QSOs, 
all correctly recorded in cabrillo.log.  I did not use JTAlert, but I 
opted to send logging information to N1MM+.  As expected, the N1MM+ log 
shows all QSOs but does not have correct signal reports or exchange 
information.


From notes I kept during the test, here are a few additional ideas that 
occurred to me:


1. In  contest it might be best not to require clicking "OK" to log each 
QSO.  Instead, log the contact automatically when we receive or transmit 
RR73 or 73.


2. We need to implement a simple way for a "Run" station to queue up the 
next station to be called, during a QSO already in progress.  This could 
double the maximum possible QSO rate.


3. Activity during a real contest will not fit into a single 3 kHz 
sub-band.  We need to seek the best possible way to organize use of a 
wider band, 

Re: [wsjt-devel] OE100KFV non-standard call

[Joe Taylor]

Frank --

The signals decoded for my screen shot are artificial signals that I 
generated for the purpose.  I made up the call OE1KFV.  I thought we 
were discussing color highlighting.


-- Joe, K1JT

On 9/27/2018 2:52 AM, oe9...@ft8.at wrote:

Hello Joe,

just for info:

OE1KFV call is not issued in Austria!

It's either OE9KFV or OE100KFV.


73, Frank
OE9KFV
OE100KFV


-Ursprüngliche Nachricht-
Von: Joe Taylor 
Gesendet: Mittwoch, 26. September 2018 22:30
An: WSJT software development 
Betreff: Re: [wsjt-devel] Candidate release WSJT-X 2.0.0-rc2

Hi Uve,

I cannot reproduce the problem you describe.

See the attached screen shot.  OE1KFV is in the log, at JN88.  OE1KFV is 
identified as a new call, which is correct.

I don't know what your yellow color means?

-- Joe, K1JT

On 9/26/2018 1:01 PM, DG2YCB, Uwe wrote:

- Fixed a bug that color-highlighted bare CQ messages (no grid
  locator) as "New DXCC".


Joe,

Seems that the bug is still there, at least for nonstandard callsigns.
OE100KFV as well as OE100DMB are right now on 14.078 MHz calling CQ,
and both stations are highlighted as New DXCC:

73 de Uwe, DG2YCB




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




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

Re: [wsjt-devel] Candidate release WSJT-X 2.0.0-rc2

[Joe Taylor]

Hi Uve,

I cannot reproduce the problem you describe.

See the attached screen shot.  OE1KFV is in the log, at JN88.  OE1KFV is 
identified as a new call, which is correct.


I don't know what your yellow color means?

-- Joe, K1JT

On 9/26/2018 1:01 PM, DG2YCB, Uwe wrote:

    - Fixed a bug that color-highlighted bare CQ messages (no grid
  locator) as "New DXCC".


Joe,

Seems that the bug is still there, at least for nonstandard callsigns. 
OE100KFV as well as OE100DMB are right now on 14.078 MHz calling CQ, and 
both stations are highlighted as New DXCC:


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

Re: [wsjt-devel] Bug Report WSJT-X V2.0.0-rc2

[Joe Taylor]

Tnx Alex, it will be fixed in -rc3.

-- 73, Joe, K1JT

On 9/26/2018 3:19 PM, Alex Voytko wrote:

Hi!

See in the attachment..
 
Best regards..


Alex UR5NMZ



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

Re: [wsjt-devel] Tune power patch

[Joe Taylor]

Tnx Mike, it will be in -rc3.

-- Joe, K1JT

On 9/26/2018 2:22 PM, Black Michael via wsjt-devel wrote:

I submitted this before but since it's not in RC2 here it is again.

Need to turn off transmit before we reset power after Tune otherwise can 
get a power spike at the end of Tune.


else{//we'returningoffsorememberourTunepwrsettingandresettoTxpwr

if(m_config.pwrBandTuneMemory()||m_config.pwrBandTxMemory()){

+ stopTx();

m_pwrBandTuneMemory[curBand]=ui->outAttenuation->value();//rememberourTunepwr

m_PwrBandSetOK=false;



de Mike W9MDB




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




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

Re: [wsjt-devel] FT8 on 222 MHz and an aircraft scatter / Doppler shift observation

[Joe Taylor]

Hi Mark,

Thanks for your reply.  The "/R" usage is intended for NA VHF contest 
messages only.  You can't "mix and match" with the special message 
formats.  Thus, you can't use a "/R" callsign in (say) the special RTTY 
Roundup message formats.


See the example QSOs in the "Quick-Start Guide to WSJT-X 2.0".

You might want to hold off just a bit on testing Rover-style QSOs.  In 
the -rc1 and -rc2 releases, messages with "/R" callsigns are transmitted 
and decoded as they should be.  But we haven't yet enabled the 
auto-generation of these messages in the Tx1 - Tx5  entry fields.  This 
facility should be there in -rc3.


-- 73, Joe, K1JT

On 9/26/2018 1:27 PM, Mark Spencer wrote:

Hi Joe.   I am pondering running during the HF test tonight but also saw your message about 
avoiding the use of a "non standard or compound call".   Would running tonight with a 
"/R" call be ok ?  (I'm not 100 percent certain I can be on the air tonight but will try 
hard (:  My home HF station is quite modest but I expect 40M would likely work ok.)

Also to recap a prior message I'd be happy to do some on the air testing on VHF and up 
with anyone who is in range.   I'll be sure to provide feed back re the "/R" 
functionality once I have some data.

Thanks again to the team for accommodating this (and other requests) from the 
myself and others

73
Mark S
VE7AFZ



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