Re: [wsjt-devel] Feature request: Contest name

[Jim Brown via wsjt-devel]

On 10/15/2022 2:13 AM, Saku via wsjt-devel wrote:

Linux has Wine, but I do not have any need to run Windoze programs via it.


It seems that you might need it. You're asking for features to be added 
to WSJT-X that are in Windows software. An operating system is a tool, 
not a religion. Or perhaps you might write an app in Linux to do what 
you want.


73, Jim K9YC




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

Re: [wsjt-devel] Feature request: Contest name

[Saku via wsjt-devel]

HI Larry!

I am a Linux user.
I worked last 15 years with Windoze servers and clients versions up to 
W7. When retired I do not have any need to touch them any more. Linux 
has Wine, but I do not have any need to run Windoze programs via it.


Cqrlog has it all. And what it does not have I can program to it.

Now it is just a question that if user could define a contest name at 
WSJT-X end and that would be transferred via UDP datagram to external 
logging program there would be no need to fix those entries in log later on.


Now the UDP datagram sends those default, fixed, contest names that are 
in "settings/Advanced/Special operating activity".


Of course I could fix this at Cqrlog's side with few lines of code, but 
I prefer that the origin of qso data (I.E. WSJT-X) should offer this as 
user defined option. It already has fields like "operator" and 
"Propagation mode" , so why not "contest name" ?



(This will be my last reply of this subject for this list. PM to 
continue discussion)


--
Saku
OH1KH



Larry Banks via wsjt-devel kirjoitti 14.10.2022 klo 16.23:

Hi Saku,

It is much easier to use a proper contest logging program. There are 
many out there.  I use the programs from N3FJP -- they are easy to set 
up and use.  They do everything you need.


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

Re: [wsjt-devel] Feature request: Contest name

[Lance Collister, W7GJ via wsjt-devel]

You might want to take a look at the WSJT-X_IMPROVED version by DG2YCB - you can 
label the contest names however you want. GL and VY 73, Lance


On 10/14/2022 08:29:59, Saku via wsjt-devel wrote:

Hi!

Sorry if this feature exist. I did not find a mention about it from user guide.

There are now several contests that use WSJT-X contest modes. It would be nice to 
have user defined contest name to logging window.
That way name logged (also via UDP message) could be set by contest. And maybe also 
add a date to name if several contests are kept in same external log making them 
easier to find by the name of contest.


Just worked contest "NAC-6m_10/2022" that uses EU VHF mode. So my external log has 
now contest name "NAC-6m_10/2022" with all CW and SSB qsos, but "EU VHF" with FT8 
qsos that have to be changed manually afterwards.


Good place for contest name would be either:

Make "operator" column smaller and set "contest name" after that on right side.

or

Below "propagation mode".

In both cases "retain" checbox is needed too.


Thanks!


--
Lance Collister, W7GJ(ex WA3GPL, WA1JXN, WA1JXN/C6A, ZF2OC/ZF8, E51SIX, 3D2LR, 
5W0GJ, E6M, TX5K, KH8/W7GJ, V6M, T8GJ, VK9CGJ, VK9XGJ, C21GJ, CP1GJ, S79GJ, 
TX7MB, TO7GJ)
P.O. Box 73
Frenchtown, MT   59834-0073
USA
TEL: (406) 626-5728
QTH: DN27ub
URL: http://www.bigskyspaces.com/w7gj
Skype: lanceW7GJ
2m DXCC #11 - 6m DXCC #815 - FFMA #7

Interested in 6m EME?  Ask me about subscribing to the new Magic Band EME
email group, or just fill in the request box at the bottom of my web
page (above)!



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

Re: [wsjt-devel] Feature request: Contest name

[Larry Banks via wsjt-devel]

Hi Saku,

It is much easier to use a proper contest logging program. There are 
many out there.  I use the programs from N3FJP -- they are easy to set 
up and use.  They do everything you need.


Larry / W1DYJ


On 10/14/2022 4:29, Saku via wsjt-devel wrote:

Hi!

Sorry if this feature exist. I did not find a mention about it from 
user guide.


There are now several contests that use WSJT-X contest modes. It would 
be nice to have user defined contest name to logging window.
That way name logged (also via UDP message) could be set by contest. 
And maybe also add a date to name if several contests are kept in same 
external log making them easier to find by the name of contest.


Just worked contest "NAC-6m_10/2022" that uses EU VHF mode. So my 
external log has now contest name "NAC-6m_10/2022" with all CW and SSB 
qsos, but "EU VHF" with FT8 qsos that have to be changed manually 
afterwards.


Good place for contest name would be either:

Make "operator" column smaller and set "contest name" after that on 
right side.


or

Below "propagation mode".

In both cases "retain" checbox is needed too.


Thanks!

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

Re: [wsjt-devel] Feature request: Contest name

[Black Michael via wsjt-devel]

There is a CONTEST_ID ADIF field.  But NAC-6M is not one of the enumerations.  
Does is need to be added or is there another name for 
it?https://adif.org/313/ADIF_313.htm#Contest_ID

As for date doesn't the QSO date do the job?
Mike W9MDB 

On Friday, October 14, 2022 at 03:39:13 AM CDT, Saku via wsjt-devel 
 wrote:  
 
 Hi!

Sorry if this feature exist. I did not find a mention about it from user 
guide.

There are now several contests that use WSJT-X contest modes. It would 
be nice to have user defined contest name to logging window.
That way name logged (also via UDP message) could be set by contest. And 
maybe also add a date to name if several contests are kept in same 
external log making them easier to find by the name of contest.

Just worked contest "NAC-6m_10/2022" that uses EU VHF mode. So my 
external log has now contest name "NAC-6m_10/2022" with all CW and SSB 
qsos, but "EU VHF" with FT8 qsos that have to be changed manually 
afterwards.

Good place for contest name would be either:

Make "operator" column smaller and set "contest name" after that on 
right side.

or

Below "propagation mode".

In both cases "retain" checbox is needed too.


Thanks!

-- 
Saku
OH1KH



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

Re: [wsjt-devel] Feature request: Contest name

[Black Michael via wsjt-devel]

What incorrect name is being sent?  Can you show an example?
Mike W9MDB

 

On Friday, October 14, 2022 at 05:41:48 AM CDT, Saku via wsjt-devel 
 wrote:  
 
 HI Jim!

No Windozes in house.

I use Cqrlog for logging and at the moment WSJT-X is sending a contest 
name in UDP logging frame to Cqrlog that can not be defined.
That's why I always need to fix contest names of FT8 qsos afterwards 
with Cqrlog's group edit to be similar with all other modes used in contest.

It would be lovely to define correct name already at WSJT-X logging 
window and retain that.

Jim Brown via wsjt-devel kirjoitti 14.10.2022 klo 12.13:
> Hi Saku,
>
> There are logging programs that keep track of contests. I log contests 
> with N1MM+ (Freeware), export the log to DXKeeper (FREEware), choose 
> from a dropdown menu in the DXKeeper Import screen what contest it's 
> from and choose the log file. That's all it takes! And when you're 
> ready to upload to LOTW, eQSL, or ClubLog, DXKeeper does that with a 
> button-push once you've set yourself up those logging sites.
>
> I suspect that other logging programs also do some or all of this; I 
> have more than 300,000 QSOs in DXKeeper since getting back on the air 
> in 2003.
>
> 73, Jim K9YC 

-- 
Saku
OH1KH



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

Re: [wsjt-devel] Feature request: Contest name

[Saku via wsjt-devel]

HI Jim!

No Windozes in house.

I use Cqrlog for logging and at the moment WSJT-X is sending a contest 
name in UDP logging frame to Cqrlog that can not be defined.
That's why I always need to fix contest names of FT8 qsos afterwards 
with Cqrlog's group edit to be similar with all other modes used in contest.


It would be lovely to define correct name already at WSJT-X logging 
window and retain that.


Jim Brown via wsjt-devel kirjoitti 14.10.2022 klo 12.13:

Hi Saku,

There are logging programs that keep track of contests. I log contests 
with N1MM+ (Freeware), export the log to DXKeeper (FREEware), choose 
from a dropdown menu in the DXKeeper Import screen what contest it's 
from and choose the log file. That's all it takes! And when you're 
ready to upload to LOTW, eQSL, or ClubLog, DXKeeper does that with a 
button-push once you've set yourself up those logging sites.


I suspect that other logging programs also do some or all of this; I 
have more than 300,000 QSOs in DXKeeper since getting back on the air 
in 2003.


73, Jim K9YC 


--
Saku
OH1KH



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

Re: [wsjt-devel] Feature request: Contest name

[Jim Brown via wsjt-devel]

Hi Saku,

There are logging programs that keep track of contests. I log contests 
with N1MM+ (Freeware), export the log to DXKeeper (FREEware), choose 
from a dropdown menu in the DXKeeper Import screen what contest it's 
from and choose the log file. That's all it takes! And when you're ready 
to upload to LOTW, eQSL, or ClubLog, DXKeeper does that with a 
button-push once you've set yourself up those logging sites.


I suspect that other logging programs also do some or all of this; I 
have more than 300,000 QSOs in DXKeeper since getting back on the air in 
2003.


73, Jim K9YC

On 10/14/2022 1:29 AM, Saku via wsjt-devel wrote:

Hi!

Sorry if this feature exist. I did not find a mention about it from user 
guide.


There are now several contests that use WSJT-X contest modes. It would 
be nice to have user defined contest name to logging window.
That way name logged (also via UDP message) could be set by contest. And 
maybe also add a date to name if several contests are kept in same 
external log making them easier to find by the name of contest.


Just worked contest "NAC-6m_10/2022" that uses EU VHF mode. So my 
external log has now contest name "NAC-6m_10/2022" with all CW and SSB 
qsos, but "EU VHF" with FT8 qsos that have to be changed manually 
afterwards.


Good place for contest name would be either:

Make "operator" column smaller and set "contest name" after that on 
right side.


or

Below "propagation mode".

In both cases "retain" checbox is needed too.


Thanks!





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

Re: [wsjt-devel] Feature Request

[Jim Shorney via wsjt-devel]

Stan is using Kubuntu Linux. Windows suggestions are not helpful.

73

-Jim
NU0C

On Thu, 28 Jul 2022 22:50:00 -0500
Ron WV4P via wsjt-devel  wrote:

> Windows key Shift S
> 
> On Thu, Jul 28, 2022, 10:45 PM Stan Gammons via wsjt-devel <
> wsjt-devel@lists.sourceforge.net> wrote:
> 
> > I found out the reason a screen capture seem to jack up my Kubuntu 20.04
> > machine


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

Re: [wsjt-devel] Feature Request

[Stan Gammons via wsjt-devel]

Hi Jim,

On 7/28/22 22:54, Jim Shorney via wsjt-devel wrote:
> I've never had to use shift. Just prtsc by itself brings up Spectacle and 
> I've never had issues with it.

For whatever reason, that doesn't work when the save menu is open...

73

Stan
KM4HQE




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

Re: [wsjt-devel] Feature Request

[Jim Shorney via wsjt-devel]

I've never had to use shift. Just prtsc by itself brings up Spectacle and I've 
never had issues with it.

73

-Jim
NU0C

On Fri, 29 Jul 2022 03:41:00 +
Stan Gammons via wsjt-devel  wrote:

> No idea why I
> can't do a shift print screen to do a screen capture with the save menu
> open in WSJT-X...


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

Re: [wsjt-devel] Feature Request

[Ron WV4P via wsjt-devel]

Windows key Shift S

On Thu, Jul 28, 2022, 10:45 PM Stan Gammons via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> Hi Jim,
>
> Welcome.
>
> I found out the reason a screen capture seem to jack up my Kubuntu 20.04
> machine it was due to a low battery in my wireless mouse.  No idea why I
> can't do a shift print screen to do a screen capture with the save menu
> open in WSJT-X...
>
> 73
>
> Stan
> KM4HQE
>
>
> On 7/28/22 22:26, Jim Brown via wsjt-devel wrote:
> > Thanks Stan.
> >
> > 73, Jim
> >
> > On 7/28/2022 5:12 PM, Stan Gammons via wsjt-devel wrote:
> >> On 7/28/22 18:38, Jim Brown via wsjt-devel wrote:
> >>> Please provide an option to start a new ALL.TXT for each calendar
> month,
> >>> keeping each month's file and naming it by the month. Without that
> >>> option, the file grows so large that it cannot be opened by any
> software
> >>> on my computer.
> >>>
> >>> 73, Jim K9YC
> >> Hi Jim,
> >>
> >> The 2.6 RC's have that option.  It's on the save menu.  I tried to make
> >> a screen capture of it, but trying to do so jacks up my Kubuntu 20.04
> >> system royally.  Options are don't split ALL.TXT, split ALL.TXT yearly,
> >> split ALL.TXT monthly and disable writing ALL.TXT
> >>
> >>
> >> 73
> >>
> >> Stan
> >> KM4HQE
> >>
> >>
> >>
> >>
> >>
> >>
> >> ___
> >> wsjt-devel mailing list
> >> wsjt-devel@lists.sourceforge.net
> >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> >
> >
> > ___
> > wsjt-devel mailing list
> > wsjt-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Feature Request

[Stan Gammons via wsjt-devel]

Hi Jim,

Welcome.

I found out the reason a screen capture seem to jack up my Kubuntu 20.04
machine it was due to a low battery in my wireless mouse.  No idea why I
can't do a shift print screen to do a screen capture with the save menu
open in WSJT-X...

73

Stan
KM4HQE


On 7/28/22 22:26, Jim Brown via wsjt-devel wrote:
> Thanks Stan.
>
> 73, Jim
>
> On 7/28/2022 5:12 PM, Stan Gammons via wsjt-devel wrote:
>> On 7/28/22 18:38, Jim Brown via wsjt-devel wrote:
>>> Please provide an option to start a new ALL.TXT for each calendar month,
>>> keeping each month's file and naming it by the month. Without that
>>> option, the file grows so large that it cannot be opened by any software
>>> on my computer.
>>>
>>> 73, Jim K9YC
>> Hi Jim,
>>
>> The 2.6 RC's have that option.  It's on the save menu.  I tried to make
>> a screen capture of it, but trying to do so jacks up my Kubuntu 20.04
>> system royally.  Options are don't split ALL.TXT, split ALL.TXT yearly,
>> split ALL.TXT monthly and disable writing ALL.TXT
>>
>>
>> 73
>>
>> Stan
>> KM4HQE
>>
>>
>>
>>
>>
>>
>> ___
>> wsjt-devel mailing list
>> wsjt-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel




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

Re: [wsjt-devel] Feature Request

[Jim Brown via wsjt-devel]

Thanks Stan.

73, Jim

On 7/28/2022 5:12 PM, Stan Gammons via wsjt-devel wrote:

On 7/28/22 18:38, Jim Brown via wsjt-devel wrote:

Please provide an option to start a new ALL.TXT for each calendar month,
keeping each month's file and naming it by the month. Without that
option, the file grows so large that it cannot be opened by any software
on my computer.

73, Jim K9YC


Hi Jim,

The 2.6 RC's have that option.  It's on the save menu.  I tried to make
a screen capture of it, but trying to do so jacks up my Kubuntu 20.04
system royally.  Options are don't split ALL.TXT, split ALL.TXT yearly,
split ALL.TXT monthly and disable writing ALL.TXT


73

Stan
KM4HQE






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




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

Re: [wsjt-devel] Feature Request

[Jim Brown via wsjt-devel]

Hi Sam,

Yes, we talked about that several months ago, but your download site 
insists that I create a password, which I am unwilling to do. The last 
thing I need is another password. :)  I have close to a GB of 
downloadable pdf tutorials and applications notes on my website, all 
free, no password required. k9yc.com/publish.htm


73, Jim K9YC

On 7/28/2022 5:09 PM, Sam W2JDB wrote:

Hi Jim,

What is the OS on your PC.If its Windows (any version) my program 
AllText.exe can search through any size All.txt.
Given the date and callsigns it will display the data in less than 0.5 
second even if the file is larger than a 1GB.
It does not load the file into memory. It can be active while WSJT-X is 
active and can display a selected number of

records from the All.txt file while WSJT-X is appending to it.

73,

Sam W2JDB



-Original Message-
From: Jim Brown via wsjt-devel 
To: WSJT software development 
Cc: Jim Brown 
Sent: Thu, Jul 28, 2022 7:38 pm
Subject: [wsjt-devel] Feature Request

Please provide an option to start a new ALL.TXT for each calendar month,
keeping each month's file and naming it by the month. Without that
option, the file grows so large that it cannot be opened by any software
on my computer.

73, Jim K9YC


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





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

Re: [wsjt-devel] Feature Request

[Sam W2JDB via wsjt-devel]

Hi Jim,
What is the OS on your PC.If its Windows (any version) my program AllText.exe 
can search through any size All.txt.  Given the date and callsigns it will 
display the data in less than 0.5 second even if the file is larger than a 1GB. 
It does not load the file into memory. It can be active while WSJT-X is active 
and can display a selected number of records from the All.txt file while WSJT-X 
is appending to it.
73,
Sam W2JDB


-Original Message-
From: Jim Brown via wsjt-devel 
To: WSJT software development 
Cc: Jim Brown 
Sent: Thu, Jul 28, 2022 7:38 pm
Subject: [wsjt-devel] Feature Request

Please provide an option to start a new ALL.TXT for each calendar month, 
keeping each month's file and naming it by the month. Without that 
option, the file grows so large that it cannot be opened by any software 
on my computer.

73, Jim K9YC


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

Re: [wsjt-devel] Feature Request

[Stan Gammons via wsjt-devel]

On 7/28/22 18:38, Jim Brown via wsjt-devel wrote:
> Please provide an option to start a new ALL.TXT for each calendar month,
> keeping each month's file and naming it by the month. Without that
> option, the file grows so large that it cannot be opened by any software
> on my computer.
>
> 73, Jim K9YC

Hi Jim,

The 2.6 RC's have that option.  It's on the save menu.  I tried to make
a screen capture of it, but trying to do so jacks up my Kubuntu 20.04
system royally.  Options are don't split ALL.TXT, split ALL.TXT yearly,
split ALL.TXT monthly and disable writing ALL.TXT


73

Stan
KM4HQE






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

Re: [wsjt-devel] Feature Request

[Dennis Younker NE6I via wsjt-devel]

Jim,

That feature is in the new release candidate and works well..

—Dennis NE6I


> On Jul 28, 2022, at 4:40 PM, Jim Brown via wsjt-devel 
>  wrote:
> 
> Please provide an option to start a new ALL.TXT for each calendar month, 
> keeping each month's file and naming it by the month. Without that option, 
> the file grows so large that it cannot be opened by any software on my 
> computer.
> 
> 73, Jim K9YC
> 
> 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel



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

Re: [wsjt-devel] Feature Request: Hound Mode

[Jeff Stillinger via wsjt-devel]

Thank you Bill, Neil, and James for helping make my earlier point. Open 
source code allows a station to completely customize the U.I. for their 
style of operations.   So for those that are on the fox/hound hunt and 
desire the checkbox in a specific location for their operations, simply 
move it to the location desired. Otherwise, we have to recognize and 
understand that this particular development team has thought EVERYTHING 
through to the end point. From robo stations, to operational mistakes.   
All thought of and dealt with in a very reasonable way, with providing 
the flexibility to allow customizing a station.


If someone isn't skilled with coding, then hire someone.  People hire 
painters to do a custom job on a house or car.  People hire landscapers 
to create a custom yard.  People hire tailors to customize a suit or 
dress.  The barber or hair stylist to create a custom hair cut.   People 
even hire breeders to produce custom pets.  So why not custom software?





On 10/11/21 4:17 AM, Bill Somerville via wsjt-devel wrote:

Jon,

that was an attempt to defeat some of the more trivial robot stations, 
unfortunately the mass opinion was that it was a misfeature so perhaps 
everyone is quite happy for the FT8 sub-bands to gradually fill with 
unattended robot operations?


73
Bill
G4WJS.

On 11/10/2021 03:48, Jon Anhold via wsjt-devel wrote:
This seems like similar logic to that that led to the 
ill-conceived "move the log-it button randomly" feature.


On Sun, Oct 10, 2021 at 10:45 PM James Shaver (N2ADV) via wsjt-devel 
 wrote:


The check box used to be on the main screen of the UI and people
kept checking it by mistake and causing all sorts of issues and
questions so it was moved to the menu and those questions and
issues ceased to be replaced by a less frequent request to put it
back where it was. The needs of the many and all that…





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


--
Jeff Stillinger - KB6IBB
KB6IBB Laboratories
Wylie, Texas - United States
http://kb6ibb-15.ham-radio-op.net/Ham-Radio/

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

Re: [wsjt-devel] Feature Request: Hound Mode

[Neil Zampella via wsjt-devel]

Grant,

I have no idea where you got the idea that I said a 'clear frequency'
doesn't matter, not sure that James said anything of the sort
either.  You always check for a clear spot to Tx from, no matter
what mode or special contest activity you're using.    For Fox/Hound,
you wait one period to see where the other hounds are, find the spot
above 1000 hz, and go for it.

Of course, what may be 'clear' to you, may not be clear to someone 1000
miles away, such is the nature of propagation.

Neil, KN3ILZ

On 10/10/2021 11:20 PM, Grant Willis wrote:

Jim,

FYI - Neil and James don't believe a clear frequency matters based on
past conversations I have had with them. I contend they have never
tried chasing DX where every path starts at 8000 miles (ie out of VK).
The standard FT8 channels are so congested these days that trying to
target working particular stations can be futile because I can't find
(and don't know) a clear RX slot at the other end of the path to try
calling on. I have called it the "hidden transmitter" syndrome in a
conversation with Joe K1JT in the past, but he didn't seem to
understand the reference (it was an old description of CSMA problems
we used to have on AX.25 packet nets when not everyone could hear
everyone). A similar situation impacts the decision making when
picking a channel to transmit on today in FT8 - which notably Phil
Karn KA9Q also has picked up on in some of his recent posts to the list.

As for the choice of 40m FT4 frequency - I had quite animated
arguments with Bill Somerville about it - and all logic fell on deaf
ears. Through my IARU global HF band planning reform proposals I am
hoping we can finally address that injustice.

Best regards,
Grant VK5GR
IARU R3 HF Band Planning Chair


On Mon, Oct 11, 2021 at 2:20 PM Jim Brown via wsjt-devel
mailto:wsjt-devel@lists.sourceforge.net>> wrote:

On 10/10/2021 7:12 PM, Neil Zampella via wsjt-devel wrote:
> as F/H specifically requires you to reply to a Fox CQ above 1000
hz, and
> since the decoder decodes the entire passband based on the base
> frequency set, you would not need any 'waterfall history' to
determine
> where to Tx your reply.

Sure we do -- we want to choose a relatively clear frequency to
TX, and
you need that history to make that judgement call. And smart
operators
will occasionally skip TX for a sequence to see what might have
changed.

I had exactly that experience working S9OK today on 12M. Although
they're not running F/H, they are multi-streamed using other
software.
By making what turned out to be a good choice of TX, I worked them
with
two calls from NorCal, an 8,000 mile path.

73, Jim K9YC




___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net

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


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

Re: [wsjt-devel] Feature Request: Hound Mode

[Grant VK5GR via wsjt-devel]

-Original Message-
From: James Shaver (N2ADV) [mailto:n2...@windstream.net] 
Sent: Monday, 11 October 2021 11:58 PM
To: WSJT software development
Subject: Re: [wsjt-devel] Feature Request: Hound Mode


"Not sure where in fantasy land you had these conversations but the dev list 
isn’t the place to float personal issues."

It looks like I owe you and others a sincere apology as that email was not 
intended for the list.



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

Re: [wsjt-devel] Feature Request: Hound Mode

[James Shaver (N2ADV) via wsjt-devel]

“ Neil and James don't believe a clear frequency matters based on past 
conversations I have had with them.”

Not sure where in fantasy land you had these conversations but the dev list 
isn’t the place to float personal issues. 



> On Oct 11, 2021, at 12:22 AM, Grant Willis via wsjt-devel 
>  wrote:
> 
> Neil and James don't believe a clear frequency matters based on past 
> conversations I have had with them.



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

Re: [wsjt-devel] Feature Request: Hound Mode

[Jim Brown via wsjt-devel]

On 10/11/2021 2:22 AM, Bill Somerville via wsjt-devel wrote:
that space is basically an illusion. The reason is that the main window 
layout is largely shared by all modes and variants, the exceptions to 
that are WSPR, FST4W, Frequency calibration, and EME Echo mode. What 
appears to be empty space is almost always a hidden widget that appears 
with some other mode or mode variant.


I understand -- a byproduct of simplifying code, and worthy in the goal 
of getting product out the door, with which I agree. Perhaps, over time, 
and the product has been out the door for a while, the simplicity in 
writing code might be sacrificed on the altar of improving usability by 
taking another approach to generating those screens? Note that my 
programming background is old and limited, but even that was enough to 
appreciate the skills and attention to detail of those like you who 
practice it.


But I was a FAR better designer and consultant for performance sound 
systems because I had also worked providing and recording live sound, 
and having listened to others with similar but sometimes very different 
experience. I also served (and still do) on the Standards Committee of 
the Audio Engineering Society, and our Standards benefit from Working 
Group members who work in many different parts of pro audio, from radio 
and television to recording and live sound, and many who have worked in 
several of these areas.


As a writer of international Standards, I've always tried to understand 
and while understanding the "big picture" of needs, good engineering 
practice, and the practicalities of marketing and economics.


73, Jim K9YC


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

Re: [wsjt-devel] Feature Request: Hound Mode

[Bill Somerville via wsjt-devel]

On 11/10/2021 08:45, Jim Brown via wsjt-devel wrote:

On 10/10/2021 11:02 PM, Peter Sumner via wsjt-devel wrote:

Rather than extra buttons / tick boxes on the existing busy screen


I hardly see the FT8/FT4 main screen as "busy" -- indeed, I see plenty 
of empty real estate for these two tick boxes with labels (or buttons 
with labels within the buttons that change state). I really object to 
the "lowest common denominator" view of what hams should be able to 
understand, especially with those who can't bother to read the manual! 
After all, a minimal test is required for VHF operation, and a greater 
one for most HF privileges.


As has been observed, the conflict between contest mode and normal 
mode drives all users nuts, contesters and non-contesters, on VHF/UHF, 
where contest operation is on the usual channels. And the need for the 
F/H switch is pretty obvious to those who use it. Granted, thanks to 
COVID, there have been precious few expeditions to work, but hopefully 
that will soon get us back to more normal conditions.


73, Jim K9YC 


Jim,

that space is basically an illusion. The reason is that the main window 
layout is largely shared by all modes and variants, the exceptions to 
that are WSPR, FST4W, Frequency calibration, and EME Echo mode. What 
appears to be empty space is almost always a hidden widget that appears 
with some other mode or mode variant.


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

Re: [wsjt-devel] Feature Request: Hound Mode

[Bill Somerville via wsjt-devel]

Jon,

that was an attempt to defeat some of the more trivial robot stations, 
unfortunately the mass opinion was that it was a misfeature so perhaps 
everyone is quite happy for the FT8 sub-bands to gradually fill with 
unattended robot operations?


73
Bill
G4WJS.

On 11/10/2021 03:48, Jon Anhold via wsjt-devel wrote:
This seems like similar logic to that that led to the 
ill-conceived "move the log-it button randomly" feature.


On Sun, Oct 10, 2021 at 10:45 PM James Shaver (N2ADV) via wsjt-devel 
 wrote:


The check box used to be on the main screen of the UI and people
kept checking it by mistake and causing all sorts of issues and
questions so it was moved to the menu and those questions and
issues ceased to be replaced by a less frequent request to put it
back where it was. The needs of the many and all that…

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

Re: [wsjt-devel] Feature Request: Hound Mode

[Jim Brown via wsjt-devel]

On 10/10/2021 11:02 PM, Peter Sumner via wsjt-devel wrote:

Rather than extra buttons / tick boxes on the existing busy screen


I hardly see the FT8/FT4 main screen as "busy" -- indeed, I see plenty 
of empty real estate for these two tick boxes with labels (or buttons 
with labels within the buttons that change state). I really object to 
the "lowest common denominator" view of what hams should be able to 
understand, especially with those who can't bother to read the manual! 
After all, a minimal test is required for VHF operation, and a greater 
one for most HF privileges.


As has been observed, the conflict between contest mode and normal mode 
drives all users nuts, contesters and non-contesters, on VHF/UHF, where 
contest operation is on the usual channels. And the need for the F/H 
switch is pretty obvious to those who use it. Granted, thanks to COVID, 
there have been precious few expeditions to work, but hopefully that 
will soon get us back to more normal conditions.


73, Jim K9YC




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

Re: [wsjt-devel] Feature Request: Hound Mode

[Peter Sumner via wsjt-devel]

for the F/H - Contest brigade

Rather than extra buttons / tick boxes on the existing busy screen for a
dedicated group of users, would a small pop-out window like that used for
the Astronomical data display be a better proposal?

I know its a bit of a radical shift of thinking and of course would
initially require an extra mouse click but once opened it is from my eme
experience it is remembered.

The DEV team may consider this as a viable option to duplicate / group the
extra contest and F/H bits on rather than a re-hash of the GUI?

just a passing thought..

Regards,
Peter vk5pj



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

Re: [wsjt-devel] Feature Request: Hound Mode

[Grant Willis via wsjt-devel]

Jim,

FYI - Neil and James don't believe a clear frequency matters based on past
conversations I have had with them. I contend they have never tried chasing
DX where every path starts at 8000 miles (ie out of VK). The standard FT8
channels are so congested these days that trying to target working
particular stations can be futile because I can't find (and don't know) a
clear RX slot at the other end of the path to try calling on. I have called
it the "hidden transmitter" syndrome in a conversation with Joe K1JT in the
past, but he didn't seem to understand the reference (it was an old
description of CSMA problems we used to have on AX.25 packet nets when not
everyone could hear everyone). A similar situation impacts the
decision making when picking a channel to transmit on today in FT8 - which
notably Phil Karn KA9Q also has picked up on in some of his recent posts to
the list.

As for the choice of 40m FT4 frequency - I had quite animated arguments
with Bill Somerville about it - and all logic fell on deaf ears. Through my
IARU global HF band planning reform proposals I am hoping we can finally
address that injustice.

Best regards,
Grant VK5GR
IARU R3 HF Band Planning Chair


On Mon, Oct 11, 2021 at 2:20 PM Jim Brown via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> On 10/10/2021 7:12 PM, Neil Zampella via wsjt-devel wrote:
> > as F/H specifically requires you to reply to a Fox CQ above 1000 hz, and
> > since the decoder decodes the entire passband based on the base
> > frequency set, you would not need any 'waterfall history' to determine
> > where to Tx your reply.
>
> Sure we do -- we want to choose a relatively clear frequency to TX, and
> you need that history to make that judgement call. And smart operators
> will occasionally skip TX for a sequence to see what might have changed.
>
> I had exactly that experience working S9OK today on 12M. Although
> they're not running F/H, they are multi-streamed using other software.
> By making what turned out to be a good choice of TX, I worked them with
> two calls from NorCal, an 8,000 mile path.
>
> 73, Jim K9YC
>
>
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Feature Request: Hound Mode

[Jim Brown via wsjt-devel]

On 10/10/2021 7:12 PM, Neil Zampella via wsjt-devel wrote:
as F/H specifically requires you to reply to a Fox CQ above 1000 hz, and 
since the decoder decodes the entire passband based on the base 
frequency set, you would not need any 'waterfall history' to determine 
where to Tx your reply.


Sure we do -- we want to choose a relatively clear frequency to TX, and 
you need that history to make that judgement call. And smart operators 
will occasionally skip TX for a sequence to see what might have changed.


I had exactly that experience working S9OK today on 12M. Although 
they're not running F/H, they are multi-streamed using other software. 
By making what turned out to be a good choice of TX, I worked them with 
two calls from NorCal, an 8,000 mile path.


73, Jim K9YC




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

Re: [wsjt-devel] Feature Request: Hound Mode

[Jim Brown via wsjt-devel]

Well said, Grant. From where I sit, very active on 6M, and both DX 
chasing and contesting on HF and MF, the only poor decisions made by by 
the design team are based on their lack of broad experience below VHF. 
That's the only possible explanation for how 40M FT4 ended up where it did.


Your comments are spot on, and describe how active contesters and DX 
chasers operate, and the PITA you describe is 1) why configurations are 
NOT a viable solution, and why main screen access to OPERATIONAL 
controls like Fox/Hound mode and Contest Mode is vital to serious 
operators.


73, Jim K9YC

On 10/10/2021 6:49 PM, Grant Willis via wsjt-devel wrote:

Neil,

I wish to take a moment please to outline what I see is the problem with 
the configuration options as a solution that everyone keeps answering 
with when this comes up. I dont think the case why the configuration 
mode changes annoy many has ever been clearly articulated.


If I am tuning around the band and see some FT8, dial my receiver onto 
it and see what is happening. If I see they are running in F/H mode - 
then if I use configurations to change to that mode,  I need to often a) 
add a frequency to the config, b) reselect the frequency I was just on 
and c) loose the waterfall history I would want to use to pick where to 
drop my transmitter to start calling.


In quick fire DX Chasing that is all lost time and multiplication of 
effort that to be frank is a PITA.


The reason people keep asking for a button to switch to hound mode and 
back on the main screen is so they can do what people should more 
naturally be doing - that is spin the dial of their radio, look at 
what's on the band, and then pick the right mode to work what they hear 
*/_quickly and efficiently_/*. Sure the work arounds work - but they are 
clunky and kludgy to a DX operator.


The alternative solutions might be - preserve the 
frequency/band/sub-frequency settings across a configuration settings 
change and get the waterfall not to be reset when you swap 
configurations. I believe that would be much more work for the 
programming team than having a simple tick switch linked to hound mode 
on / off on the main page. Having said that, the developers have made it 
clear they are not interested - so yes it is also a lost cause.


Oh and to those that say "grab the source and roll your own" - not 
everyone can or has the time to write software and roll their own.


Regards,
Grant VK5GR




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

Re: [wsjt-devel] Feature Request: Hound Mode

[Jon Anhold via wsjt-devel]

This seems like similar logic to that that led to the ill-conceived "move
the log-it button randomly" feature.

On Sun, Oct 10, 2021 at 10:45 PM James Shaver (N2ADV) via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> The check box used to be on the main screen of the UI and people kept
> checking it by mistake and causing all sorts of issues and questions so it
> was moved to the menu and those questions and issues ceased to be replaced
> by a less frequent request to put it back where it was. The needs of the
> many and all that…
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Feature Request: Hound Mode

[James Shaver (N2ADV) via wsjt-devel]

The check box used to be on the main screen of the UI and people kept checking 
it by mistake and causing all sorts of issues and questions so it was moved to 
the menu and those questions and issues ceased to be replaced by a less 
frequent request to put it back where it was. The needs of the many and all 
that…

> On Oct 10, 2021, at 10:14 PM, Neil Zampella via wsjt-devel 
>  wrote:
> 
> 
> Grant,
> 
> as F/H specifically requires you to reply to a Fox CQ above 1000 hz, and 
> since the decoder decodes the entire passband based on the base frequency 
> set, you would not need any 'waterfall history' to determine where to Tx your 
> reply.
> 
> Maybe I'm missing the point.
> 
> That said, my reply was specifically to Dennis who was saying he would forget 
> to switch back to normal FT8 mode after using one of the 'special' modes.
> 
> Neil, KN3ILZ
> 
> On 10/10/2021 8:49 PM, Grant Willis wrote:
>> Neil,
>> 
>> I wish to take a moment please to outline what I see is the problem with the 
>> configuration options as a solution that everyone keeps answering with when 
>> this comes up. I dont think the case why the configuration mode changes 
>> annoy many has ever been clearly articulated.
>> 
>> If I am tuning around the band and see some FT8, dial my receiver onto it 
>> and see what is happening. If I see they are running in F/H mode - then if I 
>> use configurations to change to that mode,  I need to often a) add a 
>> frequency to the config, b) reselect the frequency I was just on and c) 
>> loose the waterfall history I would want to use to pick where to drop my 
>> transmitter to start calling.
>> 
>> In quick fire DX Chasing that is all lost time and multiplication of effort 
>> that to be frank is a PITA.
>> 
>> The reason people keep asking for a button to switch to hound mode and back 
>> on the main screen is so they can do what people should more naturally be 
>> doing - that is spin the dial of their radio, look at what's on the band, 
>> and then pick the right mode to work what they hear quickly and efficiently. 
>> Sure the work arounds work - but they are clunky and kludgy to a DX operator.
>> 
>> The alternative solutions might be - preserve the 
>> frequency/band/sub-frequency settings across a configuration settings change 
>> and get the waterfall not to be reset when you swap configurations. I 
>> believe that would be much more work for the programming team than having a 
>> simple tick switch linked to hound mode on / off on the main page. Having 
>> said that, the developers have made it clear they are not interested - so 
>> yes it is also a lost cause.
>> 
>> Oh and to those that say "grab the source and roll your own" - not everyone 
>> can or has the time to write software and roll their own. 
>> 
>> Regards,
>> Grant VK5GR
>> 
>> 
>> 
>> 
>> 
>> On Mon, Oct 11, 2021 at 11:55 AM Neil Zampella via wsjt-devel 
>>  wrote:
>>> In your case I would suggest create a separate CONFIGURATION for each mode 
>>> you're using.You can setup one for regular use, then one for other 
>>> special modes such as the NA VHF contest, Field Day, Fox & Hound, etc. 
>>> 
>>> All you need to do is switch over to the mode you're going to use by 
>>> selecting the configuration. 
>>> 
>>> I've been using this feature since it was first created.
>>> 
>>> Neil, KN3ILZ
>>> 
>>> On 10/10/2021 6:12 PM, Dennis Younker NE6I wrote:
>>>> Put me down for also wishing to have that on the main screen. Or more 
>>>> accurately in my case, having a check box or link on the main screen that 
>>>> is linked to Special Operating Activity. Yes, handy to quickly go to and 
>>>> from F/H mode but also convenient at the start and end of one of the 
>>>> contests listed on the Advanced tab. I have, for example, operated an NA 
>>>> VHF Contest over a weekend and then forgot to uncheck the box after the 
>>>> contest. And then been bitten for a moment later in the week when 
>>>> operating normal FT8 or MSK.
>>>> 
>>>>  
>>>> 
>>>> I am not a programmer and not interested in becoming one (again). It’s 
>>>> great that the source code is available for anyone to modify to their 
>>>> heart’s content but I’m not interested in doing that. I did a lot of 
>>>> programming and compiling of code several decades ago, and spent MANY an 
>>>> all nighte

Re: [wsjt-devel] Feature Request: Hound Mode

[Neil Zampella via wsjt-devel]

Grant,

as F/H specifically requires you to reply to a Fox CQ above 1000 hz, and
since the decoder decodes the entire passband based on the base
frequency set, you would not need any 'waterfall history' to determine
where to Tx your reply.

Maybe I'm missing the point.

That said, my reply was specifically to Dennis who was saying he would
forget to switch back to normal FT8 mode after using one of the
'special' modes.

Neil, KN3ILZ

On 10/10/2021 8:49 PM, Grant Willis wrote:

Neil,

I wish to take a moment please to outline what I see is the problem
with the configuration options as a solution that everyone keeps
answering with when this comes up. I dont think the case why the
configuration mode changes annoy many has ever been clearly articulated.

If I am tuning around the band and see some FT8, dial my receiver onto
it and see what is happening. If I see they are running in F/H mode -
then if I use configurations to change to that mode,  I need to often
a) add a frequency to the config, b) reselect the frequency I was just
on and c) loose the waterfall history I would want to use to pick
where to drop my transmitter to start calling.

In quick fire DX Chasing that is all lost time and multiplication of
effort that to be frank is a PITA.

The reason people keep asking for a button to switch to hound mode and
back on the main screen is so they can do what people should more
naturally be doing - that is spin the dial of their radio, look at
what's on the band, and then pick the right mode to work what they
hear */_quickly and efficiently_/*. Sure the work arounds work - but
they are clunky and kludgy to a DX operator.

The alternative solutions might be - preserve the
frequency/band/sub-frequency settings across a configuration settings
change and get the waterfall not to be reset when you swap
configurations. I believe that would be much more work for the
programming team than having a simple tick switch linked to hound mode
on / off on the main page. Having said that, the developers have made
it clear they are not interested - so yes it is also a lost cause.

Oh and to those that say "grab the source and roll your own" - not
everyone can or has the time to write software and roll their own.

Regards,
Grant VK5GR





On Mon, Oct 11, 2021 at 11:55 AM Neil Zampella via wsjt-devel
mailto:wsjt-devel@lists.sourceforge.net>> wrote:

In your case I would suggest create a separate CONFIGURATION for
each mode you're using.    You can setup one for regular use, then
one for other special modes such as the NA VHF contest, Field Day,
Fox & Hound, etc.

All you need to do is switch over to the mode you're going to use
by selecting the configuration.

I've been using this feature since it was first created.

Neil, KN3ILZ

On 10/10/2021 6:12 PM, Dennis Younker NE6I wrote:


Put me down for also wishing to have that on the main screen. Or
more accurately in my case, having a check box or link on the
main screen that is linked to Special Operating Activity. Yes,
handy to quickly go to and from F/H mode but also convenient at
the start and end of one of the contests listed on the Advanced
tab. I have, for example, operated an NA VHF Contest over a
weekend and then forgot to uncheck the box after the contest. And
then been bitten for a moment later in the week when operating
normal FT8 or MSK.

I am not a programmer and not interested in becoming one (again).
It’s great that the source code is available for anyone to modify
to their heart’s content but I’m not interested in doing that. I
did a lot of programming and compiling of code several decades
ago, and spent MANY an all nighter doing that. That ship has now
sailed for me, and I’m not interested in getting on board again.

I am hugely appreciative of K1JT and the entire WSJT-X team for
their work. I for one know how much time and effort goes into
this. It’s truly a labor of love.

--Dennis NE6I

*From:* Jeff Stillinger via wsjt-devel

<mailto:wsjt-devel@lists.sourceforge.net>
*Sent:* Sunday, October 10, 2021 9:53 AM
*To:* WSJT software development

<mailto:wsjt-devel@lists.sourceforge.net>
    *Cc:* Jeff Stillinger 
    <mailto:kb6...@zohomail.com>
*Subject:* Re: [wsjt-devel] Feature Request: Hound Mode

Not exactly a secret.  For building on Microsoft virus, the sdk
is located here:

https://sourceforge.net/projects/jtsdk/
<https://sourceforge.net/projects/jtsdk/>

It is my understanding that it's going through some updates, but
what is posted should work.  Last time I played with it was back
in version 1.7.  I haven't kept up with that platform since I do
everything on Linux.



On 10/10/21 10:43 AM, Jon Anhold wrote:

Hi Jeff,

Yes, I agree - I am a contributor to some ot

Re: [wsjt-devel] Feature Request: Hound Mode

[Grant Willis via wsjt-devel]

Neil,

I wish to take a moment please to outline what I see is the problem with
the configuration options as a solution that everyone keeps answering with
when this comes up. I dont think the case why the configuration mode
changes annoy many has ever been clearly articulated.

If I am tuning around the band and see some FT8, dial my receiver onto it
and see what is happening. If I see they are running in F/H mode - then if
I use configurations to change to that mode,  I need to often a) add a
frequency to the config, b) reselect the frequency I was just on and c)
loose the waterfall history I would want to use to pick where to drop my
transmitter to start calling.

In quick fire DX Chasing that is all lost time and multiplication of effort
that to be frank is a PITA.

The reason people keep asking for a button to switch to hound mode and back
on the main screen is so they can do what people should more naturally be
doing - that is spin the dial of their radio, look at what's on the band,
and then pick the right mode to work what they hear *quickly and
efficiently*. Sure the work arounds work - but they are clunky and kludgy
to a DX operator.

The alternative solutions might be - preserve the
frequency/band/sub-frequency settings across a configuration settings
change and get the waterfall not to be reset when you swap configurations.
I believe that would be much more work for the programming team than having
a simple tick switch linked to hound mode on / off on the main page. Having
said that, the developers have made it clear they are not interested - so
yes it is also a lost cause.

Oh and to those that say "grab the source and roll your own" - not everyone
can or has the time to write software and roll their own.

Regards,
Grant VK5GR





On Mon, Oct 11, 2021 at 11:55 AM Neil Zampella via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> In your case I would suggest create a separate CONFIGURATION for each mode
> you're using.You can setup one for regular use, then one for other
> special modes such as the NA VHF contest, Field Day, Fox & Hound, etc.
>
> All you need to do is switch over to the mode you're going to use by
> selecting the configuration.
>
> I've been using this feature since it was first created.
>
> Neil, KN3ILZ
> On 10/10/2021 6:12 PM, Dennis Younker NE6I wrote:
>
> Put me down for also wishing to have that on the main screen. Or more
> accurately in my case, having a check box or link on the main screen that
> is linked to Special Operating Activity. Yes, handy to quickly go to and
> from F/H mode but also convenient at the start and end of one of the
> contests listed on the Advanced tab. I have, for example, operated an NA
> VHF Contest over a weekend and then forgot to uncheck the box after the
> contest. And then been bitten for a moment later in the week when operating
> normal FT8 or MSK.
>
>
>
> I am not a programmer and not interested in becoming one (again). It’s
> great that the source code is available for anyone to modify to their
> heart’s content but I’m not interested in doing that. I did a lot of
> programming and compiling of code several decades ago, and spent MANY an
> all nighter doing that. That ship has now sailed for me, and I’m not
> interested in getting on board again.
>
>
>
> I am hugely appreciative of K1JT and the entire WSJT-X team for their
> work. I for one know how much time and effort goes into this. It’s truly a
> labor of love.
>
>
>
> --Dennis NE6I
>
>
>
> *From:* Jeff Stillinger via wsjt-devel 
> 
> *Sent:* Sunday, October 10, 2021 9:53 AM
> *To:* WSJT software development 
> 
> *Cc:* Jeff Stillinger  
> *Subject:* Re: [wsjt-devel] Feature Request: Hound Mode
>
>
>
> Not exactly a secret.  For building on Microsoft virus, the sdk is located
> here:
>
> https://sourceforge.net/projects/jtsdk/
>
> It is my understanding that it's going through some updates, but what is
> posted should work.  Last time I played with it was back in version 1.7.  I
> haven't kept up with that platform since I do everything on Linux.
>
>
>
> On 10/10/21 10:43 AM, Jon Anhold wrote:
>
> Hi Jeff,
>
>
>
> Yes, I agree - I am a contributor to some other open source projects.
> Thanks for your helpful suggestion.
>
>
>
> I've given that some thought, but at least the last time I looked the
> build process / toolkit for building WSJT-X on Windows is like top secret
> or something, and I haven't spent any time recently trying to uncover it or
> get it to build.
>
>
>
> Also, unfortunately, it doesn't seem that the authors are very open to
> pull requests, so I make feature suggestions here.
>
>
>
> Thanks & 73 de KM8V Jon
>
>

Re: [wsjt-devel] Feature Request: Hound Mode

[Neil Zampella via wsjt-devel]

In your case I would suggest create a separate CONFIGURATION for each
mode you're using.    You can setup one for regular use, then one for
other special modes such as the NA VHF contest, Field Day, Fox & Hound,
etc.

All you need to do is switch over to the mode you're going to use by
selecting the configuration.

I've been using this feature since it was first created.

Neil, KN3ILZ

On 10/10/2021 6:12 PM, Dennis Younker NE6I wrote:


Put me down for also wishing to have that on the main screen. Or more
accurately in my case, having a check box or link on the main screen
that is linked to Special Operating Activity. Yes, handy to quickly go
to and from F/H mode but also convenient at the start and end of one
of the contests listed on the Advanced tab. I have, for example,
operated an NA VHF Contest over a weekend and then forgot to uncheck
the box after the contest. And then been bitten for a moment later in
the week when operating normal FT8 or MSK.

I am not a programmer and not interested in becoming one (again). It’s
great that the source code is available for anyone to modify to their
heart’s content but I’m not interested in doing that. I did a lot of
programming and compiling of code several decades ago, and spent MANY
an all nighter doing that. That ship has now sailed for me, and I’m
not interested in getting on board again.

I am hugely appreciative of K1JT and the entire WSJT-X team for their
work. I for one know how much time and effort goes into this. It’s
truly a labor of love.

--Dennis NE6I

*From:* Jeff Stillinger via wsjt-devel 
*Sent:* Sunday, October 10, 2021 9:53 AM
*To:* WSJT software development 
*Cc:* Jeff Stillinger 
*Subject:* Re: [wsjt-devel] Feature Request: Hound Mode

Not exactly a secret.  For building on Microsoft virus, the sdk is
located here:

https://sourceforge.net/projects/jtsdk/
<https://sourceforge.net/projects/jtsdk/>

It is my understanding that it's going through some updates, but what
is posted should work.  Last time I played with it was back in version
1.7.  I haven't kept up with that platform since I do everything on
Linux.



On 10/10/21 10:43 AM, Jon Anhold wrote:

Hi Jeff,

Yes, I agree - I am a contributor to some other open source
projects. Thanks for your helpful suggestion.

I've given that some thought, but at least the last time I looked
the build process / toolkit for building WSJT-X on Windows is like
top secret or something, and I haven't spent any time recently
trying to uncover it or get it to build.

Also, unfortunately, it doesn't seem that the authors are very
open to pull requests, so I make feature suggestions here.

Thanks & 73 de KM8V Jon

On Sun, Oct 10, 2021 at 9:37 AM Jeff Stillinger via wsjt-devel
mailto:wsjt-devel@lists.sourceforge.net>> wrote:

How about an alternative to your prediction.   WSJT-X is open
source.  You have complete access to the source code, and one
of the wonderful conveniences of the package is the ability to
customize the software to a specific style of station operations.

That is the fancy and PC way to say, if you want a button
somewhere specific, then you are free to put it there.  There
are no licensing restrictions, other than your modification
would stay local to your station.   All of the compilers and
libraries are also free and open source.

Have at it and let us know about your progress.




On 10/9/21 9:05 PM, Jon Anhold via wsjt-devel wrote:

I know that this is going to get ignored, or I'm going to
be told to "make a configuration" to "solve" this problem,
but I'll again put in a vote to have a Hound mode checkbox
on the main screen to switch in and out of that mode.

There are several DXPeditions right now, some running
Fox/Hound mode, others running multi-stream NOT fox/hound
mode, and I've found myself switching a LOT back and forth.

Maybe an option to enable an "expert" mode to then display
some of these controls in an easy to use location?

73 de KM8V



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

Re: [wsjt-devel] Feature Request: Hound Mode

[Dennis Younker NE6I via wsjt-devel]

Put me down for also wishing to have that on the main screen. Or more 
accurately in my case, having a check box or link on the main screen that is 
linked to Special Operating Activity. Yes, handy to quickly go to and from F/H 
mode but also convenient at the start and end of one of the contests listed on 
the Advanced tab. I have, for example, operated an NA VHF Contest over a 
weekend and then forgot to uncheck the box after the contest. And then been 
bitten for a moment later in the week when operating normal FT8 or MSK. 

 

I am not a programmer and not interested in becoming one (again). It’s great 
that the source code is available for anyone to modify to their heart’s content 
but I’m not interested in doing that. I did a lot of programming and compiling 
of code several decades ago, and spent MANY an all nighter doing that. That 
ship has now sailed for me, and I’m not interested in getting on board again.

 

I am hugely appreciative of K1JT and the entire WSJT-X team for their work. I 
for one know how much time and effort goes into this. It’s truly a labor of 
love. 

 

--Dennis NE6I

 

From: Jeff Stillinger via wsjt-devel  
Sent: Sunday, October 10, 2021 9:53 AM
To: WSJT software development 
Cc: Jeff Stillinger 
Subject: Re: [wsjt-devel] Feature Request: Hound Mode

 

Not exactly a secret.  For building on Microsoft virus, the sdk is located 
here: 

https://sourceforge.net/projects/jtsdk/

It is my understanding that it's going through some updates, but what is posted 
should work.  Last time I played with it was back in version 1.7.  I haven't 
kept up with that platform since I do everything on Linux.  





On 10/10/21 10:43 AM, Jon Anhold wrote:

Hi Jeff, 

 

Yes, I agree - I am a contributor to some other open source projects. Thanks 
for your helpful suggestion. 

 

I've given that some thought, but at least the last time I looked the build 
process / toolkit for building WSJT-X on Windows is like top secret or 
something, and I haven't spent any time recently trying to uncover it or get it 
to build.

 

Also, unfortunately, it doesn't seem that the authors are very open to pull 
requests, so I make feature suggestions here.

 

Thanks & 73 de KM8V Jon

 

On Sun, Oct 10, 2021 at 9:37 AM Jeff Stillinger via wsjt-devel 
mailto:wsjt-devel@lists.sourceforge.net> > 
wrote:

How about an alternative to your prediction.   WSJT-X is open source.  You have 
complete access to the source code, and one of the wonderful conveniences of 
the package is the ability to customize the software to a specific style of 
station operations.

That is the fancy and PC way to say, if you want a button somewhere specific, 
then you are free to put it there.  There are no licensing restrictions, other 
than your modification would stay local to your station.   All of the compilers 
and libraries are also free and open source. 

Have at it and let us know about your progress.






On 10/9/21 9:05 PM, Jon Anhold via wsjt-devel wrote:

I know that this is going to get ignored, or I'm going to be told to "make a 
configuration" to "solve" this problem, but I'll again put in a vote to have a 
Hound mode checkbox on the main screen to switch in and out of that mode. 

 

There are several DXPeditions right now, some running Fox/Hound mode, others 
running multi-stream NOT fox/hound mode, and I've found myself switching a LOT 
back and forth.

 

Maybe an option to enable an "expert" mode to then display some of these 
controls in an easy to use location?

 

73 de KM8V





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

Re: [wsjt-devel] Feature Request: Hound Mode

[Jeff Stillinger via wsjt-devel]

Not exactly a secret.  For building on Microsoft virus, the sdk is 
located here:


https://sourceforge.net/projects/jtsdk/

It is my understanding that it's going through some updates, but what is 
posted should work.  Last time I played with it was back in version 
1.7.  I haven't kept up with that platform since I do everything on Linux.





On 10/10/21 10:43 AM, Jon Anhold wrote:

Hi Jeff,

Yes, I agree - I am a contributor to some other open source projects. 
Thanks for your helpful suggestion.


I've given that some thought, but at least the last time I looked the 
build process / toolkit for building WSJT-X on Windows is like top 
secret or something, and I haven't spent any time recently trying to 
uncover it or get it to build.


Also, unfortunately, it doesn't seem that the authors are very open to 
pull requests, so I make feature suggestions here.


Thanks & 73 de KM8V Jon

On Sun, Oct 10, 2021 at 9:37 AM Jeff Stillinger via wsjt-devel 
> wrote:


How about an alternative to your prediction.   WSJT-X is open
source.  You have complete access to the source code, and one of
the wonderful conveniences of the package is the ability to
customize the software to a specific style of station operations.

That is the fancy and PC way to say, if you want a button
somewhere specific, then you are free to put it there. There are
no licensing restrictions, other than your modification would stay
local to your station.   All of the compilers and libraries are
also free and open source.

Have at it and let us know about your progress.





On 10/9/21 9:05 PM, Jon Anhold via wsjt-devel wrote:

I know that this is going to get ignored, or I'm going to be told
to "make a configuration" to "solve" this problem, but I'll again
put in a vote to have a Hound mode checkbox on the main screen to
switch in and out of that mode.

There are several DXPeditions right now, some running Fox/Hound
mode, others running multi-stream NOT fox/hound mode, and I've
found myself switching a LOT back and forth.

Maybe an option to enable an "expert" mode to then display some
of these controls in an easy to use location?

73 de KM8V


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



-- 
Jeff Stillinger - KB6IBB

KB6IBB Laboratories
Wylie, Texas - United States
http://kb6ibb-15.ham-radio-op.net/Ham-Radio/  


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net

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




--
Jeff Stillinger - KB6IBB
KB6IBB Laboratories
Wylie, Texas - United States
http://kb6ibb-15.ham-radio-op.net/Ham-Radio/

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

Re: [wsjt-devel] Feature Request: Hound Mode

[Jon Anhold via wsjt-devel]

Hi Jeff,

Yes, I agree - I am a contributor to some other open source projects.
Thanks for your helpful suggestion.

I've given that some thought, but at least the last time I looked the build
process / toolkit for building WSJT-X on Windows is like top secret or
something, and I haven't spent any time recently trying to uncover it or
get it to build.

Also, unfortunately, it doesn't seem that the authors are very open to pull
requests, so I make feature suggestions here.

Thanks & 73 de KM8V Jon

On Sun, Oct 10, 2021 at 9:37 AM Jeff Stillinger via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> How about an alternative to your prediction.   WSJT-X is open source.  You
> have complete access to the source code, and one of the wonderful
> conveniences of the package is the ability to customize the software to a
> specific style of station operations.
>
> That is the fancy and PC way to say, if you want a button somewhere
> specific, then you are free to put it there.  There are no licensing
> restrictions, other than your modification would stay local to your
> station.   All of the compilers and libraries are also free and open
> source.
>
> Have at it and let us know about your progress.
>
>
>
>
>
> On 10/9/21 9:05 PM, Jon Anhold via wsjt-devel wrote:
>
> I know that this is going to get ignored, or I'm going to be told to "make
> a configuration" to "solve" this problem, but I'll again put in a vote to
> have a Hound mode checkbox on the main screen to switch in and out of that
> mode.
>
> There are several DXPeditions right now, some running Fox/Hound mode,
> others running multi-stream NOT fox/hound mode, and I've found myself
> switching a LOT back and forth.
>
> Maybe an option to enable an "expert" mode to then display some of these
> controls in an easy to use location?
>
> 73 de KM8V
>
>
> ___
> wsjt-devel mailing 
> listwsjt-devel@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
> --
> Jeff Stillinger - KB6IBB
> KB6IBB Laboratories
> Wylie, Texas - United Stateshttp://kb6ibb-15.ham-radio-op.net/Ham-Radio/
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Feature Request: Hound Mode

[Jeff Stillinger via wsjt-devel]

How about an alternative to your prediction.   WSJT-X is open source.  
You have complete access to the source code, and one of the wonderful 
conveniences of the package is the ability to customize the software to 
a specific style of station operations.


That is the fancy and PC way to say, if you want a button somewhere 
specific, then you are free to put it there.  There are no licensing 
restrictions, other than your modification would stay local to your 
station.   All of the compilers and libraries are also free and open 
source.


Have at it and let us know about your progress.





On 10/9/21 9:05 PM, Jon Anhold via wsjt-devel wrote:
I know that this is going to get ignored, or I'm going to be told to 
"make a configuration" to "solve" this problem, but I'll again put in 
a vote to have a Hound mode checkbox on the main screen to switch in 
and out of that mode.


There are several DXPeditions right now, some running Fox/Hound mode, 
others running multi-stream NOT fox/hound mode, and I've found myself 
switching a LOT back and forth.


Maybe an option to enable an "expert" mode to then display some of 
these controls in an easy to use location?


73 de KM8V


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


--
Jeff Stillinger - KB6IBB
KB6IBB Laboratories
Wylie, Texas - United States
http://kb6ibb-15.ham-radio-op.net/Ham-Radio/

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

Re: [wsjt-devel] Feature Request: Highlight DX Call

[Jon Anhold]

Sorry for multiple emails, but I meant to add: this would highlight any
decodes from that callsign, not just CQs.

Thanks &  73

On Tue, May 25, 2021 at 11:42 AM Jon Anhold  wrote:

> I think it would be useful if there was a way to configure highlighting of
> decodes matching the callsign currently in the DX Call box.
>
> For example, you see a spot for KM8V on 18.100 so you tune to that
> frequency. You pop KM8V into the DX Call box, and in the Band Activity
> window, if you are decoding KM8V that row is highlighted.
>
> 73 de KM8V Jon
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Feature request: Rx level input slider

[David Schmocker]

Mike:
Thank you for settings cross-check (current settings):  Others have proposed 
reducing RF level (need to adjust AF level to preserve EME system noise figure)

 

K3S entryValuecomments
AF GAINLOreduces output level by about 10dB vs. HI setting
AF LIMNOR 030don’t want AGC limiting levels for optimal EME decoding
LIN OUT=PHONESNOR 000 gives 0dB while NOR 001 saturates WSJT-X at +78dB

 

With LIN OUT set to =PHONES, I can use the radio K3S AF control to somewhat 
control the audio out level via the USB port, but it’s super sensitive.  A 
10-Turn trimmer AF control would be required to set it properly. 

The audio output abruptly jumps from zero to too hot when using the radio’s AF 
(volume) control. 
Also I’ve checked the computer MIDI settings (already at minimum). 

 

I have searched for WSJT-X audio settings and K3S on internet 
(N5XLHamRadio.blogspot.com has one good post but it must have referenced an 
older WSJT-X version that had Rx input slider).   

 

I’ll keep researching settings and welcome an email off-list from anyone who 
finds alternate solution on this to kj9idave (at) charter ( d ot)  net    

 

Absent an Rx input level slider-control, I believe I just need to live 
with/accept the the 57dB level currently showing (no signals) on WSJT-X with 
Ref Spectrum measured viewing Cold Sky North.   

thank you 

 

Very 73, 
Dave KJ9I

 

From: Black Michael via wsjt-devel 
Reply-To: Black Michael , WSJT software development 

Date: Monday, March 15, 2021 at 12:01 AM
To: WSJT software development 
Cc: Black Michael 
Subject: Re: [wsjt-devel] Feature request: Rx level input slider

 

Have you tried this setting?  Seesms reducing this should work.

 

LIN OUT NOR 010 

Sets the LINE OUT level. LINE OUT connections go to PC soundcard inputs.

Settings above 10 may result in overdrive of the soundcard or saturation of the

KIO3’s isolation transformers; monitor signals using the PC to avoid this.

Note: Normally, LIN OUT sets a fixed-level receive-only output for main/sub

(L/R), compatible with digitalmodes. Tapping 1 switches LINOUT to

=PHONES, where the line outputs match headphone audio, audio level is

controlled by AF/SUB gain controls, and both RX andTX audio are available.

 

Mike W9MDB

 

 

 

On Sunday, March 14, 2021, 11:31:56 AM CDT, David Schmocker 
 wrote: 

 

 

Dear WSJT-X development team:
Feature request:

Could we eliminate the Tx Power slider (lower right of main screen) and replace 
it with an Rx input level slider (far lower left of screen immediately adjacent 
to the Rx dB level) to allow attenuation of input Rx signal please?

 

More detail/context:

Elecraft K3S radio with WSJT-X users who use the USB-to-K3S radio interface can 
only reduce the input volume so far (typically maintains 60dB WSJT-X level on 
the Rx dB level indicator).   Further reducing the audio output of the K3S 
drops the Signal to the point we see ‘jail bars’ (internal noise). 

To enable setting K3S output to WSJT-X recommended 30dB, the above Rx level 
slider would help.

Tx slider seems unnecessary because every radio (correct me if wrong) allows a 
Tx or drive level reduction on the radio itself). 

 

Very 73, 

Dave KJ9I

 

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

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

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

Re: [wsjt-devel] Feature request: Rx level input slider

[Jim Brown]

On 3/14/2021 9:58 PM, Black Michael via wsjt-devel wrote:

Sets the LINE OUT level. LINE OUT connections go to PC soundcard inputs.
Settings above 10 may result in overdrive of the soundcard or saturation 
of the

KIO3’s isolation transformers; monitor signals using the PC to avoid this.


Great advice, Mike, and I'd keep the LINE OUT level even lower, not 
above 5. I discovered this issue when my first K3 arrived in 2008 and I 
put my distortion analyzer on it. The design error was adding series 
resistance between the output stage and the transformer.


73, Jim K9YC




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

Re: [wsjt-devel] Feature request: Rx level input slider

[Black Michael via wsjt-devel]

Have you tried this setting?  Seesms reducing this should work.
LIN OUT NOR 010 Sets the LINE OUT level. LINE OUT connections go to PC 
soundcard inputs.Settings above 10 may result in overdrive of the soundcard or 
saturation of theKIO3’s isolation transformers; monitor signals using the PC to 
avoid this.Note: Normally, LIN OUT sets a fixed-level receive-only output for 
main/sub(L/R), compatible with digitalmodes. Tapping 1 switches LINOUT 
to=PHONES, where the line outputs match headphone audio, audio level 
iscontrolled by AF/SUB gain controls, and both RX andTX audio are available.
Mike W9MDB
 

On Sunday, March 14, 2021, 11:31:56 AM CDT, David Schmocker 
 wrote:  
 
 
Dear WSJT-X development team:
Feature request:

Could we eliminate the Tx Power slider (lower right of main screen) and replace 
it with an Rx input level slider (far lower left of screen immediately adjacent 
to the Rx dB level) to allow attenuation of input Rx signal please?

  

More detail/context:

Elecraft K3S radio with WSJT-X users who use the USB-to-K3S radio interface can 
only reduce the input volume so far (typically maintains 60dB WSJT-X level on 
the Rx dB level indicator).   Further reducing the audio output of the K3S 
drops the Signal to the point we see ‘jail bars’ (internal noise). 

To enable setting K3S output to WSJT-X recommended 30dB, the above Rx level 
slider would help.

Tx slider seems unnecessary because every radio (correct me if wrong) allows a 
Tx or drive level reduction on the radio itself). 

  

Very 73, 

Dave KJ9I

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

Re: [wsjt-devel] Feature request: Rx level input slider

[Bill Frantz]

On 3/14/21 at 12:32 PM, g4...@classdesign.com (Bill Somerville) wrote:

>the only input level WSJT-X has access to is in the digital 
>domain, i.e. after the soundcard ADC, that means it cannot make 
>any useful adjustment if the level is too high. The level 
>adjustment must be made in the analog domain before the ADC, in 
>your case within the rig. If the level from your K3S is too 
>high then something is wrong with the settings in the rig.

I use the RF gain control to keep the input within range.

73 Bill AE6JV

---
Bill Frantz|The nice thing about standards| Periwinkle
(408)348-7900  |is there are so many to choose| 150 Rivermead Rd #235
www.pwpconsult.com |from.   - Andrew Tanenbaum| Peterborough, NH 03458



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

Re: [wsjt-devel] Feature request: Rx level input slider

[David Tiller]

You wrote:

“Tx slider seems unnecessary because every radio (correct me if wrong) allows a 
Tx or drive level reduction on the radio itself).”

That is very much not the case. Many rigs require a different drive level per 
band, something that WSJTX handles perfectly.


> On Mar 14, 2021, at 12:25, David Schmocker  wrote:
> 
> Tx slider seems unnecessary because every radio (correct me if wrong) allows 
> a Tx or drive level reduction on the radio itself).



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

Re: [wsjt-devel] Feature request: Rx level input slider

[Bill Somerville]

On 14/03/2021 16:25, David Schmocker wrote:


Dear WSJT-X development team:
Feature request:

Could we eliminate the Tx Power slider (lower right of main screen) 
and replace it with an Rx input level slider (far lower left of screen 
immediately adjacent to the Rx dB level) to allow attenuation of input 
Rx signal please?


More detail/context:

Elecraft K3S radio with WSJT-X users who use the USB-to-K3S radio 
interface can only reduce the input volume so far (typically maintains 
60dB WSJT-X level on the Rx dB level indicator).   Further reducing 
the audio output of the K3S drops the Signal to the point we see ‘jail 
bars’ (internal noise).


To enable setting K3S output to WSJT-X recommended 30dB, the above Rx 
level slider would help.


Tx slider seems unnecessary because every radio (correct me if wrong) 
allows a Tx or drive level reduction on the radio itself).


Very 73,

Dave KJ9I


Hi Dave,

the only input level WSJT-X has access to is in the digital domain, i.e. 
after the soundcard ADC, that means it cannot make any useful adjustment 
if the level is too high. The level adjustment must be made in the 
analog domain before the ADC, in your case within the rig. If the level 
from your K3S is too high then something is wrong with the settings in 
the rig.


73
Bill
G4WJS.

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

Re: [wsjt-devel] Feature request: Rx level input slider

[Christoph Berg]

Re: David Schmocker
> Tx slider seems unnecessary because every radio (correct me if wrong) allows 
> a Tx or drive level reduction on the radio itself). 

By that argument, you could as well put an attenuator into your
antenna line to have the RX level reduced to what you wanted.

Christoph


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

Re: [wsjt-devel] Feature request for FT8 Band Activity list

[jeff millar]

Hello Frank,

JTalert is apparently Windows only...so doesn't work for me

jeff, wa1hco

On Sun, Feb 14, 2021 at 12:43 PM Frank Birch  wrote:

> If you use helper JTalert
> View mode activity window F9
> All responses scroll through continuously. You can adjust the size of the
> window to acclimate many cycles   Of decode - continuously.
> I use this all the time.
> Of course JTalert has many other useful features.
> Frank
> VE3FBZ
>
> > On Feb 14, 2021, at 11:52 AM, jeff millar  wrote:
> >
> > 
> > Hello all,
> >
> > Sometimes I need to search the Band Activity list for a specific station
> who is known to be on the air.  That is not easy to do.
> >- the list scrolls a lot every 15 seconds
> >- the transmitting station callsign is not aligned in columns and
> hard to visually search
> >
> > My current "thing" is to hunt for grid squares.  At this point, it's
> mostly search and pounce.  I use GridTracker (N0TTL) to watch band activity
> and show a call or grid that is new or not confirmed.
> >
> > Some possible improvements
> >- Align the transmitting station in a column, similar to how the DXCC
> is aligned
> >   - Might as well align the grid square as well
> >- Highlight the call in the Band Activity list when a call sign
> matches the DX Call box
> >   - Maybe highlight the grid square the same way?
> >
> > thanks,
> >
> > jeff, wa1hco
> >
> >
> >
> > ___
> > wsjt-devel mailing list
> > wsjt-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Feature request for FT8 Band Activity list

[Frank Birch]

If you use helper JTalert
View mode activity window F9
All responses scroll through continuously. You can adjust the size of the 
window to acclimate many cycles   Of decode - continuously.
I use this all the time.
Of course JTalert has many other useful features.
Frank
VE3FBZ

> On Feb 14, 2021, at 11:52 AM, jeff millar  wrote:
> 
> 
> Hello all,
> 
> Sometimes I need to search the Band Activity list for a specific station who 
> is known to be on the air.  That is not easy to do.
>- the list scrolls a lot every 15 seconds
>- the transmitting station callsign is not aligned in columns and hard to 
> visually search
> 
> My current "thing" is to hunt for grid squares.  At this point, it's mostly 
> search and pounce.  I use GridTracker (N0TTL) to watch band activity and show 
> a call or grid that is new or not confirmed.
> 
> Some possible improvements
>- Align the transmitting station in a column, similar to how the DXCC is 
> aligned
>   - Might as well align the grid square as well
>- Highlight the call in the Band Activity list when a call sign matches 
> the DX Call box
>   - Maybe highlight the grid square the same way?
> 
> thanks, 
> 
> jeff, wa1hco
> 
> 
> 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel


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

Re: [wsjt-devel] Feature request for FT8 Band Activity list

[jeff millar]

Hello Alan,

WSJT knows what is in the log, but...
   - doesn't know if the grid is confirmed, about 20% of my logged grids
are not confirmed, so still needed
   - only highlights stations calling CQ.
  - More and more I need to "tail end" a station after is finishes an
ongoing QSO
  - Rare stations don't need to call CQ, so highlighting doesn't work

jeff, wa1hco

On Sun, Feb 14, 2021 at 12:06 PM Alan Groups 
wrote:

> Hi, use the colour highlighting settings?  There are options in there for
> grids not already in the log, and also grids not in the log by band.
>
> Alan G0TLK
>
> On 14/02/2021 16:48, jeff millar wrote:
>
> Hello all,
>
> Sometimes I need to search the Band Activity list for a specific station
> who is known to be on the air.  That is not easy to do.
>- the list scrolls a lot every 15 seconds
>- the transmitting station callsign is not aligned in columns and hard
> to visually search
>
> My current "thing" is to hunt for grid squares.  At this point, it's
> mostly search and pounce.  I use GridTracker (N0TTL) to watch band activity
> and show a call or grid that is new or not confirmed.
>
> Some possible improvements
>- Align the transmitting station in a column, similar to how the DXCC
> is aligned
>   - Might as well align the grid square as well
>- Highlight the call in the Band Activity list when a call sign matches
> the DX Call box
>   - Maybe highlight the grid square the same way?
>
> thanks,
>
> jeff, wa1hco
>
>
>
>
>
> ___
> wsjt-devel mailing 
> listwsjt-devel@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Feature request for FT8 Band Activity list

[Alan Groups]

Hi, use the colour highlighting settings? There are options in there for 
grids not already in the log, and also grids not in the log by band.


Alan G0TLK

On 14/02/2021 16:48, jeff millar wrote:

Hello all,

Sometimes I need to search the Band Activity list for a specific 
station who is known to be on the air.  That is not easy to do.

   - the list scrolls a lot every 15 seconds
   - the transmitting station callsign is not aligned in columns and 
hard to visually search


My current "thing" is to hunt for grid squares.  At this point, it's 
mostly search and pounce.  I use GridTracker (N0TTL) to watch band 
activity and show a call or grid that is new or not confirmed.


Some possible improvements
   - Align the transmitting station in a column, similar to how the 
DXCC is aligned

      - Might as well align the grid square as well
   - Highlight the call in the Band Activity list when a call sign 
matches the DX Call box

      - Maybe highlight the grid square the same way?

thanks,

jeff, wa1hco





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

Re: [wsjt-devel] #Feature request. 2.4.0

[Joe Taylor]

Hi Dave,

I don't think you have sent us any .wav files for EME QSOs on 6 meters. 
 It would be very useful to have some indication of your on-the-air 
experience with Q65 for 6m EME.


Have you at least studied the example files for 6m EME mentioned in the 
Quick-Start Guide to Q65?  Or read the "Sensitivity Comparison of JT65A 
and Q65-60A"?  (A copy is posted here: 
https://physics.princeton.edu/pulsar/k1jt/JT65A_And_Q65.pdf.)


What conclusions has your 6m EME experience lead you to draw concerning 
Q65?  If your conclusions differ from ours, can you explain why?


-- 73, Joe, K1JT

On 2/9/2021 9:36 AM, David Schmocker wrote:

GA/GM Bill and all of the developers,

_Thank you so much_ for all the team is doing.

Can Short-Hand messages be added for Q65A (used at 6m)  also please?

It’s helpful to have those single-tone messages  Q65A at 6m EME because 
I have had at least one 6m EME JT65A weak signal QSO where the decoder 
didn’t decode the SH message, yet I was able to visibly see a ‘paint 
splash’ (partial trace) at the right frequencies knowing that SH message 
that was being sent so I could visually decode this.   Also, if I go on 
a DXpedition (which I plan to), [my apologies in advance this is going 
to open a hornet’s nest], I am interested in working more stations, not 
spending time distinguishing between level-based reports.  Perhaps 
my HF background where contesters give “599” no matter what colors this 
request.   With EME,  SH messages help.  Having the choice of SH or not 
gives the level-sensitive or SH option.


I appreciate your consideration. Thank you!   Very 73,

Dave KJ9I

(flames if any to be sent to me directly not to the list please)

*From: *Bill Somerville 
*Reply-To: *WSJT software development 
*Date: *Tuesday, February 9, 2021 at 5:00 AM
*To: *
*Subject: *Re: [wsjt-devel] #Feature request. 2.4.0

On 09/02/2021 03:54, Hattori, Yoshihisa wrote:

Hi all.

I am testing Q65 and realized that we are missing Short hand
indicator on waterfall display, which is provided for JT65. (three
yellow lines suggesting the RO/RRR/73 tones.) While less Q65/QRA64
users are using shorthand, it is good to have those since Sh will
not be decoded and users need to visually identify the signal. Can
you please implement it?

De JO1LVZ/Hatt

Hi Hatt-san,

the single tone short code markers are shown for sub-modes C or wider.

73
Bill
G4WJS.

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




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




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

Re: [wsjt-devel] #Feature request. 2.4.0

[David Schmocker]

GA/GM Bill and all of the developers, 

Thank you so much for all the team is doing.   

 

Can Short-Hand messages be added for Q65A (used at 6m)  also please?   

 

It’s helpful to have those single-tone messages  Q65A at 6m EME because I have 
had at least one 6m EME JT65A weak signal QSO where the decoder didn’t decode 
the SH message, yet I was able to visibly see a ‘paint splash’ (partial trace) 
at the right frequencies knowing that SH message that was being sent so I could 
visually decode this.   Also, if I go on a DXpedition (which I plan to), [my 
apologies in advance this is going to open a hornet’s nest], I am interested in 
working more stations, not spending time distinguishing between level-based 
reports.  Perhaps my HF background where contesters give “599” no matter 
what colors this request.   With EME,  SH messages help.  Having the choice of 
SH or not gives the level-sensitive or SH option. 

 

I appreciate your consideration. Thank you!   Very 73,

 

Dave KJ9I

 

(flames if any to be sent to me directly not to the list please)

 

From: Bill Somerville 
Reply-To: WSJT software development 
Date: Tuesday, February 9, 2021 at 5:00 AM
To: 
Subject: Re: [wsjt-devel] #Feature request. 2.4.0

 

On 09/02/2021 03:54, Hattori, Yoshihisa wrote:

Hi all.

I am testing Q65 and realized that we are missing Short hand indicator on 
waterfall display, which is provided for JT65. (three yellow lines suggesting 
the RO/RRR/73 tones.) While less Q65/QRA64 users are using shorthand, it is 
good to have those since Sh will not be decoded and users need to visually 
identify the signal. Can you please implement it?

 

De JO1LVZ/Hatt

Hi Hatt-san,

the single tone short code markers are shown for sub-modes C or wider.

73
Bill
G4WJS.

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

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

Re: [wsjt-devel] #Feature request. 2.4.0

[Bill Somerville]

On 09/02/2021 03:54, Hattori, Yoshihisa wrote:


Hi all.

I am testing Q65 and realized that we are missing Short hand indicator 
on waterfall display, which is provided for JT65. (three yellow lines 
suggesting the RO/RRR/73 tones.) While less Q65/QRA64 users are using 
shorthand, it is good to have those since Sh will not be decoded and 
users need to visually identify the signal. Can you please implement it?


De JO1LVZ/Hatt


Hi Hatt-san,

the single tone short code markers are shown for sub-modes C or wider.

73
Bill
G4WJS.

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

Re: [wsjt-devel] Feature Request

[Mike Lewis]

I use a Python program to monitor the WSJT-X UDP status message broadcasts. It 
has radio dial  frequency and more. I use the frequency to load the correct 
calibration data for my remote VHF+ wattmeter. It in turn can be used to drive 
other things.

The wattmeter is a Arduino or PSoC5 device attached to a rf log detector and 
standard dual directional coupler.

It would seem the UDP status message has all you would need?

Mike
K7MDL

Sent from my T-Mobile 4G LTE Device
Get Outlook for Android<https://aka.ms/ghei36>


From: alaw...@mudhawk.com 
Sent: Monday, July 20, 2020 12:46:50 PM
To: WSJT software development 
Subject: Re: [wsjt-devel] Feature Request

 Thank you Bill (And Bill) - that worked great and does exactly what I was 
looking for!  (In fact, I can feed it to Python's simple webserver and watch 
for DX from anywhere... :)

  I'm also going to try  WB6DJI (Mike's) suggestion of JTDX.


  I would really love it if the user_hardware request saw the light of day at 
some point.  I currently have 2 Raspberry PI / SDR combos   which band hop on 
wspr all day, but  if I could get some extra data passed in around the wsjt-x 
operating mode, and the frequency, I could do a lot in terms of integrating the 
FT-8 setup into the rest of my shack so it can drive my network aware antenna 
switches etc.

73, and thanks!

  --al
  WB1BQE



 Original Message ----
Subject: Re: [wsjt-devel] Feature Request
From: Bill Somerville mailto:g4...@classdesign.com>>
Date: Mon, July 20, 2020 12:59 pm
To: wsjt-devel@lists.sourceforge.net<mailto:wsjt-devel@lists.sourceforge.net>

On 20/07/2020 17:29, alaw...@mudhawk.com<mailto:alaw...@mudhawk.com> wrote:
HI Folks,

  I've been lurking in read-only mode for a while here,  and just upgraded to 
2.2.2 up on my Atomic-Pi.  Building the code was simple and all works well.

 I was wondering if I could ask for 2 feature requests as time permits, please?

1)  user_hardware:  (I understand this is currently temporarily broken) 
Looking at the code, it seems that this feature was implemented only for WSPR 
but not for some of the other sub-modules within the program.   My request is 
two-fold.First,  Please consider calling this script at any mode or band 
change  program-wide.

  Secondly,  in addition to the band information,  if additional information 
could be included in the calling arguments,  (Mode, Band and Frequency)  this 
would be extremely helpful, and might help forstall other feature requests 
since folks would be able to implement more powerful side functionality.

  In my case,  I have been using an FT736r for the "JT Modes",  however I also 
use the same rig for satellite use, repeater use etc.   (I do this via a very 
old piece of code called FT-7361 which I dragged kicking and screaming into 
this century... :)   With FT-7361, I can schedule the radio to do various 
things at various times  and if I could get the above requested parameters, 
would bypass hamlib altogether for this particular use case.  The end result 
would be WSPR during the day, automatically shifting to satellite use at 
certain times, and listening to my local repeater during commute hours.  IN 
this case,  WSJTX becomes a client, rather than the master of the relationship 
with the radio.


 2)  My second feature request is to allow certain callsigns to be excluded 
from the list of stations that are displayed during decode.   The use case here 
is that on 6 meters,  many of the local stations call CQ repeatedly all day,  
essentially causing other interesting dx to scroll off the screen.   Being able 
to filter at least their cq calls would make it easier to see when the band 
opens to interesting places.

  Thanks for any consideration!

  --al
  WB1BQE
Hi Al,
for your second request: as you are running on Linux; have you considered a 
simple command line in a terminal like:
tail -f ~/.local/share/WSJT-X/ALL.TXT | grep -v '\(WB1BQE\|W1LOCAL\)'

Add what what you wish to filter to the grep inverse regexp alternation.

73
Bill
G4WJS.


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net<mailto:wsjt-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/wsjt-devel<https://eur06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fwsjt-devel&data=02%7C01%7C%7Cf48b41b439eb4bcac4f608d82ce64c6c%7C84df9e7fe9f640afb435%7C1%7C0%7C637308714922513485&sdata=Cm7SGExDhWj94RPk9L3MKIZ4%2FabmTdce1bHSfUi3FU4%3D&reserved=0>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Feature Request

[alawler]

 Thank you Bill (And Bill) - that worked great and does exactly what I was looking for!  (In fact, I can feed it to Python's simple webserver and watch for DX from anywhere... :)  I'm also going to try  WB6DJI (Mike's) suggestion of JTDX.    I would really love it if the user_hardware request saw the light of day at some point.  I currently have 2 Raspberry PI / SDR combos   which band hop on wspr all day, but  if I could get some extra data passed in around the wsjt-x operating mode, and the frequency, I could do a lot in terms of integrating the FT-8 setup into the rest of my shack so it can drive my network aware antenna switches etc.    73, and thanks!  --al  WB1BQE

 Original Message --------
Subject: Re: [wsjt-devel] Feature Request
From: Bill Somerville <g4...@classdesign.com>
Date: Mon, July 20, 2020 12:59 pm
To: wsjt-devel@lists.sourceforge.net

 On 20/07/2020 17:29, alaw...@mudhawk.com wrote:HI Folks,     I've been lurking in read-only mode for a while here,  and just upgraded to 2.2.2 up on my Atomic-Pi.  Building the code was simple and all works well.   I was wondering if I could ask for 2 feature requests as time permits, please?   1)  user_hardware:  (I understand this is currently temporarily broken) Looking at the code, it seems that this feature was implemented only for WSPR but not for some of the other sub-modules within the program.   My request is two-fold.    First,  Please consider calling this script at any mode or band change  program-wide.     Secondly,  in addition to the band information,  if additional information could be included in the calling arguments,  (Mode, Band and Frequency)  this would be extremely helpful, and might help forstall other feature requests since folks would be able to implement more powerful side functionality.    In my case,  I have been using an FT736r for the "JT Modes",  however I also use the same rig for satellite use, repeater use etc.   (I do this via a very old piece of code called FT-7361 which I dragged kicking and screaming into this century... :)   With FT-7361, I can schedule the radio to do various things at various times  and if I could get the above requested parameters, would bypass hamlib altogether for this particular use case.  The end result would be WSPR during the day, automatically shifting to satellite use at certain times, and listening to my local repeater during commute hours.  IN this case,  WSJTX becomes a client, rather than the master of the relationship with the radio.     2)  My second feature request is to allow certain callsigns to be excluded from the list of stations that are displayed during decode.   The use case here is that on 6 meters,  many of the local stations call CQ repeatedly all day,  essentially causing other interesting dx to scroll off the screen.   Being able to filter at least their cq calls would make it easier to see when the band opens to interesting places.     Thanks for any consideration!     --al   WB1BQE  Hi Al, for your second request: as you are running on Linux; have you considered a simple command line in a terminal like: tail -f ~/.local/share/WSJT-X/ALL.TXT | grep -v '\(WB1BQE\|W1LOCAL\)'
 Add what what you wish to filter to the grep inverse regexp alternation. 73 Bill G4WJS.___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel




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

Re: [wsjt-devel] Feature Request

[Bill Frantz]

On 7/20/20 at 12:59 PM, g4...@classdesign.com (Bill Somerville) wrote:


On 20/07/2020 17:29, alaw...@mudhawk.com wrote:

...> >
 2)  My second feature request is to allow certain callsigns 
to be excluded from the list of stations that are displayed 
during decode.   The use case here is that on 6 meters,  
many of the local stations call CQ repeatedly all day,  
essentially causing other interesting dx to scroll off the 
screen.   Being able to filter at least their cq calls would 
make it easier to see when the band opens to interesting places.


  Thanks for any consideration!

  --al
  WB1BQE


Hi Al,

for your second request: as you are running on Linux; have you 
considered a simple command line in a terminal like:


tail -f ~/.local/share/WSJT-X/ALL.TXT | grep -v '\(WB1BQE\|W1LOCAL\)'

Add what what you wish to filter to the grep inverse regexp alternation.


Note that this technique will also work on MacOS using the 
Terminal application found in the Applications->Utilities.


73 Bill AE6JV

---
Bill Frantz| When an old person dies, a   | Periwinkle
(408)348-7900  | library burns. - Joe McGawon | 150 
Rivermead Rd #235
www.pwpconsult.com | Irish Ethnographer   | 
Peterborough, NH 03458




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

Re: [wsjt-devel] Feature Request

[Bill Somerville]

On 20/07/2020 17:29, alaw...@mudhawk.com wrote:

HI Folks,

  I've been lurking in read-only mode for a while here, and just 
upgraded to 2.2.2 up on my Atomic-Pi.  Building the code was simple 
and all works well.


 I was wondering if I could ask for 2 feature requests as time 
permits, please?


1)  user_hardware:  (I understand this is currently temporarily 
broken) Looking at the code, it seems that this feature was 
implemented only for WSPR but not for some of the other sub-modules 
within the program.   My request is two-fold.    First,  Please 
consider calling this script at any mode or band change  program-wide.


  Secondly,  in addition to the band information,  if additional 
information could be included in the calling arguments,  (Mode, Band 
and Frequency)  this would be extremely helpful, and might help 
forstall other feature requests since folks would be able to implement 
more powerful side functionality.


  In my case,  I have been using an FT736r for the "JT Modes",  
however I also use the same rig for satellite use, repeater use etc.   
(I do this via a very old piece of code called FT-7361 which I dragged 
kicking and screaming into this century... :)   With FT-7361, I 
can schedule the radio to do various things at various times  and if I 
could get the above requested parameters, would bypass hamlib 
altogether for this particular use case.  The end result would be WSPR 
during the day, automatically shifting to satellite use at certain 
times, and listening to my local repeater during commute hours.  IN 
this case,  WSJTX becomes a client, rather than the master of the 
relationship with the radio.



 2)  My second feature request is to allow certain callsigns to be 
excluded from the list of stations that are displayed during decode.   
The use case here is that on 6 meters,  many of the local stations 
call CQ repeatedly all day,  essentially causing other interesting dx 
to scroll off the screen.   Being able to filter at least their cq 
calls would make it easier to see when the band opens to interesting 
places.


  Thanks for any consideration!

  --al
  WB1BQE


Hi Al,

for your second request: as you are running on Linux; have you 
considered a simple command line in a terminal like:


tail -f ~/.local/share/WSJT-X/ALL.TXT | grep -v '\(WB1BQE\|W1LOCAL\)'

Add what what you wish to filter to the grep inverse regexp alternation.

73
Bill
G4WJS.

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

Re: [wsjt-devel] Feature Request

[Bill Somerville]

On 29/06/2020 03:47, Jim Brown wrote:
There are times when it could be quite helpful to be able to switch 
special operating features on and off from the main operating window. 
One of those times occurred this weekend, when I wanted to be able to 
switch between FD messages to work FD stations and normal mode to work 
DX stations. My primary objective was to pick up new grids and DX 
entities on 6M. At other times, it can be useful to turn DXpedition 
Mode on and off.


Thanks and 73,
Jim K9YC 


Hi Jim,

rightly or wrongly, settings that require more than trivial internal 
reconfiguration are placed on the Settings panels. When any Settings 
change is accepted WSJT-X goes through a large number of 
re-initializations to ensure that everything is consistent with any 
changed settings. In many ways such settings changes are similar to 
operating mode changes or rig control changes. Many users find that 
creating a new configuration is the easiest way to initiate such 
changes. Switching configurations is equivalent to restarting the 
application with a different collection of settings.


73
Bill
G4WJS.



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

Re: [wsjt-devel] Feature Request - Reconfigure Split Tx freq upon QSY while in Split: Rig mode

[Topher Petty]

It seems that having WSJT-X send the the new RX frequency  to both VFOs
when a band change happens would be the simplest solution. The user could
then hit the TUNE button while still in split mode, get a match, then set
up the split TX freq on the other VFO...
Another option would be for the user to to use the "Fake It" split mode,
which , I believe will accomplish the same thing without all the fuss...

73 de AI8W, Chris

On Fri, Jan 10, 2020 at 5:19 PM W5MMW Matt Manjos  wrote:

> Well I found what was preventing me from building wsjtx (qt5-5.14.0 on
> Arch seems to have introduced the issue, rolling it back to qt5-5.13.2 got
> me back in business)
>
> But that change I thought might implement the behavior I'm hoping for
> didn't do the trick. I'll keep poking at it, but I'm not familiar with the
> wsjt codebase at all.
>
> On Wed, Jan 8, 2020 at 12:13 PM W5MMW Matt Manjos  wrote:
>
>> Unfortunately something broke my build toolchain so I can't poke around
>> at testing a change myself until I have time to find out what broke it, but
>> I suspect this might have something to do with setting next_state_.split in
>> PollingTransceiver::do_post_frequency (PollingTransceiver.cpp:80)
>>
>>
>>
>> On Wed, Jan 8, 2020 at 4:51 AM Christoph Berg  wrote:
>>
>>> Re: W5MMW Matt Manjos 2020-01-07
>>> 
>>> > - User chooses to QSY to 160m band via the drop-down in WSJT. Their 40m
>>> > antenna will not tune to 160m, so they need their rig to be ready to
>>> send
>>> > RF on 1.840 MHz in order for their antenna switcher/tuner to operate
>>>
>>> I'm seeing the same problem with IC706, the tune button doesn't work
>>> until I manually disable split in the radio.
>>>
>>> Christoph
>>>
>>>
>>> ___
>>> wsjt-devel mailing list
>>> wsjt-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>>>
>> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Feature Request - Reconfigure Split Tx freq upon QSY while in Split: Rig mode

[W5MMW Matt Manjos]

Well I found what was preventing me from building wsjtx (qt5-5.14.0 on Arch
seems to have introduced the issue, rolling it back to qt5-5.13.2 got me
back in business)

But that change I thought might implement the behavior I'm hoping for
didn't do the trick. I'll keep poking at it, but I'm not familiar with the
wsjt codebase at all.

On Wed, Jan 8, 2020 at 12:13 PM W5MMW Matt Manjos  wrote:

> Unfortunately something broke my build toolchain so I can't poke around at
> testing a change myself until I have time to find out what broke it, but I
> suspect this might have something to do with setting next_state_.split in
> PollingTransceiver::do_post_frequency (PollingTransceiver.cpp:80)
>
>
>
> On Wed, Jan 8, 2020 at 4:51 AM Christoph Berg  wrote:
>
>> Re: W5MMW Matt Manjos 2020-01-07
>> 
>> > - User chooses to QSY to 160m band via the drop-down in WSJT. Their 40m
>> > antenna will not tune to 160m, so they need their rig to be ready to
>> send
>> > RF on 1.840 MHz in order for their antenna switcher/tuner to operate
>>
>> I'm seeing the same problem with IC706, the tune button doesn't work
>> until I manually disable split in the radio.
>>
>> Christoph
>>
>>
>> ___
>> wsjt-devel mailing list
>> wsjt-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>>
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Feature Request - Reconfigure Split Tx freq upon QSY while in Split: Rig mode

[W5MMW Matt Manjos]

Unfortunately something broke my build toolchain so I can't poke around at
testing a change myself until I have time to find out what broke it, but I
suspect this might have something to do with setting next_state_.split in
PollingTransceiver::do_post_frequency (PollingTransceiver.cpp:80)



On Wed, Jan 8, 2020 at 4:51 AM Christoph Berg  wrote:

> Re: W5MMW Matt Manjos 2020-01-07
> 
> > - User chooses to QSY to 160m band via the drop-down in WSJT. Their 40m
> > antenna will not tune to 160m, so they need their rig to be ready to send
> > RF on 1.840 MHz in order for their antenna switcher/tuner to operate
>
> I'm seeing the same problem with IC706, the tune button doesn't work
> until I manually disable split in the radio.
>
> Christoph
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Feature Request - Reconfigure Split Tx freq upon QSY while in Split: Rig mode

[Christoph Berg]

Re: W5MMW Matt Manjos 2020-01-07 

> - User chooses to QSY to 160m band via the drop-down in WSJT. Their 40m
> antenna will not tune to 160m, so they need their rig to be ready to send
> RF on 1.840 MHz in order for their antenna switcher/tuner to operate

I'm seeing the same problem with IC706, the tune button doesn't work
until I manually disable split in the radio.

Christoph


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

Re: [wsjt-devel] Feature Request

[Topher Petty]

Personally, I'd like to see some improvement to the "Coffee Brew" code...
The coffee my WSJT-X makes isn't nearly strong enough.

Happy 1 April!

73 de AI8W

On Mon, Apr 1, 2019 at 3:28 PM Frank Kirschner 
wrote:

> George,
>
> I believe you've explained the anomaly.
>
> LOL
>
> 73,
> Frank
> KF6E
>
> On Mon, Apr 1, 2019, 12:33 George J Molnar  wrote:
>
>> KF6E has spilled the beans! The secret “whine mode” feature in WSJT-X has
>> been revealed. On April 1st, of all days.
>>
>> Whine mode is exotic code that scans the operator’s brainwaves for signs
>> of frustration, and just as he/she is about to give up (afterwards on
>> slower computers) permits a DX decode. Otherwise, only calls from your ITU
>> region are displayed.
>>
>> If you’re calling CQ DX, the software also generates multiple callers
>> from your DXCC entity. Only when you give up and/or answer one will the
>> application unlock DX decoding.
>>
>> There are variants on this mode for VHF/UHF, described in the
>> supplemental operators’ guide, chapter 42.
>>
>> George J Molnar
>> KF2T - Virginia, USA
>>
>>
>>
>>
>> ___
>> wsjt-devel mailing list
>> wsjt-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Feature Request

[Frank Kirschner]

George,

I believe you've explained the anomaly.

LOL

73,
Frank
KF6E

On Mon, Apr 1, 2019, 12:33 George J Molnar  wrote:

> KF6E has spilled the beans! The secret “whine mode” feature in WSJT-X has
> been revealed. On April 1st, of all days.
>
> Whine mode is exotic code that scans the operator’s brainwaves for signs
> of frustration, and just as he/she is about to give up (afterwards on
> slower computers) permits a DX decode. Otherwise, only calls from your ITU
> region are displayed.
>
> If you’re calling CQ DX, the software also generates multiple callers from
> your DXCC entity. Only when you give up and/or answer one will the
> application unlock DX decoding.
>
> There are variants on this mode for VHF/UHF, described in the supplemental
> operators’ guide, chapter 42.
>
> George J Molnar
> KF2T - Virginia, USA
>
>
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Feature Request

[James Shaver]

Ha!  I have experienced this so often lol


> On Apr 1, 2019, at 12:27 PM, George J Molnar  wrote:
> 
> KF6E has spilled the beans! The secret “whine mode” feature in WSJT-X has 
> been revealed. On April 1st, of all days.
> 
> Whine mode is exotic code that scans the operator’s brainwaves for signs of 
> frustration, and just as he/she is about to give up (afterwards on slower 
> computers) permits a DX decode. Otherwise, only calls from your ITU region 
> are displayed. 
> 
> If you’re calling CQ DX, the software also generates multiple callers from 
> your DXCC entity. Only when you give up and/or answer one will the 
> application unlock DX decoding.
> 
> There are variants on this mode for VHF/UHF, described in the supplemental 
> operators’ guide, chapter 42.
> 
> George J Molnar
> KF2T - Virginia, USA
> 
> 
> 
> 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel


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

Re: [wsjt-devel] Feature Request

[George J Molnar]

KF6E has spilled the beans! The secret “whine mode” feature in WSJT-X has been 
revealed. On April 1st, of all days.

Whine mode is exotic code that scans the operator’s brainwaves for signs of 
frustration, and just as he/she is about to give up (afterwards on slower 
computers) permits a DX decode. Otherwise, only calls from your ITU region are 
displayed. 

If you’re calling CQ DX, the software also generates multiple callers from your 
DXCC entity. Only when you give up and/or answer one will the application 
unlock DX decoding.

There are variants on this mode for VHF/UHF, described in the supplemental 
operators’ guide, chapter 42.

George J Molnar
KF2T - Virginia, USA




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

Re: [wsjt-devel] Feature Request

[Lorin Hollander]

Hello Frank and Mike 

I believe Mike is correct in suspecting an audio dropout. He helped me 
understand the complex power-use issues in Windows 10 (made even more 
complicated when running Parallels on a Mac).. instead of using the Halt button 
(which I never tried} I have to leave the WSJT FT8 program by switching to 
Safari or email or something else for a minute or two and then return to find 
my FT8 window covered in red with incoming received calls from the exotic DX 
stations I had called for hours that seemed to never reply for those hours on 
end.

 While I don’t know exactly what’s happening, I had spent months with only a 
rare return call and then in frustration started to do something else to then 
return to see the fruits of the program’s labors.

Fascinating question about whether the laptop display screen on the Macbook Pro 
effects the power usage of wsjtx FT8 enough to prevent or distort reception 
and/or decoding. 

Would love to know more from anyone about what might be going on,

Best, and thanks 
Lorin 
WA1PGB 



Sent from my iPhone

> On Apr 1, 2019, at 8:18 AM, Black Michael via wsjt-devel 
>  wrote:
> 
> This can also be a symptom of audio dropouts.
> 
> Here is a version of WSJT-X that shows you when you have audio problems.  You 
> get a few messages at startup that are expected as the audio syncs up and 
> then you should never see them again unless you have problems.  Catchup 
> messages indicate audio pausing and dropout messages indicate audio dropped 
> on the floor which can cause the WAV files to NOT get recorded due to 
> insufficient audio packets.
> 
> https://www.dropbox.com/s/isxwjybws1i8u6f/wsjtx-2.0.1-win32-dropouts.exe?dl=1
> 
> de Mike W9MDB
> 
> 
> On Monday, April 1, 2019, 10:10:23 AM CDT, Frank Kirschner 
>  wrote:
> 
> 
> Almost every time I'm trying to work a DX station, I call and call with no 
> success, until I hit Halt TX. As soon as I do that, the DX station comes back 
> to me.
> 
> Could you write some software that would get the DX station to respond 
> sooner? This would help everyone, including the DX station.
> 
> Also, some software that encouraged DX stations to respond to QSLs would be 
> nice. I've sent lots of "green stamps" with no result.
> 
> Thanks, and happy April 1!
> 
> 73,
> Frank
> KF6E
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Feature Request

[Sam W2JDB via wsjt-devel]

Shot in the dark. Is it possible that there is an abnormally long delay in 
switching from Xmt mode to Rcv in your rig ?  73, Sam W2JDB
  -Original Message-
From: Black Michael via wsjt-devel 
To: WSJT software development 
Cc: Black Michael 
Sent: Mon, Apr 1, 2019 11:22 am
Subject: Re: [wsjt-devel] Feature Request

This can also be a symptom of audio dropouts.
Here is a version of WSJT-X that shows you when you have audio problems.  You 
get a few messages at startup that are expected as the audio syncs up and then 
you should never see them again unless you have problems.  Catchup messages 
indicate audio pausing and dropout messages indicate audio dropped on the floor 
which can cause the WAV files to NOT get recorded due to insufficient audio 
packets.
https://www.dropbox.com/s/isxwjybws1i8u6f/wsjtx-2.0.1-win32-dropouts.exe?dl=1

de Mike W9MDB 

On Monday, April 1, 2019, 10:10:23 AM CDT, Frank Kirschner 
 wrote:  
 
 Almost every time I'm trying to work a DX station, I call and call with no 
success, until I hit Halt TX. As soon as I do that, the DX station comes back 
to me.
Could you write some software that would get the DX station to respond sooner? 
This would help everyone, including the DX station.
Also, some software that encouraged DX stations to respond to QSLs would be 
nice. I've sent lots of "green stamps" with no result.
Thanks, and happy April 1!
73,FrankKF6E
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
  ___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Feature Request

[Black Michael via wsjt-devel]

This can also be a symptom of audio dropouts.
Here is a version of WSJT-X that shows you when you have audio problems.  You 
get a few messages at startup that are expected as the audio syncs up and then 
you should never see them again unless you have problems.  Catchup messages 
indicate audio pausing and dropout messages indicate audio dropped on the floor 
which can cause the WAV files to NOT get recorded due to insufficient audio 
packets.
https://www.dropbox.com/s/isxwjybws1i8u6f/wsjtx-2.0.1-win32-dropouts.exe?dl=1

de Mike W9MDB 

On Monday, April 1, 2019, 10:10:23 AM CDT, Frank Kirschner 
 wrote:  
 
 Almost every time I'm trying to work a DX station, I call and call with no 
success, until I hit Halt TX. As soon as I do that, the DX station comes back 
to me.
Could you write some software that would get the DX station to respond sooner? 
This would help everyone, including the DX station.
Also, some software that encouraged DX stations to respond to QSLs would be 
nice. I've sent lots of "green stamps" with no result.
Thanks, and happy April 1!
73,FrankKF6E
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
  ___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Feature Request

[Christoph Berg]

Re: Frank Kirschner 2019-04-01 

> Almost every time I'm trying to work a DX station, I call and call with no
> success, until I hit Halt TX. As soon as I do that, the DX station comes
> back to me.
> 
> Could you write some software that would get the DX station to respond
> sooner? This would help everyone, including the DX station.

Fwiw, a "stop transmitting the initial message, but do respond to
received rst reports" would make much sense to have, I've been
thinking of that several times. Would be somewhat the same as the
"call 1st" checkbox.

> Thanks, and happy April 1!

:)

Christoph


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

Re: [wsjt-devel] Feature Request - xmit below 200 hz

[OG55W]

There are plenty of stations from 100 Hz up to 3500 Hz.
You should turn Your VFO to find all of them..

Keijo
EA5/OG55W

From: Richard Shaw 
Sent: Thursday, February 21, 2019 2:49 PM
To: k...@arrl.net ; WSJT software development 
Subject: Re: [wsjt-devel] Feature Request - xmit below 200 hz

On Wed, Feb 20, 2019 at 5:59 PM Jim Brown  wrote:

  On 2/20/2019 3:48 PM, Ken Miller wrote:
  > I like to utilize the lower portion of the FT8 bands down to 0 hz.

  When transmitting that low, your signal is outside the RX bandwidth of 
  many transceivers that are tuned to the standard frequency. If you want 
  to do that anyway, simply tune your RX to 200 Hz lower than the standard 
  frequency.


I haven't tried it so I'll ask... Does this limit still apply when running 
split? 

Thanks,
Richard
KF5OIM 







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

Re: [wsjt-devel] Feature Request - xmit below 200 hz

[Richard Shaw]

On Wed, Feb 20, 2019 at 5:59 PM Jim Brown 
wrote:

> On 2/20/2019 3:48 PM, Ken Miller wrote:
> > I like to utilize the lower portion of the FT8 bands down to 0 hz.
>
> When transmitting that low, your signal is outside the RX bandwidth of
> many transceivers that are tuned to the standard frequency. If you want
> to do that anyway, simply tune your RX to 200 Hz lower than the standard
> frequency.
>

I haven't tried it so I'll ask... Does this limit still apply when running
split?

Thanks,
Richard
KF5OIM
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Feature Request - xmit below 200 hz

[Ken Miller]

Understand, I do not care if the thundering herd can not hear me. I TX 
on the lower band edge to avoid QRM. Savvy DX operators and especially 
SDR  operators will hear me, just trying to make my live a tiny bit 
easier. I already tune down 200hz, it works, seems a bit clunky though. TNX



On 2/20/2019 3:54 PM, Jim Brown wrote:

On 2/20/2019 3:48 PM, Ken Miller wrote:

I like to utilize the lower portion of the FT8 bands down to 0 hz.


When transmitting that low, your signal is outside the RX bandwidth of 
many transceivers that are tuned to the standard frequency. If you 
want to do that anyway, simply tune your RX to 200 Hz lower than the 
standard frequency.


73, Jim K9YC


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





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

Re: [wsjt-devel] Feature Request - xmit below 200 hz

[Jim Brown]

On 2/20/2019 3:48 PM, Ken Miller wrote:

I like to utilize the lower portion of the FT8 bands down to 0 hz.


When transmitting that low, your signal is outside the RX bandwidth of 
many transceivers that are tuned to the standard frequency. If you want 
to do that anyway, simply tune your RX to 200 Hz lower than the standard 
frequency.


73, Jim K9YC


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

Re: [wsjt-devel] Feature request for Hound mode

[Jim Shorney]

Hi Bill,

On Sat, 1 Dec 2018 13:41:48 +
Bill Somerville  wrote:

> congratulations on the 4W ATNO!

Thanks!
 
> What rig do you use? Is CAT control simply not available for it or is 
> there some other reason why you don't have it?

Vintage Drake 7-Line twins, circa 1980. CAT is not available. It is a system 
that I can maintain and repair myself, and performance is stellar. :)

73

-Jim
NU0C


--
"Life is too short for QRP" - ETO Alpha

"DeciBels were invented to give QRPers a false sense of smugness" - NU0C
"QRO is a public service" - NU0C


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

Re: [wsjt-devel] Feature request for Hound mode

[Bill Somerville]

On 01/12/2018 04:43, Jim Shorney wrote:

I scored 4W for ATNO on 20M Fox/Hound today, pretty easily at that. Thanks to 
the JT/FT developers once again for helping my DXCC count!

This bring up something I had been thinking about before. It would be nice for 
those of us who do not use CAT for whatever reason to have an option to limit 
the lowest reply frequency in hound mode to, say, 500 Hz. The AF stages of some 
rigs starts to roll off in that region and that can create various problems. I 
realize that I could just roll the VFO down a couple hundred Hz but this would 
be a simpler solution.

73 es TIA,

-Jim
NU0C


Hi Jim,

congratulations on the 4W ATNO!

What rig do you use? Is CAT control simply not available for it or is 
there some other reason why you don't have it?


73
Bill
G4WJS.



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

Re: [wsjt-devel] Feature Request: TX Signal Feedback Image

[Tom M0LTE]

Hi Edfel 

There really are only two ways to implement this: 

1. in hardware 

 - devise some way to split off a tiny portion of your TX signal from
your antenna feed, feed it to a second rig (SDR?), second audio
interface, and second instance of WSJT-X 

2. like Barry suggests, by sending pictures of remote waterfalls (or
data that represents them) over the internet to some central searchable
repository. 

 - I actually quite like this idea :-) 

Unfortunately it cannot be done any other way - it is simply not
possible. 

Tom 

On 2018-06-29 14:01, Edfel Rivera wrote:

> Hi: 
> 
> I work most of the time (when is its time), the 6 meter band..  Other bands 
> are 40 and 80m.  20m is relatively easy (IMO) to get QSO.  
> 
> 73' 
> 
> Edfel 
> KP4AJ 
> 
> On Fri, Jun 29, 2018 at 9:33 AM, Barry Smith  wrote:
> 
>> In message > mail.com [1]>
>> Edfel Rivera  wrote:
>> 
>>> My own experience at my location, 95 watts are normally required to
>>> complete QSO (Puerto Rico - Caribbean).  Under better conditions maybe less
>>> power could be used.
>> 
>> I'm in the UK running 40 watts to a simple end-fed antenna. On 20m 
>> I've worked Canada, USA, Brazil, Japan, 1 Australian and of course 
>> lots of Europeans. I use pskreporter to look at how far away my 
>> signals are being received. I hear Indonesia, Colombia, Venezuela, 
>> etc. but my signals don't seem to get to those places. Maybe with a 
>> better antenna, but my garden is quite small.
>> 
>> I've not yet used the feature of replaying .wav files but...
>> 
>> I agree that it would be nice to see the waterfall as seen by a 
>> distant receiver. I wonder if the existing feature of saving the .wav 
>> file could be used. Maybe it could be uploaded somewhere with the 
>> filename starting with the receiving station's callsign. The file 
>> would be automatically deleted after a preset time (2 hours?) by which 
>> time the transmitting station could have downloaded the file and 
>> looked for his own signal.
>> 
>> Barry
>> G4IAT
>> -- 
>> 
>> --
>> 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 [2]
> 
> --
> 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
 

Links:
--
[1] http://mail.com
[2] 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] Feature Request: TX Signal Feedback Image

[Edfel Rivera]

Hi:

I work most of the time (when is its time), the 6 meter band..  Other bands
are 40 and 80m.  20m is relatively easy (IMO) to get QSO.

73'

Edfel
KP4AJ

On Fri, Jun 29, 2018 at 9:33 AM, Barry Smith  wrote:

> In message  mail.com>
>   Edfel Rivera  wrote:
>
> > My own experience at my location, 95 watts are normally required to
> > complete QSO (Puerto Rico - Caribbean).  Under better conditions maybe
> less
> > power could be used.
>
> I'm in the UK running 40 watts to a simple end-fed antenna. On 20m
> I've worked Canada, USA, Brazil, Japan, 1 Australian and of course
> lots of Europeans. I use pskreporter to look at how far away my
> signals are being received. I hear Indonesia, Colombia, Venezuela,
> etc. but my signals don't seem to get to those places. Maybe with a
> better antenna, but my garden is quite small.
>
> I've not yet used the feature of replaying .wav files but...
>
> I agree that it would be nice to see the waterfall as seen by a
> distant receiver. I wonder if the existing feature of saving the .wav
> file could be used. Maybe it could be uploaded somewhere with the
> filename starting with the receiving station's callsign. The file
> would be automatically deleted after a preset time (2 hours?) by which
> time the transmitting station could have downloaded the file and
> looked for his own signal.
>
> Barry
> G4IAT
> --
>
> 
> --
> 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] Feature Request: TX Signal Feedback Image

[Barry Smith]

In message 
  Edfel Rivera  wrote:

> My own experience at my location, 95 watts are normally required to
> complete QSO (Puerto Rico - Caribbean).  Under better conditions maybe less
> power could be used.

I'm in the UK running 40 watts to a simple end-fed antenna. On 20m 
I've worked Canada, USA, Brazil, Japan, 1 Australian and of course 
lots of Europeans. I use pskreporter to look at how far away my 
signals are being received. I hear Indonesia, Colombia, Venezuela, 
etc. but my signals don't seem to get to those places. Maybe with a 
better antenna, but my garden is quite small.

I've not yet used the feature of replaying .wav files but...

I agree that it would be nice to see the waterfall as seen by a 
distant receiver. I wonder if the existing feature of saving the .wav 
file could be used. Maybe it could be uploaded somewhere with the 
filename starting with the receiving station's callsign. The file 
would be automatically deleted after a preset time (2 hours?) by which 
time the transmitting station could have downloaded the file and 
looked for his own signal.

Barry
G4IAT
-- 

--
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] Feature Request: TX Signal Feedback Image

[Neil Zampella]

You can do that with a Screen Capture program now.   Windows 10 includes 
one, and Gadwin Print Screen is free for the download in 32 & 64 bit 
versions.


Neil, KN3ILZ


On 6/27/2018 5:50 PM, Bill Turner wrote:
Most FT8 users have email addresses in QRZ, so you can send them a 
screen shot. In my experience (and my end fed antenna) 60 to 70 watts 
for long haul contacts are not unusual. I might be running 5 watts if 
I had a five element beam and a 70 foot tower!


Sent from Yahoo Mail on Android 



On Wed, Jun 27, 2018 at 5:28 PM, Edfel Rivera
 wrote:
Hi:

IMO, having the program send a small capture of the generated TX
signal might be useful to know how much power is being used. 
Sometimes other radio operators complaints of too much power used
for TX.  But in my experience, some distant QSO requires more
power to get a complete contact.

What I foresee is maybe a screenshot of the waterfall own signal
so WSJTX users get an idea of how strong (or disturbing) their own
signal is.  Users could then make adjustments and use less power,
generating less QSB and making possible more QSO's.  More people
happy.

Maybe, is a matter of self-control but IMO knowing visually how
our own signal is could help a lot.

Thanks.

73'

Edfel
KP4AJ



--
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] Feature Request: TX Signal Feedback Image

[Bill Turner via wsjt-devel]

Most FT8 users have email addresses in QRZ, so you can send them a screen shot. 
In my experience (and my end fed antenna) 60 to 70 watts for long haul contacts 
are not unusual. I might be running 5 watts if I had a five element beam and a 
70 foot tower!

Sent from Yahoo Mail on Android 
 
  On Wed, Jun 27, 2018 at 5:28 PM, Edfel Rivera wrote:   
Hi:
IMO, having the program send a small capture of the generated TX signal might 
be useful to know how much power is being used.  Sometimes other radio 
operators complaints of too much power used for TX.  But in my experience, some 
distant QSO requires more power to get a complete contact.  

What I foresee is maybe a screenshot of the waterfall own signal so WSJTX users 
get an idea of how strong (or disturbing) their own signal is.  Users could 
then make adjustments and use less power, generating less QSB and making 
possible more QSO's.  More people happy.  

Maybe, is a matter of self-control but IMO knowing visually how our own signal 
is could help a lot.
Thanks.
73'
EdfelKP4AJ


--
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] Feature Request: TX Signal Feedback Image

[Black Michael via wsjt-devel]

How are you proposing this be done?
You can't see your own signal except with another rig.
de Mike W9MDB


 

On Wednesday, June 27, 2018, 4:27:57 PM CDT, Edfel Rivera 
 wrote:  
 
 Hi:
IMO, having the program send a small capture of the generated TX signal might 
be useful to know how much power is being used.  Sometimes other radio 
operators complaints of too much power used for TX.  But in my experience, some 
distant QSO requires more power to get a complete contact.  

What I foresee is maybe a screenshot of the waterfall own signal so WSJTX users 
get an idea of how strong (or disturbing) their own signal is.  Users could 
then make adjustments and use less power, generating less QSB and making 
possible more QSO's.  More people happy.  

Maybe, is a matter of self-control but IMO knowing visually how our own signal 
is could help a lot.
Thanks.
73'
EdfelKP4AJ


--
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] Feature Request: fold logger Grid Square to upper case

[Magne Mæhre]

On 04/16/2018 07:04 PM, Gustafson Neil via wsjt-devel wrote:

>    In logging contacts, it is customary to record Maidenhead Grid in the
> format AA99 where the first two characters are upper-case alpha.  (In
> the full format of AA99aa99, only subsequent alpha characters are
> lower-case.)  
Just a minor note here (not wanting to start bikeshedding):

The formal specification of the Maidenhead Locator System specifies
the use of only capital letters.

The locator system was last revised during the IARU Region 1 Conference
in Landshut in 2017. The Conference unanimously approved G4JNTs proposal
named "LA17_C5_17":

http://thf.r-e-f.org/c5_iaru_r1/17landshut/agenda/LA17_C5_17%20RSGB%20-%20Clarification%20and%20Extension%20of%20the%20IARU%20Locator%20System.pdf

"IARU Locators should always be quoted and used employing all Upper Case
(Capital) letters."


--Magne / LA1BFA

--
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] Feature Request: fold logger Grid Square to upper case

[Bill Somerville]

On 16/04/2018 18:04, Gustafson Neil via wsjt-devel wrote:

Hello:
   First, thank you for the excellent WSJT-X software!
   A low-priority feature request:
   In logging contacts, it is customary to record Maidenhead Grid in 
the format AA99 where the first two characters are upper-case alpha. 
 (In the full format of AA99aa99, only subsequent alpha characters are 
lower-case.)  Since logged information in WSJT-X is frequently 
exported to other loggers, it would be a user convenience if the input 
edit process would automatically fold the first two characters to 
upper case.  See the first ADIF example below where the grid square is 
in lower case format.
  Lastly, if there is a preferred mechanism for feature requests, 
please point me in that direction.

 Many thanks and 73,
Neil W3ZQI

Is curently: K3ABC fm19 FT8
Desired:     K3ABC FM19 FT8


Hi Neil,

thanks for picking up this issue. As we already have a grid square 
validator that enforces the canonical case for Maidenhead grid locators 
I have added that to the "Log QSO" window grid entry field. That will 
have the desirable side effect of fixing up the case as you correctly 
express above.


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] Feature request: Astro Data Az/El output to rotator controller

[Rafael]

Thank you for reply. I must confess that did not read the whole manual.
I think it would not very diffcult to read the data and pass regularly to the 
controller.

Thanks for the tip!
73, Rafael
EA4BPN


19. Mar 2018 19:29 por j...@princeton.edu :


> Hi Rafael,
>
> On 3/19/2018 2:18 PM, Rafael wrote:
>> Hi,
>> I find interesting to see the Astronomical Data information, specially for 
>> those interested in EME comms.
>> However, there is a missing function to send the Moon Az/El data to a 
>> rotator controller. So, the question is, would it be possible to include a 
>> hamlib call for this task?
>> It is not easy to find a Moon tracking software for Linux, if any.
>
> From the WSJT-X User Guide, Section 4.3:
> http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-1.9.0-rc3.html#AUDIO
>  
> 
>
> "AzEl Directory: A file named azel.dat will appear in the specified 
> directory. The file contains information usable by another program for 
> automatic tracking of the Sun or Moon, as well as calculated Doppler shift 
> for the specified EME path. The file is updated once per second whenever the 
> Astronomical Data window is displayed."
>
> Many people have written their own utility programs that read the file 
> azel.dat and control rotors for tracking the moon.
>
>   -- 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 
> --
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] Feature request: Astro Data Az/El output to rotator controller

[Joe Taylor]

Hi Rafael,

On 3/19/2018 2:18 PM, Rafael wrote:

Hi,
I find interesting to see the Astronomical Data information, specially 
for those interested in EME comms.
However, there is a missing function to send the Moon Az/El data to a 
rotator controller. So, the question is, would it be possible to include 
a hamlib call for this task?

It is not easy to find a Moon tracking software for Linux, if any.


From the WSJT-X User Guide, Section 4.3:
http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-1.9.0-rc3.html#AUDIO

"AzEl Directory: A file named azel.dat will appear in the specified 
directory. The file contains information usable by another program for 
automatic tracking of the Sun or Moon, as well as calculated Doppler 
shift for the specified EME path. The file is updated once per second 
whenever the Astronomical Data window is displayed."


Many people have written their own utility programs that read the file 
azel.dat and control rotors for tracking the moon.


-- 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] Feature request: WSJT-X

[Charles Suckling]

Hi Peter

 

Re Bill's comment about not needing Settings menu during normal operation, I
just had an instance of needing to do just that.

 

 I was monitoring a weak station on 1296 EME working someone else, and
wanted to change MyCall temporarily to that of the station the weak station
was working to see if I could decode them (with AP or DS).  Accessing
Settings, changing MyCall and then back to monitoring and freq had jumped to
first default in frequency table, needing the sked frequency to be entered
again.

 

73

 

Charlie

 

  _  

From: Peter Sumner [mailto:vk8...@gmail.com] 
Sent: 16 March 2018 20:54
To: WSJT software development
Subject: Re: [wsjt-devel] Feature request: WSJT-X

 

Hello Bill,

  for a lot of my EME contacts on 50 MHz I had been using WSJT10, which
cannot do PTT via CAT so have changed over to use WSJT-X for these contacts
now as I have recently moved the IC-7600 to use only the onboard USB
interface in the radio to reduce the complexity of the shack PC as it had
three sound cards on it and multiple serial devices.  I am still trying to
find a good combination of settings to get the same decode rates as WSJT10
gave me on 50 MHz EME signals so at present there is a bit of fiddling going
on.

 

In the last few days have been running tests with Rex VK7MO on QRA64 on 144,
he has a birdie on the standard QRA64 freq so we have moved up a bit, in a
similar way I have been experimenting with configurations to seek the best
decodes from WSJT-X and again come across the behavior of being QSY'd back
to the standard frequency mid experiment.

 

It would seem my difficulty is not very common so maybe I should just stop
fiddling : -)

 

Regards,

Peter, vk5pj

 

On Sat, Mar 17, 2018 at 7:08 AM, Bill Somerville 
wrote:

On 16/03/2018 20:29, Peter Sumner wrote:

eg. on WSPR, 144.489 if I type into the box as you suggested (not tried that
before I must admit), my test frequency was 144.085 which moved the rig all
okay, then if I open the settings menu and close I am now set back to be on
144.489. This is the behaviour I would like to be able to temporarily
supress but still be able to use PTT via CAT.

Hi Peter,

can you explain why you need to open the settings menu mid-QSO please? This
seems to be the root of the issue you are describing.

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.n <mailto:wsjt-devel@lists.sourceforge.net> et
https://lists.sourceforge.net/
<https://lists.sourceforge.net/lists/listinfo/wsjt-devel>
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] Feature request: WSJT-X

[Peter Sumner]

Hello Bill,
  for a lot of my EME contacts on 50 MHz I had been using WSJT10, which
cannot do PTT via CAT so have changed over to use WSJT-X for these contacts
now as I have recently moved the IC-7600 to use only the onboard USB
interface in the radio to reduce the complexity of the shack PC as it had
three sound cards on it and multiple serial devices.  I am still trying to
find a good combination of settings to get the same decode rates as WSJT10
gave me on 50 MHz EME signals so at present there is a bit of fiddling
going on.

In the last few days have been running tests with Rex VK7MO on QRA64 on
144, he has a birdie on the standard QRA64 freq so we have moved up a bit,
in a similar way I have been experimenting with configurations to seek the
best decodes from WSJT-X and again come across the behavior of being QSY'd
back to the standard frequency mid experiment.

It would seem my difficulty is not very common so maybe I should just stop
fiddling : -)

Regards,
Peter, vk5pj

On Sat, Mar 17, 2018 at 7:08 AM, Bill Somerville 
wrote:

> On 16/03/2018 20:29, Peter Sumner wrote:
>
>> eg. on WSPR, 144.489 if I type into the box as you suggested (not tried
>> that before I must admit), my test frequency was 144.085 which moved the
>> rig all okay, then if I open the settings menu and close I am now set back
>> to be on 144.489. This is the behaviour I would like to be able to
>> temporarily supress but still be able to use PTT via CAT.
>>
>> Hi Peter,
>
> can you explain why you need to open the settings menu mid-QSO please?
> This seems to be the root of the issue you are describing.
>
> 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] Feature request: WSJT-X

[Bill Somerville]

On 16/03/2018 20:29, Peter Sumner wrote:
eg. on WSPR, 144.489 if I type into the box as you suggested (not 
tried that before I must admit), my test frequency was 144.085 which 
moved the rig all okay, then if I open the settings menu and close I 
am now set back to be on 144.489. This is the behaviour I would like 
to be able to temporarily supress but still be able to use PTT via CAT.



Hi Peter,

can you explain why you need to open the settings menu mid-QSO please? 
This seems to be the root of the issue you are describing.


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] Feature request: WSJT-X

[Peter Sumner]

Hello Joe,
   I have just tried your suggested method, if I then go to the
configuration menu and press okay, when it returns to the main interface,
the rig reverts to the SET frequency for the WSJT mode selected.

eg. on WSPR, 144.489 if I type into the box as you suggested (not tried
that before I must admit), my test frequency was 144.085 which moved the
rig all okay, then if I open the settings menu and close I am now set back
to be on 144.489.  This is the behaviour I would like to be able to
temporarily supress but still be able to use PTT via CAT.

Regards,
Peter, vk5pj

On Fri, Mar 16, 2018 at 11:19 PM, Joe Taylor  wrote:

> Hi Peter,
>
> On 3/16/2018 1:28 AM, Peter Sumner VK5PJ wrote:
>
> I would like to see if it would be possible to include a toggle on the
>> main GUI that stops WSJT-X sending frequency set commands to the
>> transceiver.
>>
>
> I do manual QSYs all the time when using WSJ-X on VHF bands.  It's as
> simple as typing the desired new frequency into the band-selector drop-down
> control.  For example, I might type "50.285" (or abbreviated as "285k")
> into this window to escape a birdie on 20.260.
>
> Doesn't this capability address your problem?
>
> -- 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
>
--
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] Feature request: WSJT-X

[Joe Taylor]

Hi Peter,

On 3/16/2018 1:28 AM, Peter Sumner VK5PJ wrote:

I would like to see if it would be possible to include a toggle on the 
main GUI that stops WSJT-X sending frequency set commands to the 
transceiver.  


I do manual QSYs all the time when using WSJ-X on VHF bands.  It's as 
simple as typing the desired new frequency into the band-selector 
drop-down control.  For example, I might type "50.285" (or abbreviated 
as "285k") into this window to escape a birdie on 20.260.


Doesn't this capability address your problem?

-- 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] Feature request: WSJT-X

[John Ward]

Aah. Ok. One day ill get to EME.

Thanks and Regards
John Ward

73 de John
ZS1EQ

On 16 Mar 2018 08:42,  wrote:

> Hi John
>
> The problem OZ1LPR ran into was during some EME tests of the new Doppler
> modes in 1.9.0.  He was attempting to operate manual split with Doppler
> tracking set to off,  in an attempt to disable CAT frequency commands to
> his radio completely.  He found that having set up his VFO A and VFO B to
> different frequencies (so as to be able to simulate a non CAT station, eg
> someone using WSJT10) one of the VFOs would still  get reset by the
> program unexpectedly.  This behaviour prevented us from carrying out the
> test.
>
> He also could not use the Rig at None, as he used PTT via CAT.
>
> 73
>
> Charlie
>
>
>
>
> > Morning. Cant you simply avoid the birdie by adjusting the tx/rx
> frequency
> > settings with the mouse on the waterfall display and then use the "fake"
> > options in the settings?
> >
> > Thanks and Regards
> > John Ward
> >
> > 73 de John
> > ZS1EQ
> >
> > On 16 Mar 2018 8:17 AM, 
> wrote:
> >
> >> Hi Peter
> >>
> >> One option might be to arrange PTT via a serial port to the mic PTT line
> >> and not have to use CAT, in which case the Rig to 'None' would work.
> >>
> >> I have heard of one other request for what you are asking, from OZ1LPR,
> >> for much the same reasons.
> >>
> >> 73
> >>
> >> Charlie G3WDG
> >>
> >> >>
> >> >> Hello,
> >> >>
> >> >
> >> > firstly my thanks to those who are at the coal face developing WSJT
> >> and
> >> > its
> >> > brothers.
> >> >
> >> > I would like to see if it would be possible to include a toggle on the
> >> > main
> >> > GUI that stops WSJT-X sending frequency set commands to the
> >> transceiver.
> >> > When I control my IC-7600 and my IC-910 with WSJT-X it does a great
> >> job
> >> of
> >> > setting the rig to the right frequency for the mode but some times
> >> there
> >> > is
> >> > a need to be on a non standard frequency if some one has a birdie or
> >> > chasing EME.  I find if I go into the settings menu and then come out,
> >> (to
> >> > check a setting which we all do some times) the software does a
> >> frequency
> >> > set to the rig and I end up back on a standard frequency for that
> >> mode,
> >> > which is for those times very un helpful especially when chasing EME
> >> on
> >> 50
> >> > MHz
> >> >
> >> > I had in the past set WSJT-X to be "no rig" to stop this but now I
> >> need
> >> to
> >> > send PTT via CAT to the IC7600 so cannot use that strategy now.
> >> >
> >> > Could the big Green / Red indicator next to the frequency readout be
> >> made
> >> > into a toggle ? then a mouse click could change the rig mode, add the
> >> > colour BLUE (first colour that jumped into my head) to represent the
> >> rig
> >> > frequency will not be set by the software? (does not require any new
> >> GUI
> >> > real estate to add the feature).  Then a simple mouse click on the
> >> > tri-coloured dot can put it back to GREEN for automated setting of the
> >> > rig.
> >> >
> >> > Unsure if it is only me that experiences this in day to day operating,
> >> if
> >> > no others support it, then I expect this will not make it through.
> >> >
> >> > Regards,
> >> > Peter, VK5PJ
> >> > 
> >> --
> >> > 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
>
--
Check out the vibrant tech community on one of the world's most

Re: [wsjt-devel] Feature request: WSJT-X

[charlie]

Hi John

The problem OZ1LPR ran into was during some EME tests of the new Doppler
modes in 1.9.0.  He was attempting to operate manual split with Doppler
tracking set to off,  in an attempt to disable CAT frequency commands to
his radio completely.  He found that having set up his VFO A and VFO B to
different frequencies (so as to be able to simulate a non CAT station, eg
someone using WSJT10) one of the VFOs would still  get reset by the
program unexpectedly.  This behaviour prevented us from carrying out the
test.

He also could not use the Rig at None, as he used PTT via CAT.

73

Charlie




> Morning. Cant you simply avoid the birdie by adjusting the tx/rx frequency
> settings with the mouse on the waterfall display and then use the "fake"
> options in the settings?
>
> Thanks and Regards
> John Ward
>
> 73 de John
> ZS1EQ
>
> On 16 Mar 2018 8:17 AM,  wrote:
>
>> Hi Peter
>>
>> One option might be to arrange PTT via a serial port to the mic PTT line
>> and not have to use CAT, in which case the Rig to 'None' would work.
>>
>> I have heard of one other request for what you are asking, from OZ1LPR,
>> for much the same reasons.
>>
>> 73
>>
>> Charlie G3WDG
>>
>> >>
>> >> Hello,
>> >>
>> >
>> > firstly my thanks to those who are at the coal face developing WSJT
>> and
>> > its
>> > brothers.
>> >
>> > I would like to see if it would be possible to include a toggle on the
>> > main
>> > GUI that stops WSJT-X sending frequency set commands to the
>> transceiver.
>> > When I control my IC-7600 and my IC-910 with WSJT-X it does a great
>> job
>> of
>> > setting the rig to the right frequency for the mode but some times
>> there
>> > is
>> > a need to be on a non standard frequency if some one has a birdie or
>> > chasing EME.  I find if I go into the settings menu and then come out,
>> (to
>> > check a setting which we all do some times) the software does a
>> frequency
>> > set to the rig and I end up back on a standard frequency for that
>> mode,
>> > which is for those times very un helpful especially when chasing EME
>> on
>> 50
>> > MHz
>> >
>> > I had in the past set WSJT-X to be "no rig" to stop this but now I
>> need
>> to
>> > send PTT via CAT to the IC7600 so cannot use that strategy now.
>> >
>> > Could the big Green / Red indicator next to the frequency readout be
>> made
>> > into a toggle ? then a mouse click could change the rig mode, add the
>> > colour BLUE (first colour that jumped into my head) to represent the
>> rig
>> > frequency will not be set by the software? (does not require any new
>> GUI
>> > real estate to add the feature).  Then a simple mouse click on the
>> > tri-coloured dot can put it back to GREEN for automated setting of the
>> > rig.
>> >
>> > Unsure if it is only me that experiences this in day to day operating,
>> if
>> > no others support it, then I expect this will not make it through.
>> >
>> > Regards,
>> > Peter, VK5PJ
>> > 
>> --
>> > 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] Feature request: WSJT-X

[John Ward]

Morning. Cant you simply avoid the birdie by adjusting the tx/rx frequency
settings with the mouse on the waterfall display and then use the "fake"
options in the settings?

Thanks and Regards
John Ward

73 de John
ZS1EQ

On 16 Mar 2018 8:17 AM,  wrote:

> Hi Peter
>
> One option might be to arrange PTT via a serial port to the mic PTT line
> and not have to use CAT, in which case the Rig to 'None' would work.
>
> I have heard of one other request for what you are asking, from OZ1LPR,
> for much the same reasons.
>
> 73
>
> Charlie G3WDG
>
> >>
> >> Hello,
> >>
> >
> > firstly my thanks to those who are at the coal face developing WSJT and
> > its
> > brothers.
> >
> > I would like to see if it would be possible to include a toggle on the
> > main
> > GUI that stops WSJT-X sending frequency set commands to the transceiver.
> > When I control my IC-7600 and my IC-910 with WSJT-X it does a great job
> of
> > setting the rig to the right frequency for the mode but some times there
> > is
> > a need to be on a non standard frequency if some one has a birdie or
> > chasing EME.  I find if I go into the settings menu and then come out,
> (to
> > check a setting which we all do some times) the software does a frequency
> > set to the rig and I end up back on a standard frequency for that mode,
> > which is for those times very un helpful especially when chasing EME on
> 50
> > MHz
> >
> > I had in the past set WSJT-X to be "no rig" to stop this but now I need
> to
> > send PTT via CAT to the IC7600 so cannot use that strategy now.
> >
> > Could the big Green / Red indicator next to the frequency readout be made
> > into a toggle ? then a mouse click could change the rig mode, add the
> > colour BLUE (first colour that jumped into my head) to represent the rig
> > frequency will not be set by the software? (does not require any new GUI
> > real estate to add the feature).  Then a simple mouse click on the
> > tri-coloured dot can put it back to GREEN for automated setting of the
> > rig.
> >
> > Unsure if it is only me that experiences this in day to day operating, if
> > no others support it, then I expect this will not make it through.
> >
> > Regards,
> > Peter, VK5PJ
> > 
> --
> > 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] Feature request: WSJT-X

[charlie]

Hi Peter

One option might be to arrange PTT via a serial port to the mic PTT line
and not have to use CAT, in which case the Rig to 'None' would work.

I have heard of one other request for what you are asking, from OZ1LPR,
for much the same reasons.

73

Charlie G3WDG

>>
>> Hello,
>>
>
> firstly my thanks to those who are at the coal face developing WSJT and
> its
> brothers.
>
> I would like to see if it would be possible to include a toggle on the
> main
> GUI that stops WSJT-X sending frequency set commands to the transceiver.
> When I control my IC-7600 and my IC-910 with WSJT-X it does a great job of
> setting the rig to the right frequency for the mode but some times there
> is
> a need to be on a non standard frequency if some one has a birdie or
> chasing EME.  I find if I go into the settings menu and then come out, (to
> check a setting which we all do some times) the software does a frequency
> set to the rig and I end up back on a standard frequency for that mode,
> which is for those times very un helpful especially when chasing EME on 50
> MHz
>
> I had in the past set WSJT-X to be "no rig" to stop this but now I need to
> send PTT via CAT to the IC7600 so cannot use that strategy now.
>
> Could the big Green / Red indicator next to the frequency readout be made
> into a toggle ? then a mouse click could change the rig mode, add the
> colour BLUE (first colour that jumped into my head) to represent the rig
> frequency will not be set by the software? (does not require any new GUI
> real estate to add the feature).  Then a simple mouse click on the
> tri-coloured dot can put it back to GREEN for automated setting of the
> rig.
>
> Unsure if it is only me that experiences this in day to day operating, if
> no others support it, then I expect this will not make it through.
>
> Regards,
> Peter, VK5PJ
> --
> 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] Feature request

[Glen Brown]

Kim,
Yes, it should be a separate window so WSJT stays actively decoding.  For
FT8 noise would be sampled over the last 3 seconds of the period and
averaged for a single number.  For JT65, the sampling would be over the
last 12 seconds.  With WSPR sampling could be continuous unless someone
close is transmitting.
The noise window would have present time, with the value of the last
sample, on one edge (say the left) with older sample values scrolling to
the right.  When you see a jump in the noise level, it's time to call CQDX.
It would also be useful to write a comma-delimited file to compare data in
a spreadsheet app.
I suspect both FT8 and JT65 are going to be hot on 80 and 160m this
winter.  And, FT8 may well be the best way to work Bouvet on 160.  This
would be a great tool for mnioring low band condx.

Thanks,
Glen W6GJB





On Dec 12, 2017 8:38 PM, "Kim gross"  wrote:

> First let me say I would be interested in helping if not doing this, I
> know some programing just not enough about this project.
> But an option to have it look up all call signs info and giving
> heading/distance info in the band activity window off to the right. For
> larger enough screens it could be displayed and sized.
>
> Kim
>
>
> 
> --
> 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] Feature Request of FT8 TX Frequency limitation less than 2kHz

[Tsutsumi Takehiko]

Hi,

Thank you very much for providing so many additional comments to my request.

However, these comments are not directly related to my proposal. I included the 
fact that members are interested in JT65 phase out policy and it should be 
decided by the owner of wsjt-x and then reflect to the working frequency table 
accordingly.

I hope my request about FT8 TX frequency limitation will be included in the 
next GA release.

Now, I close the discussion.

Finally, we are so happy guys to be able to talk this oversighted issue as a 
happy problem.

Thank you.

Regards,

take

de JA5AEA

-

Please expand FT8 channel width from 2kHz to 2.5KHz, reduce JT65 channel width 
from 2.0kHz to 1.5kHz and add the feature to limit FT8 TX frequency less than 
2.5kHz at the next GA release. We also need to appeal to radio amateur society 
and regulatory bodies to be able to expand total wsjt-x channel, i.e. total 
5kHz considering popularity of wsjt-x formats and adaptation among major 
DX-peditions.

Reasons are stated as follow.

1. The working frequency table was and is designed and planned that the width 
of FT8 is 2kHz. However, the limitation feature of 2kHz to the operator has not 
implemented to wsjt-x software.

2. Recently we observe above 2kHz communication practice by operators who does 
not know above design concept and the interference to adjacent wsjt-x channel 
such as JT65 is created.

3. Considering FT8 traffic expansion and JT65 traffic reduction trend,  it is 
appropriate for FT8 channel width to 2.5KHz and for JT65 channel width to 
1.5kHz.

4. Such TX frequency limitation practice is  implemented to JT65 operation at 
30m to protect WSPR channel  in wsjt-x software.

Note: Members are interested in JT65phase out policy and it should be decided 
by the owner of wsjt-x and then reflect to the working frequency table 
accordingly. Details can be seen in the thread of this topic in this mailing 
list.


-


Sent from Mail for Windows 10


--
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] Feature Request of FT8 TX Frequency limitation less than 2kHz

[Karl Barth]

Hi,

I use(d) JT9(a) slow, JT65 and FT8  on 6 , 4m and 2m quite a lot  and achieved with JT9(a) quite a number of qso's iwhich did not complete in JT65 or FT8.
The actual difference between J9a and JT65 may be even slightly more that the two dB calculated theory: 2dB is a lot at flat VHF conditions .
Each mode has its merrits  and its limitations.
Charly, DF5VAE
 


Steven Franke schrieb am 22.11.2017 14:55:


Hi Mike,

> On Nov 22, 2017, at 1:31 PM, Black Michael via wsjt-devel
>  wrote:
> 
> JT65 is more sensitive than JT9 too.

I don’t think that I agree with this. According to the WSJT-X User Guide,
second paragraph, "JT9 was originally designed for the LF, MF, and lower HF
bands. Its submode JT9A is 2 dB more sensitive than JT65 while using less than
10% of the bandwidth.” 

The User Guide statement is referring to simulations based on an AWGN channel.
What’s the basis or context for your assertion?

Steve k9an
--
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] Feature Request of FT8 TX Frequency limitation less than 2kHz

[Philippe CHARDON (LaPoste) via wsjt-devel]

I figured out that FT8 operation is similar to contest operation. The band is 
crowded, there is some overlapping between stations.
Some hams choose a frequency, stick to it and call. Some others listen (or read 
with FT8), browse the band, and try to contact the ones who call.
During a contest, the portion of band devoted to SSB is fully occupied. This 
often the same with FT8, especially if the propagation is good.

Let’s compare the band slots. SSB needs 2.5Khz, FT8 needs 50 Hz.

The station « density » is 40 per 100 Khz for SSB and 20 per KHz for FT8.

On 20m for example, about 300 KHz of spectrum allocated to SSB can accommodate 
120 QSOs. In order to accommodate the same number of QSOs with FT8, we would 
need a 6 KHz slot on 20m.

In case FT8 remains or becomes more and more popular, if we want to provide the 
same opportunities to FT8 as SSB’s (an provide some band portions dedicated to 
DX), we can consider expanding the FT8 slot.

If we do the same calculation on 40m (let’s say there is 120KHz available for 
SSB), so 48 QSO for SSB, the is a need of a 2,4KHz slot for FT8 in order to 
provide a fair balance between SSB and FT8.

We can apply the same reasoning to other bands.

Considering the quick decline of JT65 operation due to the popularity of FT8, 
we cannot predict if this popularity is sustainable. Maybe there will be a more 
attracting mode popping out in the next future.

If FT8 becomes one of the preferred modes to make QSOs, my opinion is that 
there will be some needs to review band plan.

Best Regards

Phil, F5FDV


Le 22 nov. 2017 à 05:19, Gary Kohtala - K7EK via wsjt-devel 
 a écrit :

Perhaps it is time to phase out JT65 on HF, in favor of FT8 and JT9. That would 
most certainly be best use of spectrum, considering the bandwidths and 
efficiency of those modes.

Best regards,

Gary, K7EK



From: Black Michael via wsjt-devel 
To: WSJT software development  
Cc: Black Michael 
Sent: Tuesday, November 21, 2017 11:41 AM
Subject: Re: [wsjt-devel] Feature Request of FT8 TX Frequency limitation less 
than 2kHz

Is anybody on JT65 running out of room at 500-2000 offset?
Why do we need to change anything?
Yes...SOME rigs can do 3000, many cannot. So if you want to transmit above 2500 
you may be losing a lot of people (including DXpeditions).
Moving the 7.074 to 7.073 means anybody running an older version will miss out 
on the lower offset by default.

FT8 can also decode overlapping signals fairly well...

Are you really unable to find a spot to transmit?  Note that the popularity 
will decrease as everybody gets everybody else worked.


On Tuesday, November 21, 2017, 10:07:11 AM CST, Libor Holouš  
wrote:


Hello guys..
 
According this theme I'd like to ask about expanding the band possibility. FT8 
seems to be very popular these days and there are some DXpeditions operating 
there, so 2 kHz is not enough space for all that traffic. The extreme is 40 and 
20m, but when propagation allows, the other bands too (on higher bandsis not 
possible to see most of EU traffic, from DX side it must be crazy :-)
 
I'd suggest add another kHz lower. Lots of newer radios got 3kHz filter, so it 
is possible to hear whole band easily. Beginning of band should be used by DX 
stations (expeditons) using fixed freq. while using split operation (for 
transmit are freq. bellow 200Hz and above 2.4kHz practicaly unusable). For JT65 
users then should be less possibility of intrusion and there will be more space 
for non-dx operations too.
 
Example:
Expedition tunes in VFO B 14072kHz, audio sets between approx. 1100-1300. VFO-A 
for RX tunes 1kHz higher 14073 and sets 3kHz filter. Sets Hold TX freq.
CQ message "CQ UP DX1DX square".
RR73 should be a standard in this case.
 
User, normaly set on 14073 should see expedion calling betwen 100-300Hz, what 
is readable, but difficult to transmit there directly, but can use 300-2400Hz 
for call easily, if sets split on the radio, can easily use up to approx. 
2930Hz, still readible by expedition. And voila: 14073000+2930+60Hz = 
14075990Hz. So intrusion to JT65 band is solved. 
 
The only expedition was using radio split was 5T5OK - used UP2 - but it was 
unfortunately in JT65 band. Extending band by 1000Hz lower could help a bit.
 
I don't know the details of earlier mentioned developed DX mode in this 
discussion, so for today's conditions it is possible solution without some SW 
development (except overwrite freq. list in future)
 
It's theme for discussion. FT8 started revolution in digital modes, and is much 
more popular now, than PSK31 was.
The JT65 was not popular for me, due looong time procedure of the QSO, if it 
was DX there, it was for several coffies, until got QSO. It's still not as fast 
as RTTY or PSK, but there is no space for macros, most users use on PSK 
(Everybody seen the QSO, while complete PC and SW setup, WX, age and lots of 
rubbish was send on PSK), so waiting for the qso was also sometimes bor