[wsjt-devel] DT

2020-10-09 Thread Bobby Chandler 
Has anyone noticed the DT being off by .3 to .4 on FT8 on the 2.2.0-rc1 
version, even when time.is shows exact? It is OK on FT4 and V2.2.2, 
always within about .1. Seems maybe a delay in the processing that was 
not there in earlier versions.



Bobby/N4AU

--
Bobby Chandler
bob...@bellsouth.net
   n...@arrl.net



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

Re: [wsjt-devel] FST4W-120

2020-10-09 Thread Joe Taylor 

Hi Rob,

Thanks for your attention to issues of proper attributions and licensing 
on the wsprdaemon.org web site.


As Bill already reported, it would be best for the web page to make 
clear not only the terms under which our wsprd is used by your 
wsprdaemon, but also that wsprdaemon itself is licensed under GPLv3.


-- 73, Joe, K1JT

On 10/9/2020 11:35 AM, Rob Robinett wrote:

Hi Joe,

I have just checked in wsprdaemon V2.10e which adds display of the GPL 
license and an acknowledgement of its dependence on WSJT-x  each time it 
is started and it the -h help menu.
In addition, we have modified the wsprdaemon.org  
home web page to include that information as well.
Please let me know if these changes are not sufficient to meet the GPL 
requirements.


I'm sorry for the delays in making those changes.
I am leading a volunteer project to bring high speed Internet access to 
rural native Hawaiinan students so they can join their Zoom class when 
school resumes next Monday.  As a result,  WD work is currently my 
second priority.


73,

Rob


On Wed, Oct 7, 2020 at 7:07 PM Joe Taylor > wrote:


Rob --

On 10/7/2020 7:45 PM, Rob Robinett AI6VN wrote:

 > Thanks for the reminder about the license and I have added the
notices
 > to build V2.10e.
 > WD is my first open source project, so I welcome all guidance on
compliance.

Start by reading the GPLv3 license, the license under which you wish to
use our software.

You might proceed next to "How to use GNU licenses for your own
software", here: https://www.gnu.org/licenses/gpl-howto.en.html

In addition to the full license, it's easy to find summaries and
explanatory guides to it, on the web.

Please tell us where to find license information on
http://www.wsprdaemon.org/ or https://github.com/rrobinett/wsprdaemon .

Such information as well as acknowledgments of copyrights should be
prominently displayed.  I still don't see any such information,
anywhere
on the above sites.

 >  From the jt9 help menu, it appears that I can use it to expand
WD to
 > decode almost all modes except wspr.  But it appears that on
bands where
 > there might be both wspr and FST4W beacons I will need to process
the
 > wav file twice.   Doing that will surely tax the ARM CPUs in the PIS
 > used at most WD sites.

One of the main purposes of open source software -- especially that
with
a hobbyist motivation like that of WSJT-X -- is to provide starting
points for further development by others.  It's there for you to use as
you see fit, with proper attribution and within its stated copyright
and
licensing restrictions.

         -- 73, Joe, K1JT


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

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



--
Rob Robinett
AI6VN
r...@robinett.us 
mobile: +1 650 218 8896


___
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] FST4W-120

2020-10-09 Thread Bill Somerville 

Hi Rob,

you should probably make it clearer that your project is now GPLv3 
licensed. For example check this document: 
https://docs.github.com/en/free-pro-team@latest/github/building-a-strong-community/adding-a-license-to-a-repository.


FSF also have some logo icon buttons you can link in your project web 
page: https://www.gnu.org/graphics/license-logos.en.html .


Thanks for making the changes, it is appreciated.

Hope the networking changes go smoothly for the students!

73
Bill
G4WJS.

On 09/10/2020 16:35, Rob Robinett wrote:

Hi Joe,

I have just checked in wsprdaemon V2.10e which adds display of the GPL 
license and an acknowledgement of its dependence on WSJT-x  each time 
it is started and it the -h help menu.
In addition, we have modified the wsprdaemon.org 
 home web page to include that information as well.
Please let me know if these changes are not sufficient to meet the GPL 
requirements.


I'm sorry for the delays in making those changes.
I am leading a volunteer project to bring high speed Internet access 
to rural native Hawaiinan students so they can join their Zoom class 
when school resumes next Monday.  As a result,  WD work is currently 
my second priority.


73,

Rob


On Wed, Oct 7, 2020 at 7:07 PM Joe Taylor > wrote:


Rob --

On 10/7/2020 7:45 PM, Rob Robinett AI6VN wrote:

> Thanks for the reminder about the license and I have added the
notices
> to build V2.10e.
> WD is my first open source project, so I welcome all guidance on
compliance.

Start by reading the GPLv3 license, the license under which you
wish to
use our software.

You might proceed next to "How to use GNU licenses for your own
software", here: https://www.gnu.org/licenses/gpl-howto.en.html

In addition to the full license, it's easy to find summaries and
explanatory guides to it, on the web.

Please tell us where to find license information on
http://www.wsprdaemon.org/ or
https://github.com/rrobinett/wsprdaemon .

Such information as well as acknowledgments of copyrights should be
prominently displayed.  I still don't see any such information,
anywhere
on the above sites.

>  From the jt9 help menu, it appears that I can use it to expand
WD to
> decode almost all modes except wspr.  But it appears that on
bands where
> there might be both wspr and FST4W beacons I will need to
process the
> wav file twice.   Doing that will surely tax the ARM CPUs in the
PIS
> used at most WD sites.

One of the main purposes of open source software -- especially
that with
a hobbyist motivation like that of WSJT-X -- is to provide starting
points for further development by others.  It's there for you to
use as
you see fit, with proper attribution and within its stated
copyright and
licensing restrictions.

        -- 73, Joe, K1JT


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

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



--
Rob Robinett
AI6VN



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

Re: [wsjt-devel] FST4W-120

2020-10-09 Thread Rob Robinett 
Hi Joe,

I have just checked in wsprdaemon V2.10e which adds display of the GPL
license and an acknowledgement of its dependence on WSJT-x  each time it is
started and it the -h help menu.
In addition, we have modified the wsprdaemon.org home web page to include
that information as well.
Please let me know if these changes are not sufficient to meet the GPL
requirements.

I'm sorry for the delays in making those changes.
I am leading a volunteer project to bring high speed Internet access to
rural native Hawaiinan students so they can join their Zoom class when
school resumes next Monday.  As a result,  WD work is currently my second
priority.

73,

Rob


On Wed, Oct 7, 2020 at 7:07 PM Joe Taylor  wrote:

> Rob --
>
> On 10/7/2020 7:45 PM, Rob Robinett AI6VN wrote:
>
> > Thanks for the reminder about the license and I have added the notices
> > to build V2.10e.
> > WD is my first open source project, so I welcome all guidance on
> compliance.
>
> Start by reading the GPLv3 license, the license under which you wish to
> use our software.
>
> You might proceed next to "How to use GNU licenses for your own
> software", here: https://www.gnu.org/licenses/gpl-howto.en.html
>
> In addition to the full license, it's easy to find summaries and
> explanatory guides to it, on the web.
>
> Please tell us where to find license information on
> http://www.wsprdaemon.org/ or https://github.com/rrobinett/wsprdaemon .
>
> Such information as well as acknowledgments of copyrights should be
> prominently displayed.  I still don't see any such information, anywhere
> on the above sites.
>
> >  From the jt9 help menu, it appears that I can use it to expand WD to
> > decode almost all modes except wspr.  But it appears that on bands where
> > there might be both wspr and FST4W beacons I will need to process the
> > wav file twice.   Doing that will surely tax the ARM CPUs in the PIS
> > used at most WD sites.
>
> One of the main purposes of open source software -- especially that with
> a hobbyist motivation like that of WSJT-X -- is to provide starting
> points for further development by others.  It's there for you to use as
> you see fit, with proper attribution and within its stated copyright and
> licensing restrictions.
>
> -- 73, Joe, K1JT
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>


-- 
Rob Robinett
AI6VN
r...@robinett.us
mobile: +1 650 218 8896
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] "Tune" prevents "Tx Next" from transmitting in next cycle

2020-10-09 Thread Gary McDuffie 



> On Oct 9, 2020, at 07:36, Gene  wrote:
> 
> To reproduce:
> - Select FT8 mode
> - Press and release "Tune"
> - Activate Tx 6 message that displays "CQ callsign grid" and then click 
> either "Next" or "Now"
> -> It will not transmit in the immediate transmit cycle and has to wait a 
> cycle prior to initiating the CQ.

I assume you just forgot to mention that you also press and release the tune 
button after the tuner has had a chance to do its thing?  The tune button is a 
goggle, not a momentary.

Gary - AG0N

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

Re: [wsjt-devel] "Tune" prevents "Tx Next" from transmitting in next cycle

2020-10-09 Thread Gene 
Thanks to Wernli's message 2020-10-08 I was able to better document a bug
in the way WSJT-X in FT8 inhibits the next cycle transmission including the
*CQ* message *Tx 6* (*Next *or *Now *buttons). I noticed many times when
calling a station, my transmitter would not transmit on the next cycle. I
have now related it to the use of the *TUNE *button prior to selecting a
station to call. This also happens when using *TUNE *and then Calling CQ
via the* Tx 6* message, both *NEXT *and *NOW* buttons.

I regularly use the TUNE button when changing bands to tune a remote tuner
and have found it is not related to changing the bands in WSJT-X but rather
using the TUNE button.

To reproduce:
- Select FT8 mode
- Press and release "Tune"
- Activate *Tx 6* message that displays "*CQ* *callsign grid*" and then
click either "*Next*" *or* "*Now*"
-> It will not transmit in the immediate transmit cycle and has to wait a
cycle prior to initiating the CQ.

I am using WSJT-X v2.3.0-rc1, Windows 10, 64-bit O/S.

Hope this helps and can be fixed in the next -rc release.

Thank you,
Gene, K5PA

On Thu, Oct 8, 2020 at 5:06 PM Stefan Wernli  wrote:

> Hi,
>
> Albrecht pointed earlier to the behavior that "Tx Next" doesn't always
> transmit in the next cycle.
>
> I noticed that this reproducibly happens, if the "Tune" button was used;
> Using the "Tune" button in WSPR- or FST4W-modes prevents from
> transmitting in the follwing cylcle, even if "Tx Next" is activated.
>
> To reproduce:
> - Select WSPR or FST4W-mode
> - Press and release "Tune"
> - Activate "Enable Tx" and "Tx Next"
> -> It will not transmit in the next cycle
>
>
> It would be good if this could be fixed.
>
> Thanks and 73
> Stefan
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>


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