Topics

WSJT-X 2.1.0-rc7

Joe
 

To: Users of WSJT-X -- especially those interested in radio contesting
From: WSJT Development Group

We apologize for the confusion created by release yesterday of WSJT-X 2.1.0-rc6. That program version had a bug that prevented it from running for some users. This bug has been fixed in Release Candidate 7, which is now available for download. We have also corrected a problem seen by some users of Omni-Rig.

The remainder of this message is mostly a repeat of things in yesterday's announcement, with "rc7" replacing "rc6".


As you know, we have been developing a protocol called FT4 for use in radio contesting. A new version of FT4 is now available for testing in WSJT-X 2.1.0-rc7.

PLEASE NOTE THAT FT4 IN RELEASE CANDIDATE 7 IS NOT COMPATIBLE WITH THAT IN RELEASES RC5 and EARLIER.

Therefore: Please stop using WSJT-X 2.1.0-rc5 and WSJT-X 2.1.0-rc6. If you wish to use FT4 after today or to take advantage of other recent program corrections or enhancements, you should use WSJT-X 2.1.0-rc7.

MOCK CONTEST SESSION
--------------------
A special session for testing the contesting features of FT4 is scheduled for six hours from June 4, 1900 UTC through June 5, 0100 UTC: Tuesday afternoon/evening, North American time, starting about 24 hours from now. Get on the air whenever you can during this mock contest session, using dial frequency 7.090 or 14.080 MHz, as appropriate to the time of day. As in previous tests, be sure to check "RTTY Roundup messages" on the Settings | Advanced tab.


Here's a list of changes, improvements, and bug fixes that have been made since WSJT-X 2.1.0-rc5:

IMPORTANT CHANGES TO THE FT4 PROTOCOL *** NOT BACKWARD COMPATIBLE ***
- T/R sequence length increased from 6.0 to 7.5 seconds
- Symbol rate decreased from 23.4375 to 20.8333 baud
- Signal bandwidth decreased from 90 Hz to 80 Hz

OTHER FT4 IMPROVEMENTS
- Allowable time offsets -1.0 < DT < +1.0 s
- Tx4 message with RRR now allowed, except in contest messages
- Audio frequency is now sent to PSK Reporter
- Add a third decoding pass
- Add ordered statistics decoding
- Improved sensitivity: threshold S/N is now -17.5 dB
- Improved S/N calculation
- In FT4 mode, Shift+F11/F12 moves Tx freq by ± 100 Hz

OTHER IMPROVEMENTS
- Improvements to accessibility
- Updates to the User Guide (not yet complete, however)
- New user option: "Calling CQ forces Call 1st"
- N1MM Logger+ now uses the standard WSJT-X UDP messages
- OK/Cancel buttons on Log QSO window maintain fixed positions
- Put EU VHF contest serial numbers into the ADIF SRX and STX fields

BUG FIXES
- Fix generation of Tx5 message when one callsign is nonstandard
- Fix a bug that prevented use on macOS
- Fix a bug that caused mode switch from FT4 to FT8
- Fix a bug that caused FT4 to do WSPR-style band hopping
- Fix a bug that caused a Fortran bounds error

Release candidate WSJT-X 2.1.0-rc7 will be available for beta-testing through July 21, 2019. It will be inoperable during the ARRL June VHF QSO Party (June 8-10) or ARRL Field Day (June 22-23). It will permanently cease to function after July 21, 2019. If all goes according to plan, by that time we will have made a General Availability (GA) release of WSJT-X 2.1.0.

Downloadable installation packages for WSJT-X 2.1.0-rc7 under Windows, Linux, and macOS are available on the WSJT-X web page:

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

-- 73 from Joe, K1JT; Steve, K9AN; and Bill, G4WJS

Dave Hachadorian
 

I am finding that, with "Best S&P" enabled, I am sometimes calling stations who are not calling CQ.

Dave Hachadorian, K6LL
Yuma, AZ

-----Original Message-----
From: Joe
Sent: Monday, June 3, 2019 10:56 AM
To: rttydigital@groups.io
Subject: [RttyDigital] WSJT-X 2.1.0-rc7

To: Users of WSJT-X -- especially those interested in radio contesting
From: WSJT Development Group

We apologize for the confusion created by release yesterday of WSJT-X
2.1.0-rc6. That program version had a bug that prevented it from
running for some users. This bug has been fixed in Release Candidate 7,
which is now available for download. We have also corrected a problem
seen by some users of Omni-Rig.

The remainder of this message is mostly a repeat of things in
yesterday's announcement, with "rc7" replacing "rc6".


As you know, we have been developing a protocol called FT4 for use in
radio contesting. A new version of FT4 is now available for testing in
WSJT-X 2.1.0-rc7.

PLEASE NOTE THAT FT4 IN RELEASE CANDIDATE 7 IS NOT COMPATIBLE WITH THAT
IN RELEASES RC5 and EARLIER.

Therefore: Please stop using WSJT-X 2.1.0-rc5 and WSJT-X 2.1.0-rc6. If
you wish to use FT4 after today or to take advantage of other recent
program corrections or enhancements, you should use WSJT-X 2.1.0-rc7.

MOCK CONTEST SESSION
--------------------
A special session for testing the contesting features of FT4 is
scheduled for six hours from June 4, 1900 UTC through June 5, 0100 UTC:
Tuesday afternoon/evening, North American time, starting about 24 hours
from now. Get on the air whenever you can during this mock contest
session, using dial frequency 7.090 or 14.080 MHz, as appropriate to the
time of day. As in previous tests, be sure to check "RTTY Roundup
messages" on the Settings | Advanced tab.


Here's a list of changes, improvements, and bug fixes that have been
made since WSJT-X 2.1.0-rc5:

IMPORTANT CHANGES TO THE FT4 PROTOCOL *** NOT BACKWARD COMPATIBLE ***
- T/R sequence length increased from 6.0 to 7.5 seconds
- Symbol rate decreased from 23.4375 to 20.8333 baud
- Signal bandwidth decreased from 90 Hz to 80 Hz

OTHER FT4 IMPROVEMENTS
- Allowable time offsets -1.0 < DT < +1.0 s
- Tx4 message with RRR now allowed, except in contest messages
- Audio frequency is now sent to PSK Reporter
- Add a third decoding pass
- Add ordered statistics decoding
- Improved sensitivity: threshold S/N is now -17.5 dB
- Improved S/N calculation
- In FT4 mode, Shift+F11/F12 moves Tx freq by ± 100 Hz

OTHER IMPROVEMENTS
- Improvements to accessibility
- Updates to the User Guide (not yet complete, however)
- New user option: "Calling CQ forces Call 1st"
- N1MM Logger+ now uses the standard WSJT-X UDP messages
- OK/Cancel buttons on Log QSO window maintain fixed positions
- Put EU VHF contest serial numbers into the ADIF SRX and STX fields

BUG FIXES
- Fix generation of Tx5 message when one callsign is nonstandard
- Fix a bug that prevented use on macOS
- Fix a bug that caused mode switch from FT4 to FT8
- Fix a bug that caused FT4 to do WSPR-style band hopping
- Fix a bug that caused a Fortran bounds error

Release candidate WSJT-X 2.1.0-rc7 will be available for beta-testing
through July 21, 2019. It will be inoperable during the ARRL June VHF
QSO Party (June 8-10) or ARRL Field Day (June 22-23). It will
permanently cease to function after July 21, 2019. If all goes
according to plan, by that time we will have made a General Availability
(GA) release of WSJT-X 2.1.0.

Downloadable installation packages for WSJT-X 2.1.0-rc7 under Windows,
Linux, and macOS are available on the WSJT-X web page:

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

-- 73 from Joe, K1JT; Steve, K9AN; and Bill, G4WJS

Hoop K9QJS
 

Same thing happened to me last night.   I got several calls while I was trying to work someone else.  Problem was, I never got their grid acquire.   

Hoop
K9QJS
San Juan Island, WA 



On Jun 3, 2019, at 4:23 PM, Dave Hachadorian <k6ll.dave@...> wrote:

I am finding that, with "Best S&P" enabled, I am sometimes calling stations who are not calling CQ.

Dave Hachadorian, K6LL
Yuma, AZ


Joe
 

Dave --

Thanks for the report. We need to know what you did, and what happened afterward. Can you send an example screen shot?

-- Joe, K1JT

On 6/3/2019 7:23 PM, Dave Hachadorian wrote:
I am finding that, with "Best S&P" enabled, I am sometimes calling stations who are not calling CQ.
Dave Hachadorian, K6LL
Yuma, AZ
-----Original Message----- From: Joe
Sent: Monday, June 3, 2019 10:56 AM
To: rttydigital@groups.io
Subject: [RttyDigital] WSJT-X 2.1.0-rc7
To:   Users of WSJT-X -- especially those interested in radio contesting
From: WSJT Development Group
We apologize for the confusion created by release yesterday of WSJT-X
2.1.0-rc6.  That program version had a bug that prevented it from
running for some users.  This bug has been fixed in Release Candidate 7,
which is now available for download.  We have also corrected a problem
seen by some users of Omni-Rig.
The remainder of this message is mostly a repeat of things in
yesterday's announcement, with "rc7" replacing "rc6".
As you know, we have been developing a protocol called FT4 for use in
radio contesting.  A new version of FT4 is now available for testing in
WSJT-X 2.1.0-rc7.
PLEASE NOTE THAT FT4 IN RELEASE CANDIDATE 7 IS NOT COMPATIBLE WITH THAT
IN RELEASES RC5 and EARLIER.
Therefore: Please stop using WSJT-X 2.1.0-rc5 and WSJT-X 2.1.0-rc6.  If
you wish to use FT4 after today or to take advantage of other recent
program corrections or enhancements, you should use WSJT-X 2.1.0-rc7.
MOCK CONTEST SESSION
--------------------
A special session for testing the contesting features of FT4 is
scheduled for six hours from June 4, 1900 UTC through June 5, 0100 UTC:
Tuesday afternoon/evening, North American time, starting about 24 hours
from now.  Get on the air whenever you can during this mock contest
session, using dial frequency 7.090 or 14.080 MHz, as appropriate to the
time of day.  As in previous tests, be sure to check "RTTY Roundup
messages" on the Settings | Advanced tab.
Here's a list of changes, improvements, and bug fixes that have been
made since WSJT-X 2.1.0-rc5:
IMPORTANT CHANGES TO THE FT4 PROTOCOL *** NOT BACKWARD COMPATIBLE ***
 - T/R sequence length increased from 6.0 to 7.5 seconds
 - Symbol rate decreased from 23.4375 to 20.8333 baud
 - Signal bandwidth decreased from 90 Hz to 80 Hz
OTHER FT4 IMPROVEMENTS
 - Allowable time offsets -1.0 < DT < +1.0 s
 - Tx4 message with RRR now allowed, except in contest messages
 - Audio frequency is now sent to PSK Reporter
 - Add a third decoding pass
 - Add ordered statistics decoding
 - Improved sensitivity: threshold S/N is now -17.5 dB
 - Improved S/N calculation
 - In FT4 mode, Shift+F11/F12 moves Tx freq by ± 100 Hz
OTHER IMPROVEMENTS
 - Improvements to accessibility
 - Updates to the User Guide (not yet complete, however)
 - New user option: "Calling CQ forces Call 1st"
 - N1MM Logger+ now uses the standard WSJT-X UDP messages
 - OK/Cancel buttons on Log QSO window maintain fixed positions
 - Put EU VHF contest serial numbers into the ADIF SRX and STX fields
BUG FIXES
 - Fix generation of Tx5 message when one callsign is nonstandard
 - Fix a bug that prevented use on macOS
 - Fix a bug that caused mode switch from FT4 to FT8
 - Fix a bug that caused FT4 to do WSPR-style band hopping
 - Fix a bug that caused a Fortran bounds error
Release candidate WSJT-X 2.1.0-rc7 will be available for beta-testing
through July 21, 2019.  It will be inoperable during the ARRL June VHF
QSO Party (June 8-10) or ARRL Field Day (June 22-23).  It will
permanently cease to function after July 21, 2019.  If all goes
according to plan, by that time we will have made a General Availability
(GA) release of WSJT-X 2.1.0.
Downloadable installation packages for WSJT-X 2.1.0-rc7 under Windows,
Linux, and macOS are available on the WSJT-X web page:
http://physics.princeton.edu/pulsar/k1jt/wsjtx.html
    -- 73 from Joe, K1JT; Steve, K9AN; and Bill, G4WJS

Dave Hachadorian
 

Below is one contiguous unedited section of ALL.TXT, showing where I called, first, AK1P, and near the end, AG5AT.  Neither of them had called CQ, and I remember enabling Best S&P one or two sequences before my transmitter called them.  Relevant lines are marked with an asterisk.  The sequence begins with AK1P trying to contact NP3DM. 
 
Dave Hachadorian, K6LL
Yuma, AZ
 
*190603_230553    14.080 Rx FT4     -4 -0.0 1281 NP3DM AK1P FN42
190603_230553    14.080 Rx FT4     19 -0.0 1996 ZP6ARO W9PA EN60
*190603_230600    14.080 Rx FT4     -4 -0.0 1281 NP3DM AK1P FN42
190603_230600    14.080 Rx FT4     19 -0.0 1996 ZP6ARO W9PA EN60
190603_230600    14.080 Rx FT4    -13 -0.2 1278 CQ NP3DM FK68
190603_230600    14.080 Rx FT4     -8 -0.0 1668 CQ AE1N FN42
190603_230600    14.080 Rx FT4    -10 -0.1 1613 CQ KE1AF FN41
*190603_230608    14.080 Rx FT4     -1  0.0 1281 NP3DM AK1P FN42
190603_230608    14.080 Rx FT4     -8 -0.0 1367 CQ NN6XX CM87
190603_230608    14.080 Rx FT4     12  0.0 1996 ZP6ARO W9PA EN60
190603_230615    14.080 Rx FT4    -17 -0.1 1278 CQ NP3DM FK68
190603_230615    14.080 Rx FT4     -3 -0.0 1668 CQ AE1N FN42
190603_230615    14.080 Rx FT4     -8 -0.0 1613 CQ KE1AF FN41
190603_230623    14.080 Rx FT4     11  0.5 1367 HK4FZ N6AR EL98
190603_230623    14.080 Rx FT4    -10 -0.0 1667 AE1N W2GPK EL88
*190603_230623    14.080 Rx FT4      1 -0.0 1281 NP3DM AK1P FN42
190603_230623    14.080 Rx FT4     -8 -0.0 1367 CQ NN6XX CM87
190603_230630    14.080 Rx FT4     -4 -0.0 1668 CQ AE1N FN42
190603_230630    14.080 Rx FT4     -7 -0.0 1613 CQ KE1AF FN41
190603_230638    14.080 Rx FT4     14  0.5 1367 HK4FZ N6AR R-06
190603_230638    14.080 Rx FT4     -7 -0.0 1668 AE1N W2GPK EL88
*190603_230638    14.080 Rx FT4     -4 -0.0 1281 NP3DM AK1P FN42
190603_230645    14.080 Rx FT4     -7 -0.0  894 W9PA W2JC FN20
190603_230645    14.080 Rx FT4     -5 -0.0 1613 CQ KE1AF FN41
190603_230645    14.080 Rx FT4     -8 -0.0 1669 CQ AE1N FN42
*190603_230653    14.080 Rx FT4      2 -0.0 1281 NP3DM AK1P FN42
190603_230653    14.080 Rx FT4      7  0.5 1366 HK4FZ N6AR 73
190603_230653    14.080 Rx FT4     19 -0.0 1667 AE1N W9PA EN60
190603_230653    14.080 Rx FT4     -9 -0.0 1366 CQ NN6XX CM87
*190603_230700    14.080 Tx FT4      0  0.0 2301 AK1P K6LL DM22                      
190603_230708    14.080 Rx FT4     -2 -0.0  893 HK4FZ W2JC FN20
*190603_230708    14.080 Rx FT4     -3 -0.0 1280 NP3DM AK1P FN42
190603_230708    14.080 Rx FT4     -8 -0.0 1367 CQ NN6XX CM87
190603_230708    14.080 Rx FT4     20 -0.0 1668 AE1N W9PA R+17
190603_230708    14.080 Rx FT4     -7  0.0 1997 ZP6ARO KG5RJR EM13
*190603_230715    14.080 Tx FT4      0  0.0 2301 AK1P K6LL DM22                      
190603_230723    14.080 Rx FT4     -1 -0.1  894 HK4FZ W2JC FN20
190603_230723    14.080 Rx FT4      8  0.5 1367 ZP6ARO N6AR EL98
190603_230723    14.080 Rx FT4     20 -0.0 1667 AE1N W9PA 73
*190603_230723    14.080 Rx FT4     -3  0.0 1804 K6LL AK1P +10
190603_230723    14.080 Rx FT4     -2  0.0 1996 ZP6ARO KG5RJR EM13
*190603_230730    14.080 Tx FT4      0  0.0 2301 AK1P K6LL DM22                      
190603_230738    14.080 Rx FT4      5  0.5 1367 ZP6ARO N6AR R-11
*190603_230738    14.080 Rx FT4      3 -0.0 1805 K6LL AK1P +07
190603_230738    14.080 Rx FT4     -9 -0.0 1367 CQ NN6XX CM87
*190603_230745    14.080 Tx FT4      0  0.0 2301 AK1P K6LL R+03                      
190603_230753    14.080 Rx FT4      4  0.5 1366 ZP6ARO N6AR 73
190603_230753    14.080 Rx FT4     12 -0.0 1668 PA3GQY W9PA RR73
*190603_230753    14.080 Rx FT4      6 -0.0 1804 K6LL AK1P RR73
190603_230753    14.080 Rx FT4      3  0.0 1996 ZP6ARO KG5RJR EM13
*190603_230800    14.080 Tx FT4      0  0.0 2301 AK1P K6LL 73                        
190603_230808    14.080 Rx FT4    -10 -0.0 1668 CQ AE1N FN42
190603_230808    14.080 Rx FT4     -2  0.0 1997 ZP6ARO KG5RJR EM13
*190603_230815    14.080 Rx FT4     -3 -0.0 1668 AE1N AG5AT EM63
*190603_230815    14.080 Tx FT4      0  0.0 2301 AG5AT K6LL DM22                     
*190603_230830    14.080 Rx FT4     -3 -0.0 1668 AE1N AG5AT EM63
190603_230830    14.080 Rx FT4    -10 -0.0 1197 CQ KE1AF FN41
*190603_230830    14.080 Rx FT4     -1 -0.0 1668 AE1N AG5AT EM63
*190603_230830    14.080 Tx FT4      0  0.0 2301 AG5AT K6LL DM22                     
190603_230845    14.080 Rx FT4    -12 -0.0 1196 CQ KE1AF FN41
*190603_230845    14.080 Rx FT4     -5 -0.0 1668 K6LL AG5AT -05
*190603_230845    14.080 Tx FT4      0  0.0 2301 AG5AT K6LL R-05                     
190603_230900    14.080 Rx FT4    -13 -0.2 1594 N6AR NP3DM RR73
*190603_230900    14.080 Rx FT4     -6 -0.0 1801 K6LL AG5AT RR73
*190603_230900    14.080 Tx FT4      0  0.0 2301 AG5AT K6LL 73  
 
 
 

-----Original Message-----
From: Joe
Sent: Tuesday, June 4, 2019 7:44 AM
To: rttydigital@groups.io
Subject: Re: [RttyDigital] WSJT-X 2.1.0-rc7
 
Dave --
 
Thanks for the report.  We need to know what you did, and what happened
afterward.  Can you send an example screen shot?
 
-- Joe, K1JT
 
On 6/3/2019 7:23 PM, Dave Hachadorian wrote:
> I am finding that, with "Best S&P" enabled, I am sometimes calling
> stations who are not calling CQ.
>
> Dave Hachadorian, K6LL
> Yuma, AZ
>
>
>
> -----Original Message----- From: Joe
> Sent: Monday, June 3, 2019 10:56 AM
> To: rttydigital@groups.io
> Subject: [RttyDigital] WSJT-X 2.1.0-rc7
>
> To:   Users of WSJT-X -- especially those interested in radio contesting
> From: WSJT Development Group
>
> We apologize for the confusion created by release yesterday of WSJT-X
> 2.1.0-rc6.  That program version had a bug that prevented it from
> running for some users.  This bug has been fixed in Release Candidate 7,
> which is now available for download.  We have also corrected a problem
> seen by some users of Omni-Rig.
>
> The remainder of this message is mostly a repeat of things in
> yesterday's announcement, with "rc7" replacing "rc6".
>
>
> As you know, we have been developing a protocol called FT4 for use in
> radio contesting.  A new version of FT4 is now available for testing in
> WSJT-X 2.1.0-rc7.
>
> PLEASE NOTE THAT FT4 IN RELEASE CANDIDATE 7 IS NOT COMPATIBLE WITH THAT
> IN RELEASES RC5 and EARLIER.
>
> Therefore: Please stop using WSJT-X 2.1.0-rc5 and WSJT-X 2.1.0-rc6.  If
> you wish to use FT4 after today or to take advantage of other recent
> program corrections or enhancements, you should use WSJT-X 2.1.0-rc7.
>
> MOCK CONTEST SESSION
> --------------------
> A special session for testing the contesting features of FT4 is
> scheduled for six hours from June 4, 1900 UTC through June 5, 0100 UTC:
> Tuesday afternoon/evening, North American time, starting about 24 hours
> from now.  Get on the air whenever you can during this mock contest
> session, using dial frequency 7.090 or 14.080 MHz, as appropriate to the
> time of day.  As in previous tests, be sure to check "RTTY Roundup
> messages" on the Settings | Advanced tab.
>
>
> Here's a list of changes, improvements, and bug fixes that have been
> made since WSJT-X 2.1.0-rc5:
>
> IMPORTANT CHANGES TO THE FT4 PROTOCOL *** NOT BACKWARD COMPATIBLE ***
>   - T/R sequence length increased from 6.0 to 7.5 seconds
>   - Symbol rate decreased from 23.4375 to 20.8333 baud
>   - Signal bandwidth decreased from 90 Hz to 80 Hz
>
> OTHER FT4 IMPROVEMENTS
>   - Allowable time offsets -1.0 < DT < +1.0 s
>   - Tx4 message with RRR now allowed, except in contest messages
>   - Audio frequency is now sent to PSK Reporter
>   - Add a third decoding pass
>   - Add ordered statistics decoding
>   - Improved sensitivity: threshold S/N is now -17.5 dB
>   - Improved S/N calculation
>   - In FT4 mode, Shift+F11/F12 moves Tx freq by ± 100 Hz
>
> OTHER IMPROVEMENTS
>   - Improvements to accessibility
>   - Updates to the User Guide (not yet complete, however)
>   - New user option: "Calling CQ forces Call 1st"
>   - N1MM Logger+ now uses the standard WSJT-X UDP messages
>   - OK/Cancel buttons on Log QSO window maintain fixed positions
>   - Put EU VHF contest serial numbers into the ADIF SRX and STX fields
>
> BUG FIXES
>   - Fix generation of Tx5 message when one callsign is nonstandard
>   - Fix a bug that prevented use on macOS
>   - Fix a bug that caused mode switch from FT4 to FT8
>   - Fix a bug that caused FT4 to do WSPR-style band hopping
>   - Fix a bug that caused a Fortran bounds error
>
> Release candidate WSJT-X 2.1.0-rc7 will be available for beta-testing
> through July 21, 2019.  It will be inoperable during the ARRL June VHF
> QSO Party (June 8-10) or ARRL Field Day (June 22-23).  It will
> permanently cease to function after July 21, 2019.  If all goes
> according to plan, by that time we will have made a General Availability
> (GA) release of WSJT-X 2.1.0.
>
> Downloadable installation packages for WSJT-X 2.1.0-rc7 under Windows,
> Linux, and macOS are available on the WSJT-X web page:
>
> http://physics.princeton.edu/pulsar/k1jt/wsjtx.html
>
>      -- 73 from Joe, K1JT; Steve, K9AN; and Bill, G4WJS
>
>
>
>
>
>
 

Fred Castello
 

On 14.080 and cant seem to get “Best S&P” to work?  Are there other settings that have to be checked also (such as Call 1st)?

Thanks,

Fred – KF4FC

 

 

From: Joe
Sent: Tuesday, June 4, 2019 10:44 AM
To: rttydigital@groups.io
Subject: Re: [RttyDigital] WSJT-X 2.1.0-rc7

 

Dave --

 

Thanks for the report.  We need to know what you did, and what happened

afterward.  Can you send an example screen shot?

 

                -- Joe, K1JT

 

On 6/3/2019 7:23 PM, Dave Hachadorian wrote:

> I am finding that, with "Best S&P" enabled, I am sometimes calling

> stations who are not calling CQ.

>

> Dave Hachadorian, K6LL

> Yuma, AZ

>

>

>

> -----Original Message----- From: Joe

> Sent: Monday, June 3, 2019 10:56 AM

> To: rttydigital@groups.io

> Subject: [RttyDigital] WSJT-X 2.1.0-rc7

>

> To:   Users of WSJT-X -- especially those interested in radio contesting

> From: WSJT Development Group

>

> We apologize for the confusion created by release yesterday of WSJT-X

> 2.1.0-rc6.  That program version had a bug that prevented it from

> running for some users.  This bug has been fixed in Release Candidate 7,

> which is now available for download.  We have also corrected a problem

> seen by some users of Omni-Rig.

>

> The remainder of this message is mostly a repeat of things in

> yesterday's announcement, with "rc7" replacing "rc6".

>

>

> As you know, we have been developing a protocol called FT4 for use in

> radio contesting.  A new version of FT4 is now available for testing in

> WSJT-X 2.1.0-rc7.

>

> PLEASE NOTE THAT FT4 IN RELEASE CANDIDATE 7 IS NOT COMPATIBLE WITH THAT

> IN RELEASES RC5 and EARLIER.

>

> Therefore: Please stop using WSJT-X 2.1.0-rc5 and WSJT-X 2.1.0-rc6.  If

> you wish to use FT4 after today or to take advantage of other recent

> program corrections or enhancements, you should use WSJT-X 2.1.0-rc7.

>

> MOCK CONTEST SESSION

> --------------------

> A special session for testing the contesting features of FT4 is

> scheduled for six hours from June 4, 1900 UTC through June 5, 0100 UTC:

> Tuesday afternoon/evening, North American time, starting about 24 hours

> from now.  Get on the air whenever you can during this mock contest

> session, using dial frequency 7.090 or 14.080 MHz, as appropriate to the

> time of day.  As in previous tests, be sure to check "RTTY Roundup

> messages" on the Settings | Advanced tab.

>

>

> Here's a list of changes, improvements, and bug fixes that have been

> made since WSJT-X 2.1.0-rc5:

>

> IMPORTANT CHANGES TO THE FT4 PROTOCOL *** NOT BACKWARD COMPATIBLE ***

>   - T/R sequence length increased from 6.0 to 7.5 seconds

>   - Symbol rate decreased from 23.4375 to 20.8333 baud

>   - Signal bandwidth decreased from 90 Hz to 80 Hz

>

> OTHER FT4 IMPROVEMENTS

>   - Allowable time offsets -1.0 < DT < +1.0 s

>   - Tx4 message with RRR now allowed, except in contest messages

>   - Audio frequency is now sent to PSK Reporter

>   - Add a third decoding pass

>   - Add ordered statistics decoding

>   - Improved sensitivity: threshold S/N is now -17.5 dB

>   - Improved S/N calculation

>   - In FT4 mode, Shift+F11/F12 moves Tx freq by ± 100 Hz

>

> OTHER IMPROVEMENTS

>   - Improvements to accessibility

>   - Updates to the User Guide (not yet complete, however)

>   - New user option: "Calling CQ forces Call 1st"

>   - N1MM Logger+ now uses the standard WSJT-X UDP messages

>   - OK/Cancel buttons on Log QSO window maintain fixed positions

>   - Put EU VHF contest serial numbers into the ADIF SRX and STX fields

>

> BUG FIXES

>   - Fix generation of Tx5 message when one callsign is nonstandard

>   - Fix a bug that prevented use on macOS

>   - Fix a bug that caused mode switch from FT4 to FT8

>   - Fix a bug that caused FT4 to do WSPR-style band hopping

>   - Fix a bug that caused a Fortran bounds error

>

> Release candidate WSJT-X 2.1.0-rc7 will be available for beta-testing

> through July 21, 2019.  It will be inoperable during the ARRL June VHF

> QSO Party (June 8-10) or ARRL Field Day (June 22-23).  It will

> permanently cease to function after July 21, 2019.  If all goes

> according to plan, by that time we will have made a General Availability

> (GA) release of WSJT-X 2.1.0.

>

> Downloadable installation packages for WSJT-X 2.1.0-rc7 under Windows,

> Linux, and macOS are available on the WSJT-X web page:

>

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

>

>      -- 73 from Joe, K1JT; Steve, K9AN; and Bill, G4WJS

>

>

>

>

>

>

 

 

 

---

This email has been checked for viruses by AVG.

https://www.avg.com

 

 

Joe
 

“Best S&P” must be activated during a Rx sequence.

-- Joe, K1JT

On 6/4/2019 15:40, Fred Castello wrote:
On 14.080 and cant seem to get “Best S&P” to work?  Are there other settings that have to be checked also (such as Call 1^st )?
Thanks,
Fred – KF4FC
*From: *Joe <mailto:@K1JT>
*Sent: *Tuesday, June 4, 2019 10:44 AM
*To: *rttydigital@groups.io <mailto:rttydigital@groups.io>
*Subject: *Re: [RttyDigital] WSJT-X 2.1.0-rc7
Dave --
Thanks for the report.  We need to know what you did, and what happened
afterward.  Can you send an example screen shot?
                -- Joe, K1JT
On 6/3/2019 7:23 PM, Dave Hachadorian wrote:

> I am finding that, with "Best S&P" enabled, I am sometimes calling

> stations who are not calling CQ.

>

> Dave Hachadorian, K6LL

> Yuma, AZ

>

>

>

> -----Original Message----- From: Joe

> Sent: Monday, June 3, 2019 10:56 AM

> To: rttydigital@groups.io

> Subject: [RttyDigital] WSJT-X 2.1.0-rc7

>

> To:   Users of WSJT-X -- especially those interested in radio contesting

> From: WSJT Development Group

>

> We apologize for the confusion created by release yesterday of WSJT-X

> 2.1.0-rc6.  That program version had a bug that prevented it from

> running for some users.  This bug has been fixed in Release Candidate 7,

> which is now available for download.  We have also corrected a problem

> seen by some users of Omni-Rig.

>

> The remainder of this message is mostly a repeat of things in

> yesterday's announcement, with "rc7" replacing "rc6".

>

>

> As you know, we have been developing a protocol called FT4 for use in

> radio contesting.  A new version of FT4 is now available for testing in

> WSJT-X 2.1.0-rc7.

>

> PLEASE NOTE THAT FT4 IN RELEASE CANDIDATE 7 IS NOT COMPATIBLE WITH THAT

> IN RELEASES RC5 and EARLIER.

>

> Therefore: Please stop using WSJT-X 2.1.0-rc5 and WSJT-X 2.1.0-rc6.  If

> you wish to use FT4 after today or to take advantage of other recent

> program corrections or enhancements, you should use WSJT-X 2.1.0-rc7.

>

> MOCK CONTEST SESSION

> --------------------

> A special session for testing the contesting features of FT4 is

> scheduled for six hours from June 4, 1900 UTC through June 5, 0100 UTC:

> Tuesday afternoon/evening, North American time, starting about 24 hours

> from now.  Get on the air whenever you can during this mock contest

> session, using dial frequency 7.090 or 14.080 MHz, as appropriate to the

> time of day.  As in previous tests, be sure to check "RTTY Roundup

> messages" on the Settings | Advanced tab.

>

>

> Here's a list of changes, improvements, and bug fixes that have been

> made since WSJT-X 2.1.0-rc5:

>

> IMPORTANT CHANGES TO THE FT4 PROTOCOL *** NOT BACKWARD COMPATIBLE ***

>   - T/R sequence length increased from 6.0 to 7.5 seconds

>   - Symbol rate decreased from 23.4375 to 20.8333 baud

>   - Signal bandwidth decreased from 90 Hz to 80 Hz

>

> OTHER FT4 IMPROVEMENTS

>   - Allowable time offsets -1.0 < DT < +1.0 s

>   - Tx4 message with RRR now allowed, except in contest messages

>   - Audio frequency is now sent to PSK Reporter

>   - Add a third decoding pass

>   - Add ordered statistics decoding

>   - Improved sensitivity: threshold S/N is now -17.5 dB

>   - Improved S/N calculation

>   - In FT4 mode, Shift+F11/F12 moves Tx freq by ± 100 Hz

>

> OTHER IMPROVEMENTS

>   - Improvements to accessibility

>   - Updates to the User Guide (not yet complete, however)

>   - New user option: "Calling CQ forces Call 1st"

>   - N1MM Logger+ now uses the standard WSJT-X UDP messages

>   - OK/Cancel buttons on Log QSO window maintain fixed positions

>   - Put EU VHF contest serial numbers into the ADIF SRX and STX fields

>

> BUG FIXES

>   - Fix generation of Tx5 message when one callsign is nonstandard

>   - Fix a bug that prevented use on macOS

>   - Fix a bug that caused mode switch from FT4 to FT8

>   - Fix a bug that caused FT4 to do WSPR-style band hopping

>   - Fix a bug that caused a Fortran bounds error

>

> Release candidate WSJT-X 2.1.0-rc7 will be available for beta-testing

> through July 21, 2019.  It will be inoperable during the ARRL June VHF

> QSO Party (June 8-10) or ARRL Field Day (June 22-23).  It will

> permanently cease to function after July 21, 2019.  If all goes

> according to plan, by that time we will have made a General Availability

> (GA) release of WSJT-X 2.1.0.

>

> Downloadable installation packages for WSJT-X 2.1.0-rc7 under Windows,

> Linux, and macOS are available on the WSJT-X web page:

>

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

>

>      -- 73 from Joe, K1JT; Steve, K9AN; and Bill, G4WJS

>

>

>

>

>

>
---
This email has been checked for viruses by AVG.
https://www.avg.com

Fred Castello
 

I have been Joe, so I must be missing something.  There are a number of green CQ’s after I activate it and I have yet to have it send a transmit during many (20) cycles.

Tnx,

Fred – KF4FC

 

 

From: Joe
Sent: Tuesday, June 4, 2019 3:43 PM
To: rttydigital@groups.io
Subject: Re: [RttyDigital] WSJT-X 2.1.0-rc7

 

“Best S&P” must be activated during a Rx sequence.

 

                -- Joe, K1JT

 

On 6/4/2019 15:40, Fred Castello wrote:

> On 14.080 and cant seem to get “Best S&P” to work?  Are there other

> settings that have to be checked also (such as Call 1^st )?

>

> Thanks,

>

> Fred – KF4FC

>

> *From: *Joe <mailto:joe@...>

> *Sent: *Tuesday, June 4, 2019 10:44 AM

> *To: *rttydigital@groups.io <mailto:rttydigital@groups.io>

> *Subject: *Re: [RttyDigital] WSJT-X 2.1.0-rc7

>

> Dave --

>

> Thanks for the report.  We need to know what you did, and what happened

>

> afterward.  Can you send an example screen shot?

>

>                  -- Joe, K1JT

>

> On 6/3/2019 7:23 PM, Dave Hachadorian wrote:

>

>  > I am finding that, with "Best S&P" enabled, I am sometimes calling

>

>  > stations who are not calling CQ.

>

>  >

>

>  > Dave Hachadorian, K6LL

>

>  > Yuma, AZ

>

>  >

>

>  >

>

>  >

>

>  > -----Original Message----- From: Joe

>

>  > Sent: Monday, June 3, 2019 10:56 AM

>

>  > To: rttydigital@groups.io

>

>  > Subject: [RttyDigital] WSJT-X 2.1.0-rc7

>

>  >

>

>  > To:   Users of WSJT-X -- especially those interested in radio contesting

>

>  > From: WSJT Development Group

>

>  >

>

>  > We apologize for the confusion created by release yesterday of WSJT-X

>

>  > 2.1.0-rc6.  That program version had a bug that prevented it from

>

>  > running for some users.  This bug has been fixed in Release Candidate 7,

>

>  > which is now available for download.  We have also corrected a problem

>

>  > seen by some users of Omni-Rig.

>

>  >

>

>  > The remainder of this message is mostly a repeat of things in

>

>  > yesterday's announcement, with "rc7" replacing "rc6".

>

>  >

>

>  >

>

>  > As you know, we have been developing a protocol called FT4 for use in

>

>  > radio contesting.  A new version of FT4 is now available for testing in

>

>  > WSJT-X 2.1.0-rc7.

>

>  >

>

>  > PLEASE NOTE THAT FT4 IN RELEASE CANDIDATE 7 IS NOT COMPATIBLE WITH THAT

>

>  > IN RELEASES RC5 and EARLIER.

>

>  >

>

>  > Therefore: Please stop using WSJT-X 2.1.0-rc5 and WSJT-X 2.1.0-rc6.  If

>

>  > you wish to use FT4 after today or to take advantage of other recent

>

>  > program corrections or enhancements, you should use WSJT-X 2.1.0-rc7.

>

>  >

>

>  > MOCK CONTEST SESSION

>

>  > --------------------

>

>  > A special session for testing the contesting features of FT4 is

>

>  > scheduled for six hours from June 4, 1900 UTC through June 5, 0100 UTC:

>

>  > Tuesday afternoon/evening, North American time, starting about 24 hours

>

>  > from now.  Get on the air whenever you can during this mock contest

>

>  > session, using dial frequency 7.090 or 14.080 MHz, as appropriate to the

>

>  > time of day.  As in previous tests, be sure to check "RTTY Roundup

>

>  > messages" on the Settings | Advanced tab.

>

>  >

>

>  >

>

>  > Here's a list of changes, improvements, and bug fixes that have been

>

>  > made since WSJT-X 2.1.0-rc5:

>

>  >

>

>  > IMPORTANT CHANGES TO THE FT4 PROTOCOL *** NOT BACKWARD COMPATIBLE ***

>

>  >   - T/R sequence length increased from 6.0 to 7.5 seconds

>

>  >   - Symbol rate decreased from 23.4375 to 20.8333 baud

>

>  >   - Signal bandwidth decreased from 90 Hz to 80 Hz

>

>  >

>

>  > OTHER FT4 IMPROVEMENTS

>

>  >   - Allowable time offsets -1.0 < DT < +1.0 s

>

>  >   - Tx4 message with RRR now allowed, except in contest messages

>

>  >   - Audio frequency is now sent to PSK Reporter

>

>  >   - Add a third decoding pass

>

>  >   - Add ordered statistics decoding

>

>  >   - Improved sensitivity: threshold S/N is now -17.5 dB

>

>  >   - Improved S/N calculation

>

>  >   - In FT4 mode, Shift+F11/F12 moves Tx freq by ± 100 Hz

>

>  >

>

>  > OTHER IMPROVEMENTS

>

>  >   - Improvements to accessibility

>

>  >   - Updates to the User Guide (not yet complete, however)

>

>  >   - New user option: "Calling CQ forces Call 1st"

>

>  >   - N1MM Logger+ now uses the standard WSJT-X UDP messages

>

>  >   - OK/Cancel buttons on Log QSO window maintain fixed positions

>

>  >   - Put EU VHF contest serial numbers into the ADIF SRX and STX fields

>

>  >

>

>  > BUG FIXES

>

>  >   - Fix generation of Tx5 message when one callsign is nonstandard

>

>  >   - Fix a bug that prevented use on macOS

>

>  >   - Fix a bug that caused mode switch from FT4 to FT8

>

>  >   - Fix a bug that caused FT4 to do WSPR-style band hopping

>

>  >   - Fix a bug that caused a Fortran bounds error

>

>  >

>

>  > Release candidate WSJT-X 2.1.0-rc7 will be available for beta-testing

>

>  > through July 21, 2019.  It will be inoperable during the ARRL June VHF

>

>  > QSO Party (June 8-10) or ARRL Field Day (June 22-23).  It will

>

>  > permanently cease to function after July 21, 2019.  If all goes

>

>  > according to plan, by that time we will have made a General Availability

>

>  > (GA) release of WSJT-X 2.1.0.

>

>  >

>

>  > Downloadable installation packages for WSJT-X 2.1.0-rc7 under Windows,

>

>  > Linux, and macOS are available on the WSJT-X web page:

>

>  >

>

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

>

>  >

>

>  >      -- 73 from Joe, K1JT; Steve, K9AN; and Bill, G4WJS

>

>  >

>

>  >

>

>  >

>

>  >

>

>  >

>

>  >

>

> ---

>

> This email has been checked for viruses by AVG.

>

> https://www.avg.com

>

>

 

 

 

W7CD John <john@...>
 

Same here; Best S+P is doing nothing.  I’m arming it during a receive cycle, then decoding new stations on the band, and nothing occurs or my CQ continues (tried both situations).  I may not be understanding the if/then/else of the process.

Tnx & 73

John W7CD

 

From: rttydigital@groups.io [mailto:rttydigital@groups.io] On Behalf Of Fred Castello
Sent: Tuesday, June 4, 2019 12:40 PM
To: rttydigital@groups.io
Subject: Re: [RttyDigital] WSJT-X 2.1.0-rc7

 

On 14.080 and cant seem to get “Best S&P” to work?  Are there other settings that have to be checked also (such as Call 1st)?

Thanks,

Fred – KF4FC

 

 

From: Joe
Sent: Tuesday, June 4, 2019 10:44 AM
To: rttydigital@groups.io
Subject: Re: [RttyDigital] WSJT-X 2.1.0-rc7

 

Dave --

 

Thanks for the report.  We need to know what you did, and what happened

afterward.  Can you send an example screen shot?

 

                -- Joe, K1JT

 

On 6/3/2019 7:23 PM, Dave Hachadorian wrote:

> I am finding that, with "Best S&P" enabled, I am sometimes calling

> stations who are not calling CQ.

>

> Dave Hachadorian, K6LL

> Yuma, AZ

>

>

>

> -----Original Message----- From: Joe

> Sent: Monday, June 3, 2019 10:56 AM

> To: rttydigital@groups.io

> Subject: [RttyDigital] WSJT-X 2.1.0-rc7

>

> To:   Users of WSJT-X -- especially those interested in radio contesting

> From: WSJT Development Group

>

> We apologize for the confusion created by release yesterday of WSJT-X

> 2.1.0-rc6.  That program version had a bug that prevented it from

> running for some users.  This bug has been fixed in Release Candidate 7,

> which is now available for download.  We have also corrected a problem

> seen by some users of Omni-Rig.

>

> The remainder of this message is mostly a repeat of things in

> yesterday's announcement, with "rc7" replacing "rc6".

>

>

> As you know, we have been developing a protocol called FT4 for use in

> radio contesting.  A new version of FT4 is now available for testing in

> WSJT-X 2.1.0-rc7.

>

> PLEASE NOTE THAT FT4 IN RELEASE CANDIDATE 7 IS NOT COMPATIBLE WITH THAT

> IN RELEASES RC5 and EARLIER.

>

> Therefore: Please stop using WSJT-X 2.1.0-rc5 and WSJT-X 2.1.0-rc6.  If

> you wish to use FT4 after today or to take advantage of other recent

> program corrections or enhancements, you should use WSJT-X 2.1.0-rc7.

>

> MOCK CONTEST SESSION

> --------------------

> A special session for testing the contesting features of FT4 is

> scheduled for six hours from June 4, 1900 UTC through June 5, 0100 UTC:

> Tuesday afternoon/evening, North American time, starting about 24 hours

> from now.  Get on the air whenever you can during this mock contest

> session, using dial frequency 7.090 or 14.080 MHz, as appropriate to the

> time of day.  As in previous tests, be sure to check "RTTY Roundup

> messages" on the Settings | Advanced tab.

>

>

> Here's a list of changes, improvements, and bug fixes that have been

> made since WSJT-X 2.1.0-rc5:

>

> IMPORTANT CHANGES TO THE FT4 PROTOCOL *** NOT BACKWARD COMPATIBLE ***

>   - T/R sequence length increased from 6.0 to 7.5 seconds

>   - Symbol rate decreased from 23.4375 to 20.8333 baud

>   - Signal bandwidth decreased from 90 Hz to 80 Hz

>

> OTHER FT4 IMPROVEMENTS

>   - Allowable time offsets -1.0 < DT < +1.0 s

>   - Tx4 message with RRR now allowed, except in contest messages

>   - Audio frequency is now sent to PSK Reporter

>   - Add a third decoding pass

>   - Add ordered statistics decoding

>   - Improved sensitivity: threshold S/N is now -17.5 dB

>   - Improved S/N calculation

>   - In FT4 mode, Shift+F11/F12 moves Tx freq by ± 100 Hz

>

> OTHER IMPROVEMENTS

>   - Improvements to accessibility

>   - Updates to the User Guide (not yet complete, however)

>   - New user option: "Calling CQ forces Call 1st"

>   - N1MM Logger+ now uses the standard WSJT-X UDP messages

>   - OK/Cancel buttons on Log QSO window maintain fixed positions

>   - Put EU VHF contest serial numbers into the ADIF SRX and STX fields

>

> BUG FIXES

>   - Fix generation of Tx5 message when one callsign is nonstandard

>   - Fix a bug that prevented use on macOS

>   - Fix a bug that caused mode switch from FT4 to FT8

>   - Fix a bug that caused FT4 to do WSPR-style band hopping

>   - Fix a bug that caused a Fortran bounds error

>

> Release candidate WSJT-X 2.1.0-rc7 will be available for beta-testing

> through July 21, 2019.  It will be inoperable during the ARRL June VHF

> QSO Party (June 8-10) or ARRL Field Day (June 22-23).  It will

> permanently cease to function after July 21, 2019.  If all goes

> according to plan, by that time we will have made a General Availability

> (GA) release of WSJT-X 2.1.0.

>

> Downloadable installation packages for WSJT-X 2.1.0-rc7 under Windows,

> Linux, and macOS are available on the WSJT-X web page:

>

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

>

>      -- 73 from Joe, K1JT; Steve, K9AN; and Bill, G4WJS

>

>

>

>

>

>

 

 

 

---

This email has been checked for viruses by AVG.

https://www.avg.com

 

 

Joe
 

Green CQs are stations you have already worked. Best S+P will not answer them, they are "dupes".

On 6/4/2019 15:46, Fred Castello wrote:
I have been Joe, so I must be missing something.  There are a number of green CQ’s after I activate it and I have yet to have it send a transmit during many (20) cycles.
Tnx,
Fred – KF4FC
*From: *Joe <mailto:@K1JT>
*Sent: *Tuesday, June 4, 2019 3:43 PM
*To: *rttydigital@groups.io <mailto:rttydigital@groups.io>
*Subject: *Re: [RttyDigital] WSJT-X 2.1.0-rc7
“Best S&P” must be activated during a Rx sequence.
                -- Joe, K1JT
On 6/4/2019 15:40, Fred Castello wrote:

> On 14.080 and cant seem to get “Best S&P” to work?  Are there other

> settings that have to be checked also (such as Call 1^st )?

>

> Thanks,

>

> Fred – KF4FC

>

> *From: *Joe <mailto:@K1JT>

> *Sent: *Tuesday, June 4, 2019 10:44 AM

> *To: *rttydigital@groups.io <mailto:rttydigital@groups.io>

> *Subject: *Re: [RttyDigital] WSJT-X 2.1.0-rc7

>

> Dave --

>

> Thanks for the report.  We need to know what you did, and what happened

>

> afterward.  Can you send an example screen shot?

>

>                  -- Joe, K1JT

>

> On 6/3/2019 7:23 PM, Dave Hachadorian wrote:

>

>  > I am finding that, with "Best S&P" enabled, I am sometimes calling

>

>  > stations who are not calling CQ.

>

>  >

>

>  > Dave Hachadorian, K6LL

>

>  > Yuma, AZ

>

>  >

>

>  >

>

>  >

>

>  > -----Original Message----- From: Joe

>

>  > Sent: Monday, June 3, 2019 10:56 AM

>

>  > To: rttydigital@groups.io

>

>  > Subject: [RttyDigital] WSJT-X 2.1.0-rc7

>

>  >

>

>  > To:   Users of WSJT-X -- especially those interested in radio
contesting

>

>  > From: WSJT Development Group

>

>  >

>

>  > We apologize for the confusion created by release yesterday of WSJT-X

>

>  > 2.1.0-rc6.  That program version had a bug that prevented it from

>

>  > running for some users.  This bug has been fixed in Release
Candidate 7,

>

>  > which is now available for download.  We have also corrected a problem

>

>  > seen by some users of Omni-Rig.

>

>  >

>

>  > The remainder of this message is mostly a repeat of things in

>

>  > yesterday's announcement, with "rc7" replacing "rc6".

>

>  >

>

>  >

>

>  > As you know, we have been developing a protocol called FT4 for use in

>

>  > radio contesting.  A new version of FT4 is now available for
testing in

>

>  > WSJT-X 2.1.0-rc7.

>

>  >

>

>  > PLEASE NOTE THAT FT4 IN RELEASE CANDIDATE 7 IS NOT COMPATIBLE WITH
THAT

>

>  > IN RELEASES RC5 and EARLIER.

>

>  >

>

>  > Therefore: Please stop using WSJT-X 2.1.0-rc5 and WSJT-X
2.1.0-rc6.  If

>

>  > you wish to use FT4 after today or to take advantage of other recent

>

>  > program corrections or enhancements, you should use WSJT-X 2.1.0-rc7.

>

>  >

>

>  > MOCK CONTEST SESSION

>

>  > --------------------

>

>  > A special session for testing the contesting features of FT4 is

>

>  > scheduled for six hours from June 4, 1900 UTC through June 5, 0100
UTC:

>

>  > Tuesday afternoon/evening, North American time, starting about 24
hours

>

>  > from now.  Get on the air whenever you can during this mock contest

>

>  > session, using dial frequency 7.090 or 14.080 MHz, as appropriate
to the

>

>  > time of day.  As in previous tests, be sure to check "RTTY Roundup

>

>  > messages" on the Settings | Advanced tab.

>

>  >

>

>  >

>

>  > Here's a list of changes, improvements, and bug fixes that have been

>

>  > made since WSJT-X 2.1.0-rc5:

>

>  >

>

>  > IMPORTANT CHANGES TO THE FT4 PROTOCOL *** NOT BACKWARD COMPATIBLE ***

>

>  >   - T/R sequence length increased from 6.0 to 7.5 seconds

>

>  >   - Symbol rate decreased from 23.4375 to 20.8333 baud

>

>  >   - Signal bandwidth decreased from 90 Hz to 80 Hz

>

>  >

>

>  > OTHER FT4 IMPROVEMENTS

>

>  >   - Allowable time offsets -1.0 < DT < +1.0 s

>

>  >   - Tx4 message with RRR now allowed, except in contest messages

>

>  >   - Audio frequency is now sent to PSK Reporter

>

>  >   - Add a third decoding pass

>

>  >   - Add ordered statistics decoding

>

>  >   - Improved sensitivity: threshold S/N is now -17.5 dB

>

>  >   - Improved S/N calculation

>

>  >   - In FT4 mode, Shift+F11/F12 moves Tx freq by ± 100 Hz

>

>  >

>

>  > OTHER IMPROVEMENTS

>

>  >   - Improvements to accessibility

>

>  >   - Updates to the User Guide (not yet complete, however)

>

>  >   - New user option: "Calling CQ forces Call 1st"

>

>  >   - N1MM Logger+ now uses the standard WSJT-X UDP messages

>

>  >   - OK/Cancel buttons on Log QSO window maintain fixed positions

>

>  >   - Put EU VHF contest serial numbers into the ADIF SRX and STX fields

>

>  >

>

>  > BUG FIXES

>

>  >   - Fix generation of Tx5 message when one callsign is nonstandard

>

>  >   - Fix a bug that prevented use on macOS

>

>  >   - Fix a bug that caused mode switch from FT4 to FT8

>

>  >   - Fix a bug that caused FT4 to do WSPR-style band hopping

>

>  >   - Fix a bug that caused a Fortran bounds error

>

>  >

>

>  > Release candidate WSJT-X 2.1.0-rc7 will be available for beta-testing

>

>  > through July 21, 2019.  It will be inoperable during the ARRL June VHF

>

>  > QSO Party (June 8-10) or ARRL Field Day (June 22-23).  It will

>

>  > permanently cease to function after July 21, 2019.  If all goes

>

>  > according to plan, by that time we will have made a General
Availability

>

>  > (GA) release of WSJT-X 2.1.0.

>

>  >

>

>  > Downloadable installation packages for WSJT-X 2.1.0-rc7 under Windows,

>

>  > Linux, and macOS are available on the WSJT-X web page:

>

>  >

>

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

>

>  >

>

>  >      -- 73 from Joe, K1JT; Steve, K9AN; and Bill, G4WJS

>

>  >

>

>  >

>

>  >

>

>  >

>

>  >

>

>  >

>

> ---

>

> This email has been checked for viruses by AVG.

>

> https://www.avg.com

>

>

W7CD John <john@...>
 

I have blue CQs, which are new and Best S+P didn't react. However, when VP8LP called CQ (purple default for new DXCC), Best S+P reacted and called.

Afterwards, still no reaction from new blue CQs (domestics).


John W7CD

-----Original Message-----
From: rttydigital@groups.io [mailto:rttydigital@groups.io] On Behalf Of Joe
Sent: Tuesday, June 4, 2019 1:31 PM
To: rttydigital@groups.io
Subject: Re: [RttyDigital] WSJT-X 2.1.0-rc7

Green CQs are stations you have already worked. Best S+P will not answer them, they are "dupes".

On 6/4/2019 15:46, Fred Castello wrote:
I have been Joe, so I must be missing something. There are a number
of green CQ’s after I activate it and I have yet to have it send a
transmit during many (20) cycles.

Tnx,

Fred – KF4FC

*From: *Joe <mailto:@K1JT>
*Sent: *Tuesday, June 4, 2019 3:43 PM
*To: *rttydigital@groups.io <mailto:rttydigital@groups.io>
*Subject: *Re: [RttyDigital] WSJT-X 2.1.0-rc7

“Best S&P” must be activated during a Rx sequence.

-- Joe, K1JT

On 6/4/2019 15:40, Fred Castello wrote:

> On 14.080 and cant seem to get “Best S&P” to work? Are there other

> settings that have to be checked also (such as Call 1^st )?

>

> Thanks,

>

> Fred – KF4FC

>

> *From: *Joe <mailto:@K1JT>

> *Sent: *Tuesday, June 4, 2019 10:44 AM

> *To: *rttydigital@groups.io <mailto:rttydigital@groups.io>

> *Subject: *Re: [RttyDigital] WSJT-X 2.1.0-rc7

>

> Dave --

>

> Thanks for the report. We need to know what you did, and what
happened

>

> afterward. Can you send an example screen shot?

>

> -- Joe, K1JT

>

> On 6/3/2019 7:23 PM, Dave Hachadorian wrote:

>

> > I am finding that, with "Best S&P" enabled, I am sometimes
calling

>

> > stations who are not calling CQ.

>

> >

>

> > Dave Hachadorian, K6LL

>

> > Yuma, AZ

>

> >

>

> >

>

> >

>

> > -----Original Message----- From: Joe

>

> > Sent: Monday, June 3, 2019 10:56 AM

>

> > To: rttydigital@groups.io

>

> > Subject: [RttyDigital] WSJT-X 2.1.0-rc7

>

> >

>

> > To: Users of WSJT-X -- especially those interested in radio
contesting

>

> > From: WSJT Development Group

>

> >

>

> > We apologize for the confusion created by release yesterday of
WSJT-X

>

> > 2.1.0-rc6. That program version had a bug that prevented it
from

>

> > running for some users. This bug has been fixed in Release
Candidate 7,

>

> > which is now available for download. We have also corrected a
problem

>

> > seen by some users of Omni-Rig.

>

> >

>

> > The remainder of this message is mostly a repeat of things in

>

> > yesterday's announcement, with "rc7" replacing "rc6".

>

> >

>

> >

>

> > As you know, we have been developing a protocol called FT4 for
use in

>

> > radio contesting. A new version of FT4 is now available for
testing in

>

> > WSJT-X 2.1.0-rc7.

>

> >

>

> > PLEASE NOTE THAT FT4 IN RELEASE CANDIDATE 7 IS NOT COMPATIBLE
WITH THAT

>

> > IN RELEASES RC5 and EARLIER.

>

> >

>

> > Therefore: Please stop using WSJT-X 2.1.0-rc5 and WSJT-X
2.1.0-rc6. If

>

> > you wish to use FT4 after today or to take advantage of other
recent

>

> > program corrections or enhancements, you should use WSJT-X 2.1.0-rc7.

>

> >

>

> > MOCK CONTEST SESSION

>

> > --------------------

>

> > A special session for testing the contesting features of FT4 is

>

> > scheduled for six hours from June 4, 1900 UTC through June 5,
0100
UTC:

>

> > Tuesday afternoon/evening, North American time, starting about
24 hours

>

> > from now. Get on the air whenever you can during this mock
contest

>

> > session, using dial frequency 7.090 or 14.080 MHz, as
appropriate to the

>

> > time of day. As in previous tests, be sure to check "RTTY
Roundup

>

> > messages" on the Settings | Advanced tab.

>

> >

>

> >

>

> > Here's a list of changes, improvements, and bug fixes that have
been

>

> > made since WSJT-X 2.1.0-rc5:

>

> >

>

> > IMPORTANT CHANGES TO THE FT4 PROTOCOL *** NOT BACKWARD
COMPATIBLE ***

>

> > - T/R sequence length increased from 6.0 to 7.5 seconds

>

> > - Symbol rate decreased from 23.4375 to 20.8333 baud

>

> > - Signal bandwidth decreased from 90 Hz to 80 Hz

>

> >

>

> > OTHER FT4 IMPROVEMENTS

>

> > - Allowable time offsets -1.0 < DT < +1.0 s

>

> > - Tx4 message with RRR now allowed, except in contest messages

>

> > - Audio frequency is now sent to PSK Reporter

>

> > - Add a third decoding pass

>

> > - Add ordered statistics decoding

>

> > - Improved sensitivity: threshold S/N is now -17.5 dB

>

> > - Improved S/N calculation

>

> > - In FT4 mode, Shift+F11/F12 moves Tx freq by ± 100 Hz

>

> >

>

> > OTHER IMPROVEMENTS

>

> > - Improvements to accessibility

>

> > - Updates to the User Guide (not yet complete, however)

>

> > - New user option: "Calling CQ forces Call 1st"

>

> > - N1MM Logger+ now uses the standard WSJT-X UDP messages

>

> > - OK/Cancel buttons on Log QSO window maintain fixed positions

>

> > - Put EU VHF contest serial numbers into the ADIF SRX and STX
fields

>

> >

>

> > BUG FIXES

>

> > - Fix generation of Tx5 message when one callsign is
nonstandard

>

> > - Fix a bug that prevented use on macOS

>

> > - Fix a bug that caused mode switch from FT4 to FT8

>

> > - Fix a bug that caused FT4 to do WSPR-style band hopping

>

> > - Fix a bug that caused a Fortran bounds error

>

> >

>

> > Release candidate WSJT-X 2.1.0-rc7 will be available for
beta-testing

>

> > through July 21, 2019. It will be inoperable during the ARRL
June VHF

>

> > QSO Party (June 8-10) or ARRL Field Day (June 22-23). It will

>

> > permanently cease to function after July 21, 2019. If all goes

>

> > according to plan, by that time we will have made a General
Availability

>

> > (GA) release of WSJT-X 2.1.0.

>

> >

>

> > Downloadable installation packages for WSJT-X 2.1.0-rc7 under
Windows,

>

> > Linux, and macOS are available on the WSJT-X web page:

>

> >

>

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

>

> >

>

> > -- 73 from Joe, K1JT; Steve, K9AN; and Bill, G4WJS

>

> >

>

> >

>

> >

>

> >

>

> >

>

> >

>

> ---

>

> This email has been checked for viruses by AVG.

>

> https://www.avg.com

>

>

Fred Castello
 

Not according to my “Contest Log”.  There are new green stations calling CQ on the left side that I have not worked before and when I activate “Best S&P” during a receive sequence and leave it activated (for many more T&R sequences with new green CQ stations on the left, the radio does not activate.  Thanks so much for your work with this.  I am not complaining, just reporting as a Beta tester!!!

Regards,

Fred – KF4FC

 

 

From: Joe
Sent: Tuesday, June 4, 2019 4:31 PM
To: rttydigital@groups.io
Subject: Re: [RttyDigital] WSJT-X 2.1.0-rc7

 

Green CQs are stations you have already worked. Best S+P will not answer

them, they are "dupes".

 

On 6/4/2019 15:46, Fred Castello wrote:

> I have been Joe, so I must be missing something.  There are a number of

> green CQ’s after I activate it and I have yet to have it send a transmit

> during many (20) cycles.

>

> Tnx,

>

> Fred – KF4FC

>

> *From: *Joe <mailto:joe@...>

> *Sent: *Tuesday, June 4, 2019 3:43 PM

> *To: *rttydigital@groups.io <mailto:rttydigital@groups.io>

> *Subject: *Re: [RttyDigital] WSJT-X 2.1.0-rc7

>

> “Best S&P” must be activated during a Rx sequence.

>

>                  -- Joe, K1JT

>

> On 6/4/2019 15:40, Fred Castello wrote:

>

>  > On 14.080 and cant seem to get “Best S&P” to work?  Are there other

>

>  > settings that have to be checked also (such as Call 1^st )?

>

>  >

>

>  > Thanks,

>

>  >

>

>  > Fred – KF4FC

>

>  >

>

>  > *From: *Joe <mailto:joe@...>

>

>  > *Sent: *Tuesday, June 4, 2019 10:44 AM

>

>  > *To: *rttydigital@groups.io <mailto:rttydigital@groups.io>

>

>  > *Subject: *Re: [RttyDigital] WSJT-X 2.1.0-rc7

>

>  >

>

>  > Dave --

>

>  >

>

>  > Thanks for the report.  We need to know what you did, and what happened

>

>  >

>

>  > afterward.  Can you send an example screen shot?

>

>  >

>

>  >                  -- Joe, K1JT

>

>  >

>

>  > On 6/3/2019 7:23 PM, Dave Hachadorian wrote:

>

>  >

>

>  >  > I am finding that, with "Best S&P" enabled, I am sometimes calling

>

>  >

>

>  >  > stations who are not calling CQ.

>

>  >

>

>  >  >

>

>  >

>

>  >  > Dave Hachadorian, K6LL

>

>  >

>

>  >  > Yuma, AZ

>

>  >

>

>  >  >

>

>  >

>

>  >  >

>

>  >

>

>  >  >

>

>  >

>

>  >  > -----Original Message----- From: Joe

>

>  >

>

>  >  > Sent: Monday, June 3, 2019 10:56 AM

>

>  >

>

>  >  > To: rttydigital@groups.io

>

>  >

>

>  >  > Subject: [RttyDigital] WSJT-X 2.1.0-rc7

>

>  >

>

>  >  >

>

>  >

>

>  >  > To:   Users of WSJT-X -- especially those interested in radio

> contesting

>

>  >

>

>  >  > From: WSJT Development Group

>

>  >

>

>  >  >

>

>  >

>

>  >  > We apologize for the confusion created by release yesterday of WSJT-X

>

>  >

>

>  >  > 2.1.0-rc6.  That program version had a bug that prevented it from

>

>  >

>

>  >  > running for some users.  This bug has been fixed in Release

> Candidate 7,

>

>  >

>

>  >  > which is now available for download.  We have also corrected a problem

>

>  >

>

>  >  > seen by some users of Omni-Rig.

>

>  >

>

>  >  >

>

>  >

>

>  >  > The remainder of this message is mostly a repeat of things in

>

>  >

>

>  >  > yesterday's announcement, with "rc7" replacing "rc6".

>

>  >

>

>  >  >

>

>  >

>

>  >  >

>

>  >

>

>  >  > As you know, we have been developing a protocol called FT4 for use in

>

>  >

>

>  >  > radio contesting.  A new version of FT4 is now available for

> testing in

>

>  >

>

>  >  > WSJT-X 2.1.0-rc7.

>

>  >

>

>  >  >

>

>  >

>

>  >  > PLEASE NOTE THAT FT4 IN RELEASE CANDIDATE 7 IS NOT COMPATIBLE WITH

> THAT

>

>  >

>

>  >  > IN RELEASES RC5 and EARLIER.

>

>  >

>

>  >  >

>

>  >

>

>  >  > Therefore: Please stop using WSJT-X 2.1.0-rc5 and WSJT-X

> 2.1.0-rc6.  If

>

>  >

>

>  >  > you wish to use FT4 after today or to take advantage of other recent

>

>  >

>

>  >  > program corrections or enhancements, you should use WSJT-X 2.1.0-rc7.

>

>  >

>

>  >  >

>

>  >

>

>  >  > MOCK CONTEST SESSION

>

>  >

>

>  >  > --------------------

>

>  >

>

>  >  > A special session for testing the contesting features of FT4 is

>

>  >

>

>  >  > scheduled for six hours from June 4, 1900 UTC through June 5, 0100

> UTC:

>

>  >

>

>  >  > Tuesday afternoon/evening, North American time, starting about 24

> hours

>

>  >

>

>  >  > from now.  Get on the air whenever you can during this mock contest

>

>  >

>

>  >  > session, using dial frequency 7.090 or 14.080 MHz, as appropriate

> to the

>

>  >

>

>  >  > time of day.  As in previous tests, be sure to check "RTTY Roundup

>

>  >

>

>  >  > messages" on the Settings | Advanced tab.

>

>  >

>

>  >  >

>

>  >

>

>  >  >

>

>  >

>

>  >  > Here's a list of changes, improvements, and bug fixes that have been

>

>  >

>

>  >  > made since WSJT-X 2.1.0-rc5:

>

>  >

>

>  >  >

>

>  >

>

>  >  > IMPORTANT CHANGES TO THE FT4 PROTOCOL *** NOT BACKWARD COMPATIBLE ***

>

>  >

>

>  >  >   - T/R sequence length increased from 6.0 to 7.5 seconds

>

>  >

>

>  >  >   - Symbol rate decreased from 23.4375 to 20.8333 baud

>

>  >

>

>  >  >   - Signal bandwidth decreased from 90 Hz to 80 Hz

>

>  >

>

>  >  >

>

>  >

>

>  >  > OTHER FT4 IMPROVEMENTS

>

>  >

>

>  >  >   - Allowable time offsets -1.0 < DT < +1.0 s

>

>  >

>

>  >  >   - Tx4 message with RRR now allowed, except in contest messages

>

>  >

>

>  >  >   - Audio frequency is now sent to PSK Reporter

>

>  >

>

>  >  >   - Add a third decoding pass

>

>  >

>

>  >  >   - Add ordered statistics decoding

>

>  >

>

>  >  >   - Improved sensitivity: threshold S/N is now -17.5 dB

>

>  >

>

>  >  >   - Improved S/N calculation

>

>  >

>

>  >  >   - In FT4 mode, Shift+F11/F12 moves Tx freq by ± 100 Hz

>

>  >

>

>  >  >

>

>  >

>

>  >  > OTHER IMPROVEMENTS

>

>  >

>

>  >  >   - Improvements to accessibility

>

>  >

>

>  >  >   - Updates to the User Guide (not yet complete, however)

>

>  >

>

>  >  >   - New user option: "Calling CQ forces Call 1st"

>

>  >

>

>  >  >   - N1MM Logger+ now uses the standard WSJT-X UDP messages

>

>  >

>

>  >  >   - OK/Cancel buttons on Log QSO window maintain fixed positions

>

>  >

>

>  >  >   - Put EU VHF contest serial numbers into the ADIF SRX and STX fields

>

>  >

>

>  >  >

>

>  >

>

>  >  > BUG FIXES

>

>  >

>

>  >  >   - Fix generation of Tx5 message when one callsign is nonstandard

>

>  >

>

>  >  >   - Fix a bug that prevented use on macOS

>

>  >

>

>  >  >   - Fix a bug that caused mode switch from FT4 to FT8

>

>  >

>

>  >  >   - Fix a bug that caused FT4 to do WSPR-style band hopping

>

>  >

>

>  >  >   - Fix a bug that caused a Fortran bounds error

>

>  >

>

>  >  >

>

>  >

>

>  >  > Release candidate WSJT-X 2.1.0-rc7 will be available for beta-testing

>

>  >

>

>  >  > through July 21, 2019.  It will be inoperable during the ARRL June VHF

>

>  >

>

>  >  > QSO Party (June 8-10) or ARRL Field Day (June 22-23).  It will

>

>  >

>

>  >  > permanently cease to function after July 21, 2019.  If all goes

>

>  >

>

>  >  > according to plan, by that time we will have made a General

> Availability

>

>  >

>

>  >  > (GA) release of WSJT-X 2.1.0.

>

>  >

>

>  >  >

>

>  >

>

>  >  > Downloadable installation packages for WSJT-X 2.1.0-rc7 under Windows,

>

>  >

>

>  >  > Linux, and macOS are available on the WSJT-X web page:

>

>  >

>

>  >  >

>

>  >

>

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

>

>  >

>

>  >  >

>

>  >

>

>  >  >      -- 73 from Joe, K1JT; Steve, K9AN; and Bill, G4WJS

>

>  >

>

>  >  >

>

>  >

>

>  >  >

>

>  >

>

>  >  >

>

>  >

>

>  >  >

>

>  >

>

>  >  >

>

>  >

>

>  >  >

>

>  >

>

>  > ---

>

>  >

>

>  > This email has been checked for viruses by AVG.

>

>  >

>

>  > https://www.avg.com

>

>  >

>

>  >

>

>

 

 

 

Bill N4iQ
 

I experienced the same thing - S&P button activated (I thought), but nothing happening when clearly there were  non-worked  CQ stations.  However, after clicking on the button several times, the S&P button would activate the function and all was OK.  Part of the problem, at least to me, is that most of the time I cannot tell if the button is activated or not.  On my the screen I cannot tell much indication of on or off with the button.  When clicked, the button appears to fade in or out slightly, but nothing I can really tell.  I had significant problem telling if the button was activated or not.  Perhaps it is my monitor, my poor color perception eyesight, or something else.  I wish the button had a dark color, or high contract color, to know when it is activated or not.  I think my problem with the S&P was not the the function operating but knowing when it was actually turned on or off. 

I though rc7 worked great!   I did have a problem on a couple of instances when a CQing station did not complete the QSO with a R 73 sequence.   I looked at the timing of the exchange and saw the other station just did not send the final R 73 but instead immediately started to CQ again.   Not sure why that happened - was it their program or was it operator initiated?  Onlly happened a few times out of about 60 compled QSOs over less than two hours.

I want to thank the development team for all the work they put into this software.  I have WSJT-X integrated into SO2R N1MM+ with RTTY on one radio and FT4 WSJT-X on the other.  Although there were no RTTY contacts actually made, I simulated a few RTTY contacts just to see how N1MM+ would handle the logging: both RTTY and WSJT-X FT4 logging worked perfectly including the recognition of RTTY dupes on the N1MM+ WSJT-X List.   Integrating all this just has to be super intricate!!!  Beyond me how the team does it with all the different modes and operating schemes (Contest, F/H, etc etc).

Thanks again!
73  Bill N4iQ

stephen shearer
 

I felt I need to read more about the button...  So, I guess it was not just me...  (also difficult to tell when active)

I did have fun.

I operated a total of 3 hours at the beginning and at the end.
I operated 20m then 40m.
I started with an 80m loop on 40m and changed to a R8 vertical.
I ran 60 watts and later 90watts - using KX3/amp.

My RST Rec ranged (low) 4/539 with 1/529  and Sent 6/549 with 1/539

25 states/prov
14 countries
30 grids

73, steve WB3LGC FM29 DE

On 6/5/19 11:31 AM, Bill N4iQ wrote:
I experienced the same thing - S&P button activated (I thought),