[wsjt-devel] Open SSL problem.

[Tom Ramberg via wsjt-devel]

I’ve installed the WIN64OpenSSL_Light-1_0_2s, but the the lotw user activity 
file won’t load. Se error message



73 de Tom OH6VDA 

Sendt fra min iPhone___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.1.0-rc7

[Black Michael via wsjt-devel]

Did you follow the directions in the help file closely?

Install the package and accept the default options, including the option to 
copy the OpenSSL DLLs to the Windows system directory

de Mike W9MDB 

On Monday, June 3, 2019, 10:32:52 PM CDT, Jim Nuytens via wsjt-devel 
 wrote:  
 
 Tried that. Still getting the error.

On 6/4/2019 00:27, Bill Somerville wrote:
>
> Hi Jim,
>
> you need to install the 64-bit version of the OpenSSL libraries. 
> Follow the instructions in the WSJT-X v2.0.1 User Guide but pick the 
> Win64 variant of the OpenSSL package. The one you need is the 
> Win64_OpenSSL_v1.0.2s_Light package.
>
> http://physics.princeton.edu/pulsar/k1jt/wsjtx-doc/wsjtx-main-2.0.1.html#INSTALL_WIN
>  
>
>
> 73
> Bill
> G4WJS.

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



___
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-X 2.1.0-rc7

[Jim Nuytens via wsjt-devel]

Windows 64-bit version seems to be running fine on W10 Pro.

I did find 1 issue. Trying to fetch the latest LoTW .csv file results in 
a "SSL/TLS support not installed" message.


WSJT-X 2.0.1 32-bit does not have this problem.


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



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

[wsjt-devel] Rc7

[VE3FBZ]

Downloaded RC7 Win 10 64 bit version 
Works great.
QSOs On 14.080
Working with JTALERT 12.13.7 ok.
Logging ok.
Response great.
Thanks a million Development Team.

 Regards and 73s
VE3FBZ
London Amateur Radio Club
www.larc.ca 





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

Re: [wsjt-devel] RC7 FT4 & JTALert

[Laurie, VK3AMA]

On 4/06/2019 5:53 am, Al wrote:

FYI

JTAlert seems to have a strange response to RC7/RC4.  When I am making 
engaged in a contact on Ft4, JTAlert displays MY call sign for each 
time the other station sends it.


JTAlert correctly displays call signs for FT8.

AL, K0VM


That's to be expected when your using a version of JTAlert produced 
before FT4 ever existed.


Initial support for FT4 was added with version 2.13.4, according to the 
HamSpots logs, your spotting using 2.12.10.
Upgrading WSJT-X to embrace a new mode without a corresponding upgrade 
of JTAlert will always produce unpredictable results.


There have been some further FT4 specific changes to JTAlert since 
2.13.4. The latest build is 2.13.7, I strongly suggest you upgrade to 
that build, there is no reason to stay with 2.12.10.


de Laurie VK3AMA

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

Re: [wsjt-devel] WSJT-X 2.1.0-rc7

[Hasan al-Basri]

Working fine 64 bit Win10 Home
Tnx quick fix! 73, N0AN
Hasan


On Mon, Jun 3, 2019 at 2:04 PM Al  wrote:

> RC 7 OK so far..
> AL, K0VM
>
> On 6/3/2019 12:56 PM, Joe Taylor wrote:
>
> 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
>
>
> ___
> 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] RC7 FT4 & JTALert

[Bill Somerville]

On 03/06/2019 20:53, Al wrote:

FYI

JTAlert seems to have a strange response to RC7/RC4.  When I am making 
engaged in a contact on Ft4, JTAlert displays MY call sign for each 
time the other station sends it.


JTAlert correctly displays call signs for FT8.

AL, K0VM


Al,

Laurie has made it quite clear that support for processing FT4 decodes 
in JTAlert is not available in the current version. A future version 
will extend support to newer modes. Relaying log records is still 
supported by JTAlert, whatever the mode.


73
Bill
G4WJS.

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

[wsjt-devel] RC7 FT4 & JTALert

[Al]

FYI

JTAlert seems to have a strange response to RC7/RC4.  When I am making 
engaged in a contact on Ft4, JTAlert displays MY call sign for each time 
the other station sends it.


JTAlert correctly displays call signs for FT8.

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

Re: [wsjt-devel] WSJT-X 2.1.0-rc7

[Al]

RC 7 OK so far..
AL, K0VM

On 6/3/2019 12:56 PM, Joe Taylor wrote:

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


___
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-X 2.1.0-rc7

[Gary Rogers]

Mac OS version is working FB, no issues changing configurations…Thanks for a 
great program! 73 KO3F

> On Jun 3, 2019, at 1:56 PM, Joe Taylor  wrote:
> 
> 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
> 
> 
> ___
> 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-X 2.1.0-rc7

[V. Scott Moore via wsjt-devel]

All:

Mac version works so far.  No crash on CONFIGURATION switch between FT4/8 and 
double click call for FT4 initiates call just dandy (two whole contacts).

TNX
Scott
w1ssn

> On Jun 3, 2019, at 13:56, Joe Taylor  wrote:
> 
> 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
> 
> 
> ___
> 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] WSJT-X 2.1.0-rc7

[Joe Taylor]

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


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

Re: [wsjt-devel] Plans for JT6m / FSK144

[Tom Melvin]

Hi

Thanks for update - much appreciated.

Tom


--
73’s

Tom
GM8MJV (IO85)





On 3 Jun 2019, at 16:33, Joe Taylor  wrote:

> Hi Tom,
> 
> There are no plans to support JT6m or FSK441 (which I assume you meant) in 
> WSJT-X.  These modes are deprecated because they have been superseded by 
> superior protocols.
> 
>   -- 73, Joe, K1JT
> 
> On 5/31/2019 7:10 PM, Tom Melvin wrote:
>> Hi Dev Team
>> WSJT supports JT6m and FSK144 while WSJT-X does not. There are a few people 
>> who, depending on mode / activity, still use those modes.
>> Can anyone tell me if adding those ‘older’ modes into WSJT-X is on the to-do 
>> list or will we still need to use V10 of WSJT?
>> 73’s
>> Tom
>> GM8MJV (IO85)
> 
> 
> ___
> 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] hash size

[Joe Taylor]

On 6/2/2019 9:07 AM, Black Michael W9MDB via wsjt-devel wrote:
Was looking at the nhash.c function and it's always masking the result 
to 16 bits.


   final(a,b,c);
   c=(32767);

   return c;

Don't we want 32 bits from nhash for FT8 so we can use 28 bits or such 
for the message?  Or at least nhash.c to not automatically mask to 16 
bits for future needs?  How many bits do we use for the FT8 hashed call 
signs?


See descriptive document .../wsjtx/lib/77bit/77bit.txt and related code 
in .../wsjtx/lib/77bit/packjt77.f90.


Hashed callsigns in the 77-bit protocols MSK144, FT8, and FT4 can use 
10, 12, or 22 bits depending on the message type.  These hash values are 
not derived from nhash.c.


-- Joe, K1JT


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

Re: [wsjt-devel] Time

[Reino Talarmo]

Claude wrote: 
" as well as the propagation delay and the time needed to decode."
We may forget propagation time that is less than 0.1 s on globe, moonbounce
is another issue.
To my understanding dT is calculated based on  message time sync location on
the received timeslot and is fully independent of decoding time.
Mean dT do give a good hint about local clock time error. It may not be
reliable for adjusting local clock, if too many starts to do so.
73, Reino oh3ma




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

Re: [wsjt-devel] Time

[Claude Frantz]

On 6/3/19 1:56 PM, Dave Slotter wrote:

It doesn't do much good to be "in-your-face" about clock synchronization 
issues to the receivers of signals which are off by too high a delta, 
because it's the sender that needs their clock adjusted, not the receiver.


Exactly, Dave ! The DT, at the receiver, includes the time error at the 
TX side, as well as the propagation delay and the time needed to decode. 
Therefore, it's not a great idea to use this DT at the RX side for a 
time correction of the local clock of the RX system.


If you see a really divergent DT value among many other values of the 
same order, on our RX, you can suspect a time error at the TX side. But 
probably not really more.


Claude


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

Re: [wsjt-devel] Time

[Black Michael via wsjt-devel]

Actually it's both.  If your clock is spot on you have more "slop" in the time 
then if your own clock is off by any amount.Yeah...it's mostly the sender when 
it shows up far too high on the receiver side but it does work both ways.  
The idea of this "majority" was brought up before but don't believe I heard any 
comment from the team.  I think a message in the Band Activity for "Check your 
clock" and a reference in the manual to http://time.is and software for 
Windows/Unix would be quite helpful.
It would have to be something like "more than 4 decodes and 60% or more are off 
by too much".  So 3-out-of-5 would trigger it.
de Mike W9MDB

 

On Monday, June 3, 2019, 6:56:44 AM CDT, Dave Slotter 
 wrote:  
 
 Mike,
It doesn't do much good to be "in-your-face" about clock synchronization issues 
to the receivers of signals which are off by too high a delta, because it's the 
sender that needs their clock adjusted, not the receiver.
However, your attention to the issue gives me an idea... If an instance of 
WSJT-X sees that most (90%) of remote signals it sees are too far off from its 
own, the chances are is that it's the local user's clock that needs adjusting, 
and that user could be alerted to sync their clock in that case.
What do you think?
-Dave W3DJS
On Mon, Jun 3, 2019 at 7:48 AM Black Michael via wsjt-devel 
 wrote:

Would probably be good if WSJT-X did what JTAlert has started 
doing...highlighting DT values > 1.5 sec.
For FT4 perhaps highlight > 0.5 seconds since if both sides are off -.5 and 0.5 
I assume that would be an unlikely decode.This is what JTAlert does now.Then, 
also put some help in the manual about time setting on common platforms when 
people what to know why all of the DT values are being colored.  I've been 
notifying quite a few people about their clocks but a lot of them don't even 
have email addresses on QRZ so can't be notified easily.  There needs to be 
something a bit more in-your-face about time problems.  



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] Time

[VE3FBZ]

Morning all, continued super support group.

I use Dimension 4 to keep my Win 10 laptop in sync.

I like the the red flag on an out of step clock. I simply avoid the call.
I’ve tried to inform the user in the past to no avail.

Regards and 73s
VE3FBZ
London Amateur Radio Club
www.larc.ca 




> On Jun 3, 2019, at 07:56, Dave Slotter  wrote:
> 
> Mike,
> 
> It doesn't do much good to be "in-your-face" about clock synchronization 
> issues to the receivers of signals which are off by too high a delta, because 
> it's the sender that needs their clock adjusted, not the receiver.
> 
> However, your attention to the issue gives me an idea... If an instance of 
> WSJT-X sees that most (90%) of remote signals it sees are too far off from 
> its own, the chances are is that it's the local user's clock that needs 
> adjusting, and that user could be alerted to sync their clock in that case.
> 
> What do you think?
> 
> -Dave
>  W3DJS
> 
>> On Mon, Jun 3, 2019 at 7:48 AM Black Michael via wsjt-devel 
>>  wrote:
>> Would probably be good if WSJT-X did what JTAlert has started 
>> doing...highlighting DT values > 1.5 sec.
>> 
>> For FT4 perhaps highlight > 0.5 seconds since if both sides are off -.5 and 
>> 0.5 I assume that would be an unlikely decode.
>> This is what JTAlert does now.
>> Then, also put some help in the manual about time setting on common 
>> platforms when people what to know why all of the DT values are being 
>> colored.  I've been notifying quite a few people about their clocks but a 
>> lot of them don't even have email addresses on QRZ so can't be notified 
>> easily.  There needs to be something a bit more in-your-face about time 
>> problems.  
>> 
>> <1559561734243blob.jpg>
>> 
>> 
>> 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
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] color of time slide

[Wolfgang]

Hello Black,

having the time slide (increasing to the full cycle time) in red
during TX (or even the same like the setting of 'Transmitted message
color') and green, any other color during RX would help a lot.

Did I miss something, is there any setting for this ?

73 de Wolfgang
OE1MWW

--
Amateur radio is the most expensive type of free-of-charge communication!
Amateurfunk ist die teuerste Art der kostenlosen Kommunikation!



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

Re: [wsjt-devel] Time

[Dave Slotter]

Mike,

It doesn't do much good to be "in-your-face" about clock synchronization
issues to the receivers of signals which are off by too high a delta,
because it's the sender that needs their clock adjusted, not the receiver.

However, your attention to the issue gives me an idea... If an instance of
WSJT-X sees that most (90%) of remote signals it sees are too far off from
its own, the chances are is that it's *the local user's* clock that needs
adjusting, and that user could be alerted to sync their clock in that case.

What do you think?

-Dave
 W3DJS 

On Mon, Jun 3, 2019 at 7:48 AM Black Michael via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> Would probably be good if WSJT-X did what JTAlert has started
> doing...highlighting DT values > 1.5 sec.
>
> For FT4 perhaps highlight > 0.5 seconds since if both sides are off -.5
> and 0.5 I assume that would be an unlikely decode.
> This is what JTAlert does now.
> Then, also put some help in the manual about time setting on common
> platforms when people what to know why all of the DT values are being
> colored.  I've been notifying quite a few people about their clocks but a
> lot of them don't even have email addresses on QRZ so can't be notified
> easily.  There needs to be something a bit more in-your-face about time
> problems.
>
> [image: Inline image]
>
>
> 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

[wsjt-devel] Time

[Black Michael via wsjt-devel]

Would probably be good if WSJT-X did what JTAlert has started 
doing...highlighting DT values > 1.5 sec.
For FT4 perhaps highlight > 0.5 seconds since if both sides are off -.5 and 0.5 
I assume that would be an unlikely decode.This is what JTAlert does now.Then, 
also put some help in the manual about time setting on common platforms when 
people what to know why all of the DT values are being colored.  I've been 
notifying quite a few people about their clocks but a lot of them don't even 
have email addresses on QRZ so can't be notified easily.  There needs to be 
something a bit more in-your-face about time problems.  



de Mike W9MDB



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

Re: [wsjt-devel] WSJT-X 2.1.0-rc6

[Dave Slotter]

Bill,

I did a little investigating on what would trigger the segfault (crash) on
WSJT-X 2.1.0-rc6, and it appears that having an ADIF log with as little as
two lines will trigger the crash for me. I am including the two lines from
my log below:

CN2MA IM64 FT8 -10
-10 20190529 025930
20190529 030030 30m 10.137900
W3DJS EM83bx 33
Roman Levichev 
WA0YPC DM67 FT8 -13
-18 20190529 030545
20190529 030630 30m 10.137900
W3DJS EM83bx 33
Dennis A Dugan 

If I reduce this log file to just one of those two lines, then WSJT-X
2.1.0-rc6 starts up normally. And, even better. If I launch wsjtx normally
with the old (huge) log file renamed, it also starts up normally. (Meaning:
no -r switch needed for a test profile).

Hope this helps.

-Dave
 W3DJS 

On Mon, Jun 3, 2019 at 7:00 AM rjai...@gmail.com  wrote:

> Same here, running under parallels in macOS simply don’t work, crashes and
> leaves behind a lock file. Old version works.
>
> Ria
> N2RJ
>
> On Sun, Jun 2, 2019 at 4:13 PM Dana Myers  wrote:
>
>> On 6/2/2019 11:32 AM, Joe Taylor wrote:
>> > To: Users of WSJT-X -- especially those interested in radio contesting
>> > From: WSJT Development Group
>> >
>> > 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-rc6.
>> >
>> > PLEASE NOTE THAT FT4 IN RELEASE CANDIDATE 6 IS NOT COMPATIBLE WITH THAT
>> IN ANY PREVIOUS RELEASE.
>> >
>> > Therefore: Please stop using WSJT-X 2.1.0-rc5.  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-rc6.
>>
>> On Windows 10 Pro 64-bit 1903:
>> I've installed -rc6 64-bit  in a new folder and attempts to launch it
>> simply... don't
>> launch anything that I can see. -rc5 64-bit works correctly.
>>
>> Any suggestions where to look first?
>>
>> Thanks,
>> Dana  K6JQ
>>
>>
>>
>> ___
>> 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] WSJT-X 2.1.0-rc6

[rjai...@gmail.com]

Same here, running under parallels in macOS simply don’t work, crashes and
leaves behind a lock file. Old version works.

Ria
N2RJ

On Sun, Jun 2, 2019 at 4:13 PM Dana Myers  wrote:

> On 6/2/2019 11:32 AM, Joe Taylor wrote:
> > To: Users of WSJT-X -- especially those interested in radio contesting
> > From: WSJT Development Group
> >
> > 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-rc6.
> >
> > PLEASE NOTE THAT FT4 IN RELEASE CANDIDATE 6 IS NOT COMPATIBLE WITH THAT
> IN ANY PREVIOUS RELEASE.
> >
> > Therefore: Please stop using WSJT-X 2.1.0-rc5.  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-rc6.
>
> On Windows 10 Pro 64-bit 1903:
> I've installed -rc6 64-bit  in a new folder and attempts to launch it
> simply... don't
> launch anything that I can see. -rc5 64-bit works correctly.
>
> Any suggestions where to look first?
>
> Thanks,
> Dana  K6JQ
>
>
>
> ___
> 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] Cannot download RC6

[WB5JJJ]

It had multiple bugs and was removed for fixing.

On Mon, Jun 3, 2019 at 12:47 AM Tom Ramberg via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> Clicking on the download link for RC5 produces this reactio (Similar for
> both 32- and 64-bits versions):
> Not Found
>
> The requested URL /pulsar/K1JT/wsjtx-2.1.0-rc6-win64.exe was not found on
> this server.
> --
> Apache/2.2.15 (Scientific Linux) Server at physics.princeton.edu Port 80
>
> ___
> 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