Re: [wsjt-devel] Field Day Frequencies

[rjai...@gmail.com]

You’re correct that ARRL doesn’t suggest any different frequencies for FT8
on field day. ARRL doesn’t suggest any specific frequencies for field day
on any mode, in fact.

Last year, however, a group of hams on a Facebook group suggested that FD
participants use different frequencies so as not to interfere with normal
FT8 traffic. This year they have stated that they will not have a frequency
list because it didn’t work last year.

This year there is also FT4 available which may be better for rapid fire FD
contacts.

73
Ria
N2RJ

On Wed, Jun 24, 2020 at 6:01 AM Neil Zampella  wrote:

> The ARRL has not set any 'different' frequencies for Field Day other than
> the usual no contests on WARC bands and 60 meters.   The standard FT8 & FT4
> frequencies should be used.   You can verify this by going to the ARRL
> website under Field Day rules.
>
> Neil, KN3ILZ
> On 6/23/2020 10:09 PM, Matthew Miller wrote:
>
> For ARRL Field Day 2019, I recall there was a different set of frequencies
> used for FT8.
>
>
>
> Does anyone know if there will be a de-facto set of frequencies to use for
> Field Day 2020 for FT8, and also for FT4?  Or the default ones?
>
>
>
> I did a Google search but I didn’t come up with anything recent.
>
>
>
> -Matt / KK4NDE
>
>
>
> 
>  Virus-free.
> www.avg.com
> 
> <#m_7644369794834708075_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> ___
> 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] K1JT?

[rjai...@gmail.com]

Hi Rudy,

He travels sometimes so he may be just busy.

73
Ria, N2RJ

On Wed, Jan 1, 2020 at 7:45 AM on4ckt  wrote:

>
> Hello, Does anyone know anything about Joe K1JT? A few weeks ago I sent
> him the user manual of WSJT-X v2.1.2 in Dutch. I have not heard from him
> since. I do not know whether he has received the file or not. Or is he sick
> or on vacation. Like info.
>
> With best regards,
> ON4CKT Rudy
>
>
> Verzonden vanaf mijn Samsung Galaxy-smartphone.
>
> ___
> 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] Illegal auto mode?

[rjai...@gmail.com]

There is a difference. They don’t auto CQ and full auto are in restricted
sub-bands.

Ria
N2RJ

On Sat, Aug 17, 2019 at 2:02 PM Ryan Tourge  wrote:

> It’s short sighted attempts to blat. Packet, APRS, the Winlink modes, all
> auto sequence after a connection is initiated. There really is no
> difference.
>
> On Sat, Aug 17, 2019 at 1:53 PM Jim Shorney 
> wrote:
>
>>
>> Rules pertaining to Automatic Operation can be found in Part 97 sections:
>>
>> 97.3(6)
>> 97.221
>>
>> 73
>>
>> -Jim
>> NU0C
>>
>> On Sat, 17 Aug 2019 17:07:20 +
>> Andy Durbin  wrote:
>>
>> > "This is illegal software in the US and probably elsewhere, and should
>> > not be used, even with the added line "always attend to your transceive
>> > when using" this does not make it legal."
>> >
>> > What specific FCC regulations permit a single QSO to be auto sequenced
>> but prohibit auto sequencing of 2 or more QSO?
>> >
>> > I had been under the impression that disallowing auto QSO sequencing
>> was a preference of the developers so, if it is illegal, I'd appreciate a
>> reference.   I can legally allow an unlicensed operator to make my QSO but
>> I can't allow a supervised computer to do it?
>> >
>> > Before you all jump on me - I have no interest in running an automatic
>> QSO machine.  I'm only interested in the regulatory aspect of this.
>> >
>> > 73,
>> > Andy, k3wyc
>>
>>
>>
>> ___
>> 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] Illegal auto mode?

[rjai...@gmail.com]

It’s not illegal to have fully automated stations but current fcc
regulations have stipulations which are detailed in 97.221.

Technically a ft8 auto responding station would be covered under 97.221(c)
- it is responding to interrogation under local or remote control, and less
than 500Hz.

However, fully automatic, unattended CQs may be illegal, except in the ACDS
bands under 97.221(b).

This is different from the recent resolution for ARRL awards and contests.
That specific resolution only pertains to ARRL contest and awards activity
and has no legal binding like FCC rules.

In my personal opinion, claiming full automatic unattended robot operation
for awards or contest credit is unethical and shouldn’t be done.  It also
adds fuel to the fire to those who want to see FT8 banned from the airwaves
or restricted out of “their” awards sandbox.

But for an experiment? Knock yourself out.

73
Ria, N2RJ

§ 97.221 Automatically controlled digital station.

(a) This rule section does not apply to an auxiliary station, a  beaconstation,
a  repeater station, an  earth station, a  space station, or a space
telecommand
station.

(b) A station may be automatically controlled while transmitting a RTTYor
data emission on the 6 m or shorter wavelength bands, and on the
28.120-28.189 MHz, 24.925-24.930 MHz, 21.090-21.100 MHz, 18.105-18.110 MHz,
14.0950-14.0995 MHz, 14.1005-14.112 MHz, 10.140-10.150 MHz, 7.100-7.105
MHz, or 3.585-3.600 MHz segments.

(c) Except for channels specified in § 97.303(h)
, a station may be
automatically controlled while transmitting a  RTTY or  dataemission on any
other frequency authorized for such emission types provided that:

(1) The station is responding to interrogation by a station under
local or remote
control; and

(2) No transmission from the automatically controlled station occupies a
bandwidth of more than 500  Hz.

On Sat, Aug 17, 2019 at 1:27 PM Andy Durbin  wrote:

> "This is illegal software in the US and probably elsewhere, and should
> not be used, even with the added line "always attend to your transceive
> when using" this does not make it legal."
>
> What specific FCC regulations permit a single QSO to be auto sequenced but
> prohibit auto sequencing of 2 or more QSO?
>
> I had been under the impression that disallowing auto QSO sequencing was a
> preference of the developers so, if it is illegal, I'd appreciate a
> reference.   I can legally allow an unlicensed operator to make my QSO but
> I can't allow a supervised computer to do it?
>
> Before you all jump on me - I have no interest in running an automatic QSO
> machine.  I'm only interested in the regulatory aspect of this.
>
> 73,
> Andy, k3wyc
> ___
> 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] Lid operators or bad design?

[rjai...@gmail.com]

Are they in the same time slot? If they are on odd and you are on even, no
real harm. FT8 is operated primarily split anyway.

I do know this used to be an issue when lock rx=tx was a thing that people
would work you then transmit in your frequency slot.

73,
Ria
N2RJ

On Sun, Jul 28, 2019 at 11:58 AM Andy Durbin  wrote:

> Everyone who uses WSJT-X for FT8 must have noticed the number of operators
> who answer a CQ and then, when the QSO is complete, call CQ on the same
> frequency.   Are all these operators really stupid or are they being
> trapped by a weakness in the user interface design?
>
> 73,
> Andy, k3wyc
> ___
> 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] Contest confusion

[rjai...@gmail.com]

At least on the ARRL end, full auto is being addressed.

Ria
N2RJ

On Thu, Jul 25, 2019 at 6:57 AM James Shaver  wrote:

> Well, the people who went off-reservation and decided to take outside
> steps to make it fully automated despite it being said over and over that
> making an “automated QSO machine” was never the intention certainly did not
> help that cause. I know more than one disabled ham who has been able to
> play in contests for the first time in decades because of FT8 and they’ll
> be the ones getting hurt in the end. And before this becomes a back and
> forth, I’ll head some of it off by saying that making “separate categories”
> is not acceptable.
>
> > On Jul 24, 2019, at 7:45 PM, "rjai...@gmail.com" 
> wrote:
> >
> > From all indications they're out with the torches and pitchforks to
> > ban FT8 from "serious" contesting anyway. So you won't have to put up
> > with this for too long.
> >
> > I really don't get it... FT8 has brought many more out to play radio
> > on a contest weekend (and other times). Maybe some people just love
> > hearing dead air.
> >
> > Ria
> > N2RJ
> >
> >> On Wed, 24 Jul 2019 at 19:16, John Kludt  wrote:
> >>
> >> Folks,
> >>
> >> I just work'em.  Most don't seem to mind.  I have an exchange of calls
> and grids.  Yes, I suppose if for some reason somebody not in the contest
> where to decide to send in a log and they hadn't logged me because they
> didn't get a signal report - why would they send in a log as they are not
> in the contest - I could get dinged.  In this weekends contest I did not
> have a single person persist in sending R-xx.  They just seemed to move on,
> too.  If they didn't, I did and let it go.
> >>
> >> The real answer is to move to FT4.  From the ground up, a contest
> mode.  Using 6 as an example let the non-contesters have FT8 and 50.313 and
> move the contesters to FT4 and 50.318.  If you can run FT8 you can run
> FT4.  The upgrade is a no-brainer.  And FT4 is really, really fast and you
> have to pay attention - actually very cool!
> >>
> >> How much more kvetching we going to have about this?  It's a  hobby.
> >>
> >> John
> >>
> >>> On Wed, Jul 24, 2019 at 6:34 PM Bill Frantz  wrote:
> >>>
> >>>> On 7/22/19 at 4:03 PM, _vk3a...@vkdxer.net (Laurie, VK3AMA) wrote:
> >>>>
> >>>>> On 22/07/2019 7:16 am, Jim Brown wrote:
> >>>>> so I quickly switched out of contest mode to work him. :)
> >>>>>
> >>>>> What I WOULD like is to able to do this without going to
> >>>>> Settings Advanced. All those clicks loses a TX cycle.
> >>>>>
> >>>>> 73, Jim K9YC
> >>>>
> >>>> Simple and only requires a single mouse click. Setup two
> >>>> configurations in WSJT-X, one for you desired contest and the
> >>>> other non-contest. Once setup, it is a single click using the
> >>>> "Configuration" menu to switch between contest and non-contest.
> >>>>
> >>>> de Laurie VK3AMA
> >>>
> >>> I'm sorry to disagree Laurie. On my Mac (10.14.6 with wsjt-x
> >>> v2.1.0 24fcd1), when I switch between my F configuration and
> >>> my plain QSO one, I lose all my waterfall history, and my two
> >>> windows become top left justified on top of each other. They
> >>> also return to their default sizes. There's a big cost to get
> >>> things back to a workable configuration and refill the
> >>> waterfall. It may just be better to pay the mouse clicks to go
> >>> to the Advanced menu.
> >>>
> >>> Does anyone else see this behavior?
> >>>
> >>> 73 Bill AE6JV
> >>>
> >>> ---
> >>> Bill Frantz| When an old person dies, a   | Periwinkle
> >>> (408)356-8506  | library burns. - Joe McGawon | 16345
> >>> Englewood Ave
> >>> www.pwpconsult.com | Irish Ethnographer   | Los Gatos,
> >>> CA 95032
> >>>
> >>>
> >>>
> >>> ___
> >>> 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
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Contest confusion

[rjai...@gmail.com]

>From all indications they're out with the torches and pitchforks to
ban FT8 from "serious" contesting anyway. So you won't have to put up
with this for too long.

I really don't get it... FT8 has brought many more out to play radio
on a contest weekend (and other times). Maybe some people just love
hearing dead air.

Ria
N2RJ

On Wed, 24 Jul 2019 at 19:16, John Kludt  wrote:
>
> Folks,
>
> I just work'em.  Most don't seem to mind.  I have an exchange of calls and 
> grids.  Yes, I suppose if for some reason somebody not in the contest where 
> to decide to send in a log and they hadn't logged me because they didn't get 
> a signal report - why would they send in a log as they are not in the contest 
> - I could get dinged.  In this weekends contest I did not have a single 
> person persist in sending R-xx.  They just seemed to move on, too.  If they 
> didn't, I did and let it go.
>
> The real answer is to move to FT4.  From the ground up, a contest mode.  
> Using 6 as an example let the non-contesters have FT8 and 50.313 and move the 
> contesters to FT4 and 50.318.  If you can run FT8 you can run FT4.  The 
> upgrade is a no-brainer.  And FT4 is really, really fast and you have to pay 
> attention - actually very cool!
>
> How much more kvetching we going to have about this?  It's a  hobby.
>
> John
>
> On Wed, Jul 24, 2019 at 6:34 PM Bill Frantz  wrote:
>>
>> On 7/22/19 at 4:03 PM, _vk3a...@vkdxer.net (Laurie, VK3AMA) wrote:
>>
>> >On 22/07/2019 7:16 am, Jim Brown wrote:
>> >>so I quickly switched out of contest mode to work him. :)
>> >>
>> >>What I WOULD like is to able to do this without going to
>> >>Settings Advanced. All those clicks loses a TX cycle.
>> >>
>> >>73, Jim K9YC
>> >
>> >Simple and only requires a single mouse click. Setup two
>> >configurations in WSJT-X, one for you desired contest and the
>> >other non-contest. Once setup, it is a single click using the
>> >"Configuration" menu to switch between contest and non-contest.
>> >
>> >de Laurie VK3AMA
>>
>> I'm sorry to disagree Laurie. On my Mac (10.14.6 with wsjt-x
>> v2.1.0 24fcd1), when I switch between my F configuration and
>> my plain QSO one, I lose all my waterfall history, and my two
>> windows become top left justified on top of each other. They
>> also return to their default sizes. There's a big cost to get
>> things back to a workable configuration and refill the
>> waterfall. It may just be better to pay the mouse clicks to go
>> to the Advanced menu.
>>
>> Does anyone else see this behavior?
>>
>> 73 Bill AE6JV
>>
>> ---
>> Bill Frantz| When an old person dies, a   | Periwinkle
>> (408)356-8506  | library burns. - Joe McGawon | 16345
>> Englewood Ave
>> www.pwpconsult.com | Irish Ethnographer   | Los Gatos,
>> CA 95032
>>
>>
>>
>> ___
>> wsjt-devel mailing list
>> wsjt-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel


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

Re: [wsjt-devel] WSJT Audio Input Loss

[rjai...@gmail.com]

I’ve seen this with other radios. Definitely not a flex only issue.

Ria
N2RJ

On Wed, Jul 3, 2019 at 4:58 PM DX Jami via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> Peter,
>
> Flex has its own set of unique problems and fixes.  Suggest you post your
> question on the Flex forum page.  Good luck.
>
> Danny
> AH6FX/W4
>
> On Wednesday, July 3, 2019, 3:11:48 PM EDT, Peter Putnam 
> wrote:
>
>
> Greetings,
>
> I have been using WSJT-X quite successfully for several years during
> June VHF Contests. I experienced a failure of the WSJT program to accept
> received audio input after several hours of proper operation during the
> recent Field Day exercise.
>
> I'll provide a brief outline and reply with more detail, should it be
> needed.
>
> My computer is a Dell Optiplex 780 running Win 7 Pro SP1, 64-bit. The
> WSJT-X software version is 2.0.1 7ddcb7.
>
> My receiver is a Flex 6500. It passes data to a Flex-supplied "DAX"
> program that interfaces various applications that wish to receive the
> audio stream. WSJT accepts the stream and displays results on the Wide
> Graph and a small audio signal-strength window. Activity proceeded
> normally for the first three hours of Field Day, until both the Wide
> Graph and the audio signal-strength stopped showing any incoming audio.
>
> I can't offer any help on what might have caused the problem. It was
> abrupt and seemingly unrelated to any other system actions. I am unable
> to reproduce the problem.
>
> Several operators spent several hours speculating about what a solution
> might be. Program restarts and computer re-boots (time-tested favorite
> of generations) changed nothing. The only useful clue was that the DAX
> audio output stream was present and could be re-directed to Fldigi, but
> not to WSJT-X.
>
> I was able to restore operation for a brief period by stopping WSJT,
> renaming WSJT.ini and restarting WSJT. That fix lasted for a half hour.
> Repeating the procedure provided operation for the rest of Field Day.
>
> The two .ini files that were renamed are available for your inspection,
> along with the one that continued to function.
>
> Any suggestions you can offer to prevent a recurrence would be greatly
> appreciated.
>
> Regards,
> Peter
> NI6E
>
>
>
>
>
>
> ___
> 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] Please remove me from your mailing list.

[rjai...@gmail.com]

I believe simply replying “unsubscribe” will also do the trick

Ria
N2RJ

On Tue, Jun 25, 2019 at 4:20 PM James Shaver  wrote:

> You need to click on the link at the bottom of every email from this list
> to unsubscribe.
>
> 73,
>
> Jim S.
> N2ADV
>
> On Jun 25, 2019, at 1:58 PM, James Buffington 
> wrote:
>
> j...@jimbuffington.com
> ___
>
> *IN GOD WE TRUST*
>
> "The Ultimate in Website Design for Exceptional Clients"
>
> Thorns may hurt you, men desert you, sunlight turn to fog; but you're
> never friendless ever, if you have a dog. - *Douglas Malloch*
>
>
> 662-813-3145
> j i...@jimbuffington.com
>
> *CONFIDENTIALITY DISCLAIMER*
> This email (including attachments) is confidential information protected
> by the Electronic Communications Privacy Act 18 U.S.C. §2510-2521 and any
> other applicable law, and may not be opened or forwarded without consent of
> the named recipient(s). It is intended only for the use of the individual
> or entity named herein. If the reader of this message is not the intended
> recipient, or the employee or agent responsible to deliver it to the
> intended recipient, you are hereby notified that any retention,
> dissemination, distribution or copying of this communication is strictly
> prohibited. If you have received this communication in error, please
> immediately notify us by return email. Thank you.
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

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

[rjai...@gmail.com]

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

Ria
N2RJ

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

> On 6/2/2019 11:32 AM, Joe Taylor wrote:
> > To: Users of WSJT-X -- especially those interested in radio contesting
> > From: WSJT Development Group
> >
> > As you know, we have been developing a protocol called FT4 for use in
> radio contesting.  A new version of FT4 is now available
> > for testing in WSJT-X 2.1.0-rc6.
> >
> > PLEASE NOTE THAT FT4 IN RELEASE CANDIDATE 6 IS NOT COMPATIBLE WITH THAT
> IN ANY PREVIOUS RELEASE.
> >
> > Therefore: Please stop using WSJT-X 2.1.0-rc5.  If you wish to use FT4
> after today or to take advantage of other recent program
> > corrections or enhancements, you should use WSJT-X 2.1.0-rc6.
>
> On Windows 10 Pro 64-bit 1903:
> I've installed -rc6 64-bit  in a new folder and attempts to launch it
> simply... don't
> launch anything that I can see. -rc5 64-bit works correctly.
>
> Any suggestions where to look first?
>
> Thanks,
> Dana  K6JQ
>
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] New, unpublished mode?

[rjai...@gmail.com]

I suspect this is one of the email systems like WinMor or ardop

Ria
N2RJ

On Sat, May 18, 2019 at 3:11 PM DG2YCB, Uwe  wrote:

> Hi,
>
> I just saw on 14.080 MHz an interesting signal. TX/RX cycle like FT4, but
> bandwidth like FT8. Signal could not be decoded. Is someone testing a new,
> unpublished mode?
>
>
>
>
>
> 73 de Uwe, DG2YCB
>
>
> ___
> 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] Expiration Date on Software

[rjai...@gmail.com]

The online check is good except some may then modify hosts file and similar
to defeat it. If it comes with a kill switch if it can’t phone home
successfully then that may work out. An auto update feature, I suppose

Older versions on the air did cause problems in the past. Some users hung
on to them either deliberately or unintentionally.

73
Ria
N2RJ


On Thu, May 9, 2019 at 10:52 PM Matthew Miller 
wrote:

> I would recommend against it -- how would you pick a reasonable date to
> ensure you don't need it to be updated sooner, and also not too soon that
> people have to reinstall just to update the date?
>
> A more reasonable approach would be to have it poll a file on the server
> that tells the software what the most recent version is that is released,
> and possibly have a flag or option telling it if the update will break
> backward-compatibility (like 2.0 did).  Then you could have a nag screen
> that tells you to download the latest version X and links to the changelog.
>
> I will point out I was unaware for many months that v2.0 had come out
> because I had no reason to check the website since what I have was working
> fine.
>
> Also, at least for Linux distributions, you could set up a software
> repository channel instead of just having the download packages, this way
> the updates would be pushed out seamlessly to everyone in real time, other
> apps such as CHIRP do this and it is very convenient.  I don't know if Mac
> has anything similar, I don't believe Windows does (unless you get set up
> in the Win10 store).
>
> Point is, for a beta the expiration makes sense like a trial expires.  For
> production software, there are much more conventional reasonable  ways to
> encourage users to update.
>
> -Matt / KK4NDE
>
> -Original Message-
> From: rjai...@gmail.com [mailto:rjai...@gmail.com]
> Sent: Tuesday, May 07, 2019 7:19 PM
> To: WSJT software development
> Cc: Gustafson Neil
> Subject: Re: [wsjt-devel] Expiration Date on Software
>
> That's a good idea. Some held on to old versions so they could retain
> features that were detrimental to the herd, such as lock rx=tx.
>
> Expiring the versions is a very good idea.
>
> Ria
> N2RJ
>
> On Tue, 7 May 2019 at 19:14, Gustafson Neil via wsjt-devel <
> wsjt-devel@lists.sourceforge.net> wrote:
> >
> > Hi All:
> >   Recent mention of an expiration date on RC 5 of WSJT-X...  Perhaps all
> releases of WSJT-X should expire in some reasonable timeframe.  Today I
> debugged a failing FT8 station that had not been used as such in some
> months.   After some effort in checking connections, config., etc., it was
> realized that release 1.8 was installed (e.g. obsolete payload format).
> One example of why older releases should be disabled at some point in time.
> >
> > Thanks and 73,
> > Neil W3ZQI
> > ___
> > 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] 2.1.0-rc5 OK logging button problematic for blind hams

[rjai...@gmail.com]

Thanks Bill,

He is using NVDA under Windows 10.

If you want, he has agreed to allow TeamViewer access if you need to see
the issues and possible solutions. But you can download the reader and
attempt to re-create the problem yourself.

https://www.nvaccess.org/

Many thanks
73
Ria
N2RJ


On Thu, May 2, 2019 at 6:16 AM Bill Somerville 
wrote:

> On 02/05/2019 01:52, rjai...@gmail.com wrote:
> > I was helping a blind ham set up WSJT-X 2.1.0-rc5 today and it was
> > apparent that this new arrangement to thwart robots simply isn't
> > working for blind hams who rely upon screen readers and other
> > accessibility technologies. There is no way for his screen reader
> > software to focus on OK.
> >
> > Any help with this would be appreciated.
> >
> > 73
> > Ria, N2RJ
>
> Hi Ria,
>
> sorry to here that, an unfortunate consequence of a few LIDs making
> things worse for the good guys. As the community appears to have no
> interest in stopping them from destroying the WSJT-X modes for everyone
> who is adopting them, we are in a tough place. We could easily
> distribute a version of WSJT-X with these defences disabled for those
> that ask for it. All this noise in the defence of sight-challenged
> operators seems selfish to me, yours is the first that actually mentions
> someone having difficulty. We use tools that automatically build in
> accessibility on all platforms, we work with other software developers
> who are developing special tools for sight-challenged ops (e.g. Sam,
> W2JDB, with his application Qlog). Yet when we have to make a change to
> one pair of buttons within the hundreds of controls in WSJT-X, for
> reasons we don't like either but we think they are justified, we are
> branded as anti-accessibility.
>
> Come on folks, try and see the big  picture.
>
> Ria, which operating system is your colleague using? Also what screen
> reader is their preference, if it is free of charge or otherwise easy to
> obtain I would like to review how WSJT-X plays out when accessing the
> programmatic accessible interfaces. I ask because we could do a lot more
> with the accessible names and descriptions of the various windows and
> controls in WSJT-X. They are largely at default values presently which
> can't be very helpful.
>
> 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] Log QSO Window -> OK and Cancel buttons oddbehavior -CRACKED

[rjai...@gmail.com]

Apart from ADA stuff it simply isn't working for blind hams. Besides, the
autobots have gotten advanced now to the point where they are simply
modifying source code and bypassing all manual input.

Not sure what can be done other than maybe invalidate awards from automated
robot cheating.

Ria
N2RJ

On Wed, 1 May 2019 at 14:22, Mark James  wrote:

> Note: I think this post is appropriate on this list because it involves an
> important software development issue.
>
> I'm not going to comment on the details of the interface, but I think it
> is worth pointing out that a software interface that requires using a mouse
> to click a button is in violation of the US Americans with Disabilities
> Act. Under the ADA you must provide a keyboard option.
>
> While a free, open-source program might not face any specific penalty
> here, but not being ADA-compliant at least in theory could result in the
> software not being allowed to be used in schools, colleges, or any public
> institution.
>
> Besides, being ADA complaint is just the right thing to do.
>
> Frankly I think any attempt to make it harder to use macros will result in
> flunking the accessibility goal.
>
>
> 
>  Virus-free.
> www.avg.com
> 
> <#m_-883129225528624055_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
> On Wed, May 1, 2019 at 12:22 AM Aaron Jones  wrote:
>
>> Dev Team,
>>
>> I'm sure everyone's burned out on the OK/Cancel BUTTon discussion but
>> since it was such a hot "button" topic (LOL) I thought I'd give cracking it
>> a try.  I'm very impressed that the window and button are as elusive to
>> automation as they are, nice programming.  Here's what I found:
>>
>>- You cannot use "Alt-O" to focus on the OK button
>>- You cannot Tab through the fields to the OK button, it only sets
>>focus on the cancel and then back around to the beginning field
>>- Using a macro tool I could not focus the Log QSO window, it somehow
>>was at the top of all windows and I couldn't "read" it using two different
>>macro tools (not to be named)
>>
>> Things I could do:
>>
>>- Using a freely available macro tool I noticed I COULD query for
>>open windows title bars and verify "log qso" existed
>>- I could screenshot the OK button using a screenshot tool
>>- Using a  freely available macro toolI was able to search the screen
>>for "image" of the button and specify a location to focus on, in this case
>>the upper left hand where the window always pops up for me, OR if I wanted
>>I probably could have moved it using the information from finding it was
>>available
>>- Once found the macro software focused the mouse on the coordinates
>>of the "image" of the "OK button" and VOILA! I was able to "click OK"
>>
>> To test it I put the six line macro script loop (two of those lines were
>> the loop itself) and ran it while I QSO'd with three different stations in
>> the matter of a couple of minutes, each time the script was able to find
>> and click the OK button wherever it landed on the LOG QSO screen.
>>
>>  I spent about an hour fanagling with it and found two different ways to
>> do it (the other way was to watch my WSJT-X computer via remote desktop or
>> similar VNC and do the same "image find" dance and click remotely - this
>> would probably be better because the scripting computer would have no need
>> to worry or knowledge of the Z-index of the Log QSO window, it would see
>> the entire screen as an image and just find the OK button regardless of
>> other windows handle considerations.
>>
>> *So  - my point is not to be a pain and hack this or explain how to do it
>> but rather to postulate*, other than annoying normal users what does
>> this really accomplish other than screw up the unwary button clicker when
>> the OK / Cancel switch and they are too focused on the next QSO to notice
>> they just nuked their first DX entry to Antarctica and missed out on
>> finalizing their DXCC award?  Or screwing up the visually impaired or late
>> night impaired operator?
>>
>> If I had a vote I'd not punish the law abiding citizen and the 99% for
>> the 1% abusers of automation.
>>
>> PS. IF you need a video of my macro I'll be glad to post it but won't to
>> the group as that would make it far easier than it already is to circumvent
>> this precaution.
>>
>> AG7GK
>>
>> Aaron
>>
>> 73
>>
>>
>> ___
>> 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] 2.1.0-rc5 OK logging button problematic for blind hams

[rjai...@gmail.com]

I was helping a blind ham set up WSJT-X 2.1.0-rc5 today and it was
apparent that this new arrangement to thwart robots simply isn't
working for blind hams who rely upon screen readers and other
accessibility technologies. There is no way for his screen reader
software to focus on OK.

Any help with this would be appreciated.

73
Ria, N2RJ


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

Re: [wsjt-devel] FT4 2.1.0-rc5 - Failed QSO

[rjai...@gmail.com]

I also experience same.

Ria
N2RJ

On Tue, 30 Apr 2019 at 19:33, John T Haworth  wrote:
>
> Hello,
>
> I have had a large number of failed QSO’s. The station responds with Tx2 
> within a couple of calls, but then it appears they are not decoding my Tx3 
> response and eventually abandon the QSO. The stations are normally very 
> strong and give an equally strong report.
>
> What could be some areas to investigate?
>
> Configuration:
>
> -Ubuntu 18.04 LTS
> -Elecraft K3 with USB/Sound Card upgrade
>
> Thanks and 73 John NU8M___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel



-- 
Ria Jairam, N2RJ
Director, Hudson Division
ARRL - The national association for Amateur Radio™
+1.973.594.6275
https://hudson.arrl.org
n...@arrl.org


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

Re: [wsjt-devel] FT4 frequency choice - problematic

[rjai...@gmail.com]

Thanks Joe.

I heard you brought down the house at FLARC! They appreciated the
visit very much. I am a member of that club.

Thank you for your comments on the frequencies. I am going to reach
out again to the groups that had contacted me and I'll provide some
suggestions.

I am enjoying the mode quite a lot. It is an adjustment from FT8 but
it seems like it will be a winner.





On Tue, 30 Apr 2019 at 15:06, Joe Taylor  wrote:
>
> Hi Ria,
>
> Good to hear from you!
>
> On 4/30/2019 14:10, rjai...@gmail.com wrote:
> > Hi Joe, Bill, Steve and team,
> >
> > I'm getting feedback about the frequency choices for the initial FT4
> > rollout. There is conflict with users because it is so low down in the
> > band on 40 meters (7047). The QRP fox hunt (CW) guys are up in arms
> > because that's where they operate. Other hams have been complaining to
> > their ARRL officials (including me) about the QRM.
> >
> > I love the FT/JT modes and think that what the WSJT development team
> > is doing is absolutely fantastic but I think some more thought has to
> > go into where we want these modes to live so we can have peaceful
> > coexistence on the bands.
> >
> > vy 73
> > Ria
> Experience shows that it's impossible to select even 1% of a band --
> say, a ~3 kHz slice in a 300 kHz band -- for a new purpose without
> stepping on some toes.  Experience also shows that nobody wants to help
> with this important band-planning task.  (Maybe something like a new
> ARRL and/or IARU Committee?)
>
> Finally, our experience shows that sometimes we have to try something,
> see how it plays, and then (if necessary) try something else.
>
> Our frequency choices are not arbitrary -- far from it.  We're very
> willing to make changes when a balanced assessment shows them desirable.
>
> FT4 has been on 7047 kHz for all of 24 hours.  Not much time, but enough
> to make it clear that a better frequency should be found on 40 meters.
>
> I hope those who experience QRM from FT8 or FT4 will keep in mind that
> (by some measures) these modes account for something like 70% of ham
> radio activity, world wide, while occupying something like 1-2% of our
> allocated HF spectrum.
>
> Please send us your suggestions for default frequencies for FT4 and/or
> other WSJT-X modes, doing your best to find choices acceptable worldwide.
>
> -- 73, Joe, K1JT



--
Ria Jairam, N2RJ
Director, Hudson Division
ARRL - The national association for Amateur Radio™
+1.973.594.6275
https://hudson.arrl.org
n...@arrl.org


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

Re: [wsjt-devel] FT4 frequency choice - problematic

[rjai...@gmail.com]

Hi Bill,

Yes, the W1AW code practice bulletins is an issue. I'm going to
consult with our station manager, Joe, NJ1Q as to what his thoughts
are, as well as others.

73
Ria, N2RJ

On Tue, 30 Apr 2019 at 16:53, Bill Somerville  wrote:
>
> On 30/04/2019 19:10, rjai...@gmail.com wrote:
> > Hi Joe, Bill, Steve and team,
> >
> > I'm getting feedback about the frequency choices for the initial FT4
> > rollout. There is conflict with users because it is so low down in the
> > band on 40 meters (7047). The QRP fox hunt (CW) guys are up in arms
> > because that's where they operate. Other hams have been complaining to
> > their ARRL officials (including me) about the QRM.
> >
> > I love the FT/JT modes and think that what the WSJT development team
> > is doing is absolutely fantastic but I think some more thought has to
> > go into where we want these modes to live so we can have peaceful
> > coexistence on the bands.
> >
> > vy 73
> > Ria
> > -- Ria Jairam, N2RJ Director, Hudson Division ARRL - The national
> > association for Amateur Radio™ +1.973.594.6275 https://hudson.arrl.org
> > n...@arrl.org
>
> Hi Ria,
>
> we had several requests, including some from members of band planning
> committees, that we should choose a spot below 7050 on 40m, this based
> on that being the upper edge of any globally coordinated narrow band
> digital section. It was also pointed out that region three has an EMCOMM
> frequency at 7050 so with hindsight 7047 is not that good. Region 1 has
> digital modes up to 2700 Hz bandwidth including automatic stations
> between 7050 and 7053 and more automatic unattended <= 2700 Hz bandwidth
> allocation between 7053 and 7060 where the digital modes section ends.
> Region 2 is similar except 7060 is another EMCOMM QRG.
>
> Given that 7047 does not look so low as far as I can see. I missed that
> there was a W1AW code practice broadcast on 7074.5, which was
> unfortunate, but it looks to me that further down towards 7040 is the
> only way to go unless there are better options up in the all modes
> sections above 7060?
>
> Thanks in advance for any helpful input you can provide, we do have the
> advantage that in general everyone using a WSJT-X mode on HF tend to
> stick very close together and move as a pack. So changes are possible
> and we really want to find the least contentious spot.
>
> 73
> Bill
> G4WJS.
>
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel



-- 
Ria Jairam, N2RJ
Director, Hudson Division
ARRL - The national association for Amateur Radio™
+1.973.594.6275
https://hudson.arrl.org
n...@arrl.org


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

[wsjt-devel] FT4 frequency choice - problematic

[rjai...@gmail.com]

Hi Joe, Bill, Steve and team,

I'm getting feedback about the frequency choices for the initial FT4
rollout. There is conflict with users because it is so low down in the
band on 40 meters (7047). The QRP fox hunt (CW) guys are up in arms
because that's where they operate. Other hams have been complaining to
their ARRL officials (including me) about the QRM.

I love the FT/JT modes and think that what the WSJT development team
is doing is absolutely fantastic but I think some more thought has to
go into where we want these modes to live so we can have peaceful
coexistence on the bands.

vy 73
Ria
-- 
Ria Jairam, N2RJ
Director, Hudson Division
ARRL - The national association for Amateur Radio™
+1.973.594.6275
https://hudson.arrl.org
n...@arrl.org


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

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

[rjai...@gmail.com]

Hi Joe and team,

So far so good. Testing remote with my Flex-6700 and using remote DAX,
under Parallels in Windows. You definitely notice the sensitivity
drop. But I made some QSOs on 80m. So far so good. I see PSKReporter
is taking and parsing the reports as well without issue.

73
Ria, N2RJ

On Mon, 29 Apr 2019 at 14:09, Joe Taylor  wrote:
>
> To:   Users of WSJT-X -- especially those interested in radio contesting
> From: WSJT Development Group
>
> By now most of you know about the FT4 protocol under development for
> eventual release in WSJT-X 2.1.0.  The new mode is particularly
> optimized for use in radio contesting.
>
> FT4 is mostly like FT8, but is 2.5 x faster, uses 1.8 x the bandwidth,
> and is 4.6 dB less sensitive.  Many other details are summarized in "The
> FT4 Protocol for Digital Contesting", available here:
> http://physics.princeton.edu/pulsar/k1jt/FT4_Protocol.pdf
> Links to translations in other languages are available on the WSJT-X web
> page:
> http://physics.princeton.edu/pulsar/k1jt/wsjtx.html
>
> Release candidate WSJT-X 2.1.0-rc5 is intended for beta-testing through
> June 7, 2019.  Please note that the FT4 mode should NOT be used in the
> ARRL June VHF QSO Party (June 8-10) or ARRL Field Day (June 22-23).
>
> We have done our best to provide suggested operating frequencies for the
> test period consistent as far as possible with world-wide band plans and
> existing usage.  Please note that thanks to good user feedback, some of
> these frequencies are different from those suggested in the document
> linked above.
>
> Default frequencies currently recommended for FT4 are as follows:
>
> Band   MHzNotes
> -
> 803.575   (3.568 MHz in Region 3)
> 407.047
> 30   10.140
> 20   14.080
> 17   18.104
> 15   21.140
> 12   24.919
> 10   28.180
>   6   50.318
>   2  144.170
>
> FT4 is designed for contesting, but it will likely find some use for
> normal QSOs as well, especially during the beta test period.  In the
> coming month we hope to receive useful feedback on the user interface,
> message sequencing, interaction with logging programs, etc.  Probably
> it's best to use "normal" (non-contest) messages except during the
> mock-contest practice sessions scheduled for  - 0100 UTC on May 9
> and May 14, and (if needed) June 5.
>
> Downloadable installation packages for WSJT-X 2.1.0-rc5 under Windows,
> Linux, and macOS are available on the WSJT-X web page:
>
> http://physics.princeton.edu/pulsar/k1jt/wsjtx.html
>
> Windows users will discover that WSJT-X v2.1.0 has been made available
> as a 64-bit MS Windows build for 64-bit versions of Windows since Vista.
> This veraion has one known defect. The audio input device level will be
> reset to 100% when WSJT-X is started, when the input audio device is
> changed, and when switching to a new configuration. This is a Qt
> framework defect that we have reported and is being fixed in a future
> release; until then users should take care to set the device audio level
> back to 0dB or lower depending on requirements. Note that many sound
> cards and chips have real gain ahead of the ADC, as much as 14dB, which
> will be turned to the maximum due to this defect and is usually
> undesirable when using WSJT-X.
>
> Despite this annoying defect, we recommend the 64-bit version of WSJT-X
> on MS Windows as it has significant advantages in decoding speed.
>
> -- 73 from Joe, K1JT; Steve, K9AN; and Bill, G4WJS
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel



-- 
Ria Jairam, N2RJ
Director, Hudson Division
ARRL - The national association for Amateur Radio™
+1.973.594.6275
https://hudson.arrl.org
n...@arrl.org


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

Re: [wsjt-devel] The FT4 Protocol for Digital Contesting

[rjai...@gmail.com]

I'm not sure a WARC ban (not band, but ban) is necessary. This is
touted as a contest mode but people will use it for regular DX
contacts if it saves them time versus FT8. I can even see some
DXpeditions using it to replace or supplement RTTY contacts. Does it
have or support Fox and Hound mode? If it does, that reason alone is
good to keep it on WARC.  Ultimately contest sponsors will give zero
points for WARC QSOs anyway so it's essentially a non-issue.

73
Ria, N2RJ

On Fri, 26 Apr 2019 at 19:22, Brian Dickman  wrote:
>
> Grant, I'd respectfully discourage any lower than about .065 for 20/15/10m. 
> .060 is the standard CW QRP activity frequency for each of those bands, and 
> .061 to .064 are the standard calling frequencies for CW SOTA activations in 
> most if not all IARU regions. The majority of the activity centers on 062. 
> Many dedicated chasers monitor 062 throughout the day for mountaintop 
> portable QRP signals.
>
> 73,
> Brian AF7MD
>
> On Fri, Apr 26, 2019 at 4:19 AM Grant VK5GR  wrote:
>>
>> Joe et al,
>>
>> A word if I may about frequency choices. Some of those proposed for FT4
>> probably leave a bit to be desired. Here are some thoughts to consider:
>>
>> 80m 3.595 - PROPOSE 3562kHz - 3595 is completely out of band for JA
>> completely and into the phone part of the band outside of Region 2. My
>> suggestion based on occupancy and proximity to existing digital sub-bands is
>> something around 3562kHz (at least keeping away from 3560 which is sometimes
>> a CW QRP frequency). While the IARU band plans currently have digital as
>> 3570-3590kHz a case can be made for expanding that - and given other
>> restrictions in some countries on 80m, expanding digital down at least 8kHz
>> to 3562kHz makes some sense. A case to be made for the IARU - but you can
>> "help" their decision by starting to use it anyway. BTW 3600kHz is the
>> centre frequency for IARU R3 80m disaster comms - LSB - so FT4 on 3595 USB
>> will badly clash with that - another reason not to use 3595.
>>
>> 40m 7.090 - PROPOSE 7052kHz (inside the digital sub-band) or 7062kHz (just
>> above the digital sub-band noting it is heavily used for SSB at least in
>> region 3) - 7090 only makes sense in the USA! Many other countries have this
>> as SSB voice use. The IARU digital segment is (depending on region)
>> 7040-7060 or 7040-7060. With 7056 already being used for FT8 F/H mode on a
>> fairly regular basis it would make sense to use say 7050 or 7052kHz instead.
>> Note that 7090 is the designated SSB QRP frequency. I would promote 7050 for
>> FT4. The only reason not to is that the RTTY guys if FT4 and RTTY are in the
>> same contest might object - but during the contests the RTTY guys spread out
>> and use anything from 7030 to 7120 anyway in complete disregard of the band
>> plans. If they are going to be that unruly then putting FT4 down there
>> doesn't seem all that bad.
>>
>> * 30m / 17m / 12m - should NOT have FT4 allocations at all. FT4 is a
>> CONTESTING mode and CONTESTING is by global agreement excluded from those
>> WRC79 bands!!! *
>>
>> 20m 14.140 - PROPOSE 14062kHz - the original proposed use of 14140KHz again
>> is well outside the digital segments where FT4 belongs. If anything,
>> creeping down into 14060-14070 might be considered acceptable despite not
>> being in the band plan if the aim was to separate RTTY and FT4 users in the
>> same contest. Going high above 14.112 (the acknowledged edge of the global
>> 20m digital band plan segment) will be frowned upon. Take a leaf from 80m
>> and use 14062kHz - again at least that keeps it away from the CW QRP Centre
>> of activity and meets the objective of separating it from RTTY.
>>
>> 15m 21.140 - PROPOSE 21062kHz - follow 20m and choose 21062kHz - although
>> 21140kHz is the first proposed FT4 frequency that fell inside a digital
>> subband...
>>
>> 10m 28.180 - POROPOSE 28062kHz - again follow 20m
>>
>> 6m 50.318 - PROPOSE somewhere below 50.313 not above. Moving above is just
>> moving further into several countries beacon segments. Not likely to get a
>> lot of airplay as a international contesting band for FT8 so not as critical
>> - but my suggestion would be look below 50.313 not above.
>>
>> For discussion folks.
>>
>> Regards,
>> Grant VK5GR
>> WIA Appointee to the IARU Region 3 Band Plan committee
>>
>>
>>
>>
>> -Original Message-
>> From: Joe Taylor [mailto:j...@princeton.edu]
>> Sent: Tuesday, 23 April 2019 1:04 AM
>> To: WSJT software development
>> Subject: [wsjt-devel] The FT4 Protocol for Digital Contesting
>>
>> To:   WSJT-X users interested in testing FT4
>> From: K1JT, K9AN, and G4WJS
>>
>> Soon after the "FT8 Roundup" held on December 1-2, 2018, we started
>> serious work on a faster, more contest-friendly digital mode that can
>> compete with RTTY-contesting QSO rates while preserving many of the
>> benefits of FT8.  The result is FT4 -- a new digital mode specifically
>> designed for radio contesting.
>>
>> Over 

Re: [wsjt-devel] Someone released an Auto CQ mod - my 2 cents

[rjai...@gmail.com]

Sorry guys - pandora's box has already been opened. I do not support
automatic, unattended robot QSOs (which are illegal in USA and some
other countries) but to ignore it as not happening is denying reality.
Stathis has demonstrated this some months ago and I am certain that
many are using his technique (macros) without modifying WSJT-X source.

What we can hope is that people exercise their good judgment and not
abuse it. Or just realize that some people will always "cheat" and
live by your own moral compass.

Ria
N2RJ

On Sun, 31 Mar 2019 at 17:58, Jim Brown  wrote:
>
> On 3/31/2019 9:53 AM, Bill Somerville wrote:
> > most Amateur Radio operators would not consider a QSO with a machine to
> > be worthwhile and to find out that they had done so unknowingly would be
> > very annoying.
>
> That depends on what you might be trying to accomplish. I certainly
> would automate my FT8 operation in this manner, but about a year ago I
> made a QSO with a robot KX3 floating from KH6 to the west coast of NA on
> a scientific raft studying oceanography of some sort. That QSO went into
> my log, because my operation was not robotic! And it filled in a very
> rare CQ Field for that award.
>
> Likewise, if I'm trying to add EU countries on 160M, I really don't care
> what is creating and controlling the signal on the other end of the QSO.
> My accomplishment is building RX and TX antennas that will get my signal
> from near San Francisco 6,000 miles over the auroral oval to EU, and dig
> that station's signal out of the noise. When I count that for DXCC, I
> did my part of the work.
>
> OTOH, I do view auto-CQ in any form, attended or not, as cluttering up
> the spectrum. I almost never call CQ using FT8 on any band but 6M, and
> even there do so sparingly. And I'm talking about the auto-repeat CQ
> built into WSJT-X.
>
> 73, Jim K9YC
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel



-- 
Ria Jairam, N2RJ
Director, Hudson Division
ARRL - The national association for Amateur Radio™
+1.973.594.6275
https://hudson.arrl.org
n...@arrl.org


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

Re: [wsjt-devel] Use of sourceforge.net

[rjai...@gmail.com]

See below from Joe:

Joe Taylor j...@princeton.edu via lists.sourceforge.net

Tue 10 Jul, 10:39
to wsjt-devel
One of the changes associated with moving source code for WSJT and
related programs from SVN to Git is a change in policy regarding
development code and the frequency of "commits" to the public repository.

Code development now takes place in limited-access git repositories.
New code is made publicly available when we consider it stable; we then
do a "push" to the relevant Git repository on SourceForge. These events
will be less frequent than our commits to SVN have been in the past.

There are several reasons why this policy change is necessary and
desirable.  One is to prevent wasted time caused by people carelessly
using development code on the air before new developments are finished
and tested.  Some users have even distributed untested, unauthorized
program builds that contain significant errors -- which only compounds
the problem.

A more serious issue has been the appearance of our ideas, algorithms,
protocols, GUI features, and source code in "copycat software" even
before we have frozen the design and released the new ideas in our own
software.  We are very much in favor of cooperative development of
open-source code, with a bi-directional exchange of ideas.  We believe
this model fits very well into the cooperative nature of the Amateur
Radio hobby.  We are not favorably disposed to a one-way flow of ideas:
in particular, to separate efforts that "take" liberally, but do not
"gave back" at all.

WSJT-X and its sister programs remain open-source software.  Our
released General Availability (GA) program versions are licensed under
version 3 of the GNU General Public License (GPLv3).  Full source code
for these versions is always publicly available.

Development code, or "work in progress", is shared among those working
on it and contributing to it.  In general such code is not made publicly
available until design parameters are frozen and thorough testing has
been done, and new code is merged into the Git "master" branch.

-- 73, Joe, K1JT
On Mon, 24 Sep 2018 at 12:10, Jay Hainline  wrote:
>
> Has Sourceforge been abandoned for posting new revisions that can be build? I 
> have not seen any updates posted since July 2. Just wondering.
>
>
>
> 73,
>
> Jay Hainline KA9CFD
>
> Colchester, IL  EN40om
>
>
>
> ___
> 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] Contest mode CQVHF

[rjai...@gmail.com]

The problem with using it with DX friendly propagation is the antipode
being used for R  . Yes people should know better but many don’t.

In fact there is guidance that it should be turned off when propagation
favors DX.

Ria
N2RJ

On Mon, Jul 23, 2018 at 8:33 PM W0MU Mike Fatchett  wrote:

> This had nothing to do with DX.  The exchange was the grid DX or not.
>
> The issue is that you cannot work people if they are in contest mode and
> you are not.
>
> W0MU
>
>
> On 7/23/2018 6:22 PM, rjai...@gmail.com wrote:
> > NA VHF Contest mode should not be used in a DX contest, or at least
> > one with significant potential for DX.
> >
> > It was frustrating for me too, mostly because of the inconsistency.
> >
> > 73
> > Ria, N2RJ
> > On Mon, Jul 23, 2018 at 8:15 PM David Fisher 
> wrote:
> >> Sometimes stations would call “CQ WW  ”.  In that case, it was
> easy to select contest mode and return the call.  But in many other cases,
> the other station would give no hint he was in contest mode until his
> mangled grid square was received.  In those cases I got the pop up that
> prompted me to turn on contest mode.  I did so, but all of that takes time,
> coordination and practice to make work smoothly.
> >>
> >>
> >>
> >> I one case that I ran as an experiment, I called CQ in contest mode,
> got a reply, then got a message through JTAlertX asking what I was doing
> and why my grid square didn’t make sense.  Etc. etc. etc.
> >>
> >>
> >>
> >> Bottom line – I wasn’t in the contest, but I made a mess of a number of
> other station’s contest mode QSOs, which defeated the intent of contest
> mode.
> >>
> >>
> >>
> >> Dave / NX6D
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> 
> >> From: W0MU Mike Fatchett 
> >> Sent: Monday, July 23, 2018 4:37:07 PM
> >> To: wsjt-devel@lists.sourceforge.net
> >> Subject: [wsjt-devel] Contest mode CQVHF
> >>
> >> First of all I want to thank everyone for this great advancement in the
> >> hobby!
> >>
> >>
> >> The CQ WW VHF was my first exposure to contest mode and it was a very
> >> frustrating 27 hours.
> >>
> >> If I am in contest mode and I call CQ and get an answer from someone who
> >> is not, there is essentially no way to complete a qso unless one side
> >> changes into or out of contest mode.  What happened to me is I would
> >> switch and then the other side would switch and we would be opposite.
> >> Frustrating!
> >>
> >> The main issue is that we cannot expect those not in the contest to have
> >> to switch into a specific mode to work us.  This does not happen in any
> >> other contest.  We cannot expect this from casual ops.  I am glad they
> >> want to work me.  Being able to work them should be painless too!
> >>
> >> Why is contest mode needed?  If a qso is good in contest mode with less
> >> sequences I suggest that all FT8 exchanges be the same. Is there a
> >> specific reason two have multiple sets of exchanges for in a contest and
> >> not in a contest?  I don't think so.
> >>
> >> I understand that this was an issue for the June VHF contest too.
> >>
> >> If you guys can move my xmit around in fox/hound mode, which worked out
> >> really well, there has to be a solution for this.  I believe that the
> >> fox was still able to work people not running hound?  We need the same
> >> ability in contest mode.
> >>
> >> I believe that this is already being examined but I thought I would give
> >> my feedback.  I would be happy to provide more information if desired.
> >>
> >> Thanks again for all the hard work in bringing us FT8!
> >>
> >> W0MU
> >>
> >>
> >>
> --
> >> Check out the vibrant tech community on one of the world's most
> >> engaging tech sites, Slashdot.org!
> https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fsdm.link%2Fslashdotdata=02%7C01%7C%7Cbe807b8121b94f841e5808d5f0f86e14%7C84df9e7fe9f640afb435%7C1%7C0%7C636679872141956608sdata=4ngp%2FoSOWuPUakyW3qTn6b49JD01iE6jHJc%2BQlc6qbM%3Dreserved=0
> >> ___
> >> wsjt-devel mailing list
> >> wsjt-devel@lists.sourceforge.net
> >>
> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fl

Re: [wsjt-devel] Contest mode CQVHF

[rjai...@gmail.com]

NA VHF Contest mode should not be used in a DX contest, or at least
one with significant potential for DX.

It was frustrating for me too, mostly because of the inconsistency.

73
Ria, N2RJ
On Mon, Jul 23, 2018 at 8:15 PM David Fisher  wrote:
>
> Sometimes stations would call “CQ WW  ”.  In that case, it was easy 
> to select contest mode and return the call.  But in many other cases, the 
> other station would give no hint he was in contest mode until his mangled 
> grid square was received.  In those cases I got the pop up that prompted me 
> to turn on contest mode.  I did so, but all of that takes time, coordination 
> and practice to make work smoothly.
>
>
>
> I one case that I ran as an experiment, I called CQ in contest mode, got a 
> reply, then got a message through JTAlertX asking what I was doing and why my 
> grid square didn’t make sense.  Etc. etc. etc.
>
>
>
> Bottom line – I wasn’t in the contest, but I made a mess of a number of other 
> station’s contest mode QSOs, which defeated the intent of contest mode.
>
>
>
> Dave / NX6D
>
>
>
>
>
>
>
> 
> From: W0MU Mike Fatchett 
> Sent: Monday, July 23, 2018 4:37:07 PM
> To: wsjt-devel@lists.sourceforge.net
> Subject: [wsjt-devel] Contest mode CQVHF
>
> First of all I want to thank everyone for this great advancement in the
> hobby!
>
>
> The CQ WW VHF was my first exposure to contest mode and it was a very
> frustrating 27 hours.
>
> If I am in contest mode and I call CQ and get an answer from someone who
> is not, there is essentially no way to complete a qso unless one side
> changes into or out of contest mode.  What happened to me is I would
> switch and then the other side would switch and we would be opposite.
> Frustrating!
>
> The main issue is that we cannot expect those not in the contest to have
> to switch into a specific mode to work us.  This does not happen in any
> other contest.  We cannot expect this from casual ops.  I am glad they
> want to work me.  Being able to work them should be painless too!
>
> Why is contest mode needed?  If a qso is good in contest mode with less
> sequences I suggest that all FT8 exchanges be the same. Is there a
> specific reason two have multiple sets of exchanges for in a contest and
> not in a contest?  I don't think so.
>
> I understand that this was an issue for the June VHF contest too.
>
> If you guys can move my xmit around in fox/hound mode, which worked out
> really well, there has to be a solution for this.  I believe that the
> fox was still able to work people not running hound?  We need the same
> ability in contest mode.
>
> I believe that this is already being examined but I thought I would give
> my feedback.  I would be happy to provide more information if desired.
>
> Thanks again for all the hard work in bringing us FT8!
>
> W0MU
>
>
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! 
> https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fsdm.link%2Fslashdotdata=02%7C01%7C%7Cbe807b8121b94f841e5808d5f0f86e14%7C84df9e7fe9f640afb435%7C1%7C0%7C636679872141956608sdata=4ngp%2FoSOWuPUakyW3qTn6b49JD01iE6jHJc%2BQlc6qbM%3Dreserved=0
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fwsjt-develdata=02%7C01%7C%7Cbe807b8121b94f841e5808d5f0f86e14%7C84df9e7fe9f640afb435%7C1%7C0%7C636679872141956608sdata=AiDSOG94NAAree6BMP1FFzeJk%2B6exoF2EylLUp9fu08%3Dreserved=0
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! 
> http://sdm.link/slashdot___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel

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

[wsjt-devel] Use of FT8 in a VHF rover - observations

[rjai...@gmail.com]

This weekend I was part of rover team K2EZ/R. Andrea basically let me run 6
meters and she handled 2 meters and up.

I found that in general, if I used the callsign K2EZ/R it worked fairly
well except when more than one caller responds. In that case I had to
manually sequence and put the other station’s call in, and generate a reply
message for them.

Rover rules require us to use /R or /ROVER.

2 meters didn’t have a frequency defined in the software but 144.174 seemed
to be popular.

So it worked out fairly well.

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

[wsjt-devel] Fail-safe for failed QSY

[rjai...@gmail.com]

I'd like to propose a fail safe mechanism for when a radio fails to
QSY, like what happened to me today during the public test.

Problem: DXPedition mode using fake it. User locks her VFO. Radio
doesn't QSY. DXpedition mode still transmits on the wrong frequency
anyway.

Proposed solution: WSJT-X should check to see if the radio did indeed
change frequency, and halt transmission if it did not. This way there
is no unnecessary QRM to the fox by an errant caller whose radio did
not QSY. Optionally, display an error saying your radio did not QSY.

This of course is moot if you don't use split or fake it.

I think it would be helpful in quickly identifying an issue. I didn't
even realize this had happened until Steve K9AN pointed out the
behavior.

73
Ria, N2RJ

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

[wsjt-devel] Using DXpedition mode without split on a SDR

[rjai...@gmail.com]

Is it possible to not have to use split mode with a SDR like an Anan
or a Flex-6000 series? The audio chain on my Flex-6700 is all digital,
and I can set my receive bandwidth as high as 12kHz and the transmit
as high as 10kHz on SSB digital (DIGU/DIGL). I wouldn't need to use
"Fake it" or split.

73
Ria, N2RJ

--
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] r8603 power at qso start

[rjai...@gmail.com]

I thought it was just me, but yes I also see this.

Ria
N2RJ

On Thu, Apr 5, 2018 at 1:01 PM, Black Michael via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> Running R8603 and seeing a power level that seems too high at start of
> transmission (both Tune and standard messages on FT8).
> This is about 50% more power than the rest of the signal being transmitted.
> Is this intentional?
>
> [image: Inline image]
>
>
> de Mike W9MDB
>
>
> 
> --
> 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] New FT8 Frequencies?

[rjai...@gmail.com]

How do you know we're running power? I run gain antennas including a 3
element beam at height on 30 meters. I get complaints from some that I
am running excessive power. (I run 50 watts except on 80/160 and 6m
where I will run up to 1500W)

Should I just run a G5RV so as not to bend the needle now?

Ria
N2RJ

On Fri, Mar 23, 2018 at 2:33 PM, Gary McDuffie  wrote:
>
>
>> On Mar 23, 2018, at 2:48 AM, David Alloza  wrote:
>>
>> The concentration of traffic on the narrow 2.5khz (certainly at excessive 
>> power)  causes a significant rise in the noise floor and therefore reduces 
>> the performance of this mode.
>> I think this is something that needs to be considered for the future of 
>> these digital mode.
>
> This brings up a topic I would like to see discussed.  Similar to the 
> DXpedition mode, I would like to see a setting available to either ignore or 
> not even display signals over a certain SNR.  For instance, allow me to say I 
> don’t care about this guy that is bending the needle.  Show me only the ones 
> that are -15 or weaker.  If not a problem, allow ME to set that level for 
> flexibility and band condx.
>
> Gary - AG0N
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel

--
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] Monitoring stops suddenly in 1.80 and 1.90 RC2

[rjai...@gmail.com]

One of my friends has reported something similar - decodes stop for no
reason and start back at random. He doesn't use a Raspberry Pi. He
uses a recent 27" iMac and runs Windows in a Parallels instance. The
rig is a Flex-6300 and uses the COM port for CAT control (via SmartSDR
CAT).

CPU usage seems fine, memory usage seems fine. We have been unable to
pin it down. Audio from the Flex DAX sound card device seems fine too.
Clock is sync'ed.

He's using 1.9.0-rc2 (I'll ask him to upgrade to RC3).

Just a data point.

73
Ria, N2RJ

On Fri, Mar 23, 2018 at 12:14 PM, FRANK DB5FP  wrote:
>
>
>> On 22/03/2018 18:42, FRANK DB5FP wrote:
>> > Hello,
>> >
>> > I'm back with some more Information :
>> >
>> > - the soundcard is not a cheapie:-)  It's a Terratec Aureon
>> > I've used it several years for decoding NOAA sats, without
>> > any notice, even under linux and on RPI2 together with wxtoimg.
>> > - the problem looks like an RPI USB problem.
>> >
>> >I have been searching the internet and found "dwc_otg"
>> >problems.there are many forum entries and debug hints like
>> > kernel command line options etc., but at least nothing will help
>> > solving that usb-driver (that is my conclusion).
>> > - Main problem is of cours that linux-usb handling will loose some
>> >audiodata -> this causes the /usr/bin/JT9 process to stop working
>> >correctly (lower cpu usage than normal), no decode no waterfall
>> >This stops processing audiodata even after a short wile
>> >audiodatat is back again
>> >
>> > --> wsjt-x gui should supervise JT9 process to observe any
>> > irregularities , like it does when JT9 process is shut down
>> > manually.
>> >
>> > 73
>> >
>> > Frank
>> > DB5FP
>>
>> Hi Frank,
>>
>> a couple of clarifications.
>>
>> The jt9 process does not directly handle audio samples, they are read
>> and written by a thread of the wsjtx process.
>>
>> The jt9 process is monitored by the wsjtx process and failures are
>> reported via a message box including the reason for failure.
>>
>> If the source of sound samples stops delivering samples; the wsjtx
>> waterfall and decoding will also stop.
>>
>> 73
>> Bill
>> G4WJS.
>>
> Hi Bill,
>
> interesting Information, because :
>
> Soundcard has an indicator LED, LED ON means, power ok.
> Flashing means data is being read from the soundcard.
>
> And the LED is flashing(all the time)even when waterfall and decode
> stopped.
> -> wsjtx reads data from soundcard??? but does not pass data to jt9 ???
>
> No Error Messages are generated in wsjtx.
>
> Behavior is the same like I'm pulling USB cord while wsjtx is running->
> no message is generated and decode and waterfall is stopped.
>
>
> 73
> Frank
> DB5FP
>
>
>
>
> --
> 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] New FT8 Frequencies?

[rjai...@gmail.com]

I would concede that in Europe it is a problem. My antennas are beamed
to Europe most of the time but there aren't many strong band openings
these days.

I have also heard grumbling among the PSK31 and Olivia crowd that FT8
is interfering with them. They can move but when we move it may cause
conflict. WinLink and Pactor may expand, especially if the new
Technician privilege proposal is approved by the FCC.

So any change has to be considered carefully and with the
understanding that we may just not get what we want.

73
Ria
N2RJ

On Fri, Mar 23, 2018 at 10:15 AM, Andras Bato <ha6nn.a...@gmail.com> wrote:
> It's only you Ria!
> All FT8 subbands are much too crowded, even in the WARC bands.
> We badly need the higher bands like 21, 24 and 28 MHz but it takes several
> years when
> there will be regular openings on those bands.
> I am terribly surprised when you are living in the USA where there are ARRL,
> IARU HQ,
> and Administrative Council members like K1ZZ and the president is a
> Canadian.
> Is it a problem to ask them for their opinion and propose new band plans
> which would precisely devide e.g. the digital band portions
> to RTTY, PSK, FT8, JT65, JT9 subbands?
> gl de ha6nn
> Andras
>
> On Fri, Mar 23, 2018 at 2:00 PM, rjai...@gmail.com <rjai...@gmail.com>
> wrote:
>>
>> I don't think there needs to really be more room. There are several
>> bands that we can use. I prefer to use WARC bands because I have my
>> fill of DX on 20 meters but WARC bands offer additional opportunities.
>> Especially 30 meters where I have gain antennas.
>>
>> 73
>> Ria, N2RJ
>>
>> On Fri, Mar 23, 2018 at 6:51 AM, Andras Bato <ha6nn.a...@gmail.com> wrote:
>> > Hi all,
>> > let me repeat a URL which is to be read and someone is to call the
>> > attention
>> > of members of IARU Administrative Council.
>> > http://www.iaru.org/administrative-council-meetings.html
>> > I guess it's the high time for them to meet asap!
>> > gl de ha6nn
>> > Andras
>> >
>> > On Fri, Mar 23, 2018 at 8:48 AM, David Alloza <da...@alloza.eu> wrote:
>> >>
>> >> Hi,
>> >>
>> >> I would like to add something to the discussion.
>> >>
>> >> At my location (JN25UE) at maximum propagation ( near noon) , the FT8
>> >> band's noise floor on the 30M is 5db higher than on the rest of the 30M
>> >> band.
>> >>
>> >> The concentration of traffic on the narrow 2.5khz (certainly at
>> >> excessive
>> >> power)  causes a significant rise in the noise floor and therefore
>> >> reduces
>> >> the performance of this mode.
>> >>
>> >> I think this is something that needs to be considered for the future of
>> >> these digital mode.
>> >>
>> >> My 73,
>> >>
>> >> David, F4HTQ.
>> >>
>> >>
>> >>
>> >> De : g...@isect.com [mailto:g...@isect.com]
>> >> Envoyé : vendredi 23 mars 2018 00:41
>> >> À : 'WSJT software development'
>> >> Objet : Re: [wsjt-devel] New FT8 Frequencies?
>> >>
>> >>
>> >>
>> >> “There is no doubt that with the super success of the FT8 mode, it is
>> >> imperative that additional frequency “Channels” within each HF band be
>> >> identified for not only the new DXpedition mode, but more importantly
>> >> for
>> >> normal day to day FT8 operations.”
>> >>
>> >>
>> >>
>> >> On the contrary, Rich, it is plainly evident that in normal use we can
>> >> successfully pack in loads of FT8 signals sharing the present fairly
>> >> narrow
>> >> slices of the HF bands.  Don’t get me wrong, I fully support the idea
>> >> of
>> >> monitoring trends and projecting forward but, as things stand, I see
>> >> very
>> >> little hard evidence of an impending crisis.  Just because there are
>> >> few
>> >> obvious clear columns on the waterfall does not mean the band segment
>> >> is
>> >> “full”, since in practice FT8 is extremely good at separating
>> >> overlapping
>> >> signals.  So I refute your assertion that “there is no doubt” that
>> >> additional frequences are needed.  There most certainly is doubt, hence
>> >> I
>> >> disagree that expansion is “imperative”.
>> >>
>> >>
>> >>
>> >> A more scientific way to address issue this would b

Re: [wsjt-devel] New FT8 Frequencies?

[rjai...@gmail.com]

I don't think there needs to really be more room. There are several
bands that we can use. I prefer to use WARC bands because I have my
fill of DX on 20 meters but WARC bands offer additional opportunities.
Especially 30 meters where I have gain antennas.

73
Ria, N2RJ

On Fri, Mar 23, 2018 at 6:51 AM, Andras Bato  wrote:
> Hi all,
> let me repeat a URL which is to be read and someone is to call the attention
> of members of IARU Administrative Council.
> http://www.iaru.org/administrative-council-meetings.html
> I guess it's the high time for them to meet asap!
> gl de ha6nn
> Andras
>
> On Fri, Mar 23, 2018 at 8:48 AM, David Alloza  wrote:
>>
>> Hi,
>>
>> I would like to add something to the discussion.
>>
>> At my location (JN25UE) at maximum propagation ( near noon) , the FT8
>> band's noise floor on the 30M is 5db higher than on the rest of the 30M
>> band.
>>
>> The concentration of traffic on the narrow 2.5khz (certainly at excessive
>> power)  causes a significant rise in the noise floor and therefore reduces
>> the performance of this mode.
>>
>> I think this is something that needs to be considered for the future of
>> these digital mode.
>>
>> My 73,
>>
>> David, F4HTQ.
>>
>>
>>
>> De : g...@isect.com [mailto:g...@isect.com]
>> Envoyé : vendredi 23 mars 2018 00:41
>> À : 'WSJT software development'
>> Objet : Re: [wsjt-devel] New FT8 Frequencies?
>>
>>
>>
>> “There is no doubt that with the super success of the FT8 mode, it is
>> imperative that additional frequency “Channels” within each HF band be
>> identified for not only the new DXpedition mode, but more importantly for
>> normal day to day FT8 operations.”
>>
>>
>>
>> On the contrary, Rich, it is plainly evident that in normal use we can
>> successfully pack in loads of FT8 signals sharing the present fairly narrow
>> slices of the HF bands.  Don’t get me wrong, I fully support the idea of
>> monitoring trends and projecting forward but, as things stand, I see very
>> little hard evidence of an impending crisis.  Just because there are few
>> obvious clear columns on the waterfall does not mean the band segment is
>> “full”, since in practice FT8 is extremely good at separating overlapping
>> signals.  So I refute your assertion that “there is no doubt” that
>> additional frequences are needed.  There most certainly is doubt, hence I
>> disagree that expansion is “imperative”.
>>
>>
>>
>> A more scientific way to address issue this would be to gather and analyze
>> data, objectively, rather than us simply asserting and refuting stuff,
>> subjectively.  So what data would be needed?  How would it be gathered and
>> analyzed?  By whom?  These questions are worth exploring.
>>
>>
>>
>> If the data indicate impending crisis, there are other concerns about the
>> options for avoiding or resolving it.  Aside from the problems
>> making/taking/stealing space from other modes to allow for more FT8, being
>> able to monitor all the FT8 activity on one screen at once is a major
>> advantage of the current arrangement, whereas splitting it up across
>> additional band segments will make things harder.  It could prove
>> counterproductive.
>>
>>
>>
>> Having said that, though, I agree there clearly are incompatibilities and
>> conflicts between normal everyday FT8 activity and the new DXpedition
>> fox-n-hounds mode, so I would agree with the suggestion to make more space
>> for DXpedition use, specifically.
>>
>>
>>
>> I’d therefore like to make a suggestions: how about we designate a
>> digimode DXpedition zone on each of the HF bands without specifying the
>> digimode?  That way, the same chunk of band can be used for RTTY, PSK, FT8,
>> JT9, JT65, CW or whatever the DXpeditioners choose, and revert to being a
>> multimode segment when no DXpeditions are using it.  It would be a good
>> place to experiment with new modes and variants, for instance.
>>
>>
>>
>> There will still be occasional conflicts if multiple DXpeditions attempt
>> to use the area at the same time, which suggests they might need to slice
>> the zone more thinly and stick to narrowmode digimodes with tighter pileups,
>> or agree amongst themselves some sort of schedule, or simply check that the
>> area is clear before transmitting – standard practice for polite DXers.
>>
>>
>>
>> 73
>>
>> Gary  ZL2iFB
>>
>>
>>
>> PS  This thread is not really about WSJT-X software development, hence we
>> should probably shift over to the other WSJT-X reflector.
>>
>>
>>
>> From: Rich - K1HTV 
>> Sent: Friday, 23 March 2018 10:18 a.m.
>> To: WSJT 
>> Subject: [wsjt-devel] New FT8 Frequencies?
>>
>>
>>
>> As we all know, when bands are open, it is not unusual to find the
>> standard FT8 frequencies packed, end-to-end with stations. The waterfall is
>> full of dozens of QSOs and many more dozens of stations calling others.
>> There is no doubt that with the super success of the FT8 mode, it is
>> imperative 

Re: [wsjt-devel] A suggestion for segrating FT8 and FT8 DXpedition frequencies

[rjai...@gmail.com]

I do agree that care needs to be taken. Already there are loud
complaints about PSK31 windows being pushed out by other modes. We
don't want to exacerbate this more.

However I think the onus is more on the dxpedition operator rather
than WSJT-X developers. There are frequencies higher up or lower down
in the window seldom used, where 3kHz can be found.

Like all modes in the end the operator is responsible.

73
Ria, N2RJ

On Wed, Mar 14, 2018 at 12:56 PM, Erik Icket  wrote:
> Hi,
>
>
>
> What about this suggestion so that FT8 and FT8 Dxpedition do not step on
> each other's frequencies and modes are not mixed up in the allocated
> segments ?
>
>
>
> Introduce a new "Mode" in the menu "FT8 DXexp"
> By default (after a software installation or frequency reset) the "FT8
> DXexp" frequency list is empty
>
>
>
> The behaviour of the GUI could be such that :
>
>
>
> If either fox or hound sets up a frequency for DXExp mode, frequencies
> reserved for other modes cannot be entered.
> If FT8 mode is selected from the menu, only frequencies for FT8 mode can be
> selected
> If "FT8 Dxexp" mode is selected from the menu, only frequencies for "FT8
> Dxexp" mode can be selected (if these were entered previously)
>
>
>
> This suggestion is not foolproof (one can still tweak it such that modes
> overlap, for whatever intentions) but could maybe serve as a start for
> exchanging some ideas on how to handle this.
>
>
>
> With all my respect for bringing FT8 to the ham community,
>
>
>
> Erik,
>
> ON4PB
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> --
> 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] WSJT-X 1.9.0 rc2 Waterfall

[rjai...@gmail.com]

Smeared is going to get some people angry emails about power, even though
they aren’t running power. Hope it works out

Ria
N2RJ
On Wed, Mar 7, 2018 at 2:30 PM Gary McDuffie  wrote:

>
>
> > On Mar 7, 2018, at 9:59 AM, Lawrence Lopez  wrote:
> >
> > I found the really liked the new format of the waterfall.
> > It was much less critical to adjust in order to get data.
>
> The waterfall has no bearing on the ability to decode.  It isn’t even
> needed.
>
> Gary - AG0N
>
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
--
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