Re: [wsjt-devel] FT8: IMPORTANT NOTICE

[Tsutsumi Takehiko]

Joe, Bill and all members,

I sincerely appreciate the kindness and genericity to accept my proposal on 80m 
transition knowing the painful burden to the rest of the world.

I believe this transition will provide the window to access to the world for 
all JA station on 80m and will ultimately promote the success of the software.

Thank you very much.

take

de JA5AEA


Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10

From: Joe Taylor<mailto:j...@princeton.edu>
Sent: Saturday, July 8, 2017 8:58 AM
To: WSJT software development<mailto:wsjt-devel@lists.sourceforge.net>
Subject: Re: [wsjt-devel] FT8: IMPORTANT NOTICE

To:  Users of FT8
From:WSJT Development Team
Subject: IMPORTANT NOTICE ABOUT FT8

If you are building WSJT-X for yourself from source code, you may now
upgrade to r7812 and recompile. You will then have access to the latest
version of FT8 plus some new features for setting default operating
frequencies by mode and IARU region.  The program built in this way will
be called WSJT-X v1.7.1 r7812.

Note that essentially the same program will soon be packaged for wider
distribution as as "WSJT-X Version 1.8.0-rc1" (release candidate 1), see
below).

Remember that FT8 in code revisions 7812 are higher is NOT COMPATIBLE
with that in 7782 and earlier.  To use FT8 you must upgrade to r7812.
If you see FT8 signals that do not decode, they may be using the
obsolete protocol.

About the Default Working Frequencies
=

FT8 will likely be popular with MF and HF users as well as the VHF
multi-hop sporadic-E DXers it was designed for.  After consultation with
the user community, we have reworked the suggested operating frequency
defaults to include FT8.  This was not easy on every relevant band;
where possible, we have suggested a 2 kHz range for exclusive FT8 use.
(Exclusivity is important, as the T/R period is 15 s which will not mix
well with mode that use one-minute sequences.)

In general the FT8 frequencies are set 2kHz below the current JT65
allocation.  This should allow operation using a normal SSB filter width
without too much interference from strong JT65 signals up the band.  On
some bands that has not been possible since JT65 sits at the lowest
usable narrow band data mode frequency, when considering all
international band plans.

For the 660 m and 2200 m  bands we have not assigned separate
frequencies for JT65/JT9/FT8, and just expect users to coordinate
themselves.  The numbers of active operators will probably be low enough
that this will not cause issues.

For 160 m we assume that the JT65 and JT9 sub-bands can be squeezed to
1 kHz each, and FT8 can sit above using up to another 1 kHz.

Previous 80 m use of JT modes has done a disservice to JA operators, who
have no privileges on the current WSPR/JT65/JT9 allocations.  To correct
this we have moved the allocations to a part of the band where JAs can
operate.  Obviously this change will impact other non-WSJT-X users, so
for now we suggest that if you intend to operate on 80 m JT65/JT9/WSPR
then you manually change the working frequencies in WSJT-X
("Settings->Frequencies") back to the old allocations until a general
availability release of WSJT-X v1.8.0 is published. This will allow time
for other software teams to coordinate with us.

The old allocations are:

JT65 3.567 MHz
JT9  3.578 MHz
WSPR 3.5926 MHz

For 6 m we understand that the IARU Region 1 band plan is not to the
liking of DX chasers around the world and largely ignored by Region 1
users.  However we cannot reasonably continue to set working frequency
suggestions that drive traffic to parts of the band that are not
supposed to be used for narrow band data modes.  The v1.8.0 release will
allow Region-specific working frequencies as well as globally
coordinated ones.  Consequently we have set the Region 1 working
frequencies roughly in line with the band plan.  If you do not like the
allocations then do not complain to us, but complain to your Region 1
band coordinator along with reasons why you think it should change.  The
proposed Region 1 working frequencies are usable globally wherever 6m
data mode operation is permitted so we have set them as global rather
than Region 1 specific.  Region 2 and 3 operators will have both local
and global frequencies offered.

Other changes are in line with current usage.


Finally, if you are waiting for pre-built installation packages:

We plan to post a release candidate for WSJT-X v1.8.0-rc1 configured for
Windows, Linux, and OS X very soon -- probably early next week.  Thanks
for your patience!

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

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing li

Re: [wsjt-devel] FT8: IMPORTANT NOTICE

[Steven Franke]

Hi Bob,

Bill may have gone to bed… He was on 20m, 14.074.

Steve, k9an

> On Jul 8, 2017, at 2:05 AM, Robert Nobis  wrote:
> 
> Hi Bill,
> 
> Fantastic. Just wondering, what band were you on?
> 
> 
> Bob Nobis 
> n7...@nobis.net 
> 
> 
>> On Jul 7, 2017, at 18:10, Bill Somerville > > wrote:
>> 
>> On 08/07/2017 00:53, Joe Taylor wrote:
>>> To:  Users of FT8 
>>> From:WSJT Development Team 
>>> Subject: IMPORTANT NOTICE ABOUT FT8 
>> HI Joe,
>> 
>> working UFB here, my first FT8 long path QSO using 50W my end:
>> 
>> 010245  Tx  1212 ~  VK6KXW G4WJS IO91
>> 010230 -14  0.7 1189 ~  CQ VK6KXW OF87
>> 010246  Tx  1189 ~  VK6KXW G4WJS IO91
>> 010300 -16  0.2 1189 ~  G4WJS VK6KXW -14
>> 010300 -16  0.2 1189 ~  G4WJS VK6KXW -14
>> 010315  Tx  1189 ~  VK6KXW G4WJS R-16
>> 010330 -16  0.2 1188 ~  G4WJS VK6KXW RRR
>> 010330 -16  0.2 1188 ~  G4WJS VK6KXW RRR
>> 010345  Tx  1189 ~  VK6KXW G4WJS 73
>> 73 Bill G4WJS.
>> 
>> --
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org ! 
>> http://sdm.link/slashdot___ 
>> 
>> wsjt-devel mailing list
>> wsjt-devel@lists.sourceforge.net 
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel 
>> 
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org ! 
> http://sdm.link/slashdot___ 
> 
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net 
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel 
> 
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FT8: IMPORTANT NOTICE

[Dave Clouser]

Thank you Joe and team. looking forward to it.

Dave NZ3M


On 7/7/2017 9:10 PM, Bill Somerville wrote:

On 08/07/2017 00:53, Joe Taylor wrote:

To: Users of FT8
From:WSJT Development Team
Subject: IMPORTANT NOTICE ABOUT FT8


HI Joe,

working UFB here, my first FT8 long path QSO using 50W my end:

010245  Tx  1212 ~  VK6KXW G4WJS IO91

010230 -14  0.7 1189 ~  CQ VK6KXW OF87

010246  Tx  1189 ~  VK6KXW G4WJS IO91

010300 -16  0.2 1189 ~  G4WJS VK6KXW -14

010300 -16  0.2 1189 ~  G4WJS VK6KXW -14

010315  Tx  1189 ~  VK6KXW G4WJS R-16

010330 -16  0.2 1188 ~  G4WJS VK6KXW RRR

010330 -16  0.2 1188 ~  G4WJS VK6KXW RRR

010345  Tx  1189 ~  VK6KXW G4WJS 73

73 Bill G4WJS.



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


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


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FT8: IMPORTANT NOTICE

[Bill Somerville]

On 08/07/2017 02:10, Bill Somerville wrote:

working UFB here


12 US states, 1 VE province, 4 DXCC (K, VE, EI, VK) in less than 90 
minutes on 20m. And we haven't even beta released FT8 yet.


Thanks folks:

US Counties

   confirmed: 0
   worked   : 16

   Count   State  CountyCallsign
 QTHBandMode   Status

   1  ALMARSHALLKQ5S
 Albertville, AL 20M FT8   worked
   2  AL  SHELBY  WB4KDI
  Birmingham, AL 20M FT8   worked
   3  AZMARICOPAAA7A
  Scottsdale, AZ 20M FT8   worked
   4  FL LEEW9BS
  Fort Myers, FL 20M FT8   worked
   5  GA QUITMAN   AI5II
  Georgetown, GA 20M FT8   worked
   6  IL   CHAMPAIGNK9AN
  Urbana, IL 20M FT8   worked
   7  MOCASSNV0O
 Lees Summit, MO 20M FT8   worked
   8  MSHARRISONWQ5L
Gulfport, MS 20M FT8   worked
   9  NJ  MERCERK1JT
   Princeton, NJ 20M FT8   worked
  10  NY MADISON   N2ADV
  Oneida, NY 20M FT8   worked
  11  PA   BUCKS   W2SRH
 Morrisville, PA 20M FT8   worked
  12  PA FAYETTE  KN3ILZ
   Connellsville, PA 20M FT8   worked
  13  PA  MCKEAN  KB3MOW
   Port Allegany, PA 20M FT8   worked
  14  PA MONTOUR   N3JIX
Danville, PA 20M FT8   worked
  15  TXANGELINA   N5SDD
  Huntington, TX 20M FT8   worked
  16  VA HANOVER   K4DET
  Glen Allen, VA 20M FT8   worked

73
Bill
G4WJS.


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FT8: IMPORTANT NOTICE

[Bill Somerville]

On 08/07/2017 00:53, Joe Taylor wrote:

To: Users of FT8
From:WSJT Development Team
Subject: IMPORTANT NOTICE ABOUT FT8


HI Joe,

working UFB here, my first FT8 long path QSO using 50W my end:

010245  Tx  1212 ~  VK6KXW G4WJS IO91

010230 -14  0.7 1189 ~  CQ VK6KXW OF87

010246  Tx  1189 ~  VK6KXW G4WJS IO91

010300 -16  0.2 1189 ~  G4WJS VK6KXW -14

010300 -16  0.2 1189 ~  G4WJS VK6KXW -14

010315  Tx  1189 ~  VK6KXW G4WJS R-16

010330 -16  0.2 1188 ~  G4WJS VK6KXW RRR

010330 -16  0.2 1188 ~  G4WJS VK6KXW RRR

010345  Tx  1189 ~  VK6KXW G4WJS 73

73 Bill G4WJS.

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FT8: IMPORTANT NOTICE

[David Tiller]

Joe and the dev team,

Excellent work! The new-and-improved FT8 is working well. I'm using 7812 on a 
Mac.

One thing I'm seeing, however: I'm getting double decodes when I'm in a QSO. 
For instance:

[cid:25421FA7-3F32-40AC-9BD3-18D564FDDAC7]

Is it just me?

--
David Tiller
Sr. Architect/Lead Consultant | CapTech
(804) 304-0638 | 
dtil...@captechconsulting.com



On Jul 7, 2017, at 7:53 PM, Joe Taylor 
> wrote:

To:  Users of FT8
From:WSJT Development Team
Subject: IMPORTANT NOTICE ABOUT FT8

If you are building WSJT-X for yourself from source code, you may now upgrade 
to r7812 and recompile. You will then have access to the latest version of FT8 
plus some new features for setting default operating frequencies by mode and 
IARU region.  The program built in this way will be called WSJT-X v1.7.1 r7812.

Note that essentially the same program will soon be packaged for wider 
distribution as as "WSJT-X Version 1.8.0-rc1" (release candidate 1), see below).

Remember that FT8 in code revisions 7812 are higher is NOT COMPATIBLE with that 
in 7782 and earlier.  To use FT8 you must upgrade to r7812.
If you see FT8 signals that do not decode, they may be using the obsolete 
protocol.

About the Default Working Frequencies
=

FT8 will likely be popular with MF and HF users as well as the VHF multi-hop 
sporadic-E DXers it was designed for.  After consultation with the user 
community, we have reworked the suggested operating frequency defaults to 
include FT8.  This was not easy on every relevant band; where possible, we have 
suggested a 2 kHz range for exclusive FT8 use. (Exclusivity is important, as 
the T/R period is 15 s which will not mix well with mode that use one-minute 
sequences.)

In general the FT8 frequencies are set 2kHz below the current JT65 allocation.  
This should allow operation using a normal SSB filter width without too much 
interference from strong JT65 signals up the band.  On some bands that has not 
been possible since JT65 sits at the lowest usable narrow band data mode 
frequency, when considering all international band plans.

For the 660 m and 2200 m  bands we have not assigned separate frequencies for 
JT65/JT9/FT8, and just expect users to coordinate themselves.  The numbers of 
active operators will probably be low enough that this will not cause issues.

For 160 m we assume that the JT65 and JT9 sub-bands can be squeezed to
1 kHz each, and FT8 can sit above using up to another 1 kHz.

Previous 80 m use of JT modes has done a disservice to JA operators, who have 
no privileges on the current WSPR/JT65/JT9 allocations.  To correct this we 
have moved the allocations to a part of the band where JAs can operate.  
Obviously this change will impact other non-WSJT-X users, so for now we suggest 
that if you intend to operate on 80 m JT65/JT9/WSPR then you manually change 
the working frequencies in WSJT-X ("Settings->Frequencies") back to the old 
allocations until a general availability release of WSJT-X v1.8.0 is published. 
This will allow time for other software teams to coordinate with us.

The old allocations are:

JT65 3.567 MHz
JT9  3.578 MHz
WSPR 3.5926 MHz

For 6 m we understand that the IARU Region 1 band plan is not to the liking of 
DX chasers around the world and largely ignored by Region 1 users.  However we 
cannot reasonably continue to set working frequency suggestions that drive 
traffic to parts of the band that are not supposed to be used for narrow band 
data modes.  The v1.8.0 release will allow Region-specific working frequencies 
as well as globally coordinated ones.  Consequently we have set the Region 1 
working frequencies roughly in line with the band plan.  If you do not like the 
allocations then do not complain to us, but complain to your Region 1 band 
coordinator along with reasons why you think it should change.  The proposed 
Region 1 working frequencies are usable globally wherever 6m data mode 
operation is permitted so we have set them as global rather than Region 1 
specific.  Region 2 and 3 operators will have both local and global frequencies 
offered.

Other changes are in line with current usage.


Finally, if you are waiting for pre-built installation packages:

We plan to post a release candidate for WSJT-X v1.8.0-rc1 configured for 
Windows, Linux, and OS X very soon -- probably early next week.  Thanks for 
your patience!

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

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FT8: IMPORTANT NOTICE

[Eric Gruff]

My thanks also to Joe and the team. Two QSOs completed so far, and one with
signal levels around -18. No repeats needed, and seems like all working so
far.


NC6K

-Original Message-
From: Dan Malcolm [mailto:dan.malcol...@gmail.com] 
Sent: Friday, July 7, 2017 5:42 PM
To: 'WSJT software development' <wsjt-devel@lists.sourceforge.net>
Subject: Re: [wsjt-devel] FT8: IMPORTANT NOTICE

Thanks Joe.  I know you and your fellow developers have been hard at it, and
we appreciate the effort, and the great results.

One issue I am seeing that during a QSO, my QSO partners replies show up in
Band Activity fine, but get doubled in Rx Frequency.  I have screen shots,
and will provide them if you need them.  Thanks again.

Dan - K4SHQ

-Original Message-
From: Joe Taylor [mailto:j...@princeton.edu]
Sent: Friday, July 07, 2017 6:54 PM
To: WSJT software development <wsjt-devel@lists.sourceforge.net>
Subject: Re: [wsjt-devel] FT8: IMPORTANT NOTICE

To:  Users of FT8
From:WSJT Development Team
Subject: IMPORTANT NOTICE ABOUT FT8

If you are building WSJT-X for yourself from source code, you may now
upgrade to r7812 and recompile. You will then have access to the latest
version of FT8 plus some new features for setting default operating
frequencies by mode and IARU region.  The program built in this way will be
called WSJT-X v1.7.1 r7812.

Note that essentially the same program will soon be packaged for wider
distribution as as "WSJT-X Version 1.8.0-rc1" (release candidate 1), see
below).

Remember that FT8 in code revisions 7812 are higher is NOT COMPATIBLE with
that in 7782 and earlier.  To use FT8 you must upgrade to r7812.
If you see FT8 signals that do not decode, they may be using the obsolete
protocol.

About the Default Working Frequencies
=

FT8 will likely be popular with MF and HF users as well as the VHF multi-hop
sporadic-E DXers it was designed for.  After consultation with the user
community, we have reworked the suggested operating frequency defaults to
include FT8.  This was not easy on every relevant band; where possible, we
have suggested a 2 kHz range for exclusive FT8 use. 
(Exclusivity is important, as the T/R period is 15 s which will not mix well
with mode that use one-minute sequences.)

In general the FT8 frequencies are set 2kHz below the current JT65
allocation.  This should allow operation using a normal SSB filter width
without too much interference from strong JT65 signals up the band.  On some
bands that has not been possible since JT65 sits at the lowest usable narrow
band data mode frequency, when considering all international band plans.

For the 660 m and 2200 m  bands we have not assigned separate frequencies
for JT65/JT9/FT8, and just expect users to coordinate themselves.  The
numbers of active operators will probably be low enough that this will not
cause issues.

For 160 m we assume that the JT65 and JT9 sub-bands can be squeezed to
1 kHz each, and FT8 can sit above using up to another 1 kHz.

Previous 80 m use of JT modes has done a disservice to JA operators, who
have no privileges on the current WSPR/JT65/JT9 allocations.  To correct
this we have moved the allocations to a part of the band where JAs can
operate.  Obviously this change will impact other non-WSJT-X users, so for
now we suggest that if you intend to operate on 80 m JT65/JT9/WSPR then you
manually change the working frequencies in WSJT-X
("Settings->Frequencies") back to the old allocations until a general
availability release of WSJT-X v1.8.0 is published. This will allow time for
other software teams to coordinate with us.

The old allocations are:

JT65 3.567 MHz
JT9  3.578 MHz
WSPR 3.5926 MHz

For 6 m we understand that the IARU Region 1 band plan is not to the liking
of DX chasers around the world and largely ignored by Region 1 users.
However we cannot reasonably continue to set working frequency suggestions
that drive traffic to parts of the band that are not supposed to be used for
narrow band data modes.  The v1.8.0 release will allow Region-specific
working frequencies as well as globally coordinated ones.  Consequently we
have set the Region 1 working frequencies roughly in line with the band
plan.  If you do not like the allocations then do not complain to us, but
complain to your Region 1 band coordinator along with reasons why you think
it should change.  The proposed Region 1 working frequencies are usable
globally wherever 6m data mode operation is permitted so we have set them as
global rather than Region 1 specific.  Region 2 and 3 operators will have
both local and global frequencies offered.

Other changes are in line with current usage.


Finally, if you are waiting for pre-built installation packages:

We plan to post a release candidate for WSJT-X v1.8.0-rc1 configured for
Windows, Linux, and OS X very soon -- probably early next week.  Thanks for
your patience!

 -- 73, Joe, 

Re: [wsjt-devel] FT8: IMPORTANT NOTICE

[Dan Malcolm]

Thanks Joe.  I know you and your fellow developers have been hard at it, and
we appreciate the effort, and the great results.

One issue I am seeing that during a QSO, my QSO partners replies show up in
Band Activity fine, but get doubled in Rx Frequency.  I have screen shots,
and will provide them if you need them.  Thanks again.

Dan - K4SHQ

-Original Message-
From: Joe Taylor [mailto:j...@princeton.edu] 
Sent: Friday, July 07, 2017 6:54 PM
To: WSJT software development <wsjt-devel@lists.sourceforge.net>
Subject: Re: [wsjt-devel] FT8: IMPORTANT NOTICE

To:  Users of FT8
From:WSJT Development Team
Subject: IMPORTANT NOTICE ABOUT FT8

If you are building WSJT-X for yourself from source code, you may now
upgrade to r7812 and recompile. You will then have access to the latest
version of FT8 plus some new features for setting default operating
frequencies by mode and IARU region.  The program built in this way will be
called WSJT-X v1.7.1 r7812.

Note that essentially the same program will soon be packaged for wider
distribution as as "WSJT-X Version 1.8.0-rc1" (release candidate 1), see
below).

Remember that FT8 in code revisions 7812 are higher is NOT COMPATIBLE with
that in 7782 and earlier.  To use FT8 you must upgrade to r7812.
If you see FT8 signals that do not decode, they may be using the obsolete
protocol.

About the Default Working Frequencies
=

FT8 will likely be popular with MF and HF users as well as the VHF multi-hop
sporadic-E DXers it was designed for.  After consultation with the user
community, we have reworked the suggested operating frequency defaults to
include FT8.  This was not easy on every relevant band; where possible, we
have suggested a 2 kHz range for exclusive FT8 use. 
(Exclusivity is important, as the T/R period is 15 s which will not mix well
with mode that use one-minute sequences.)

In general the FT8 frequencies are set 2kHz below the current JT65
allocation.  This should allow operation using a normal SSB filter width
without too much interference from strong JT65 signals up the band.  On some
bands that has not been possible since JT65 sits at the lowest usable narrow
band data mode frequency, when considering all international band plans.

For the 660 m and 2200 m  bands we have not assigned separate frequencies
for JT65/JT9/FT8, and just expect users to coordinate themselves.  The
numbers of active operators will probably be low enough that this will not
cause issues.

For 160 m we assume that the JT65 and JT9 sub-bands can be squeezed to
1 kHz each, and FT8 can sit above using up to another 1 kHz.

Previous 80 m use of JT modes has done a disservice to JA operators, who
have no privileges on the current WSPR/JT65/JT9 allocations.  To correct
this we have moved the allocations to a part of the band where JAs can
operate.  Obviously this change will impact other non-WSJT-X users, so for
now we suggest that if you intend to operate on 80 m JT65/JT9/WSPR then you
manually change the working frequencies in WSJT-X
("Settings->Frequencies") back to the old allocations until a general
availability release of WSJT-X v1.8.0 is published. This will allow time for
other software teams to coordinate with us.

The old allocations are:

JT65 3.567 MHz
JT9  3.578 MHz
WSPR 3.5926 MHz

For 6 m we understand that the IARU Region 1 band plan is not to the liking
of DX chasers around the world and largely ignored by Region 1 users.
However we cannot reasonably continue to set working frequency suggestions
that drive traffic to parts of the band that are not supposed to be used for
narrow band data modes.  The v1.8.0 release will allow Region-specific
working frequencies as well as globally coordinated ones.  Consequently we
have set the Region 1 working frequencies roughly in line with the band
plan.  If you do not like the allocations then do not complain to us, but
complain to your Region 1 band coordinator along with reasons why you think
it should change.  The proposed Region 1 working frequencies are usable
globally wherever 6m data mode operation is permitted so we have set them as
global rather than Region 1 specific.  Region 2 and 3 operators will have
both local and global frequencies offered.

Other changes are in line with current usage.


Finally, if you are waiting for pre-built installation packages:

We plan to post a release candidate for WSJT-X v1.8.0-rc1 configured for
Windows, Linux, and OS X very soon -- probably early next week.  Thanks for
your patience!

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


--
Check out the vibrant tech community on one of the world's most engaging
tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.

Re: [wsjt-devel] FT8: IMPORTANT NOTICE

[Joe Taylor]

To:  Users of FT8
From:WSJT Development Team
Subject: IMPORTANT NOTICE ABOUT FT8

If you are building WSJT-X for yourself from source code, you may now 
upgrade to r7812 and recompile. You will then have access to the latest 
version of FT8 plus some new features for setting default operating 
frequencies by mode and IARU region.  The program built in this way will 
be called WSJT-X v1.7.1 r7812.


Note that essentially the same program will soon be packaged for wider 
distribution as as "WSJT-X Version 1.8.0-rc1" (release candidate 1), see 
below).


Remember that FT8 in code revisions 7812 are higher is NOT COMPATIBLE 
with that in 7782 and earlier.  To use FT8 you must upgrade to r7812.
If you see FT8 signals that do not decode, they may be using the 
obsolete protocol.


About the Default Working Frequencies
=

FT8 will likely be popular with MF and HF users as well as the VHF 
multi-hop sporadic-E DXers it was designed for.  After consultation with 
the user community, we have reworked the suggested operating frequency 
defaults to include FT8.  This was not easy on every relevant band; 
where possible, we have suggested a 2 kHz range for exclusive FT8 use. 
(Exclusivity is important, as the T/R period is 15 s which will not mix 
well with mode that use one-minute sequences.)


In general the FT8 frequencies are set 2kHz below the current JT65 
allocation.  This should allow operation using a normal SSB filter width 
without too much interference from strong JT65 signals up the band.  On 
some bands that has not been possible since JT65 sits at the lowest 
usable narrow band data mode frequency, when considering all 
international band plans.


For the 660 m and 2200 m  bands we have not assigned separate 
frequencies for JT65/JT9/FT8, and just expect users to coordinate 
themselves.  The numbers of active operators will probably be low enough 
that this will not cause issues.


For 160 m we assume that the JT65 and JT9 sub-bands can be squeezed to
1 kHz each, and FT8 can sit above using up to another 1 kHz.

Previous 80 m use of JT modes has done a disservice to JA operators, who 
have no privileges on the current WSPR/JT65/JT9 allocations.  To correct 
this we have moved the allocations to a part of the band where JAs can 
operate.  Obviously this change will impact other non-WSJT-X users, so 
for now we suggest that if you intend to operate on 80 m JT65/JT9/WSPR 
then you manually change the working frequencies in WSJT-X 
("Settings->Frequencies") back to the old allocations until a general 
availability release of WSJT-X v1.8.0 is published. This will allow time 
for other software teams to coordinate with us.


The old allocations are:

JT65 3.567 MHz
JT9  3.578 MHz
WSPR 3.5926 MHz

For 6 m we understand that the IARU Region 1 band plan is not to the 
liking of DX chasers around the world and largely ignored by Region 1 
users.  However we cannot reasonably continue to set working frequency 
suggestions that drive traffic to parts of the band that are not 
supposed to be used for narrow band data modes.  The v1.8.0 release will 
allow Region-specific working frequencies as well as globally 
coordinated ones.  Consequently we have set the Region 1 working 
frequencies roughly in line with the band plan.  If you do not like the 
allocations then do not complain to us, but complain to your Region 1 
band coordinator along with reasons why you think it should change.  The 
proposed Region 1 working frequencies are usable globally wherever 6m 
data mode operation is permitted so we have set them as global rather 
than Region 1 specific.  Region 2 and 3 operators will have both local 
and global frequencies offered.


Other changes are in line with current usage.


Finally, if you are waiting for pre-built installation packages:

We plan to post a release candidate for WSJT-X v1.8.0-rc1 configured for 
Windows, Linux, and OS X very soon -- probably early next week.  Thanks 
for your patience!


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

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FT8: IMPORTANT NOTICE

[charlie]

Thanks, Joe

> Correct.  It's not yet  UTC on July 8.
>
> On 7/7/2017 1:27 PM, char...@sucklingfamily.free-online.co.uk wrote:
>> Hi Joe
>>
>> I think the code in mainwindow.cpp still has the restriction on mycall,
>> in
>> two places.
>>
>> Program does not run unless mycall set to one of the test calls.
>>
>> Charlie
>>
>>> To:  Users of FT8
>>> From:WSJT Development Team
>>> Subject: IMPORTANT NOTICE ABOUT EXPERIMENTAL MODE FT8
>>>
>>> The planned protocol change in FT8 is now complete and tested.
>>> Effective
>>> at  UTC on July 8, 2017, you should stop using FT8 with any WSJT-X
>>> code revision earlier than r7805.
>>>
>>> If you are building WSJT-X for yourself from source code, on July 8 or
>>> later you may upgrade to the latest code revision and recompile. You
>>> will then have access to the latest version of FT8.
>>>
>>> If you are waiting for pre-built installation packages: We plan to post
>>> a release candidate for WSJT-X v1.8.0-rc1 configured for Windows,
>>> Linux,
>>> and OS X very soon -- probably early next week.  Thanks for your
>>> patience.
>>>
>>> -- 73, Joe, K1JT (for the WSJT Development Team)
>>>
>>> --
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>> ___
>>> wsjt-devel mailing list
>>> wsjt-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>>>
>>
>>
>>
>> --
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> ___
>> wsjt-devel mailing list
>> wsjt-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>>
>
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FT8: IMPORTANT NOTICE

[Joe Taylor]

Correct.  It's not yet  UTC on July 8.

On 7/7/2017 1:27 PM, char...@sucklingfamily.free-online.co.uk wrote:

Hi Joe

I think the code in mainwindow.cpp still has the restriction on mycall, in
two places.

Program does not run unless mycall set to one of the test calls.

Charlie


To:  Users of FT8
From:WSJT Development Team
Subject: IMPORTANT NOTICE ABOUT EXPERIMENTAL MODE FT8

The planned protocol change in FT8 is now complete and tested. Effective
at  UTC on July 8, 2017, you should stop using FT8 with any WSJT-X
code revision earlier than r7805.

If you are building WSJT-X for yourself from source code, on July 8 or
later you may upgrade to the latest code revision and recompile. You
will then have access to the latest version of FT8.

If you are waiting for pre-built installation packages: We plan to post
a release candidate for WSJT-X v1.8.0-rc1 configured for Windows, Linux,
and OS X very soon -- probably early next week.  Thanks for your patience.

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

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel





--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FT8: IMPORTANT NOTICE

[charlie]

Hi Joe

I think the code in mainwindow.cpp still has the restriction on mycall, in
two places.

Program does not run unless mycall set to one of the test calls.

Charlie

> To:  Users of FT8
> From:WSJT Development Team
> Subject: IMPORTANT NOTICE ABOUT EXPERIMENTAL MODE FT8
>
> The planned protocol change in FT8 is now complete and tested. Effective
> at  UTC on July 8, 2017, you should stop using FT8 with any WSJT-X
> code revision earlier than r7805.
>
> If you are building WSJT-X for yourself from source code, on July 8 or
> later you may upgrade to the latest code revision and recompile. You
> will then have access to the latest version of FT8.
>
> If you are waiting for pre-built installation packages: We plan to post
> a release candidate for WSJT-X v1.8.0-rc1 configured for Windows, Linux,
> and OS X very soon -- probably early next week.  Thanks for your patience.
>
>   -- 73, Joe, K1JT (for the WSJT Development Team)
>
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FT8: IMPORTANT NOTICE

[Joe Taylor]

To:  Users of FT8
From:WSJT Development Team
Subject: IMPORTANT NOTICE ABOUT EXPERIMENTAL MODE FT8

The planned protocol change in FT8 is now complete and tested. Effective 
at  UTC on July 8, 2017, you should stop using FT8 with any WSJT-X 
code revision earlier than r7805.


If you are building WSJT-X for yourself from source code, on July 8 or 
later you may upgrade to the latest code revision and recompile. You 
will then have access to the latest version of FT8.


If you are waiting for pre-built installation packages: We plan to post 
a release candidate for WSJT-X v1.8.0-rc1 configured for Windows, Linux, 
and OS X very soon -- probably early next week.  Thanks for your patience.


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

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] FT8: IMPORTANT NOTICE

[Joe Taylor]

To:  All WSJT-X users of FT8
From:WSJT Development Team
Subject: IMPORTANT NOTICE ABOUT EXPERIMENTAL MODE FT8

Thanks to all alpha testers who have sent us helpful information on 
their experiences with FT8.  The mode is basically working well, but 
we've determined that we can improve it further by making a change to 
the protocol that is not backward compatible.


Therefore, until further notice: DO NOT USE FT8 MODE IN CODE REVISIONS 
LATER THAN r7782.  In a few days we will issue another notice saying 
that the protocol change is complete and tested. After that time you 
must stop using FT8 mode in revisions r7782 and earlier. EVERYONE USING 
FT8 MUST THEN UPGRADE TO A NEW CODE REVISION WITH A NUMBER TO BE SPECIFIED.


For those not building WSJT-X by themselves: We will plan to release 
WSJT-X v1.8-rc1 very soon after the protocol change.  This release will 
include pre-built installation packages for Windows, Linux, and OS X.


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

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel