Re: [wsjt-devel] FT8 in r7800

[Joe Taylor]

https://physics.princeton.edu/pulsar/k1jt/ft8_Protocol_Change.txt

On 7/6/2017 9:17 PM, David wrote:
Hi ...i have just used JTSDK to upgrade to r7800 compiled 100% but 
when i started WSJT-X it came up with a message "FT8 tempory disabled" 
went to the Mode tab and found FT8 greyed out used JT65 mode and it runs 
okis there a problem with FT8 that required this action


73 David VK4BDJ


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

[wsjt-devel] FT8 in r7800

[David]

Hi ...i have just used JTSDK to upgrade to r7800 compiled 100% but 
when i started WSJT-X it came up with a message "FT8 tempory disabled"  
went to the Mode tab and found FT8 greyed out used JT65 mode and it runs 
okis there a problem with FT8 that required this action


73 David VK4BDJ


--
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] r7781 Observations

[iain macdonnell - N6ML]

On Thu, Jul 6, 2017 at 3:05 PM, Bill Somerville  wrote:
> On 06/07/2017 22:45, Rick wrote:
>>
>> Sidebar question ... while building the latest revision is a matter of
>> updating the svn (push button, computer does all the rest), is there a way
>> to select an earlier release for compilation? I'm using r7781, and probably
>> should have updated to r7782 last evening. Well, that window is closed, as
>> it's no longer the latest release. I'm assuming there is a switch available
>> to specify the correct release, if not the newest, but I can't seem to
>> locate it).
>
>
> HI Rick,
>
> sure you can. If the JTSDK doesn't directly support it, although I think it
> does, you can always achieve that from the command line with the svn
> command:
>
> $ svn update -r 

That works in JTSDK-QT, after doing "cd C:\JTSDK\src\wsjtx"... then do
"build-wsjtx ..." and decline the offer to "Update from SVN Before
Building?"

73,

~iain / N6ML

--
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] WSJT-X: Working frequency suggestions

[Gary McDuffie]

> On Jul 6, 2017, at 3:33 PM, Bill Somerville  wrote:
> 
> If you move that separator down to zero on a band full of JT65 signals you 
> will probably see the problem.

Interestingly, I’ve run 1K separator for quite some time now and I haven’t 
noticed a problem.  However, when I just tried changing it back to 2K, it does 
not stay there.  I do it in one configuration, change to a different 
configuration, come back, and it is back at 1K again.  I also tried changing to 
2K, closing the program and reopening it, and it is back at 1K again.  Not sure 
what the problem is there.  Currently on 7782.

Gary - AG0N
--
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] Frequency calibration - use of RWM Moscow in Europe

[Erik Icket]

Hi, 

When performing the Frequency Calibration using the 3 combined RWM
frequencies  (4.996 , 9.996 and 14.996 MHz), I have observed very consistent
results with the DF typically floating less than 0.2 Hz.

RWM transmit an unmodulated carrier between 0 and 8 minutes past the hour
(as well as 30 mins later). More info can be found at
https://en.wikipedia.org/wiki/RWM

Maybe worth documenting, or including in the FreqCal list, as unmodulated
carriers are not that frequent in the HF spectrum in Europe, and the FreqCal
mode handles them as an absolute breeze.

73's
ON4PB
Erik




--
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] r7781 Observations

[Bill Somerville]

On 06/07/2017 22:45, Rick wrote:

GUI Observations:

Switching configurations does not reset to the appropriate frequency 
if you edit the frequency/mode table. If you reset to the defaults, 
you can switch back and forth, and the radio will follow, however if 
you edit any entry (I changed JT-65 from 50.310 to 50.276) selecting 
the configuration for JT-65 leaves the rig set on the previous frequency.


I run two monitors, and keep a lot of the WSJT-X stuff on the right 
monitor. I have the Log QSO pop-up window set to show on the left 
screen. I have to open any programs I wish to run in the left window, 
and then start WSJT-X in order for the Log QSO screen to show on top. 
It will not pop up on top of any screens opened after WSJT-X. Not sure 
this is a windows 7 issue (64-bit) or something that can be forced. I 
probably should move the Log QSO screen on top of the wide graph as a 
quick fix. 


Hi Rick,

the settings options "Settings->General->Monitor off at startup" and 
"Monitor returns to last used frequency" control the behaviour at 
startup. Switching configurations is exactly equivalent to starting up 
the application when the destination configuration is the last used 
configuration.


The "Log QSO" window is not modal, that is necessary because you may 
want to complete the QSO using the main window before completing the 
logging operation. It should come to the top if you give keyboard focus 
to the WSJT-X main window.


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] r7781 Observations

[Bill Somerville]

On 06/07/2017 22:45, Rick wrote:
Sidebar question ... while building the latest revision is a matter of 
updating the svn (push button, computer does all the rest), is there a 
way to select an earlier release for compilation? I'm using r7781, and 
probably should have updated to r7782 last evening. Well, that window 
is closed, as it's no longer the latest release. I'm assuming there is 
a switch available to specify the correct release, if not the newest, 
but I can't seem to locate it). 


HI Rick,

sure you can. If the JTSDK doesn't directly support it, although I think 
it does, you can always achieve that from the command line with the svn 
command:


$ svn update -r 

where   is the revision you want your source workspace to be at.

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] WSJT-X: Working frequency suggestions

[Bill Somerville]

On 06/07/2017 09:14, Takehiko Tsutsumi wrote:
Finally, it is a great idea to allocate "JT9 on same frequency as 
JT65" on 2200m and 630m. I really wish you to expand this idea up to 
6m band as it is a first step to obsolete JT65 and replace to JT9 
today and FT8 later.  It is the time to deploy this transition to 
encourage newly developed frequency spectrum efficient code usage by 
the recent rapid increase of the traffic. I do not think we will see 
the side effects sharing the spectrum between JT65 and JT9. Am I right?


HI Take san,

thanks for your other comments, that is helpful as we have little 
experience or data modes usage in region 3.


There is a down side to sharing JT9 and JT65 allocations, the JT9 
decoder gets confused by JT65 signals and has to spend a lot of time 
trying to synchronize them as one or more JT9 signals. This detracts 
from the JT9 decoding turnaround. This is why the dual mode JT9+JT65 
decoder expects to decode JT9 signals above the blue separator line. If 
you move that separator down to zero on a band full of JT65 signals you 
will probably see the problem.


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] Frequency measuring modes

[Black Michael via wsjt-devel]

I wonder if the FreqCal frequencies should be removed and then  added to a list 
in the docs.
So when starting FreqCal mode and there are no frequencies defined it tells you 
to go look in the docs for recommendations on how to select calibration 
freqs...along with directions on how to do the calibration.
de Mike W9MDB

  From: David Birnbaum 
 To: wsjt-devel@lists.sourceforge.net 
 Sent: Thursday, July 6, 2017 4:24 PM
 Subject: Re: [wsjt-devel] Frequency measuring modes
   
I know that there are a set of frequencies in the table and most of them are 
useful.  But local AM radio needs to be set for each station and not all the 
time/frequency standard frequencies work for everyone all the time.
db--
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] Frequency measuring modes

[Joe Taylor]

On 7/6/2017 5:23 PM, David Birnbaum wrote:
I know that there are a set of frequencies in the table and most of them 
are useful.  But local AM radio needs to be set for each station and not 
all the time/frequency standard frequencies work for everyone all the time.


db


Delete the ones not useful to you, and enter your own additions.  The 
list is just a set of examples.


-- Joe, K1JT

--
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] Frequency measuring modes

[David Birnbaum]

I know that there are a set of frequencies in the table and most of them
are useful.  But local AM radio needs to be set for each station and not
all the time/frequency standard frequencies work for everyone all the time.

db
--
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] Frequency calibration - use of AM broadcasts

[Richard Lamont]

On 06/07/17 20:58, Joe Taylor wrote:
> Richard --
> 
> On 7/6/2017 3:48 PM, Richard Lamont wrote:
>> Is it a good idea to use AM broadcast transmitters as a frequency
>> standard when the regulatory tolerance (ITU and many countries) for such
>> transmitters is +/- 10 Hz? Is that good enough for the purpose?
>>
>> 73,
>> Richard G4DYA
> 
> As described here
> http://www.physics.princeton.edu/pulsar/K1JT/FMT_User.pdf
> my experience has been that (at least in NA) the carriers of big-city AM
> broadcast stations are "on frequency" to within better than 1 Hz.
> 
> It's always best to over-determine your fitted calibration line by using
> more independent calibrators than the minimum necessary.  Then you can
> reliably identify outliers, and remove them from your analysis.

Well the experiment I've just done certainly bears that out. Using a K3S
+ GPSDO + audio spectrum analyser, I've just measured about several
stations near me and most were within 1 Hz. The others, except one, were
all within 3 Hz. The booby prize goes to BBC Radio Stoke on 1503 kHz,
which was 9 Hz low. Still in spec though.

73,
Richard G4DYA

--
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] Preparation for WSJT-X v1.8.0-rc1

[Black Michael via wsjt-devel]

Pull the qsotime.patch again -- I just posted another one.
At least in my testing it's working for both double clicking QSOs in the Rx 
Freq column and with short modes.
de Mike W9MDB 
  From: Bill Somerville 
 To: wsjt-devel@lists.sourceforge.net 
 Sent: Thursday, July 6, 2017 11:12 AM
 Subject: Re: [wsjt-devel] Preparation for WSJT-X v1.8.0-rc1
   
 On 06/07/2017 17:00, Black Michael via wsjt-devel wrote:
  
 I've got 3 patches outstanding 
  #1 Menu controls working when controls are hidden + CTRL-E/Shift-E shortcuts 
for enabling/disabling Tx even/1st #2 Fix rigctld aborting on rigs without 
set_vfo (e.g. FT-891/991) #3 Fix QSO start times for double-click progression 
and autoseq modes 
  Here they are: 
  https://www.dropbox.com/s/d20ycgqtthckudk/rigctld_setvfo.patch?dl=1
  https://www.dropbox.com/s/frarvcjefhxn5d2/menu.patch?dl=1
  https://www.dropbox.com/s/kr4lcc7rcg00j1i/qsotime.patch?dl=1
  
  de Mike W9MDB 
 Hi Mike, thanks for the reminder. I need to pull the amended version of your 
start and end times and check it it with short T/R periods. I will look at 
those three as well. 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] Frequency measuring mode

[Black Michael via wsjt-devel]

The frequencies are in the freq table in WSJT-X.  Did you know that?  "FreqCal".
de Mike W9MDB

  From: David Birnbaum 
 To: wsjt-devel@lists.sourceforge.net 
 Sent: Thursday, July 6, 2017 3:40 PM
 Subject: [wsjt-devel] Frequency measuring mode
   
I noticed that the frequency measuring mode was in 1.7.0, but it only does 
measurement according to frequencies in table.  The averaging (fmtaverage) and 
calibration calculation (fmeasure) don't seem to be in a menu.  The partial 
integration is only partly useful.  If one wants to use it for setting up rig 
calibration there needs to be some way to pass the data on to the processing 
stream to generate the A and B constants.  If one wants to use it for FMT then 
it would be nice to have some way to enter the nominal FMT frequencies.
davek2lyv--
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] Preparation for WSJT-X v1.8.0-rc1

[Tim Carlson]

Thank you, Michael.  I’ve been confused as to the function of the slider - it 
never seemed to do anything for me because I’ve always left Flatten checked.

It seems like education is needed in either case (leaving it on the main 
window, or moving it to the waterfall window).  In that case, it makes much 
more intuitive sense to move it to the waterfall window and disabling it 
(greyed out) if Flatten is checked (if that’s possible with Qt).

-Tim (KD0GYG)


> On Jul 6, 2017, at 2:05 PM, Black Michael via wsjt-devel 
>  wrote:
> 
> The slider now only controls the waterfall level on both the Fast graph and 
> Wide graph, though if Flatten is checked on the Widegraph than the slider 
> control is not effective.

--
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] Frequency measuring mode

[David Birnbaum]

I noticed that the frequency measuring mode was in 1.7.0, but it only does
measurement according to frequencies in table.  The averaging (fmtaverage)
and calibration calculation (fmeasure) don't seem to be in a menu.  The
partial integration is only partly useful.  If one wants to use it for
setting up rig calibration there needs to be some way to pass the data on
to the processing stream to generate the A and B constants.  If one wants
to use it for FMT then it would be nice to have some way to enter the
nominal FMT frequencies.

dave
k2lyv
--
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] Preparation for WSJT-X v1.8.0-rc1

[Black Michael via wsjt-devel]

That's a good idea...if only the Wide Graph is visible and Flatten checked or 
neither graph is visible then disable the slider.I like it.  Then the question 
will be "why is the slider greyed out" :-)
de Mike W9MDB

  From: Tim Carlson 
 To: Black Michael ; WSJT software development 
 
 Sent: Thursday, July 6, 2017 3:20 PM
 Subject: Re: [wsjt-devel] Preparation for WSJT-X v1.8.0-rc1
   
Thank you, Michael.  I’ve been confused as to the function of the slider - it 
never seemed to do anything for me because I’ve always left Flatten checked.
It seems like education is needed in either case (leaving it on the main 
window, or moving it to the waterfall window).  In that case, it makes much 
more intuitive sense to move it to the waterfall window and disabling it 
(greyed out) if Flatten is checked (if that’s possible with Qt).
-Tim (KD0GYG)



On Jul 6, 2017, at 2:05 PM, Black Michael via wsjt-devel 
 wrote:
The slider now only controls the waterfall level on both the Fast graph and 
Wide graph, though if Flatten is checked on the Widegraph than the slider 
control is not effective.



   --
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] Frequency calibration - use of AM broadcasts

[Richard Lamont]

On 06/07/17 20:56, Bill Somerville wrote:
> On 06/07/2017 20:48, Richard Lamont wrote:
>> Is it a good idea to use AM broadcast transmitters as a frequency
>> standard when the regulatory tolerance (ITU and many countries) for such
>> transmitters is ± 10 Hz? Is that good enough for the purpose?
> 
> Hi Richard,
> 
> I would expect many to be at least GPS locked. Droitwich 198kHz is
> rubidium atomic clock locked at  less than 10e-11 Hz per day accuracy!
> At least until they run out of transmitting valves.

Droitwich 198 kHz is GPS-locked and/or rubidium - not sure which. Always
used to be the latter. But many broadcast transmitters just use
free-running crystal drives. They are not designed to be standard
frequency stations, and there's usually no business case for the
broadcaster to take on that role.

In the UK, the tolerance is tighter in synchronised groups (two stations
carrying the same programme). Otherwise the 10 Hz rule applies. It's in
the Ofcom broadcast specification. 10 Hz is sufficient to ensure that
the beat from a weak co-channel carrier is no more than 20 Hz and thus
sub-audible. For the broadcaster's purpose, that is sufficient.


73,
Richard G4DYA

--
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] Preparation for WSJT-X v1.8.0-rc1

[Joe Taylor]

Hi Al,

On 7/6/2017 3:59 PM, CX8AT VERA wrote:
Maybe I missed something when reading this group's mail, but something 
that I don't like is to have 2 windows (main window and wide graph)  
apart, is hard for me to keep both with the right size in a small wide 
13" notebook,  It is possible to have both just in one windows? this 
maybe imply to reorganize all the commands or there are some other 
reasons to keep them this way. Just a thought.


Al
CX8AT


Using separate windows for the Main Window, Wide Graph, Fast Graph, Echo 
Graph, Astronomical data, and several other specialized windows is 
fundamental to the way WSJT-X is designed.  It provides much more 
flexibility for the use of screen space.  This philosophy will not be 
changed.

-- Joe, K1JT

--
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] Preparation for WSJT-X v1.8.0-rc1

[Black Michael via wsjt-devel]

I don't know if expanding the explanation about the effects of things in the 
docs would help.  Like what NOT to do.Seems most don't read them anyways...but 
maybe we should do it anyways for those that do.
The more education the better IMHO
So instead of
Use the receiver gain controls and/or the computer’s audio mixer controls to 
set the background noise level (scale at lower left of main window) to around 
30 dB when no signals are present. It is usually best to turn AGC off or reduce 
the RF gain control to minimize AGC action.

This instead (comments welcome).
Set your audio card to 0dB.  In Windows you can look at the Levels on the 
Recording device and right-click to get dB scale.  As close to 0dB as you can 
get is what you want.  There should be no gain or attenuation as this is a 
digital control and any gain/attenuation does pretty much nothing.  (Mac and 
Linux directions too should be here).One your audio card is set to 0dB use the 
receiver gain controls and/or external analog audio device control (e.g. 
Signalink) to get 30dB on the meter when no signals are present.   It is 
usually best to turn AGC off or reduce the RF gain control to minimize AGC 
action.  Only analog controls should be used to adjust the incoming signal 
level.
Note:  Version 1.8.0 disconnected the slider from the meter.  The slider never 
did control recording level, it only controlled the waterfall level.  The 
slider now only controls the waterfall level on both the Fast graph and Wide 
graph, though if Flatten is checked on the Widegraph than the slider control is 
not effective.
de Mike W9MDB
  From: Bill Somerville 
 To: wsjt-devel@lists.sourceforge.net 
 Sent: Thursday, July 6, 2017 2:49 PM
 Subject: Re: [wsjt-devel] Preparation for WSJT-X v1.8.0-rc1
   
 On 06/07/2017 20:43, Black Michael via wsjt-devel wrote:
  
 This was discussed a while ago and those users who were using the FastGraph 
wanted to keep the control on the main window. 
  So...preferring usability over confusion was the result and it was decided to 
keep it on the main window. 
  It will be a teaching process and I'm sure we'll get lots of "slider doesn't 
work anymore" -- but the education process is well worth it. If we took it off 
we'd get the same questions except "what happend to the slider" -- still 
requiring the same education. 
  The tooltip on the slider tells you exactly what it does.  Maybe we should 
stick a "THIS DOESN'T CONTROL THE METER ANYMORE" in there...but they still 
wouldn't read the tooltip in all likelihood. 
  Or maybe a splash screen that tells the major differences? 
 HI Mike, my experience and that shown in some posts here is that users will 
still misunderstand and adjust the Windows audio sliders to get the level meter 
around 30 - 40dB. It is a good thing that the level is not too critical as so 
many believe that digital gain controls do something cleverer than simply 
multiplying or dividing the sample values by some factor. Clipped cannot be 
unclipped and in the noise cannot be extracted from the noise by doing that.
  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] Preparation for WSJT-X v1.8.0-rc1

[CX8AT VERA]

Hi Joe

Maybe I missed something when reading this group's mail, but something 
that I don't like is to have 2 windows (main window and wide graph)  
apart, is hard for me to keep both with the right size in a small wide 
13" notebook,  It is possible to have both just in one windows? this 
maybe imply to reorganize all the commands or there are some other 
reasons to keep them this way. Just a thought.


Al
CX8AT


On 06/07/2017 12:46, Joe Taylor wrote:

Hi all,

I'm compiling a list of important new features and other changes that 
will be in WSJT-X v1.8.


1.  New mode called FT8: QSOs 4 times faster than JT9, JT65
2.  New mode for Frequency Calibration
3.  Improved performance of decoders for JT65, QRA64, and MSK144
4.  New utility programs: msk144code, fmeasure, fmtave, fcal, ft8sim,
ft8d.
5.  Options to minimize sizes of Main window and Wide Graph window.
6.  New default table of recommended operating frequencies
7.  Improved CAT control for many rigs, including operation through
Commander and OmniRig
8.  Many minor bug fixes and tweaks to the user interface

Have I omitted anything that should be in this list?

-- Joe, K1JT

-- 


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] Frequency calibration - use of AM broadcasts

[Joe Taylor]

Richard --

On 7/6/2017 3:48 PM, Richard Lamont wrote:

Is it a good idea to use AM broadcast transmitters as a frequency
standard when the regulatory tolerance (ITU and many countries) for such
transmitters is +/- 10 Hz? Is that good enough for the purpose?

73,
Richard G4DYA


As described here
http://www.physics.princeton.edu/pulsar/K1JT/FMT_User.pdf
my experience has been that (at least in NA) the carriers of big-city AM 
broadcast stations are "on frequency" to within better than 1 Hz.


It's always best to over-determine your fitted calibration line by using 
more independent calibrators than the minimum necessary.  Then you can 
reliably identify outliers, and remove them from your analysis.


-- 73, Joe, K1JT

--
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] Frequency calibration - use of AM broadcasts

[Bill Somerville]

On 06/07/2017 20:48, Richard Lamont wrote:

Is it a good idea to use AM broadcast transmitters as a frequency
standard when the regulatory tolerance (ITU and many countries) for such
transmitters is ± 10 Hz? Is that good enough for the purpose?


Hi Richard,

I would expect many to be at least GPS locked. Droitwich 198kHz is 
rubidium atomic clock locked at  less than 10e-11 Hz per day accuracy! 
At least until they run out of transmitting valves.


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] Frequency calibration - use of AM broadcasts

[Jim Brown]

When I was working in BC, and later when looking at stations with an HP 
precision frequency measuring instrument, I regularly saw errors less 
than one Hz on the MF broadcast band with major US stations.


73, Jim K9YC

On 7/6/2017 12:48 PM, Richard Lamont wrote:

Is it a good idea to use AM broadcast transmitters as a frequency
standard when the regulatory tolerance (ITU and many countries) for such
transmitters is ± 10 Hz? Is that good enough for the purpose?




--
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] Preparation for WSJT-X v1.8.0-rc1

[Bill Somerville]

On 06/07/2017 20:43, Black Michael via wsjt-devel wrote:
This was discussed a while ago and those users who were using the 
FastGraph wanted to keep the control on the main window.


So...preferring usability over confusion was the result and it was 
decided to keep it on the main window.


It will be a teaching process and I'm sure we'll get lots of "slider 
doesn't work anymore" -- but the education process is well worth it.
If we took it off we'd get the same questions except "what happend to 
the slider" -- still requiring the same education.


The tooltip on the slider tells you exactly what it does.  Maybe we 
should stick a "THIS DOESN'T CONTROL THE METER ANYMORE" in there...but 
they still wouldn't read the tooltip in all likelihood.


Or maybe a splash screen that tells the major differences?


HI Mike,

my experience and that shown in some posts here is that users will still 
misunderstand and adjust the Windows audio sliders to get the level 
meter around 30 - 40dB. It is a good thing that the level is not too 
critical as so many believe that digital gain controls do something 
cleverer than simply multiplying or dividing the sample values by some 
factor. Clipped cannot be unclipped and in the noise cannot be extracted 
from the noise by doing that.


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

[wsjt-devel] Frequency calibration - use of AM broadcasts

[Richard Lamont]

Is it a good idea to use AM broadcast transmitters as a frequency
standard when the regulatory tolerance (ITU and many countries) for such
transmitters is +/- 10 Hz? Is that good enough for the purpose?

73,
Richard G4DYA

--
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] Preparation for WSJT-X v1.8.0-rc1

[Black Michael via wsjt-devel]

This was discussed a while ago and those users who were using the FastGraph 
wanted to keep the control on the main window.
So...preferring usability over confusion was the result and it was decided to 
keep it on the main window.
It will be a teaching process and I'm sure we'll get lots of "slider doesn't 
work anymore" -- but the education process is well worth it.If we took it off 
we'd get the same questions except "what happend to the slider" -- still 
requiring the same education.
The tooltip on the slider tells you exactly what it does.  Maybe we should 
stick a "THIS DOESN'T CONTROL THE METER ANYMORE" in there...but they still 
wouldn't read the tooltip in all likelihood.
Or maybe a splash screen that tells the major differences?
de Mike W9MDB

  From: George J Molnar 
 To: WSJT software development  
 Sent: Thursday, July 6, 2017 2:28 PM
 Subject: Re: [wsjt-devel] Preparation for WSJT-X v1.8.0-rc1
   
About the former “digital gain” slider - yes, I agree it’s time to move it out 
of the main window. If the functionality is retained in the fast and slow 
graphs, then it can be eliminated entirely. We might want to consider unifying 
the waterfall controls in a pop up that can be hidden once adjusted, leaving 
just a hide/unhide button on the graph/waterfall. 
Like Gary, I don’t adjust it too often once set up on a band.  

George J MolnarNevada, USA
KF2T  @GJMolnar


--
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] Preparation for WSJT-X v1.8.0-rc1

[George J Molnar]

About the former “digital gain” slider - yes, I agree it’s time to move it out 
of the main window. If the functionality is retained in the fast and slow 
graphs, then it can be eliminated entirely. We might want to consider unifying 
the waterfall controls in a pop up that can be hidden once adjusted, leaving 
just a hide/unhide button on the graph/waterfall. 

Like Gary, I don’t adjust it too often once set up on a band.  


George J Molnar
Nevada, USA
KF2T  @GJMolnar



--
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] Preparation for WSJT-X v1.8.0-rc1

[Gary McDuffie]

> On Jul 6, 2017, at 10:07 AM, Black Michael via wsjt-devel 
>  wrote:
> 
> We talked about removing the slider and putting it on the waterfall but some 
> wanted it to remain on the main screen.

Commenting ONLY on this part of it, the slider does seem a bit redundant, and I 
could easily do without it.  I tend to use a set calibration point.  I never 
adjust it because it is set for the particular rig to computer interface on the 
quietest band/frequency, and with the antenna in the quietest direction.  For 
me, this is done on six meters.  When I get to that calibration point, I set 
the slider at mid-scale, as we were instructed, and 0db on the sound card.  
THEN adjust the WG/FG controls for my preferred view and hide the controls.  If 
I go to some frequency or band where the level increases, I decrease it with 
the RF gain for the proper meter reading.  The original set point was with full 
RF Gain.  Remember, I calibrated on the quietest conditions I could fined.  The 
slider never moves once it is set.

Gary - AG0N
--
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] Preparation for WSJT-X v1.8.0-rc1

[Dan Malcolm]

Mike,

I discovered this change and made changes to my soundcard levels.  But I have 
to confess that the slider looks like it controls levels also.  First it is 
adjacent to the level meter on the left bottom, and second it is not labeled.  
Personally if it controls something waterfall it should be on the waterfall.  
In the end though it needs something to indicate that its effect is on the 
waterfall, and there is a tooltip to indicate that.  Perhaps a note in the 
change notes is warrented.

 

From: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] 
Sent: Thursday, July 06, 2017 11:08 AM
To: WSJT software development 
Cc: Black Michael 
Subject: Re: [wsjt-devel] Preparation for WSJT-X v1.8.0-rc1

 

What change?  The meter shows the recording level now instead of the waterfall 
level.  The slider controls the waterfall and not the meter anymore (it never 
should have).

We talked about removing the slider and putting it on the waterfall but some 
wanted it to remain on the main screen.

 

de Mike W9MDB

 

 

  _  

From: "char...@sucklingfamily.free-online.co.uk 
 " 

To: WSJT software development  > 
Sent: Thursday, July 6, 2017 11:00 AM
Subject: Re: [wsjt-devel] Preparation for WSJT-X v1.8.0-rc1

 

Hi Joe

Perhaps worth mentioning the change to the audio level setting to avoid
inadvertent clipping - folks now have to adjust soundcard level controls,
radio level  or external 'attenuator'.

Charlie

  > Hi all,
>
> I'm compiling a list of important new features and other changes that
> will be in WSJT-X v1.8.
>
> 1.  New mode called FT8: QSOs 4 times faster than JT9, JT65
> 2.  New mode for Frequency Calibration
> 3.  Improved performance of decoders for JT65, QRA64, and MSK144
> 4.  New utility programs: msk144code, fmeasure, fmtave, fcal, ft8sim,
>  ft8d.
> 5.  Options to minimize sizes of Main window and Wide Graph window.
> 6.  New default table of recommended operating frequencies
> 7.  Improved CAT control for many rigs, including operation through
>  Commander and OmniRig
> 8.  Many minor bug fixes and tweaks to the user interface
>
> Have I omitted anything that should be in this list?
>
> -- Joe, K1JT
>
> --
> 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] Suggestions for three extra bits in FT8

[Jordan Sherer]

Thanks for the insight, Bill. Is there a writeup of the protocol anywhere
for deeper understanding?

One idea I had after playing around with PSK & FSQ these past few days is
to leverage an extra bit to allow for a QSO centered around freeform
messaging on HF. Specifically, one of those bits to be used as a
"continuation bit" to signal (when true) that the message is split between
multiple transmission blocks. An example:

CQ KN4CRD EM73 (continuation)
WAS CT DE PA (continuation)
WAS NY RI MA (continuation)
CQ KN4CRD EM73 (stop)

or

G4WJS KN4CRD -10 (continuation)
DT -0.5 QSB (continuation)
NAME JORDAN (continuation)
5W INDR MLOOP (continuation)
G4WJS KN4CRD K (stop)

The nice thing is that with the FT8 transmissions, you'd see those
incremental messages come in every 15 seconds. So, it would be a middle
ground between real-time PSK decoding and the one minute delay of JT65.
Transmissions would still be synchronized to the time interval, so there
shouldn't be too much dead air between responses (15 seconds of dead air is
way easier to stomach than 60+).

The other thing that I've been noticing is that with the pace of the FT8
transmissions, repeat messages are coming in frequently because there is a
miss to engage the calling CQ station, or perhaps autoseq was disabled, or
there was some band fading that caused the decoder to missfire. The
continuation bit could be used to synchronize on a 30 second interval with
doubling of every message to ensure delivery:

CQ KN4CRD EM73 (continuation)
CQ KN4CRD EM73 (stop)

or

KN4CRD G4WJS -18 (continuation)
KN4CRD G4WJS -18 (stop)

As above, if you had a reliable signal you would see the first interval
come in (with a continuation indicator, maybe an ellipsis ... in the ui or
something next to the message). That would give the responding station 15
more seconds to write their reply while the second (duplicated)
transmission came in (which would be really useful in freeform text).

I have some other ideas regarding the other bits, but I'd like to dig into
the protocol as it is today before suggesting anything else.

Curious on what y'all think about something like this?

Best,
Jordan
KN4CRD






On Thu, Jul 6, 2017 at 9:47 AM, Bill Somerville 
wrote:

> On 06/07/2017 14:26, James Lemley wrote:
>
>> After discarding the idea of encoding eight humorous messages, and
>> without studying the rest of the protocol to see if these are already
>> implemented, here are my suggestions for the three extra bits with a
>> transmit frame:
>>
>
> HI James,
>
> adding extra ad hoc messages can be easily done by using some of the
> unused existing message space. For example the directional CQ messages were
> inserted by using the unused callsign series E9xx. These sort of things
> require no extra bits, just global agreement.
>
> With respect to your other suggestions, in the protocols as they stand
> every standard message except the 73 one expects acknowledgement. The 73
> and free text messages do not expect acknowledgement although some free
> text messages can be constructed to imply acknowledgement is expected,
> "REPORT PSE?" for example. When acknowledgement is not received then simply
> repeating the last message until acknowledgement is received is all that is
> needed. It is unfortunate that many users wish to shorten the QSO sequences
> without regard for the above. There are some cases for dropping messages
> like the initial grid reply to a CQ when propagation is unstable.
>
> I believe you are not thinking far enough outside the box with how an
> extra bit may be used. For example the current protocol is partitioned into
> two by a single bit. One half encompasses every standard message and the
> other half encompasses all the free text messages. A single extra bit opens
> up the possibility of a whole new protocol with a message space as large as
> the existing protocol. Using one or more extra bits to add value to the
> existing protcol would be missing a huge opportunity.
>
> 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] Preparation for WSJT-X v1.8.0-rc1

[Black Michael via wsjt-devel]

The slider NEVER affected recording level and caused far too many problems with 
misinterpretation.
What you see on the meter IS the recording level and it cannot and should not 
be changed from WSJT-X as that would all be in the digital space where you 
don't want to touch things.
You want 0dB on the gain in your sound card and then adjust the rig audio to 
get the 30dB minimum level.  WJST-X shows you the result of those two things 
and that's the only two things that need adjusting.
de Mike W9MDB 
  From: "char...@sucklingfamily.free-online.co.uk" 

 To: Black Michael ; WSJT software development 
 
 Sent: Thursday, July 6, 2017 11:19 AM
 Subject: Re: [wsjt-devel] Preparation for WSJT-X v1.8.0-rc1
   
Mike

The change that disconnected the thermometer from the waterfall slider.

A number of folks set the input audio at any old level and adjusted the
slider to get the thermometer mid range.  The change will force
appropriate level adjustment.

73

Charlie

> What change?  The meter shows the recording level now instead of the
> waterfall level.  The slider controls the waterfall and not the meter
> anymore (it never should have).We talked about removing the slider and
> putting it on the waterfall but some wanted it to remain on the main
> screen.
> de Mike W9MDB
>
>      From: "char...@sucklingfamily.free-online.co.uk"
> 
>  To: WSJT software development 
>  Sent: Thursday, July 6, 2017 11:00 AM
>  Subject: Re: [wsjt-devel] Preparation for WSJT-X v1.8.0-rc1
>
> Hi Joe
>
> Perhaps worth mentioning the change to the audio level setting to avoid
> inadvertent clipping - folks now have to adjust soundcard level controls,
> radio level  or external 'attenuator'.
>
> Charlie
>
>   > Hi all,
>>
>> I'm compiling a list of important new features and other changes that
>> will be in WSJT-X v1.8.
>>
>> 1.  New mode called FT8: QSOs 4 times faster than JT9, JT65
>> 2.  New mode for Frequency Calibration
>> 3.  Improved performance of decoders for JT65, QRA64, and MSK144
>> 4.  New utility programs: msk144code, fmeasure, fmtave, fcal, ft8sim,
>>      ft8d.
>> 5.  Options to minimize sizes of Main window and Wide Graph window.
>> 6.  New default table of recommended operating frequencies
>> 7.  Improved CAT control for many rigs, including operation through
>>      Commander and OmniRig
>> 8.  Many minor bug fixes and tweaks to the user interface
>>
>> Have I omitted anything that should be in this list?
>>
>>     -- Joe, K1JT
>>
>> --
>> 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] Preparation for WSJT-X v1.8.0-rc1

[Black Michael via wsjt-devel]

I'll agree that automating the freq cal would be good.
It's not real simple to make it foolproof. Since it's a linear correction I 
think only two or three points at most are needed just using WWV and one AM 
station would be good but not necessary.  The AM station would have to be 
manually entered unless we came up with a searchable list based on your grid 
location.  Or some other "in your face" prompt to force you to enter one.
The default Freq Cal stations int the AM band should be removed as they could 
easily overlap in places and provide bad results.
de Mike W9MDB


  From: Steven Franke 
 To: Joe Taylor  
 Sent: Thursday, July 6, 2017 10:57 AM
 Subject: Re: [wsjt-devel] Preparation for WSJT-X v1.8.0-rc1
   
The following come to mind:

- Phase and amplitude equalization for MSK144. (We/I need to fix the refspec 
part of this, and also write up some docs)
- SWL mode for MSK144 allows third-party monitoring Sh-message QSOs.
- Enhanced frequency management scheme (Bill should contribute the proper 
description).

I still think that it would be very useful if we could further automate the 
fmeasure/fmtave/fcal stuff so that it is as simple as pushing a button… But 
realistically, that may be something for when the snow is flying.

Steve, k9an


> On Jul 6, 2017, at 3:46 PM, Joe Taylor  wrote:
> 
> Hi all,
> 
> I'm compiling a list of important new features and other changes that will be 
> in WSJT-X v1.8.
> 
> 1.  New mode called FT8: QSOs 4 times faster than JT9, JT65
> 2.  New mode for Frequency Calibration
> 3.  Improved performance of decoders for JT65, QRA64, and MSK144
> 4.  New utility programs: msk144code, fmeasure, fmtave, fcal, ft8sim,
>    ft8d.
> 5.  Options to minimize sizes of Main window and Wide Graph window.
> 6.  New default table of recommended operating frequencies
> 7.  Improved CAT control for many rigs, including operation through
>    Commander and OmniRig
> 8.  Many minor bug fixes and tweaks to the user interface
> 
> Have I omitted anything that should be in this list?
> 
>     -- Joe, K1JT
> 
> --
> 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] Preparation for WSJT-X v1.8.0-rc1

[charlie]

Mike

The change that disconnected the thermometer from the waterfall slider.

A number of folks set the input audio at any old level and adjusted the
slider to get the thermometer mid range.  The change will force
appropriate level adjustment.

73

Charlie

> What change?  The meter shows the recording level now instead of the
> waterfall level.  The slider controls the waterfall and not the meter
> anymore (it never should have).We talked about removing the slider and
> putting it on the waterfall but some wanted it to remain on the main
> screen.
> de Mike W9MDB
>
>   From: "char...@sucklingfamily.free-online.co.uk"
> 
>  To: WSJT software development 
>  Sent: Thursday, July 6, 2017 11:00 AM
>  Subject: Re: [wsjt-devel] Preparation for WSJT-X v1.8.0-rc1
>
> Hi Joe
>
> Perhaps worth mentioning the change to the audio level setting to avoid
> inadvertent clipping - folks now have to adjust soundcard level controls,
> radio level  or external 'attenuator'.
>
> Charlie
>
>   > Hi all,
>>
>> I'm compiling a list of important new features and other changes that
>> will be in WSJT-X v1.8.
>>
>> 1.  New mode called FT8: QSOs 4 times faster than JT9, JT65
>> 2.  New mode for Frequency Calibration
>> 3.  Improved performance of decoders for JT65, QRA64, and MSK144
>> 4.  New utility programs: msk144code, fmeasure, fmtave, fcal, ft8sim,
>>      ft8d.
>> 5.  Options to minimize sizes of Main window and Wide Graph window.
>> 6.  New default table of recommended operating frequencies
>> 7.  Improved CAT control for many rigs, including operation through
>>      Commander and OmniRig
>> 8.  Many minor bug fixes and tweaks to the user interface
>>
>> Have I omitted anything that should be in this list?
>>
>>     -- Joe, K1JT
>>
>> --
>> 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] Preparation for WSJT-X v1.8.0-rc1

[Bill Somerville]

On 06/07/2017 17:00, Black Michael via wsjt-devel wrote:

I've got 3 patches outstanding

#1 Menu controls working when controls are hidden + CTRL-E/Shift-E 
shortcuts for enabling/disabling Tx even/1st

#2 Fix rigctld aborting on rigs without set_vfo (e.g. FT-891/991)
#3 Fix QSO start times for double-click progression and autoseq modes

Here they are:

https://www.dropbox.com/s/d20ycgqtthckudk/rigctld_setvfo.patch?dl=1
https://www.dropbox.com/s/frarvcjefhxn5d2/menu.patch?dl=1
https://www.dropbox.com/s/kr4lcc7rcg00j1i/qsotime.patch?dl=1

de Mike W9MDB


Hi Mike,

thanks for the reminder. I need to pull the amended version of your 
start and end times and check it it with short T/R periods. I will look 
at those three as well.


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] Preparation for WSJT-X v1.8.0-rc1

[Black Michael via wsjt-devel]

What change?  The meter shows the recording level now instead of the waterfall 
level.  The slider controls the waterfall and not the meter anymore (it never 
should have).We talked about removing the slider and putting it on the 
waterfall but some wanted it to remain on the main screen.
de Mike W9MDB

  From: "char...@sucklingfamily.free-online.co.uk" 

 To: WSJT software development  
 Sent: Thursday, July 6, 2017 11:00 AM
 Subject: Re: [wsjt-devel] Preparation for WSJT-X v1.8.0-rc1
   
Hi Joe

Perhaps worth mentioning the change to the audio level setting to avoid
inadvertent clipping - folks now have to adjust soundcard level controls,
radio level  or external 'attenuator'.

Charlie

  > Hi all,
>
> I'm compiling a list of important new features and other changes that
> will be in WSJT-X v1.8.
>
> 1.  New mode called FT8: QSOs 4 times faster than JT9, JT65
> 2.  New mode for Frequency Calibration
> 3.  Improved performance of decoders for JT65, QRA64, and MSK144
> 4.  New utility programs: msk144code, fmeasure, fmtave, fcal, ft8sim,
>      ft8d.
> 5.  Options to minimize sizes of Main window and Wide Graph window.
> 6.  New default table of recommended operating frequencies
> 7.  Improved CAT control for many rigs, including operation through
>      Commander and OmniRig
> 8.  Many minor bug fixes and tweaks to the user interface
>
> Have I omitted anything that should be in this list?
>
>     -- Joe, K1JT
>
> --
> 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] Preparation for WSJT-X v1.8.0-rc1

[Black Michael via wsjt-devel]

I've got 3 patches outstanding
#1 Menu controls working when controls are hidden + CTRL-E/Shift-E shortcuts 
for enabling/disabling Tx even/1st#2 Fix rigctld aborting on rigs without 
set_vfo (e.g. FT-891/991)#3 Fix QSO start times for double-click progression 
and autoseq modes
Here they are:
https://www.dropbox.com/s/d20ycgqtthckudk/rigctld_setvfo.patch?dl=1
https://www.dropbox.com/s/frarvcjefhxn5d2/menu.patch?dl=1
https://www.dropbox.com/s/kr4lcc7rcg00j1i/qsotime.patch?dl=1

de Mike W9MDB



  From: Joe Taylor 
 To: wsjt-devel@lists.sourceforge.net 
 Sent: Thursday, July 6, 2017 10:49 AM
 Subject: [wsjt-devel] Preparation for WSJT-X v1.8.0-rc1
   
Hi all,

I'm compiling a list of important new features and other changes that 
will be in WSJT-X v1.8.

1.  New mode called FT8: QSOs 4 times faster than JT9, JT65
2.  New mode for Frequency Calibration
3.  Improved performance of decoders for JT65, QRA64, and MSK144
4.  New utility programs: msk144code, fmeasure, fmtave, fcal, ft8sim,
    ft8d.
5.  Options to minimize sizes of Main window and Wide Graph window.
6.  New default table of recommended operating frequencies
7.  Improved CAT control for many rigs, including operation through
    Commander and OmniRig
8.  Many minor bug fixes and tweaks to the user interface

Have I omitted anything that should be in this list?

    -- Joe, K1JT

--
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] Preparation for WSJT-X v1.8.0-rc1

[charlie]

Hi Joe

Perhaps worth mentioning the change to the audio level setting to avoid
inadvertent clipping - folks now have to adjust soundcard level controls,
radio level  or external 'attenuator'.

Charlie

  > Hi all,
>
> I'm compiling a list of important new features and other changes that
> will be in WSJT-X v1.8.
>
> 1.  New mode called FT8: QSOs 4 times faster than JT9, JT65
> 2.  New mode for Frequency Calibration
> 3.  Improved performance of decoders for JT65, QRA64, and MSK144
> 4.  New utility programs: msk144code, fmeasure, fmtave, fcal, ft8sim,
>  ft8d.
> 5.  Options to minimize sizes of Main window and Wide Graph window.
> 6.  New default table of recommended operating frequencies
> 7.  Improved CAT control for many rigs, including operation through
>  Commander and OmniRig
> 8.  Many minor bug fixes and tweaks to the user interface
>
> Have I omitted anything that should be in this list?
>
>   -- Joe, K1JT
>
> --
> 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] Preparation for WSJT-X v1.8.0-rc1

[Steven Franke]

The following come to mind:

- Phase and amplitude equalization for MSK144. (We/I need to fix the refspec 
part of this, and also write up some docs)
- SWL mode for MSK144 allows third-party monitoring Sh-message QSOs.
- Enhanced frequency management scheme (Bill should contribute the proper 
description).

I still think that it would be very useful if we could further automate the 
fmeasure/fmtave/fcal stuff so that it is as simple as pushing a button… But 
realistically, that may be something for when the snow is flying.

Steve, k9an


> On Jul 6, 2017, at 3:46 PM, Joe Taylor  wrote:
> 
> Hi all,
> 
> I'm compiling a list of important new features and other changes that will be 
> in WSJT-X v1.8.
> 
> 1.  New mode called FT8: QSOs 4 times faster than JT9, JT65
> 2.  New mode for Frequency Calibration
> 3.  Improved performance of decoders for JT65, QRA64, and MSK144
> 4.  New utility programs: msk144code, fmeasure, fmtave, fcal, ft8sim,
>ft8d.
> 5.  Options to minimize sizes of Main window and Wide Graph window.
> 6.  New default table of recommended operating frequencies
> 7.  Improved CAT control for many rigs, including operation through
>Commander and OmniRig
> 8.  Many minor bug fixes and tweaks to the user interface
> 
> Have I omitted anything that should be in this list?
> 
>   -- Joe, K1JT
> 
> --
> 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

[wsjt-devel] Preparation for WSJT-X v1.8.0-rc1

[Joe Taylor]

Hi all,

I'm compiling a list of important new features and other changes that 
will be in WSJT-X v1.8.


1.  New mode called FT8: QSOs 4 times faster than JT9, JT65
2.  New mode for Frequency Calibration
3.  Improved performance of decoders for JT65, QRA64, and MSK144
4.  New utility programs: msk144code, fmeasure, fmtave, fcal, ft8sim,
ft8d.
5.  Options to minimize sizes of Main window and Wide Graph window.
6.  New default table of recommended operating frequencies
7.  Improved CAT control for many rigs, including operation through
Commander and OmniRig
8.  Many minor bug fixes and tweaks to the user interface

Have I omitted anything that should be in this list?

-- Joe, K1JT

--
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] Suggestions for three extra bits in FT8

[Bill Somerville]

On 06/07/2017 14:26, James Lemley wrote:
After discarding the idea of encoding eight humorous messages, and 
without studying the rest of the protocol to see if these are already 
implemented, here are my suggestions for the three extra bits with a 
transmit frame:


HI James,

adding extra ad hoc messages can be easily done by using some of the 
unused existing message space. For example the directional CQ messages 
were inserted by using the unused callsign series E9xx. These sort of 
things require no extra bits, just global agreement.


With respect to your other suggestions, in the protocols as they stand 
every standard message except the 73 one expects acknowledgement. The 73 
and free text messages do not expect acknowledgement although some free 
text messages can be constructed to imply acknowledgement is expected, 
"REPORT PSE?" for example. When acknowledgement is not received then 
simply repeating the last message until acknowledgement is received is 
all that is needed. It is unfortunate that many users wish to shorten 
the QSO sequences without regard for the above. There are some cases for 
dropping messages like the initial grid reply to a CQ when propagation 
is unstable.


I believe you are not thinking far enough outside the box with how an 
extra bit may be used. For example the current protocol is partitioned 
into two by a single bit. One half encompasses every standard message 
and the other half encompasses all the free text messages. A single 
extra bit opens up the possibility of a whole new protocol with a 
message space as large as the existing protocol. Using one or more extra 
bits to add value to the existing protcol would be missing a huge 
opportunity.


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

[wsjt-devel] Suggestions for three extra bits in FT8

[James Lemley]

After discarding the idea of encoding eight humorous messages, and without
studying the rest of the protocol to see if these are already implemented,
here are my suggestions for the three extra bits with a transmit frame:

Bit 0:  Must this message be acknowledged?  Some people get worked up about
what constitutes a QSO or a valid contest exchange. This bit would allow
them to define the rules on their terms.
Bit 0, value 0:  This message has a requirement to be acknowledged, unless
it is the final 73 in an exchange.
Bit 0, value 1:  This message has no requirement to be acknowledged.

Bit 1: Was the last message received as expected?  This would eliminate
messages such as "MY REPORT PLS", by telling the receiving station
automatically if what was expected in the last expected frame was received
or not.  I haven't proven to myself the utility of this bit but thought it
deserved consideration.
Bit 1, value 0:  Your last message was received as expected / I acknowledge
your last message
Bit 1, value 1:  Your last expected message was not received / I cannot
acknowledge your last message

Bit 2:  Is this message part of the defined sequence or an additional or
alternate message? This would allow required contest exchange messages to
be inserted into the order without tripping anyone up. Call signs would not
be required since it would typically be inserted in the middle of an
established QSO, and bit 0 would define if it must be acknowledged or may
be skipped.
Bit 2, value 0: This message is part of the defined sequence for this
protocol.
Bit 2, value 1:  This message is outside the defined sequence for this
protocol.

In all cases, value 0 in these bits does what we would expect, so software
that doesn't implement these three bits will continue to work normally for
a time. In the case of contests, additional messages with free-form data
that must be acknowledged can be defined and even substituted for the R-01
message if the contest does not require a signal report exchange. And,
assuming rules allow or CW-ID is implemented, an additional message such as
"FT817 5W DPOL" could be added and tagged as not needing to be
acknowledged.

Just ideas; feel free to poke holes.
James K5DRU
--
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

Re: [wsjt-devel] FT8: CW ID not a good idea

[Richard Bown]

Hi All
re 
"Morse code speeds are conventionally defined in a very precise way. See, for 
example, http://www.kent-engineers.com/codespeed.htm . 

The width of the main spectral lobe of a CW signal in Hz is roughly equal to 
the speed in WPM.  Fairly strong secondary lobes occur at multiples of this 
number.  Sending the CW ID at (say) 100 WPM, in order to squeze it into a 15 s 
Tx interval, would make the CW ID much wider than an FT8 signal. 

Most likely we will implement CW ID as a separate, dedicated transmission when 
the T/R sequence length is less than 30 s. 

NB: Since June 15, 1983 FCC does NOT require US amateurs to use a CWID with 
data modes. "

That is a convention only
As far as I know, but this might have changed since your last presidential 
election, but Kent
Engineering is not a legislative body., and there are several different morse 
alphabets apart from
latin characters.
And as Joe also says there is no legal requirement in the US for data modes.
For a convention to become law in a country it must be ratified by that 
countries legislative body,
I seriously doubt if the majority of amateurs really understand their licence 
requirements.
So in my opinion leave cw ident out.

-- 
-- 
Best wishes /73 
Richard Bown

Email : rich...@g8jvm.com
HTTP  :  http://www.g8jvm.com
nil carborundum a illegitemis
##
Ham Call: G8JVM . QRV: 50-432 MHz + Microwave 23 cms 140W, 13 cms 100W & 3cms 5W
Maidenhead QRA: IO82SP38, LAT. 52 39.720' N LONG. 2 28.171 W
QRV VHF 6mtrs 200W, 4 mtrs 150W, 2mtrs 400W, 70cms 200W
OS: Linux Mint 18.1  x86_64 on a Dell Inspiron N5030 laptop
##
 


--
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] WSJT-X: Working frequency suggestions

[Takehiko Tsutsumi]

Bill,

Thank you for compiling such a precise list concerning default working 
frequency suggestions.  I am indeed impressed by you professional manner.


Here is my comments presented in your list.

1. 80m:

Thank you for including my proposal. JARL has spent a few years to have 
international harmonized spectrum allocation on 80m and they finally 
opened 3.570-3.575MHz segment for us last year. Therefore, I am very 
much appreciated if you will move all frequencies moved down 6kHz. I 
agree with you that firmware device such as "WSPRLite" may need longer 
transition period or delay the closing date of the current working 
frequency for WSPR. But this is deployment plan of each code and can be 
separately or individually discussed.


2. 160m:

As you described, it is difficult to "cover IARU region 3" even for me 
as I, individually, can not be a member of the organization. Thus, 
neither I do know their latest bandplan for narrow band data service on 
160m. However, It is true that JARL band plan allocates 1907.5-1912.5MHz 
today but everybody know it lacks the international harmonization. 
Therefore, I personally believe it is enough the rest of the world knows 
that JA will operate at 1907.5-1912.5MHz until JARL will obtain 
1836-1846MHz chunk for radio amateur data service in future.


3. 2m:

I do not know IARU Region 3 allocation on 2m for MSK144. But I do not 
think there would be high demand for MSK144 service on 2m by the reason 
that 6m, which is better spectrum for MSK144, is available from JA 
perspective.


Finally, it is a great idea to allocate "JT9 on same frequency as JT65" 
on 2200m and 630m. I really wish you to expand this idea up to 6m band 
as it is a first step to obsolete JT65 and replace to JT9 today and FT8 
later.  It is the time to deploy this transition to encourage newly 
developed frequency spectrum efficient code usage by the recent rapid 
increase of the traffic. I do not think we will see the side effects 
sharing the spectrum between JT65 and JT9. Am I right?


Regards,

take

de JA5AEA


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